<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "journalpublishing.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" dtd-version="2.0" xml:lang="en" article-type="research-article"><front><journal-meta><journal-id journal-id-type="nlm-ta">JMIR Nursing</journal-id><journal-id journal-id-type="publisher-id">nursing</journal-id><journal-id journal-id-type="index">33</journal-id><journal-title>JMIR Nursing</journal-title><abbrev-journal-title>JMIR Nursing</abbrev-journal-title><issn pub-type="epub">2562-7600</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">v9i1e84148</article-id><article-id pub-id-type="doi">10.2196/84148</article-id><article-categories><subj-group subj-group-type="heading"><subject>Original Paper</subject></subj-group></article-categories><title-group><article-title>Readiness Assessment for AI in Nursing Care Projects: Multimethods Study</article-title></title-group><contrib-group><contrib contrib-type="author" corresp="yes"><name name-style="western"><surname>Seibert</surname><given-names>Kathrin</given-names></name><degrees>RN, Dr</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Domhoff</surname><given-names>Dominik</given-names></name><degrees>RN, MA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Altona</surname><given-names>Janissa</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff1">1</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>J&#x00E4;ger</surname><given-names>Sebastian</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bie&#x00DF;mann</surname><given-names>Felix</given-names></name><degrees>Prof Dr</degrees><xref ref-type="aff" rid="aff2">2</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Nowak</surname><given-names>Alessia</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Gubser</surname><given-names>Rahel</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Schulte-Althoff</surname><given-names>Matthias</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>F&#x00FC;rstenau</surname><given-names>Daniel</given-names></name><degrees>Prof Dr</degrees><xref ref-type="aff" rid="aff3">3</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Pohle</surname><given-names>J&#x00F6;rg</given-names></name><degrees>Dr</degrees><xref ref-type="aff" rid="aff4">4</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Bergmann</surname><given-names>Lea</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff5">5</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Walter</surname><given-names>David</given-names></name><degrees>MA</degrees><xref ref-type="aff" rid="aff6">6</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Beier</surname><given-names>Kathi</given-names></name><degrees>Dr</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Borchers</surname><given-names>Dagmar</given-names></name><degrees>Prof Dr</degrees><xref ref-type="aff" rid="aff7">7</xref></contrib><contrib contrib-type="author"><name name-style="western"><surname>Wolf-Ostermann</surname><given-names>Karin</given-names></name><degrees>Prof Dr</degrees></contrib></contrib-group><aff id="aff1"><institution>Institute of Public Health and Nursing Research, University of Bremen</institution><addr-line>Universit&#x00E4;tsallee 1B-C</addr-line><addr-line>Bremen</addr-line><country>Germany</country></aff><aff id="aff2"><institution>Faculty VI Information Science and Media, Berliner Hochschule f&#x00FC;r Technik (BHT)</institution><addr-line>Berlin</addr-line><country>Germany</country></aff><aff id="aff3"><institution>Institute of Medical Informatics, Charit&#x00E9; Universit&#x00E4;tsmedizin</institution><addr-line>Berlin</addr-line><country>Germany</country></aff><aff id="aff4"><institution>Alexander von Humboldt Institute for Internet and Society</institution><addr-line>Berlin</addr-line><country>Germany</country></aff><aff id="aff5"><institution>Association for Digitalisation in the Social Sector e.V.</institution><addr-line>Halle (Saale)</addr-line><country>Germany</country></aff><aff id="aff6"><institution>Institute of Business Administration &#x0026; Information Systems, University of Hildesheim</institution><addr-line>Hildesheim</addr-line><country>Germany</country></aff><aff id="aff7"><institution>Institute for Philosophy, University of Bremen</institution><addr-line>Bremen</addr-line><country>Germany</country></aff><contrib-group><contrib contrib-type="editor"><name name-style="western"><surname>Borycki</surname><given-names>Elizabeth</given-names></name></contrib></contrib-group><contrib-group><contrib contrib-type="reviewer"><name name-style="western"><surname>Nguyen</surname><given-names>Oliver</given-names></name></contrib><contrib contrib-type="reviewer"><name name-style="western"><surname>Wang</surname><given-names>Qing</given-names></name></contrib></contrib-group><author-notes><corresp>Correspondence to Kathrin Seibert, RN, Dr, Institute of Public Health and Nursing Research, University of Bremen, Universit&#x00E4;tsallee 1B-C, Bremen, 28359, Germany, 49 42121868903 ext 21868903; <email>kseibert@uni-bremen.de</email></corresp></author-notes><pub-date pub-type="collection"><year>2026</year></pub-date><pub-date pub-type="epub"><day>2</day><month>6</month><year>2026</year></pub-date><volume>9</volume><elocation-id>e84148</elocation-id><history><date date-type="received"><day>15</day><month>09</month><year>2025</year></date><date date-type="rev-recd"><day>08</day><month>04</month><year>2026</year></date><date date-type="accepted"><day>21</day><month>04</month><year>2026</year></date></history><copyright-statement>&#x00A9; Kathrin Seibert, Dominik Domhoff, Janissa Altona, Sebastian J&#x00E4;ger, Felix Bie&#x00DF;mann, Alessia Nowak, Rahel Gubser, Matthias Schulte-Althoff, Daniel F&#x00FC;rstenau, J&#x00F6;rg Pohle, Lea Bergmann, David Walter, Kathi Beier, Dagmar Borchers, Karin Wolf-Ostermann. Originally published in JMIR Nursing (<ext-link ext-link-type="uri" xlink:href="https://nursing.jmir.org">https://nursing.jmir.org</ext-link>), 2.6.2026. </copyright-statement><copyright-year>2026</copyright-year><license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/"><p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (<ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">https://creativecommons.org/licenses/by/4.0/</ext-link>), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Nursing, is properly cited. The complete bibliographic information, a link to the original publication on <ext-link ext-link-type="uri" xlink:href="https://nursing.jmir.org/">https://nursing.jmir.org/</ext-link>, as well as this copyright and license information must be included.</p></license><self-uri xlink:type="simple" xlink:href="https://nursing.jmir.org/2026/1/e84148"/><abstract><sec><title>Background</title><p>Integrating artificial intelligence (AI) systems into nursing care often encounters obstacles stemming from unmet requirements and insufficient engagement with well-documented sociotechnical pitfalls. Readiness models offer a systematic way to evaluate project preparedness and to build the capabilities needed for successful artificial intelligence in nursing care (AINC) research, development, and implementation. As of yet, an evidence-based AI readiness assessment prioritizing AINC projects and accounting for their diversity in care settings is missing.</p></sec><sec><title>Objective</title><p>This study aimed to develop a comprehensive artificial intelligence nursing care readiness assessment (AINCRA) to support planning, execution, and evaluation of AINC projects.</p></sec><sec sec-type="methods"><title>Methods</title><p>In a sequential exploratory multimethods bottom-up approach to maturity model development, key AI readiness dimensions and attributes were identified to develop a pilot readiness assessment. The pilot version was grounded on insights from an expert workshop (n=21) and expert interviews (n=14), an online survey (n=53), a rapid review (n=292), and a nominal group consensus process. A systematic literature review (n=7) further triangulated AI readiness attributes. Finally, a think-aloud interview study and focus group discussions involving experts (n=18) from nursing practice, nursing science, and AI research and development who had conducted AINC projects prior to data collection validated the attributes.</p></sec><sec sec-type="results"><title>Results</title><p>The resulting AINCRA encompasses 5 core dimensions: regulatory, processual, technical, social, ethical, and community building requirements and aspects. Including 69 attributes and capabilities of AI nursing care readiness, the core dimensions reflect key areas of action where AINC project stakeholders can influence project outcomes. Clinical partners can assess their organization&#x2019;s maturity level in relation to the implementation of AI. An assessment of each dimension and its attributes across 5 maturity levels allows reflecting on and proactively shaping individual project approaches. Overall, experts regarded AINCRA as a useful instrument for the development, management, and evaluation of AINC projects while emphasizing that established principles of good practice in project and data management should not be neglected when using AINCRA as a project management tool.</p></sec><sec sec-type="conclusions"><title>Conclusions</title><p>AINCRA enables practitioners from AI research and development, clinical partners, and nursing and health scientists to plan, evaluate, and enhance AI projects across their lifecycle, thereby supporting effective AI integration in nursing care. While AINCRA was developed within the European and German legal framework for AI in health care settings, respective attributes can be adapted to international requirements.</p></sec></abstract><kwd-group><kwd>artificial intelligence</kwd><kwd>nursing</kwd><kwd>care</kwd><kwd>readiness</kwd><kwd>maturity model</kwd></kwd-group></article-meta></front><body><sec id="s1" sec-type="intro"><title>Introduction</title><p>Artificial intelligence (AI) systems promise to contribute to process optimization, workload reduction, patient safety, and quality assurance in nursing care worldwide [<xref ref-type="bibr" rid="ref1">1</xref>-<xref ref-type="bibr" rid="ref3">3</xref>]. Following the European Commission&#x2019;s guidelines on AI system definition as entailed in the European Union&#x2019;s Artificial Intelligence (EU AI) Act, AI systems in nursing care refer to machine-based systems developed to function with different degrees of autonomy and potentially adapt over time after being deployed [<xref ref-type="bibr" rid="ref4">4</xref>]. AI systems process input data to produce outputs such as predictions, content, recommendations, or decisions based on explicit or implicit goals, and these outputs can affect physical or digital environments [<xref ref-type="bibr" rid="ref4">4</xref>]. Main AI techniques encompass machine learning (ML) approaches including methods such as supervised learning, unsupervised learning, self-supervised learning, and reinforcement learning, or deep learning [<xref ref-type="bibr" rid="ref4">4</xref>]. Additionally, AI systems include logic- and knowledge-based approaches that infer from encoded human knowledge or symbolic representation of the task to be solved [<xref ref-type="bibr" rid="ref4">4</xref>]. Logic- and knowledge-based methods encompass areas such as knowledge representation, inductive logic programming, inference engines, expert systems, symbolic reasoning, and search and optimization techniques [<xref ref-type="bibr" rid="ref4">4</xref>], highlighting diverse methodological possibilities for the development of AI systems in nursing care. Currently, opportunities for AI system development arising from applying generative AI models specifically trained on electronic medical record (or nursing record) data [<xref ref-type="bibr" rid="ref5">5</xref>] further expand the scope of methods and use cases.</p><p>While AI is already supporting clinical decision-making of nurses in wound assessment [<xref ref-type="bibr" rid="ref6">6</xref>] or diabetes care [<xref ref-type="bibr" rid="ref7">7</xref>], monitoring and detection of risks and clinical deterioration throughout the care process [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref10">10</xref>], or nursing documentation via hybrid speech assistants [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], many unexplored use cases in acute and long-term care persist [<xref ref-type="bibr" rid="ref13">13</xref>]. Furthermore, studies aiming to assess the effectiveness of AI systems in nursing care under real-world conditions using designs capable of determining cause-and-effect relationships are still scarce [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. The potential benefits and expectations of artificial intelligence in nursing care (AINC) are high and are emphasized by professional associations and the World Health Organization, in light of growing global challenges to ensure high-quality care despite a declining number of health care professionals and increasingly complex disease and care trajectories of patients [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref17">17</xref>]. Funding bodies are investing in AI research and development (R&#x0026;D), and the number of AINC projects is growing. In Germany, for example, the Federal Ministry of Health and the Federal Ministry of Research, Technology and Space support AINC projects in the areas of new care models, health care research, assistance of nurses and family caregivers, and enhancing autonomy and quality of life of people in need of care.</p><p>AINC projects face not only technical and regulatory requirements (eg, aspects of interoperability, compliance with national or international data laws, such as privacy and data protection laws, medical device regulations, or the EU AI Act) but also procedural, ethical, and social challenges of AI development and deployment (eg, the micro-, meso-, and macro-level impact of AI on nursing care, ethical-normative values of nursing and care, and translational factors such as acceptance of AI or added practical value) [<xref ref-type="bibr" rid="ref14">14</xref>,<xref ref-type="bibr" rid="ref18">18</xref>,<xref ref-type="bibr" rid="ref19">19</xref>]. This applies to the planning, implementation, and evaluation phases of AINC projects. Project leaders encounter different care settings with many possible use cases for AI (such as AI systems for care in hospitals, nursing homes, outpatient care, or in initial, further, and continuing education) [<xref ref-type="bibr" rid="ref2">2</xref>], with each care setting influencing the project process with its own unique organizational logic and culture. AI systems may be more complex to implement and use than many other digital technologies [<xref ref-type="bibr" rid="ref20">20</xref>]. Organizations that aim to develop, deploy, and use AI systems face technical and human-centered challenges that can be overcome by building AI maturity and ensuring they are well-prepared for AI within their organizational context [<xref ref-type="bibr" rid="ref20">20</xref>-<xref ref-type="bibr" rid="ref22">22</xref>]. We propose that the same holds true for AINC projects, for which a systematic, comprehensive reflection of AI readiness attributes across various dimensions can help align, justify, and document actions and strategies across all project stages, and may serve as a motivation to foster communication and collaboration within interprofessional project consortia.</p><p>Maturity or, often synonymously used, readiness models provide structured guidance to enhance capabilities for effective (AI) technology integration [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. Transferred from insights on organizations, readiness models provide features and guidance that help AINC projects to consider context-specific factors while not overlooking humanistic objectives and aspects of sociotechnical interplay next to focusing on technical and regulatory requirements [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref21">21</xref>]. There is a growing body of both theoretical and empirical research on readiness and maturity models [<xref ref-type="bibr" rid="ref24">24</xref>]. Among these, stage growth models are particularly prevalent in information systems research [<xref ref-type="bibr" rid="ref24">24</xref>]. These models typically define a progression of maturity levels, applied to an organization or process, ranging from minimal capability to full maturity, outlining an expected or ideal development path, accompanied by a measurement instrument [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>]. As an example, in hospitals, the maturity model for ML systems [<xref ref-type="bibr" rid="ref25">25</xref>] is structured around 3 dimensions: organization, adopter system, and patient data. These are broken down into 12 attributes and assessed across 5 maturity levels [<xref ref-type="bibr" rid="ref25">25</xref>]. The model addresses aspects such as ML strategy, technical infrastructure, ML expertise, user acceptance, and the quality and standardization of patient data [<xref ref-type="bibr" rid="ref25">25</xref>]. However, so far, an evidence-based AI readiness assessment prioritizing AINC projects and accounting for their diversity beyond R&#x0026;D on ML in diverse nursing care settings is missing. Hence, the objective for our research is to develop a comprehensive artificial intelligence nursing care readiness assessment (AINCRA) tool for planning, conducting, and evaluating AINC projects responsibly. Therefore, in a sequential exploratory multimethods study, we ask the following questions:</p><list list-type="order"><list-item><p>What are dimensions, attributes, and levels of a readiness assessment intended to support those responsible for AINC projects as a reflection tool during the planning, implementation, and evaluation phases of their projects?</p></list-item><list-item><p>How do experts with practical experience in planning, implementing, and evaluating AINC projects understand and use the AINCRA, and how do they assess it with regard to selected evaluation criteria?</p></list-item></list><p>We present AINCRA as a tool for decision-makers in R&#x0026;D and clinical partners in AINC projects to reflect on their handling of prerequisites and aspects of these projects and for designing AINC projects in a promising and successful way. Further, we compare with recommendations for the development of maturity models and common criticisms of maturity models [<xref ref-type="bibr" rid="ref24">24</xref>] to highlight methodological strengths and weaknesses of AINCRA.</p></sec><sec id="s2" sec-type="methods"><title>Methods</title><sec id="s2-1"><title>Overview</title><p>We conducted a sequential exploratory multimethods study following established design recommendations and structures of maturity models [<xref ref-type="bibr" rid="ref20">20</xref>,<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref24">24</xref>] to develop AINCRA. <xref ref-type="fig" rid="figure1">Figure 1</xref> presents the research approach, highlighting goals, activities of data collection, analysis, and outcomes for the study period lasting from December 2021 to March 2025. In a stepwise bottom-up approach, we categorized AI readiness factors into capabilities, applying an iterative validation process. Building on preliminary qualitative and quantitative findings from our research group [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref13">13</xref>], we extracted AI readiness factors and conducted a complementary systematic literature review to inform the development of an initial AINCRA version as well as guiding questions for subsequent think-aloud interviews and discussions with experts. Additionally, we triangulated results and findings from the different steps of data collection with insights from AI-related literature and from 8 AINC projects we had been involved in or which we had been accompanying during the last 5 years by repeatedly comparing preliminary drafts of AINCRA with documented project plans to assess completeness.</p><p>We follow the PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) 2020 statement for reporting systematic reviews (<xref ref-type="supplementary-material" rid="app4">Checklist 1</xref>) [<xref ref-type="bibr" rid="ref26">26</xref>]; furthermore, the COREQ (Consolidated Criteria for Reporting Qualitative Research; <xref ref-type="supplementary-material" rid="app5">Checklist 2</xref>) [<xref ref-type="bibr" rid="ref27">27</xref>] and criteria on mixed methods reporting [<xref ref-type="bibr" rid="ref28">28</xref>] guide this research where applicable. A short description of the rationale, basic methods of development, and a short generalized overview of the AINCRA dimensions has been published elsewhere [<xref ref-type="bibr" rid="ref29">29</xref>].</p><fig position="float" id="figure1"><label>Figure 1.</label><caption><p>Overview of the research approach. AI: artificial intelligence.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="nursing_v9i1e84148_fig01.png"/></fig></sec><sec id="s2-2"><title>Systematic Literature Review: Information Sources, Eligibility Criteria, and Review Protocol</title><p>Leading health and information sciences databases Scopus, PubMed, ACM Digital Library, AIS Electronic Library, and EconLit were searched in February 2023 for English- or German-language articles published from 2012 onward which either refer to a specific AI readiness assessment tool (defined by containing at least one specific question or evaluation criterion of AI readiness or maturity with a qualitative assessment option) or refer to frameworks or single studies that theoretically or empirically define AI readiness. Further, articles had to refer to AI readiness of institutions, organizations, projects, teams, or higher-level units (sectors and disciplines). Health care and nursing settings differ from other business sectors and societal areas, among other things, in that they often process highly sensitive personal data and aim to make it usable for AI systems. In addition, they are based on different sociocultural and organizational logics compared to, for example, the agricultural or logistics sector or the timelines and work culture of data science [<xref ref-type="bibr" rid="ref30">30</xref>]. Therefore, following the assumption that AI readiness models established for other sectors cannot be transferred directly to the nursing care context, publications had to refer to nursing or health care settings. Eligibility criteria were established before conducting the initial searches, and a review protocol was developed but not registered.</p></sec><sec id="s2-3"><title>Search Strategy and Selection Process</title><p>The search strategy followed a block building approach [<xref ref-type="bibr" rid="ref31">31</xref>] applied to title, abstract, and keyword searches using the Boolean operator OR within a single block and the Boolean operator AND across blocks to combine the search terms and synonyms for the blocks encompassing &#x201C;artificial intelligence,&#x201D; &#x201C;readiness,&#x201D; and &#x201C;assessment&#x201D; are depicted in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>. Two independent reviewers (KS and DW) screened titles, abstracts, and full texts according to predefined inclusion and exclusion criteria using the online resource Rayyan [<xref ref-type="bibr" rid="ref32">32</xref>]. Conflict between reviewers was resolved by including a third reviewer (DD).</p></sec><sec id="s2-4"><title>Data Collection Process and Data Items</title><p>Data extraction was carried out by one reviewer (KS) in a data extraction form created in Microsoft Excel for this purpose. Data items extracted from each included study entail the following: reference (author, year of publication, and title), country in which the study data were collected, objective of study, study design as stated, setting as stated; population: type and sample size (N); definition of AI: presented (yes or no), definition as stated; AI readiness: addressed (yes or no), definition as stated, explicit readiness assessment presented (yes or no), level of application (organization, project, team, and setting), health or nursing care addressed (yes or no), reporting of attribute origin (yes or no), origin of attributes as stated, number of attributes, description or labels of attributes, and labels of dimensions; readiness framework: presented (yes or no), name as stated, empirically tested (yes or no); success factors and challenges: reported (yes or no), success factors and challenges as stated; limitations as stated; ethics vote obtained: yes or no; funding; conflicts of interest. Missing data were coded as not reported.</p></sec><sec id="s2-5"><title>Study Risk of Bias Assessment, Effect Measures, and Synthesis Methods</title><p>As a conclusion on the effectiveness of interventions was not an intended result of the systematic literature review, we did not conduct a risk of bias assessment and other assessments associated with good practice of methodology for meta-analysis. Results were summarized narratively after inductively developing structuring categories for readiness descriptions and dimensions, as well as for readiness attributes. Key findings are described narratively in the results section and supplemented with tables and figures where appropriate.</p></sec><sec id="s2-6"><title>Think-Aloud Interviews and Group Discussions</title><p>Think-aloud interviews and group discussions were conducted online and digitally recorded with OBS Studio (version 29.1.3; OBS Project) in December 2024 and January 2025. Due to individual availability, 3 experts did not participate in a group discussion but answered group discussion guiding questions (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>) in an interview following the think-aloud task. Details about the involved researcher&#x2019;s background and relationship with participants are provided in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>.</p></sec><sec id="s2-7"><title>Selection and Recruitment of Expert Participants</title><p>We applied a purposive sampling approach [<xref ref-type="bibr" rid="ref33">33</xref>] by sending personalized, electronic invitations to 42 experts who had either been actively involved in AINC bar camps held by our study team in the past or had conducted and published AINC-related R&#x0026;D in Germany and were known to the study team. A total of 19 of 42 experts replied (response rate of 45.24%), and 17 experts consented to participation. The reason for nonparticipation was unavailability during the data collection phase. Additionally, all project leads of AINC projects in the German funding program &#x201C;Making Repositories and AI Systems Usable in Everyday Care&#x201D; were contacted via email and invited to participate or invite members of their project teams to participate. The possibility for participation was also advertised in the newsletter for said funding program, resulting in recruitment of one participant. We also asked the funding body to propose additional experts but did not receive a response.</p></sec><sec id="s2-8"><title>Ethical Considerations</title><p>The ethics committee of the German Society of Nursing Science granted ethical clearance and approved this study (application 22&#x2010;030). Participation was voluntary, and participants received no monetary or immaterial incentives or compensation. After receiving written information including statements on data protection, privacy, and confidentiality as well as concordance with the European General Data Protection Regulation, all participants provided a written informed consent to participation as well as to the pseudonymized analysis of the data obtained and to the publication of anonymized results. The study was not of an interventional nature. Participants were considered a nonvulnerable population, and participation was not classified as of particular risk.</p></sec><sec id="s2-9"><title>Data Collection</title><p>An interview guideline structured and semistandardized the data collection process, which started with a 5-minute introduction of the interviewers, including their academic degree, field of research, and personal involvement in the research project, followed by an overview of the data collection process, an explanation of data protection, consent, and voluntary participation. After that, participants were asked to introduce themselves (name, work setting, and focus) and provide a short statement on their experiences with AINC projects and implementing AINC settings. A 10-minute introduction to the objectives of the study and AINCRA, during which participants were able to ask questions for clarification, made way for the 30-minute think-aloud interview. Participants were assigned to online breakout rooms with 1 or 2 members of the study team who also took field notes. The AINCRA dimension to be discussed was accessible on a Miro Board on which participants could navigate freely. Using the prompt outlined in the &#x201C;Results&#x201D; section, participants reflected on an AINC project they either had conducted, were conducting at the time of data collection, or were planning. They were asked to imagine that they are alone in the room and to talk to themselves. All thoughts were allowed to be expressed. If they were silent for a longer period, the interviewer asked them to continue to speak. Concurrent verbal probing [<xref ref-type="bibr" rid="ref34">34</xref>] completed the think-aloud interview strategy. After the think-aloud interview, participants were guided into an online meeting room, where one researcher (KS) moderated the 35-minute group discussion structured by the guiding questions (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Other researchers took field notes and asked follow-up questions at the end of the discussion but did not intervene. Guiding questions were based on prior national research on maturity model development [<xref ref-type="bibr" rid="ref35">35</xref>], and refined in consultation with project members. A 5-minute exit phase concluded data collection, during which participants were informed about the availability of results and invited to the final study event. Afterward, researchers held a 15-minute debriefing to discuss key impressions and themes from their field notes.</p></sec><sec id="s2-10"><title>Qualitative Content Analysis</title><p>Applying a deductive qualitative content analysis approach [<xref ref-type="bibr" rid="ref36">36</xref>], coding was done by 5 members of the study team (KS, JA, LB, AN, and JP) using a coding form developed in Microsoft Excel for this purpose. Deductive content analysis allows for retesting existing data in a new context, involving testing of models [<xref ref-type="bibr" rid="ref36">36</xref>]. Units of analysis are the participants&#x2019; verbal contributions during the think-aloud interviews and focus group discussion. Audio files recorded during the think-aloud interview were randomly assigned to one coder, who listened to the recording, transcribed anchor statements, and paraphrased them. A second coder (KS) reviewed all transcripts and codes to validate the first coder&#x2019;s analysis. The structured categorization matrix [<xref ref-type="bibr" rid="ref36">36</xref>] consisted of all dimensions and attributes of the AINCRA pilot version. For each interviewed person and AINCRA dimension, attribute, and level description, statements were documented as anchor statements. The same was done for statements on the relevance of attributes and suggestions made for revision or changes to AINCRA. The coding framework for the focus group discussion followed the guiding questions, with the overall coding process being the same as for the think-aloud interviews, using an unconstrained categorization matrix, where various categories were formed within the deductive framework based on the principles of inductive content analysis [<xref ref-type="bibr" rid="ref36">36</xref>].</p></sec><sec id="s2-11"><title>Mixing of Results and Consensus-Building on Final AINCRA Version, Translation Strategy</title><p>Overall, our integration strategy consisted of the following steps: deriving AI readiness attributes and dimensions from prior work and the results of the systematic review. Building on this, an initial AINCRA version was developed, including the definition of attributes for discussion with experts. The results of these discussions were taken into account in the development of the final AINCRA version: in a half-day consensus-building workshop, results from the think-aloud interviews and focus group discussions were reviewed by 6 members of the study team and discussed one last time against overlapping or contrasting themes derived from the systematic literature search. Further, consensus on which changes suggested by the experts should be incorporated into the final AINCRA version was established by discussion, and the final AINCRA version and a user manual were developed in German and English language. As the qualitative data collection was conducted in the German language, results were first compiled in German and then translated into English for publication. Primary translation was performed by the first author (KS) who was the main researcher involved in data collection and data analysis. All members of the study team had access to the German-language results and validated and revised the translated results, with multiple researchers having extensive experience in English-language knowledge transfer and dissemination of research results (DF, FB, KWO, MS, JP).</p></sec></sec><sec id="s3" sec-type="results"><title>Results</title><sec id="s3-1"><title>Overview</title><p><xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref> presents the final AINCRA and <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref> contains the AINCRA user manual. An open-access online version of AINCRA is available [<xref ref-type="bibr" rid="ref37">37</xref>]. In the following, we outline the iterative research process to contextualize the results contributing to the final AINCRA, before presenting an overview of AINCRA and its recommended application.</p></sec><sec id="s3-2"><title>Preliminary Database</title><p>First, we built on preliminary work from our working group which has been published elsewhere: data from a rapid review [<xref ref-type="bibr" rid="ref3">3</xref>] including 292 publications on AI systems in nursing care, an expert workshop with 21 experts (including nurses, nursing directors, health care managers from hospitals, nursing homes, and home care services, digitalization officers and professionals with experience in digital health or routine nursing data analysis, informal caregivers, nursing scientists, and researchers in nursing education, computer science, AI, and ethics) as well as interviews with 14 experts and an online survey (n=53) were used to identify success factors and prerequisites of AINC projects [<xref ref-type="bibr" rid="ref13">13</xref>]. Five initial key dimensions (namely, regulatory requirements, processual and translational requirements and aspects, technical requirements, social and ethical aspects, and community building) entailing 35 codes emerged as a result of qualitative structuring content analysis involving deductive as well as inductive category and code building.</p></sec><sec id="s3-3"><title>Systematic Literature Review on AI Readiness Models in Health Care and Nursing</title><p>Second, we conducted a systematic literature review to identify existing AI readiness models focusing on nursing or health care settings and harmonize AI readiness capabilities, attributes, and dimensions with results from the first step. Screening of 4748 records identified from 5 leading health and information sciences databases resulted in the inclusion of 7 single publications (<xref ref-type="fig" rid="figure2">Figure 2</xref>) which reported either at least one question or evaluation criterion of AI readiness with a qualitative assessment option or a framework for theoretically or empirically defining AI readiness in health care or nursing care.</p><fig position="float" id="figure2"><label>Figure 2.</label><caption><p>PRISMA (Preferred Reporting Items for Systematic Reviews and Meta-Analyses) flow diagram of identification of studies via databases. AI: artificial intelligence.</p></caption><graphic alt-version="no" mimetype="image" position="float" xlink:type="simple" xlink:href="nursing_v9i1e84148_fig02.png"/></fig><p><xref ref-type="table" rid="table1">Table 1</xref> provides an overview of the included studies and reports, 3 of which used observational designs with cross-sectional surveys among health care and IT professionals [<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref40">40</xref>]. One study applied a qualitative design [<xref ref-type="bibr" rid="ref25">25</xref>], 1 paper was classified as an expert reflection [<xref ref-type="bibr" rid="ref41">41</xref>], and 2 papers did not report specific study designs to derive their results from [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref42">42</xref>]. Health care settings focused on either hospitals or selected professional groups or remained unspecified, without referencing specific nursing care settings in acute or long-term care. Overall, we extracted 74 single AI readiness attributes, which we inductively grouped into 47 codes in 13 AI readiness dimensions depicted in <xref ref-type="table" rid="table2">Table 2</xref>.</p><table-wrap id="t1" position="float"><label>Table 1.</label><caption><p>Overview of included studies (N=7).</p></caption><table id="table1" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Reference; country of origin</td><td align="left" valign="bottom">Design</td><td align="left" valign="bottom">Aim</td><td align="left" valign="bottom">Population (N)</td><td align="left" valign="bottom" colspan="4">Reporting of</td><td align="left" valign="bottom">Number of readiness attributes</td></tr><tr><td align="left" valign="bottom"/><td align="left" valign="bottom"/><td align="left" valign="bottom"/><td align="left" valign="bottom"/><td align="left" valign="bottom">Definition of AI<sup><xref ref-type="table-fn" rid="table1fn1">a</xref></sup></td><td align="left" valign="bottom">Definition of AI readiness, explicit perspective</td><td align="left" valign="bottom">Readiness assessment description</td><td align="left" valign="bottom">Origin of readiness attributes</td><td align="left" valign="bottom"/></tr></thead><tbody><tr><td align="left" valign="top">Abuzaid et al 2022 [<xref ref-type="bibr" rid="ref38">38</xref>]; United Arab Emirates</td><td align="left" valign="top">Observational, cross-sectional survey</td><td align="left" valign="top">Investigate knowledge, perception, readiness, and challenges regarding AI integration into radiology practice</td><td align="left" valign="top">Radiology professionals (n=153)</td><td align="left" valign="top">Y<sup><xref ref-type="table-fn" rid="table1fn2">b</xref></sup></td><td align="left" valign="top">N<sup><xref ref-type="table-fn" rid="table1fn3">c</xref></sup> Organizational readiness</td><td align="left" valign="top">N</td><td align="left" valign="top">N</td><td align="left" valign="top">3</td></tr><tr><td align="left" valign="top">Alami et al 2020 [<xref ref-type="bibr" rid="ref41">41</xref>]; International</td><td align="left" valign="top">Expert reflection</td><td align="left" valign="top">Bring forward the importance of studying organizational readiness to integrate AI applications</td><td align="left" valign="top">Not applicable, experiences with AI systems to support clinical decision-making reported</td><td align="left" valign="top">Y</td><td align="left" valign="top">Y Organizational readiness</td><td align="left" valign="top">Y Adapted framework from Jennett et al [<xref ref-type="bibr" rid="ref43">43</xref>]</td><td align="left" valign="top">Y</td><td align="left" valign="top">Not applicable, readiness dimensions reported</td></tr><tr><td align="left" valign="top">Andersson et al 2021 [<xref ref-type="bibr" rid="ref39">39</xref>]; Sweden</td><td align="left" valign="top">Observational, cross-sectional survey</td><td align="left" valign="top">Establish a foundation for a Swedish perspective on the potential effect of AI on the medical physics profession</td><td align="left" valign="top">Medical physicists (n=163)</td><td align="left" valign="top">N</td><td align="left" valign="top">N Workplace preparedness</td><td align="left" valign="top">N</td><td align="left" valign="top">Y</td><td align="left" valign="top">2</td></tr><tr><td align="left" valign="top">Chang 2020 [<xref ref-type="bibr" rid="ref30">30</xref>]; country not reported</td><td align="left" valign="top">Unclear</td><td align="left" valign="top">Not reported</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">N</td><td align="left" valign="top">N</td><td align="left" valign="top">Y</td><td align="left" valign="top">N</td><td align="left" valign="top">10</td></tr><tr><td align="left" valign="top">Pumplun et al 2021 [<xref ref-type="bibr" rid="ref25">25</xref>]; Germany and Switzerland</td><td align="left" valign="top">Qualitative</td><td align="left" valign="top">Explore factors that influence the adoption process of ML<sup><xref ref-type="table-fn" rid="table1fn4">d</xref></sup> systems for medical diagnostics in clinics; demonstrate how factors can be used to determine the ML maturity score of clinics</td><td align="left" valign="top">Medical experts and suppliers with profound knowledge in the field of ML (n=22)</td><td align="left" valign="top">Y</td><td align="left" valign="top">N</td><td align="left" valign="top">Y Maturity Model for ML Systems in Clinics</td><td align="left" valign="top">Y</td><td align="left" valign="top">12</td></tr><tr><td align="left" valign="top">Weinert et al 2022 [<xref ref-type="bibr" rid="ref40">40</xref>]; Germany</td><td align="left" valign="top">Observational, cross-sectional survey</td><td align="left" valign="top">Investigate factors influencing AI readiness as well as possible barriers to AI adoption and implementation in hospitals; assessed the status quo regarding the dissemination of AI tools in hospitals</td><td align="left" valign="top">Hospital chief information officers (n=40)</td><td align="left" valign="top">Y</td><td align="left" valign="top">Y Organizational readiness</td><td align="left" valign="top">Y Model by J&#x00F6;hnk et al [<xref ref-type="bibr" rid="ref21">21</xref>]</td><td align="left" valign="top">Y</td><td align="left" valign="top">47</td></tr><tr><td align="left" valign="top">Wiljer and Hakim 2019 [<xref ref-type="bibr" rid="ref42">42</xref>]; Canada</td><td align="left" valign="top">Unclear</td><td align="left" valign="top">Not reported</td><td align="left" valign="top">Not applicable</td><td align="left" valign="top">Y</td><td align="left" valign="top">N</td><td align="left" valign="top">Y AI-enabled organization</td><td align="left" valign="top">N</td><td align="left" valign="top">Not applicable, readiness dimensions reported</td></tr></tbody></table><table-wrap-foot><fn id="table1fn1"><p><sup>a</sup>AI: artificial intelligence.</p></fn><fn id="table1fn2"><p><sup>b</sup>Y: yes.</p></fn><fn id="table1fn3"><p><sup>c</sup>N: no.</p></fn><fn id="table1fn4"><p><sup>d</sup>ML: machine learning.</p></fn></table-wrap-foot></table-wrap><table-wrap id="t2" position="float"><label>Table 2.</label><caption><p>Dimensions of AI<sup><xref ref-type="table-fn" rid="table2fn1">a</xref></sup> readiness derived from the literature (thematic, nonhierarchical grouping).</p></caption><table id="table2" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">AI readiness dimension</td><td align="left" valign="bottom">Number of codes</td><td align="left" valign="bottom">Derived from</td></tr></thead><tbody><tr><td align="left" valign="top">Personnel resources and competencies</td><td align="left" valign="top">12</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref38">38</xref>-<xref ref-type="bibr" rid="ref42">42</xref>]</td></tr><tr><td align="left" valign="top">Strategic planning</td><td align="left" valign="top">7</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref38">38</xref>,<xref ref-type="bibr" rid="ref40">40</xref>-<xref ref-type="bibr" rid="ref42">42</xref>]</td></tr><tr><td align="left" valign="top">Data quality</td><td align="left" valign="top">8</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top">Financial resources and investments</td><td align="left" valign="top">4</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref40">40</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top">Acceptance and stakeholder participation</td><td align="left" valign="top">3</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref39">39</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top">Technical infrastructure</td><td align="left" valign="top">3</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]</td></tr><tr><td align="left" valign="top">Data protection and data safety</td><td align="left" valign="top">2</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top">Intangible assets</td><td align="left" valign="top">2</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref40">40</xref>]</td></tr><tr><td align="left" valign="top">Leadership culture</td><td align="left" valign="top">2</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]</td></tr><tr><td align="left" valign="top">Needs and problems (in clinical practice and of patients)</td><td align="left" valign="top">1</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top">Practical benefit and added value</td><td align="left" valign="top">1</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top">Time resources</td><td align="left" valign="top">1</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref40">40</xref>]</td></tr><tr><td align="left" valign="top">Organizational culture</td><td align="left" valign="top">1</td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>]</td></tr></tbody></table><table-wrap-foot><fn id="table2fn1"><p><sup>a</sup>AI: artificial intelligence.</p></fn></table-wrap-foot></table-wrap><p>Axial coding and contrasting of these 74 readiness attributes with the 35 codes extracted in step 1 provided the database for 2 rounds of nominal group consensus involving 5 experts (2 nursing scientists, 1 ML expert, 1 information systems specialist, and 1 expert representing the German association for digitalization in the social economy with experience in consulting of clinical partners) to harmonize and group AI readiness factors. By merging semantically equivalent attributes and removing those not directly influenced by AINC stakeholders, the AI readiness attributes were reduced to 67 codes in 5 dimensions, serving as the baseline for the development of a pilot AINCRA version.</p></sec><sec id="s3-4"><title>Indicator Development and Expert Validation</title><p>The pilot AINCRA version included feedback from 13 AINC project experts to establish a common AI readiness vocabulary for level distinctions. Building on vocabularies of existing maturity or readiness models [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref44">44</xref>], expert feedback was obtained from researchers and practitioners working in ongoing AINC projects at the time of data collection during a 45-minute bar camp session in September 2024 which was open for participation for all people currently used in 1 of 9 AINC projects in the German Ministry for Research, Technology and Space&#x2019;s funding program &#x201C;Making Repositories and AI Systems Usable in Everyday Care.&#x201D; Further, level labels, frequencies, and numbering reported in the literature [<xref ref-type="bibr" rid="ref23">23</xref>,<xref ref-type="bibr" rid="ref25">25</xref>] were discussed with these experts, resulting in the decision to adopt 5 levels (1: initial, 2: assessing, 3: determined, 4: managed, and 5: optimized) with the possibility to rate an attribute as not applicable depending on the type of AINC project, AI system, or organizational features of clinical partners. The complete AI readiness vocabulary for level distinction is included in <xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>. The use of the vocabulary and the 67 attributes derived from the third step of the research process as input for GPT-4o (OpenAI)&#x2013;generated 335 level descriptions, which, after expert review and revision by all members of the study team, were incorporated into the AINCRA pilot version.</p><p>Finally, to evaluate the AINCRA pilot version, we applied a think-aloud interview approach [<xref ref-type="bibr" rid="ref45">45</xref>,<xref ref-type="bibr" rid="ref46">46</xref>] including a concurrent think-aloud session and reflexive group discussion with 18 experts with a proven track record in carrying out AINC projects to refine AINCRA dimensions, attributes, level distinctions, and descriptions. The think-aloud approach can be useful to &#x201C;better understand thought processes during assessments as a strategy to describe what [an] assessment is measuring&#x201D; [<xref ref-type="bibr" rid="ref46">46</xref>]. Further, the think-aloud approach provided information about the cognitive thought processes of AINC project stakeholders using AINCRA &#x201C;pertaining to usability problems they would encounter&#x201D; [<xref ref-type="bibr" rid="ref47">47</xref>] to reflect on a specific AINC project. Considering possible ways to evaluate maturity models, we followed good-practice recommendations by involving experts &#x201C;on the type of process that is intended to be improved by the maturity model, but who have not been involved in the actual development of the maturity model&#x201D; [<xref ref-type="bibr" rid="ref48">48</xref>].</p></sec><sec id="s3-5"><title>Characteristics of Think-Aloud Study Participants</title><p>At the time of data collection, 10 experts are involved in AINC projects outside of the German funding program &#x201C;Making Repositories and AI Systems Usable in Everyday Care,&#x201D; while 8 experts are working in ongoing AINC projects in said funding program (characteristics of participants are depicted in <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Eight experts report less than 5 years of experience with AINC projects, while 5 experts indicate experience of 5 years or longer. These 5, as well as 5 experts who did not report conclusively on the duration of their experience, had also been involved in projects focusing on developing and implementing other digital technologies in nursing care, digitalization, and advancement of IT infrastructures in hospitals and long-term care for several years. Considering the main AINC project stakeholder groups regarding the composition of project consortia, 9 experts represent a nursing or health science perspective, often accompanied by responsibilities and roles connected to project coordination, while in some cases also holding topic-related qualifications or work experience such as nursing informatics expertise. Five experts represent clinical partners in AINC projects, and 5 experts represent AI R&#x0026;D, 2 of them working for tech companies compared to 3 experts working for institutes affiliated with universities or independent research institutions. In the think-aloud interview, 13 experts reflect on an ongoing AINC project, 4 experts reflect on a completed project, and 1 expert reflects on a project in planning.</p></sec><sec id="s3-6"><title>Think-Aloud Interview and Expert Group Discussion</title><p>Individual 30-minute think-aloud interviews and subsequent 35-minute group discussions were conducted online by 1 to 3 members of the study team in an overall 90-minute session. All participants received an overview of all AINCRA pilot version dimensions and attributes in advance. However, detailed level descriptions were only presented during the interview, along with the verbal prompt to evaluate an ongoing, in planning, or past AINC project they were familiar with. They were asked to do so by using the attributes and level descriptions of one or more selected AINCRA dimensions, referring to a recalled point in time (eg, planning, implementation, or evaluation phase), while verbalizing all their thoughts aloud. Since we anticipated the pilot version to be a complex and time-consuming assessment, participants were only presented with selected dimensions, never all of them. The selection was made with knowledge of the participants&#x2019; areas of expertise, with a slight emphasis on process-related requirements. This focus was chosen because these dimensions included attributes that are described in the literature as being often neglected in AI maturity models [<xref ref-type="bibr" rid="ref20">20</xref>], and which, according to our preliminary study, are known to significantly influence project flow and success [<xref ref-type="bibr" rid="ref13">13</xref>].</p><p>We obtained expert statements and comments on 64 of 67 attributes with a total of 70 suggestions for changes to the AINCRA pilot version (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>). Changes suggested included adding definitions, or explanations, or examples for selected terms (eg, &#x201C;data champion&#x201D; and &#x201C;ontological representation&#x201D;), simplification of terms, reordering and grouping of attributes within 1 dimension or across 2 dimensions, splitting of attributes, and adding of examples in level descriptions (eg, sponsor role as a required responsibility when compliance with the EU Medical Device Regulation is mandatory for the AI system). Some comments highlighted the need for adding information to the AINCRA user manual without resulting in changes to dimensions, attributes, or level descriptions. Overall, 37 of 70 (53%) changes suggested were realized in the final AINCRA version.</p><p>In the group discussions, experts rated and discussed the AINCRA dimensions, attributes, and level descriptions they had applied to their own AINC projects in the think-aloud interview. An overview of the discussed evaluation criteria with their respective guiding questions for the discussion can be found in the &#x201C;Methods&#x201D; section. In summary, AINCRA was assessed as a valuable tool for AINC project development, management, and evaluation by the experts. However, some experts pointed out that not all influencing aspects of AINC projects can be foreseen using AINCRA, and that a project process can also be set up without applying AINCRA. Further, general aspects of good practice of project or data management that still need to be considered in each project should not be overlooked when focusing on AINCRA as a project management tool. <xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref> displays expert ratings and feedback for each evaluation criteria. Results for each evaluation criteria are summarized below and highlighted with selected expert statements.</p></sec><sec id="s3-7"><title>Benefits and Consequences of Applying AINCRA</title><p>Considering benefits and consequences of applying the AINCRA to AINC projects, experts generally see added value. Advantages of applying the complex AINCRA are seen by some as being more suited to larger research projects rather than smaller initiatives or in-house projects, while others also recognize its value for those smaller endeavors. Added value was also noted for project consortia with little prior experience in conducting AINC projects. For clinical partners, AI R&#x0026;D, and nursing or health science research partners in AINC projects, AINCRA is seen as useful for decision-making, planning, grant applications, coordination among partners, identifying resources and expertise, aligning goals, managing projects, and conducting evaluations. Experts also pointed out AINCRA&#x2019;s usefulness for AINC project funding bodies, as AINCRA may support documentation, monitoring, evaluation, and comparison of AINC projects. Expert participants representing tech companies pointed out that AINCRA may help with their project management activities, client consulting, and long-term support of AI implementations.</p><disp-quote><p>I think another advantage is that with [AINCRA], you can already identify project risks [...] during project planning, for example the area of social and ethical success factors [...] which is very helpful if such a dimension is already represented here.</p><attrib>IP2, 00:48:18</attrib></disp-quote><p>Results of AINCRA may lead to various consequences for AINC projects: positive consequences entail advantages in grant applications for high-scoring applicants, identification of improvement areas and necessary changes, support for go or no-go AINC project decisions, and early reflection on and evaluation of an AI system&#x2019;s practical value. However, an AINCRA result may evoke emotional effects in the individuals conducting the assessment, influencing their motivation to engage with AINC readiness attributes or to push an AINC project forward. Low AINCRA scores may cause frustration or disappointment but can also spark motivation and ambition to improve. However, low-level placement may demotivate clinical partners or discourage participation if initial AINC readiness appears too low and difficult to improve.</p><disp-quote><p>Especially if the requirements are not met at the beginning, it can quickly give the impression that one doesn&#x2019;t want to do it and doesn&#x2019;t see the benefit for the effort that has to be put in, even though there actually is one.</p><attrib>IP14, 00:54:16</attrib></disp-quote></sec><sec id="s3-8"><title>Rater Entity</title><p>When asked who should carry out the assessment, experts agree that AINCRA is unlikely to be effectively carried out by a single individual. Depending on the dimension and attribute, different individuals should be involved, or AINCRA should be conducted collaboratively, either in a group or in a tandem (eg, between clinical and AI R&#x0026;D partner) within an interprofessional team. For assessing processual and translational requirements and aspects, suitable raters include experienced personnel from the clinical partner with nursing and digitalization expertise, and IT staff of the clinical partner in collaboration with nursing management with a focus on joint assessments by AI R&#x0026;D and clinical partners. Conducting AINCRA as a guided, participatory assessment involving frontline nurses was stated as a suitable approach. However, some experts caution against including certain roles (eg, nursing assistants) and emphasize that nurses should be supported during their involvement. Experts also raise the question of who holds responsibility for the AINCRA result, especially if the result impacts, for example, project funding decisions.</p><disp-quote><p>I think it would be good if the evaluation is done at the start by the project consortium, not by the individual specialists [...] it would be good if everyone in the consortium, with its different disciplines, is clear about [...] all five dimensions [...] so that together they have a clearer idea of what lies ahead.</p><attrib>IP3, 00:52:05</attrib></disp-quote></sec><sec id="s3-9"><title>Attainability of Levels</title><p>Assessing the attainability of AINCRA levels, overall, experts view the levels as realistic and reflective of the diversity among clinical partners and AINC projects. However, not all levels appear to be achievable. They emphasize that this should not necessarily be the expectation for AINC projects, as attainability of levels depends on the dimension assessed and the project context. Level 5 is ambitious and currently hard to reach for most clinical partners. But experts emphasize that level 5 should be a long-term goal and is seen as achievable, especially for clinical partners with extensive AINC project experience, but is considered unrealistic for R&#x0026;D projects. Level 4 is regarded as the upper realistic limit for R&#x0026;D projects and a desirable target for clinical partners. Level 3 is also seen as a satisfactory goal for clinical partners. While level 2 was not discussed in detail, for level 1, experts point out that some clinical partners already start AINC projects while scoring above level 1.</p><disp-quote><p>I would definitely say that we have developed. There were some levels that, from our perspective, were not achievable. But the question is also whether that&#x2019;s the goal. Maybe it&#x2019;s enough to say that you get through with a 3.</p><attrib>IP11, 00:51:18</attrib></disp-quote></sec><sec id="s3-10"><title>Achievability of Levels</title><p>Reflecting on past AINC projects that, from the experts&#x2019; point of view, were successful, experts discussed the achievement of the AINCRA levels regarding the level at the start of a project and the evolution of levels throughout the project process until completion. Overall, the achievement of AINCRA levels is rated as depending on individual goals and structures of an AINC project. Progression is inherent to AINC projects, as no project meets all requirements from the start. Participation in an AINC project can lead to the development of new structures and processes at the clinical partner organization that go beyond AINCRA attributes. In contrast, some AINC projects may not show improvement despite great efforts to advance AINC readiness attributes. All types of development trajectories are possible, with advancement, remaining, or regression of levels. Entry levels and basic conditions may help industry (or R&#x0026;D) partners to more easily identify suitable clinical partners, with level 1 being rated not as a general exclusion criterion, but a knockout criterion for certain attributes (eg, data availability).</p><disp-quote><p>I do believe that there can be deal-breaker criteria in attributes. Off the top of my head, I thought of data quality and data availability in our project. Especially structural things &#x2013; if those aren&#x2019;t in place, we don&#x2019;t need to start an AI project. If my data are just scattered on paper.</p><attrib>IP13, 00:53:24</attrib></disp-quote></sec><sec id="s3-11"><title>Step Size of Levels and Influenceability of Attributes</title><p>Step size of AINCRA levels is rated as sufficient, appropriate, and distinct with little in-depth discussion. Influenceability of the AINCRA attributes was discussed in depth: most attributes are considered influenceable within AINC projects. However, some less influenceable attributes are still important, such as regulatory requirements or legal framework changes, which are typically beyond a project&#x2019;s control. Experts highlight influenceability as a reflection criterion, especially when a project receives a low maturity level rating. Attributes considered particularly influenceable are related to attitudes, acceptance, knowledge, and willingness to change of stakeholders at the clinical partners&#x2019; organization. Limited influenceability is assigned to attributes requiring fundamental corporate decisions (eg, developing and committing to an internal AI strategy) as well as attributes dependent on external conditions of clinical partners (eg, staff shortages, turnover, and financial resources).</p><disp-quote><p>[AINCRA attributes are] all topics that I can address within the project.</p><attrib>IP11, 00:55:39</attrib></disp-quote></sec><sec id="s3-12"><title>Availability of Information, Comprehensibility, and Applicability</title><p>Discussion of the availability of the information or data needed to carry out the AINCRA revealed that the required information is rated as available or obtainable with reasonable effort for AINC project stakeholders by the experts. Involving additional stakeholders is emphasized, supporting the previous assessment that AINCRA should be conducted as an interprofessional assessment. However, the availability of additional stakeholders may be limited, for example, if IT staff of clinical partners have competing responsibilities and carrying out AINCRA is considered a lower priority compared to other tasks.</p><disp-quote><p>All [attributes] I have seen so far [.] are definitely such that you can either answer them yourself or at least know who to turn to in order to get the information.</p><attrib>IP12, 01:14:26</attrib></disp-quote><p>Regarding the comprehensibility of the AINCRA, some experts consider the instrument to be low-threshold and emphasize its comprehensibility for AINC project leaders. However, some wording is not familiar to all nursing professionals. There is also concern about whether nonnative speakers in nursing leadership or administrative roles will understand the expressions and terminology used in AINCRA. Referring to statements made in the think-aloud interview, experts provide suggestions for logically ordering, rephrasing, or explaining selected attributes, as details of the attributes and level descriptions were rated as not quickly to be grasped.</p><disp-quote><p>So, I would assess it as very understandable [...] of course, during the [think aloud interview], I naturally picked out the things I understand in order to be able to answer them [...] the comprehensibility depends on who from the consortium is conducting the assessment [...] regarding nursing topics, the IT partners probably would have said, &#x2018;I don&#x2019;t understand anything about that at all&#x2019; [...] it depends on who is sitting in front of it and which professional domain it is.</p><attrib>IP2, 01:03:33</attrib></disp-quote><p>For the applicability of AINCRA, experts assess the AINCRA pilot version as a complex, text-heavy instrument that, when applied thoroughly, can take several hours to complete depending on the dimension rated. This long application duration may reduce acceptance of AINCRA. Initial use in particular requires time to understand the instrument and is not necessarily intuitive. However, experts expect that the time required will decrease over time and that the application will become easier with continued use. Conducting AINCRA in an interprofessional team enhances its applicability. Some experts attest to the very good usability of AINCRA, though it should be noted that no expert applied the entire instrument. Application seems challenging for stakeholders in long-term care facilities due to lack of expertise in certain attributes. Experts discussed whether a shortened AINCRA version could be provided.</p></sec><sec id="s3-13"><title>Comparability and Completeness</title><p>Comparability of AINCRA results between AINC projects is assessed heterogeneously between the experts, with some pointing out that comparability is difficult, and others emphasizing that comparability of individual dimensions and attributes is possible. Further, multiple practice partners within one AINC project may be compared with AINCRA, as well as multiple AINC projects within the same funding program, and comparability can be ensured through external evaluation.</p><disp-quote><p>Of course, it&#x2019;s a self-assessment tool [...] the question is whether it&#x2019;s answered honestly and whether that allows for comparability. If it&#x2019;s evaluated in a review process by external parties, then I do believe that good comparability can be achieved.</p><attrib>IP8, 00:21:20</attrib></disp-quote><p>Completeness of AINCRA overall is rated as given, with some experts highlighting suggestions for additions or change. These address the inclusion of staff representatives of clinical partners as important stakeholders, allowing for custom attributes to be added by users, and enabling mapping of multiple clinical partners within a single AINC project.</p></sec><sec id="s3-14"><title>Overview of AINCRA Dimensions, Attributes, and Levels</title><p>AINCRA consists of 69 AINC readiness attributes across five dimensions: (1) regulatory requirements and aspects (9 attributes), (2) processual and translational requirements and aspects (40 attributes), (3) technical requirements and aspects (6 attributes), (4) ethical and social requirements and aspects (11 attributes), and (5) community building requirements and aspects (3 attributes). <xref ref-type="table" rid="table3">Table 3</xref> provides an overview of the 5 dimensions. For each attribute, 5 maturity levels are described, a recommendation for stakeholders considered as most suitable as assessors is given, along with a reference to the source from which the attribute or the justification for the relevance of the attribute is derived (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p><table-wrap id="t3" position="float"><label>Table 3.</label><caption><p>Overview of AINCRA<sup><xref ref-type="table-fn" rid="table3fn1">a</xref></sup> dimensions.</p></caption><table id="table3" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Dimension</td><td align="left" valign="bottom">Description</td></tr></thead><tbody><tr><td align="left" valign="top">Regulatory requirements and aspects (9 attributes)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>This dimension takes into account the necessary legal frameworks and data protection regulations that require an analysis of the data and an examination of data-sharing models to enable the use of AI<sup><xref ref-type="table-fn" rid="table3fn2">b</xref></sup> systems in everyday nursing practice.</p></list-item></list></td></tr><tr><td align="left" valign="top">Processual and translational requirements and aspects (40 attributes)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>This dimension captures the human, material, temporal, and intangible resources available for AI in nursing care projects in care facilities or hospitals, as well as their general and AI-specific level of digitalization.</p></list-item><list-item><p>It also assesses the maturity of overarching strategies for AI, data governance, and IT governance, as well as plans for long-term external support and evaluation of AI implementation.</p></list-item><list-item><p>Engagement with the implementation of needs-based research and development of AI systems&#x2014;focused on practical benefits and added value&#x2014;as well as the existing AI-related knowledge and competencies within care facilities and clinics, is intended to support the seamless integration of AI systems into existing care processes.</p></list-item><list-item><p>This dimension also includes reflection on attitudes toward AI, acceptance of AI technologies, and trust in their use in daily nursing practice, to foster adoption and address concerns of those affected by the deployment of AI.</p></list-item></list></td></tr><tr><td align="left" valign="top">Technical requirements and aspects (6 attributes)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>This dimension addresses the availability and functionality of the technical infrastructure, including aspects of data protection and data security, which are essential for reliable data use and analysis.</p></list-item><list-item><p>To ensure smooth, secure, and efficient data integration and exchange between different systems and stakeholders in everyday nursing practice, this dimension also considers the integration of AI systems into data infrastructures or data platforms, as well as the use of technical interoperability standards and nomenclatures.</p></list-item></list></td></tr><tr><td align="left" valign="top">Social and ethical requirements and aspects (11 attributes)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>This dimension encompasses ethical and methodological considerations related to voluntariness, privacy, fairness, and transparency, as well as the ethical and normative value orientations of the field and individual practice partners.</p></list-item><list-item><p>Engaging with the impacts of AI use at the micro, meso, and macro levels, along with a responsible approach to data handling, is intended to support the use of AI systems in everyday nursing practice.</p></list-item></list></td></tr><tr><td align="left" valign="top">Community building requirements and aspects (3 attributes)</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>This dimension aims to promote a network that strengthens knowledge exchange and the collective advancement of AI systems in everyday nursing practice. Researchers, developers, and stakeholders from nursing practice and nursing management are involved in this network.</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table3fn1"><p><sup>a</sup>AINCRA: artificial intelligence nursing care readiness assessment.</p></fn><fn id="table3fn2"><p><sup>b</sup>AI: artificial intelligence.</p></fn></table-wrap-foot></table-wrap><p>AINCRA dimension 1, regulatory requirements and aspects, involves the assessment of how detailed and specific methodological and regulatory decisions, definitions, and limitations are being addressed by an AINC project. This includes, among other things, attributes reported by Pumplun et al [<xref ref-type="bibr" rid="ref25">25</xref>] for analyzing the dataset, as well as the operationalization of data-sharing models [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]. In the latter case, for example, the degree of finalization and the progress of the implementation of the model serve as reflection criteria. This dimension also relates to the engagement with requirements arising from the EU AI Act. AINC project stakeholders recommended for assessing dimension 1 are mainly individuals representing AI R&#x0026;D, supplemented by a clinical partners&#x2019; and nursing science perspective for some attributes. An example of the attributes 1.6 Data-sharing Models and 1.9 EU AI Act<italic>,</italic> corresponding level descriptions, recommended rater entity, and sources of attribute origin is shown in <xref ref-type="table" rid="table4">Table 4</xref>.</p><p>AINCRA dimension 2, processual and translational aspects and requirements, evaluates the resources, general as well as AI-specific digital readiness, and strategic planning in place for implementing AINC. It considers infrastructure, staff skills, governance, and external support, as well as how well AI aligns with care needs and existing workflows. It also examines staff attitudes, acceptance, and trust in AI to support successful integration into everyday practice. Most attributes are targeted at the clinical partner, whose expertise is crucial for assessing this dimension and which needs to be supplemented by nursing science and AI R&#x0026;D expertise to arrive at a comprehensive assessment. This is reflected, for example, in attributes targeting the degree of digitization, which includes the use of data quality standards [<xref ref-type="bibr" rid="ref25">25</xref>], the availability of data champions [<xref ref-type="bibr" rid="ref30">30</xref>] as a personnel resource, or the systematic demonstration of practical benefit and added value of an AI system (<xref ref-type="table" rid="table4">Table 4</xref>).</p><p>AINCRA dimension 3, technical requirements and aspects, focuses on the technical infrastructure needed for reliable and secure data use in AINC projects. It includes data protection, system integration, and the use of interoperability standards to ensure smooth data exchange and effective AI implementation in clinical practice. The main AINC project stakeholder to assess dimension 3 is AI R&#x0026;D. While the technical infrastructure at clinical partner sites is an essential and priorly described prerequisite for AINC project success [<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref49">49</xref>], we recommend especially assessing IT infrastructure with a focus on AI compute capabilities and dedicated hardware, for which requirements are often underestimated or not clearly communicated between AI R&#x0026;D and clinical partners during initial AINC project planning (<xref ref-type="table" rid="table4">Table 4</xref>).</p><p>AINCRA dimension 4, ethical and social requirements and aspects, covers ethical and methodological aspects such as voluntariness, privacy, fairness, and transparency. It also considers the values of the nursing field and its practitioners, as well as the broader impacts of AI use and responsible data handling to support ethical AI integration in daily nursing care. Dimension 4 should be assessed from a multifaceted perspective, including nursing science and clinical partners. In collaboration with clinical partners and AI R&#x0026;D, nursing scientists should drive the assessment of whether and how structured engagement with ethical-normative values of nursing and care [<xref ref-type="bibr" rid="ref49">49</xref>] is operationalized in an AINC project. The same holds true for reflecting on the impact of AI on the nursing profession [<xref ref-type="bibr" rid="ref49">49</xref>], and how this impact informs AI system development, implementation, and evaluation (<xref ref-type="table" rid="table4">Table 4</xref>).</p><table-wrap id="t4" position="float"><label>Table 4.</label><caption><p>Examples of attributes and level descriptions across the AINCRA<sup><xref ref-type="table-fn" rid="table4fn1">a</xref></sup> dimensions.</p></caption><table id="table4" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Dimension and attribute number</td><td align="left" valign="bottom">Attribute</td><td align="left" valign="bottom">Level 1<break/>(initial)</td><td align="left" valign="bottom">Level 2<break/>(assessing)</td><td align="left" valign="bottom">Level 3<break/>(determined)</td><td align="left" valign="bottom">Level 4<break/>(managed)</td><td align="left" valign="bottom">Level 5<break/>(optimized)</td><td align="left" valign="bottom">Not applicable</td><td align="left" valign="bottom">(Joint) Assessment by (rater entity)</td><td align="left" valign="bottom">Source</td></tr></thead><tbody><tr><td align="left" valign="top" colspan="10">Regulatory requirements and aspects</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1.6</td><td align="left" valign="top">Data-sharing models</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Data-sharing models relevant to the AINC<sup><xref ref-type="table-fn" rid="table4fn2">b</xref></sup> project are unknown or unclear.</p></list-item><list-item><p>No considerations regarding appropriate models and approaches exist.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Initial considerations and steps toward defining and implementing a data-sharing model are being taken.</p></list-item><list-item><p>However, the model is not finalized, and necessary people and procedures are not yet fully clarified.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The data-sharing model and approach are defined, and most legal, organizational, and technical requirements are identified.</p></list-item><list-item><p>Contact persons and responsibilities are known, but detailed negotiation and implementation have not started.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The data-sharing model and approach are defined and known to all project participants.</p></list-item><list-item><p>All legal, organizational, and technical requirements are fully identified and documented in a structured manner.</p></list-item><list-item><p>Responsible contacts are involved and took part in detailed negotiations.</p></list-item><list-item><p>Implementation includes appropriate regulatory, organizational, and technical safeguards</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The model and processes of data sharing have been implemented with all necessary regulatory, organizational, and technical safeguards.</p></list-item><list-item><p>Fulfillment of requirements is proven (eg, through internal and external certification).</p></list-item><list-item><p>Data sharing and usage are fully documented, and documentation is regularly reviewed.</p></list-item><list-item><p>Processes and structures evolve based on audit results.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Not applicable</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI<sup><xref ref-type="table-fn" rid="table4fn3">c</xref></sup> R&#x0026;D<sup><xref ref-type="table-fn" rid="table4fn4">d</xref></sup></p></list-item></list></td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>1.9</td><td align="left" valign="top">EU<sup><xref ref-type="table-fn" rid="table4fn5">e</xref></sup> AI Act</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>No consideration of the EU AI Act in the AINC project.</p></list-item><list-item><p>No awareness of which parts of the project are affected.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Initial steps to comply with the EU AI Act are underway.</p></list-item><list-item><p>A basic overview exists, but the requirements are inconsistently implemented.</p></list-item><list-item><p>Responsibilities and external actors are not fully clarified.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The AINC project is committed to compliance with the EU AI Act.</p></list-item><list-item><p>A broad overview exists, responsibilities are defined.</p></list-item><list-item><p>Many requirements are implemented or planned, but coverage and documentation are not complete.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The AINC project is committed to AI Act compliance and has a structured overview of legal requirements.</p></list-item><list-item><p>Responsibilities are clear and implementation follows a defined process standard.</p></list-item><list-item><p>All requirements are planned or fulfilled with explicit deadlines and sufficient resources (time, personnel, and other).</p></list-item><list-item><p>Implementation is well-documented, tested, and regularly monitored.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Full compliance with the EU AI Act is ensured. A complete and structured legal framework exists and is shared with all participants.</p></list-item><list-item><p>Responsibilities are clear, and implementation follows international standards (eg, ISO/IEC 42001).</p></list-item><list-item><p>All requirements are planned or fulfilled with explicit deadlines and sufficient resources (time, personnel, other), documented, tested, externally certified, and continuously improved.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Not applicable</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item><list-item><p>Nursing</p><p>Science</p></list-item><list-item><p>Clinical partner</p></list-item></list></td><td align="left" valign="top">Emerged from this research</td></tr><tr><td align="left" valign="top" colspan="10">Processual and translational aspects and requirements</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>2.9</td><td align="left" valign="top">Clinical partner: personnel resources: available data champions<sup><xref ref-type="table-fn" rid="table4fn6">f</xref></sup></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>There are no data champions (at the clinical partner) in the AINC project, and the use of data is not actively promoted or supported.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>First data champions (at the clinical partner) are being identified, but their role is not yet formalized or recognized.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Some data champions (at the clinical partner) are active, their role is defined, and they promote a data culture in selected areas.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Data champions (at the clinical partner) are established and work across departments to promote and support data use.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Data champions are fully integrated into the organizational structure (of the clinical partner) and actively drive a data-driven culture forward.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Clinical partner with IT staff</p></list-item><list-item><p>AI R&#x0026;D</p></list-item></list></td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>]</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>2.32</td><td align="left" valign="top"><list list-type="simple"><list-item><p>Practical benefit and added value of the AI system</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The practical benefit or added value of the AI system is unknown, or no clear practical benefit or added value is evident.</p></list-item><list-item><p>The AINC project is predominantly theoretical.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The potential benefit of the AI system is recognized, but concrete indicators or criteria for capturing the benefit and added value are unclear.</p></list-item><list-item><p>Initial steps to evaluate the added value are being taken but are not consistently recorded and documented.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The AI system shows a recognizable practical benefit, which is represented by concrete indicators or criteria.</p></list-item><list-item><p>However, end points are only partially captured, or the benefit is only partially realized.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The practical benefit of the AI system is clearly defined and is systematically implemented and demonstrated within the AINC project.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The AI system generates significant practical benefit and added value, which is continuously measured and optimized using clearly defined criteria and indicators.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item><list-item><p>Nursing Science</p></list-item><list-item><p>Clinical Partner</p></list-item></list></td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>]</td></tr><tr><td align="left" valign="top" colspan="10">Technical requirements and aspects</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3.2</td><td align="left" valign="top">Use of technical interoperability standards and nomenclatures</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>No use of interoperability standards or nomenclatures.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Initial steps toward using and considering interoperability standards and nomenclatures in the development of the AI system within the AINC project, but not yet fully implemented.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Interoperability standards and nomenclatures are partially considered and used in the development of the AI system within the AINC project, but not consistently.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Extensive use and integration of interoperability standards and nomenclatures in the development of the AI system within the AINC project.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Complete and optimized use of interoperability standards and nomenclatures in the development of the AI system within the AINC project, regularly updated and applied across all relevant areas.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item><list-item><p>Nursing Science</p></list-item></list></td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref41">41</xref>,<xref ref-type="bibr" rid="ref49">49</xref>]</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>3.6</td><td align="left" valign="top">IT infrastructure: AI compute: hardware</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>No dedicated AI hardware available.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Dedicated AI hardware is available but not yet connected, eg, to data interfaces.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Dedicated AI hardware is available and connected (eg, to data interfaces). It is possible to transfer data into the runtime environment for model development.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Dedicated AI hardware is available and connected. Standardized interfaces are in place for data transfer and for offering model predictions.</p></list-item><list-item><p>Continuous testing and maintenance of the AI system is possible.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Fully optimized and up-to-date dedicated (hardware and software) runtime environments are available.</p></list-item><list-item><p>Model development and maintenance are implemented according to modern CI or CD components.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item></list></td><td align="left" valign="top">Emerged from this research</td></tr><tr><td align="left" valign="top" colspan="10">Social and ethical requirements and aspects</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>4.4</td><td align="left" valign="top">Engagement with ethical-normative values of nursing and care, and individual clinical partners</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>No engagement with ethical values (has taken place) in the AINC project.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Initial ideas on how to engage with ethical-normative values in the AINC project exist but are not concrete or systematic.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Methods to engage with ethical-normative values are defined but are only partially implemented or exclude some stakeholders.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Regular, systematic, and documented engagement with ethical-normative values including all stakeholders is part of the AINC project.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Regular, systematic, and documented engagement with ethical-normative values including all stakeholders is part of the AINC project, and is adapted as needed.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item><list-item><p>Nursing Science</p></list-item><list-item><p>Clinical Partner</p></list-item></list></td><td align="left" valign="top">Emerged from our prior research<break/>[<xref ref-type="bibr" rid="ref49">49</xref>]</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>4.6</td><td align="left" valign="top">Reflection on the impact of AI on the nursing profession</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>The general influence of AI on nursing is acknowledged, but there is no project-level reflection.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Initial reflections on the impact of AI on the nursing profession are present.</p></list-item><list-item><p>However, reflections are unsystematic and without an effect on system development, implementation, or evaluation.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Systematic reflection on the impact of AI on the nursing profession is part of the AINC project but lacks influence on development, implementation, or evaluation.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Comprehensive reflection on the impact of AI on the nursing profession that informs system development, implementation, and evaluation is part of the AINC project.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Fully integrated reflection on the impact of AI on the nursing profession is included in the AINC project results and documentation.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item><list-item><p>Nursing Science</p></list-item><list-item><p>Clinical Partner</p></list-item></list></td><td align="left" valign="top">Emerged from our prior research<break/>[<xref ref-type="bibr" rid="ref49">49</xref>]</td></tr><tr><td align="left" valign="top" colspan="10">Community building requirements and aspects</td></tr><tr><td align="left" valign="top"><named-content content-type="indent">&#x00A0;&#x00A0;&#x00A0;&#x00A0;</named-content>5.3</td><td align="left" valign="top">Strategic partnerships</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Existing strategic partnerships are unknown or there are no strategic partnerships in the AINC project or among individual project partners.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Initial strategic partnerships are being explored, but have not yet been fully concluded or formalized.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Strategic partnerships are partially established, but not all partners in the AINC project have strategic partnerships.</p></list-item><list-item><p>Clinical partners in particular do not have strategic partnerships outside of the project consortium.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Comprehensive strategic partnerships are established.</p></list-item><list-item><p>Clinical partners also have strategic partnerships outside of the project consortium.</p></list-item><list-item><p>Existing strategic partnerships are regularly reviewed and expanded, especially on a national level.</p></list-item></list></td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Proven and effective strategic partnerships are established for all partners in the AINC project.</p></list-item><list-item><p>Existing strategic partnerships are continuously and internationally expanded.</p></list-item></list></td><td align="left" valign="top">Not applicable</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>AI R&#x0026;D</p></list-item><list-item><p>Nursing</p></list-item><list-item><p>Science</p></list-item><list-item><p>Clinical partner</p></list-item></list></td><td align="left" valign="top">[<xref ref-type="bibr" rid="ref42">42</xref>]</td></tr></tbody></table><table-wrap-foot><fn id="table4fn1"><p><sup>a</sup>AINCRA: artificial intelligence nursing care readiness assessment.</p></fn><fn id="table4fn2"><p><sup>b</sup>AINC: artificial intelligence in nursing care.</p></fn><fn id="table4fn3"><p><sup>c</sup>AI: artificial intelligence.</p></fn><fn id="table4fn4"><p><sup>d</sup>R&#x0026;D: research and development.</p></fn><fn id="table4fn5"><p><sup>e</sup>EU: European Union.</p></fn><fn id="table4fn6"><p><sup>f</sup>Data Champions understand the types of data generated at the clinical partner, advocate for proper data handling, and mediate between nursing staff and IT. They ensure data are correct, complete, and up to date, identify and resolve data collection issues, enhance staff data literacy through training, and raise awareness about the importance of data in nursing care and research.</p></fn></table-wrap-foot></table-wrap><p>AINCRA dimension 5, community building requirements and aspects, promotes a collaborative network to support knowledge exchange and the shared development of AI systems for nursing care, involving researchers, developers, and professionals from nursing practice and management, ideally reaching beyond single-project boundaries and striving for national and international networks and shared knowledge. All AINC project stakeholders can assess dimension 5 with AI R&#x0026;D and nursing science, especially reflecting on their involvement in technical knowledge transfer [<xref ref-type="bibr" rid="ref49">49</xref>], while clinical partners should also reflect on existing strategic partnerships and how to foster these [<xref ref-type="bibr" rid="ref42">42</xref>] (<xref ref-type="table" rid="table4">Table 4</xref>).</p></sec><sec id="s3-15"><title>Applying AINCRA</title><p>AINCRA is primarily designed as a self-assessment tool for AINC project partners. It addresses topics such as the use and benefit of AINC, data representativeness and sharing, participatory design, and ethical and professional implications of AI implementation. AINCRA can be used at any project stage: a single assessment provides a snapshot of current AI readiness, while repeated assessments enable monitoring progress over time. It may also serve as an external evaluation tool. In all cases, AINCRA should be applied by an interprofessional team, ideally involving representatives from AI R&#x0026;D, nursing science, and clinical partner organizations. The tool can be used for an entire AINC project or for selected dimensions or sub-areas.</p></sec><sec id="s3-16"><title>Interpreting AINCRA</title><p>In the absence of an internationally agreed consensus on which factors most strongly determine the success of AINC projects, AINCRA does not produce an overall score. Instead, it prompts users to reflect systematically on all dimensions and attributes, which are consistently considered important for project success. AINCRA results provide a snapshot of an AINC project&#x2019;s current readiness with regard to known prerequisites for successful AI development and implementation in nursing care. The tool can be used in context analysis, project planning, and formative evaluation to identify areas for further development or prioritization, and in summative evaluation to reflect on factors that influenced project outcomes. Across all project phases, AINCRA supports alignment, justification, and documentation of strategies while fostering constructive, content-focused dialogue among project partners.</p></sec></sec><sec id="s4" sec-type="discussion"><title>Discussion</title><sec id="s4-1"><title>Principal Findings</title><p>Despite AI&#x2019;s high potential to support nursing care, many use cases in acute and long-term care are still underexplored [<xref ref-type="bibr" rid="ref13">13</xref>], and R&#x0026;D projects face multifaceted challenges when designing, implementing, or evaluating AI systems in everyday nursing care. In this study, we systematically developed dimensions, attributes, and levels of AI readiness based on published empirical evidence as well as insights from experts with practical experience in conducting AINC projects. Integrating findings from prior work, a systematic literature review and expert discussions directly shaped the development of AINCRA. Attributes and dimensions identified in earlier work provided an initial conceptual structure that was operationalized in a first AINCRA version. This version served as the basis for think-aloud interviews and discussions with experts during which the relevance, clarity, and completeness of individual attributes were critically examined. Feedback from these discussions led to the refinement and consolidation of attributes and informed adjustments. As a result, the final AINCRA reflects a synthesis of theoretical grounding, empirical evidence, and practical expert insight. The resulting AINCRA comprises 5 dimensions and 69 AI readiness attributes across 5 readiness levels that can guide AINC project planning, implementation, and evaluation. While experts with practical experience in conducting AINC projects rated the readiness level 5 (optimized) as ambitious and often unrealistic for AINC projects, they recognized AINCRA's value and overall benefit to support AINC projects, especially with respect to early identification and thus avoidance of common pitfalls of these projects.</p><p>A major strength of AINCRA is its comprehensive inclusion of evidence-based, previously established AI readiness factors, with a focus on processual and translational aspects. Prior research on a sociotechnical perspective for responsible AI maturity models has shown that organizations often focus on technical and business assessments when developing and deploying AI systems, while overlooking critical ethical, social, and human dimensions [<xref ref-type="bibr" rid="ref20">20</xref>]. We argue that this holds true for AINC projects as well, so that they will benefit from recognizing and systematically addressing the importance of both technical and social aspects [<xref ref-type="bibr" rid="ref20">20</xref>]. In addition, AINCRA sets itself apart from other freely available or commercial instruments, such as the analytics maturity assessment model promoted by the Healthcare Information and Management Systems Society through its consistent focus on the specific application context of nursing care. Many of the models existing before the AINCRA development have not been thoroughly reviewed by the scientific community. Therefore, they were not identified during the systematic literature review. AINCRA goes beyond preexisting models, offering a framework that is both more specialized and scientifically validated for use in AINC projects. As most attributes were derived from and may be transferred to a global context, we see overall generalizability of our results, even though AINCRA was developed within the European legal framework for AI in health care settings. While experiences of AINC experts stem from a German health care and research system perspective that may differ from other countries&#x2019; prerequisites and available resources, for example, for funding AINC project staff, technical infrastructure or knowledge transfer and dissemination activities, as well as structures, processes, and outcomes of nursing care, we believe that European-centric attributes can be easily adapted to other regional or national requirements.</p></sec><sec id="s4-2"><title>Implications for AI R&#x0026;D, Nursing Science, and Clinical Partner Organizations</title><p>Given the widely reported issue that actors from health care and information science often do not share the same domain language in R&#x0026;D projects and frequently work past one another [<xref ref-type="bibr" rid="ref50">50</xref>], creating transparency and a common understanding of project aims and key concepts should be a shared goal among AINC project partners. AINCRA contributes to achieving this goal by raising awareness of relevant aspects. It also provides a foundation for decision-making at the project initiation phase, helping to determine which partners need to be involved, at what stages, and with what level of resource commitment. Additionally, it enables a better estimation of the risks and costs associated with AI development and deployment. By operationalizing and making the AINC project&#x2019;s progress more visible across different domains and project partners, it fosters a shared basis for discussion and terminology, promoting more effective collaboration.</p><p>Leveraging the potential of AI in health and nursing care requires robust estimates of a variety of factors relevant for such an investment, including implementation time, associated costs, regulatory risks, and technology acceptance among potential users and patients [<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref25">25</xref>,<xref ref-type="bibr" rid="ref30">30</xref>]. These estimates call for a thorough understanding of the status quo of health care institutions with respect to a variety of dimensions as detailed in AINCRA. The structure provided with AINCRA can support strategic decisions on investments by providing reliable insights on the efforts required to implement AI technology in clinical practice. The attributes developed in this study can also help to identify gaps and future areas of improvement with regard to AI technology in nursing practice. In addition, the insights gained in expert interviews help to manage expectations in translating and disseminating AI research to nursing practice. It is evident that an assessment of AI readiness will be challenging or even impossible without transdisciplinary teams that combine expertise in technical, regulatory, and ethical questions with expertise in nursing care.</p><p>Although AINCRA is extensive and complex, by advocating for an interprofessional approach, it enables a comprehensive evaluation of AINC projects, due to its high level of detail, ensuring that no blind spots are overlooked. Furthermore, AINCRA is applicable to a wide range of projects, as the term AI is defined broadly, making it relevant across various areas within the field.</p></sec><sec id="s4-3"><title>Comparison With Design Recommendations and Common Criticism of Maturity Models</title><p>Eight requirements for designing maturity models [<xref ref-type="bibr" rid="ref23">23</xref>] were applied throughout the AINCRA development process. <xref ref-type="table" rid="table5">Table 5</xref> outlines how these requirements were addressed and implemented in this study. Above all, the comprehensive comparison with existing maturity models, alongside an iterative approach and the sequential expert evaluation of attribute and level descriptions, strengthens the presented research.</p><table-wrap id="t5" position="float"><label>Table 5.</label><caption><p>Incorporation of design recommendations in the AINCRA<sup><xref ref-type="table-fn" rid="table5fn1">a</xref></sup> development process.</p></caption><table id="table5" frame="hsides" rules="groups"><thead><tr><td align="left" valign="bottom">Requirement (R) derived from [<xref ref-type="bibr" rid="ref23">23</xref>]</td><td align="left" valign="bottom">Incorporation of requirement through...</td></tr></thead><tbody><tr><td align="left" valign="top">R1: Comparison with existing maturity models</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Systematic literature review</p></list-item><list-item><p>Further development of own prior work</p></list-item><list-item><p>Focus on AI<sup><xref ref-type="table-fn" rid="table5fn2">b</xref></sup> readiness or maturity models in health or nursing care</p></list-item></list></td></tr><tr><td align="left" valign="top">R2: Iterative procedure</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Research process with 3 iterations</p></list-item></list></td></tr><tr><td align="left" valign="top">R3: Evaluation</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Application and rating of AINCRA pilot version through experts</p></list-item></list></td></tr><tr><td align="left" valign="top">R4: Multimethodological procedure</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Sequential exploratory multimethods design</p></list-item></list></td></tr><tr><td align="left" valign="top">R5: Identification of problem relevance</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Rating and confirmation of AINCRA&#x2019;s relevance in expert group discussions</p></list-item></list></td></tr><tr><td align="left" valign="top">R6: Problem definition</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Results of preliminary work [<xref ref-type="bibr" rid="ref13">13</xref>]</p></list-item></list></td></tr><tr><td align="left" valign="top">R7: Targeted presentation of results</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Feedback from the target group of intended users</p></list-item><list-item><p>Use of discipline-specific terminology</p></list-item><list-item><p>Development of a standard vocabulary for level distinctions together with the intended users</p></list-item></list></td></tr><tr><td align="left" valign="top">R8: Scientific documentation</td><td align="left" valign="top"><list list-type="bullet"><list-item><p>Study documents</p></list-item><list-item><p>Ethics application</p></list-item><list-item><p>Mandatory reporting for funding body</p></list-item><list-item><p>Open access publication of AINCRA</p></list-item></list></td></tr></tbody></table><table-wrap-foot><fn id="table5fn1"><p><sup>a</sup>AINCRA: artificial intelligence nursing care readiness assessment.</p></fn><fn id="table5fn2"><p><sup>b</sup>AI: artificial intelligence.</p></fn></table-wrap-foot></table-wrap><p>Three main criticisms of maturity models [<xref ref-type="bibr" rid="ref24">24</xref>] should be reflected on regarding AINCRA&#x2019;s internal and external validity: (1) lack of a solid theoretical foundation without grounding elements such as maturity levels and dimensions in established academic literature [<xref ref-type="bibr" rid="ref24">24</xref>], (2) lack of sufficient empirical support for the selection of dimensions or variables, and (3) lack of a clear definition of how maturity should be measured [<xref ref-type="bibr" rid="ref24">24</xref>]. While we rigorously aimed to address the first 2 criticisms during development by review of the academic literature and iterative evaluation and consensus building with domain experts, a degree of ambiguity in the measurement of AINC readiness remains. This arises partly from the nature of AINCRA as a self-assessment instrument. On the other hand, it is worth noting that AINCRA provides qualitative but not quantitative criteria for assigning a maturity level. Hence, an answer to the question, for example, whether simply participating in one regional network is sufficient to meet the requirements for community building attributes, or whether involvement in at least 3 different networks is needed, remains open to interpretation. Users may assess individual attributes with varying degrees of realism and flexibility. Further operationalization is therefore strongly recommended.</p></sec><sec id="s4-4"><title>Limitations and Future Research</title><p>Our results have limitations that call for further research. First, experts commented on 66 of 69 readiness attributes only. Attributes 2.39 strategies for long-term external support: software and hardware: upgrades, 2.40 strategies for long-term external support: software and hardware: maintenance, and 2.29 financial resources and investments: exploring alternative financing models for including clinical partners remained without comments. Why these attributes were not addressed, even though they have been identified as relevant for AI [<xref ref-type="bibr" rid="ref41">41</xref>], is not obvious. Most likely is the limited time span of the think-aloud task, which may have constrained responses. Toward the end of the task, experts focused particularly on attributes they found interesting or especially relevant. Besides, not all invited experts participated. The findings are based on the expertise of a subset of participants. Although key stakeholders were represented, it cannot be assumed that data saturation was fully achieved, as not all invited experts took part in the study, and data collection concluded after interviewing all experts who had agreed to participation.</p><p>Second, as research on organizational AI readiness has previously highlighted as a relevant limitation [<xref ref-type="bibr" rid="ref21">21</xref>], while AINCRA was developed to systematize key attributes of AINC readiness, overlaps with readiness or frameworks for adopting and implementing other digital technologies can be recognized, such as stakeholder acceptance as a key attribute for technology adoption [<xref ref-type="bibr" rid="ref51">51</xref>]. However, the project-specific perspective of AINCRA expands preexisting frameworks, which predominantly adopt an organizational perspective, thus providing AINC projects with a reflective tool and instrument to support project management.</p><p>Third, we decided against substantially shortening or prioritizing AINC readiness attributes, despite suggestions from some experts. This makes AINCRA more time-consuming and potentially less practical for everyday project work. However, this decision is informed by our experiences with multiple AINC projects over the past 5 years, which show that many projects underestimate their complexity and are affected by domain-specific blind spots that hinder collaboration. At the same time, our findings do not fully clarify how individual attributes interact or which should be addressed together when strengthening AINC readiness. While we applied an established method for maturity model evaluation that is being used in information science for decades [<xref ref-type="bibr" rid="ref48">48</xref>], future research may strive for validating our results by applying AINCRA to real process improvement activities [<xref ref-type="bibr" rid="ref48">48</xref>] in future AINC projects.</p></sec><sec id="s4-5"><title>Conclusion</title><p>In a field where many use cases remain underexplored and R&#x0026;D projects often face substantial barriers, AINCRA offers structured guidance to enhance AI readiness for research, development, and implementation of AI projects in nursing care. AINCRA provides a balanced integration of technical, organizational, ethical, and social aspects of AI readiness, addressing a common shortcoming of existing maturity models that tend to prioritize technical or business considerations. Its nursing-specific focus further distinguishes it from other generic or commercially available assessment instruments, making it both context-sensitive and scientifically grounded. Overall, AINCRA offers both a practical tool for current projects and a foundation for future research and refinement in the evolving field of AI systems in nursing care.</p></sec></sec></body><back><ack><p>The authors declare the use of generative AI in the research and writing process. According to the GAIDeT taxonomy, the following tasks were delegated to GAI tools under full human supervision: Translation. The GAI tool used was: ChatGPT 5. Responsibility for the final manuscript lies entirely with the authors. GAI tools are not listed as authors and do not bear responsibility for the final outcomes. Declaration submitted by: Kathrin Seibert Additional note: We used ChatGPT-5 to assist with translating the German language full AINCRA version and user manual to English language. We used for GPT-4o to generate initial level descriptions based on the AI readiness vocabulary for level distinction developed by the authors for this study.</p></ack><notes><sec><title>Funding</title><p>This study was funded by the German Ministry for Research, Technology and Space, Grant ID 16SV8835, the Einstein Center Digital Future, Berlin, and the German Research Foundation (Project number: 528483508 - FIP 12). The funders played no role in study design, data collection, analysis, and interpretation of data, or the writing of this manuscript.</p></sec><sec><title>Data Availability</title><p>All data generated or analyzed for the systematic literature review are included in this published article and its supplementary information files. The datasets generated and analyzed based on think-aloud interviews and focus group discussions are not publicly available, to ensure participant privacy but are available from the corresponding author upon reasonable request. Data are stored in a controlled access data storage at the University of Bremen.</p></sec></notes><fn-group><fn fn-type="con"><p>Conceptualization: KS, DD, FB, DF, DB, KW</p><p>Data curation: KS</p><p>Formal analysis: KS, JA, AN, JP, LB, DW</p><p>Funding acquisition: FB, DF, DB, KW</p><p>Investigation: KS, JA, AN, RG, LB</p><p>Methodology: KS, DD, AN, DF</p><p>Project administration: KS, DD</p><p>Supervision: KS, FB, DF, KW</p><p>Validation: KS, SJ, FB, AN, RG, MS, DF, JP, LB, KB, KW</p><p>Visualization: KS, LB</p><p>Writing &#x2013; original draft: KS</p><p>Writing &#x2013; review &#x0026; editing: DD, JA, SJ, FB, AN, RG, MS, DF, JP, LB, DW, KB, DB, KW</p></fn><fn fn-type="conflict"><p>None declared.</p></fn></fn-group><glossary><title>Abbreviations</title><def-list><def-item><term id="abb1">AI </term><def><p>artificial intelligence</p></def></def-item><def-item><term id="abb2">AINC </term><def><p>artificial intelligence in nursing care</p></def></def-item><def-item><term id="abb3">AINCRA </term><def><p>artificial intelligence nursing care readiness assessment</p></def></def-item><def-item><term id="abb4">COREQ</term><def><p>Consolidated Criteria for Reporting Qualitative Research</p></def></def-item><def-item><term id="abb5">EU AI</term><def><p>European Union artificial intelligence</p></def></def-item><def-item><term id="abb6">ML</term><def><p>machine learning</p></def></def-item><def-item><term id="abb7">PRISMA</term><def><p>Preferred Reporting Items for Systematic Reviews and Meta-Analyses</p></def></def-item><def-item><term id="abb8">R&#x0026;D </term><def><p>research and development</p></def></def-item></def-list></glossary><ref-list><title>References</title><ref id="ref1"><label>1</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Hassanein</surname><given-names>S</given-names> </name><name name-style="western"><surname>El Arab</surname><given-names>RA</given-names> </name><name name-style="western"><surname>Abdrbo</surname><given-names>A</given-names> </name><etal/></person-group><article-title>Artificial intelligence in nursing: an integrative review of clinical and operational impacts</article-title><source>Front Digit Health</source><year>2025</year><volume>7</volume><fpage>1552372</fpage><pub-id pub-id-type="doi">10.3389/fdgth.2025.1552372</pub-id><pub-id pub-id-type="medline">40124108</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>O&#x2019;Connor</surname><given-names>S</given-names> </name><name name-style="western"><surname>Yan</surname><given-names>Y</given-names> </name><name name-style="western"><surname>Thilo</surname><given-names>FJS</given-names> </name><name name-style="western"><surname>Felzmann</surname><given-names>H</given-names> </name><name name-style="western"><surname>Dowding</surname><given-names>D</given-names> </name><name name-style="western"><surname>Lee</surname><given-names>JJ</given-names> </name></person-group><article-title>Artificial intelligence in nursing and midwifery: a systematic review</article-title><source>J Clin Nurs</source><year>2023</year><month>07</month><volume>32</volume><issue>13-14</issue><fpage>2951</fpage><lpage>2968</lpage><pub-id pub-id-type="doi">10.1111/jocn.16478</pub-id><pub-id pub-id-type="medline">35908207</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>Seibert</surname><given-names>K</given-names> </name><name name-style="western"><surname>Domhoff</surname><given-names>D</given-names> </name><name name-style="western"><surname>Bruch</surname><given-names>D</given-names> </name><etal/></person-group><article-title>Application scenarios for artificial intelligence in nursing care: rapid review</article-title><source>J Med Internet Res</source><year>2021</year><month>11</month><day>29</day><volume>23</volume><issue>11</issue><fpage>e26522</fpage><pub-id pub-id-type="doi">10.2196/26522</pub-id><pub-id pub-id-type="medline">34847057</pub-id></nlm-citation></ref><ref id="ref4"><label>4</label><nlm-citation citation-type="report"><article-title>Approval of the content of the draft communication from the commission - commission guidelines on the definition of an artificial intelligence system established by regulation (EU) 2024/1689 (AI act)</article-title><year>2025</year><access-date>2026-05-08</access-date><publisher-name>European Commission</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://ec.europa.eu/newsroom/dae/redirection/document/118559">https://ec.europa.eu/newsroom/dae/redirection/document/118559</ext-link></comment></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>Raza</surname><given-names>MM</given-names> </name><name name-style="western"><surname>Venkatesh</surname><given-names>KP</given-names> </name><name name-style="western"><surname>Kvedar</surname><given-names>JC</given-names> </name></person-group><article-title>Generative AI and large language models in health care: pathways to implementation</article-title><source>NPJ Digit Med</source><year>2024</year><month>03</month><day>7</day><volume>7</volume><issue>1</issue><fpage>62</fpage><pub-id pub-id-type="doi">10.1038/s41746-023-00988-4</pub-id><pub-id pub-id-type="medline">38454007</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>Majjouti</surname><given-names>K</given-names> </name><name name-style="western"><surname>Priester</surname><given-names>V</given-names> </name><name name-style="western"><surname>Tapp-Herrenbrueck</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Nursing-centered development of an AI-based decision support system in pressure ulcer and incontinence-associated dermatitis management - a mixed methods study</article-title><source>BMC Nurs</source><year>2025</year><month>07</month><day>1</day><volume>24</volume><issue>1</issue><fpage>808</fpage><pub-id pub-id-type="doi">10.1186/s12912-025-03448-4</pub-id><pub-id pub-id-type="medline">40598248</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>Kopanz</surname><given-names>J</given-names> </name><name name-style="western"><surname>Mader</surname><given-names>JK</given-names> </name><name name-style="western"><surname>Donsa</surname><given-names>K</given-names> </name><etal/></person-group><article-title>Digital algorithm-guided insulin therapy in home healthcare for elderly persons with type 2 diabetes: a proof-of-concept study</article-title><source>Front Clin Diabetes Healthc</source><year>2022</year><volume>3</volume><fpage>986672</fpage><pub-id pub-id-type="doi">10.3389/fcdhc.2022.986672</pub-id><pub-id pub-id-type="medline">36992745</pub-id></nlm-citation></ref><ref id="ref8"><label>8</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Majjouti</surname><given-names>K</given-names> </name><name name-style="western"><surname>Tapp-Herrenbrueck</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pinnekamp</surname><given-names>H</given-names> </name><etal/></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Yurish</surname><given-names>SY</given-names> </name></person-group><article-title>KIADEKU: identification of wound types with AI</article-title><access-date>2026-05-08</access-date><conf-name>Proceedings of the 1st International Conference on AI in Medicine and Healthcare (AiMH&#x2019; 2025)</conf-name><conf-date>Apr 8-10, 2025</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://sensorsportal.com/AIMH_2025/AIMH_2025_Proceedings.pdf">https://sensorsportal.com/AIMH_2025/AIMH_2025_Proceedings.pdf</ext-link></comment></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>Alves</surname><given-names>J</given-names> </name><name name-style="western"><surname>Azevedo</surname><given-names>R</given-names> </name><name name-style="western"><surname>Marques</surname><given-names>A</given-names> </name><name name-style="western"><surname>Encarna&#x00E7;&#x00E3;o</surname><given-names>R</given-names> </name><name name-style="western"><surname>Alves</surname><given-names>P</given-names> </name></person-group><article-title>Pressure injury prediction in intensive care units using artificial intelligence: a scoping review</article-title><source>Nurs Rep</source><year>2025</year><month>04</month><day>9</day><volume>15</volume><issue>4</issue><fpage>126</fpage><pub-id pub-id-type="doi">10.3390/nursrep15040126</pub-id><pub-id pub-id-type="medline">40338264</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>Gallo</surname><given-names>RJ</given-names> </name><name name-style="western"><surname>Shieh</surname><given-names>L</given-names> </name><name name-style="western"><surname>Smith</surname><given-names>M</given-names> </name><etal/></person-group><article-title>Effectiveness of an artificial intelligence-enabled intervention for detecting clinical deterioration</article-title><source>JAMA Intern Med</source><year>2024</year><month>05</month><day>1</day><volume>184</volume><issue>5</issue><fpage>557</fpage><lpage>562</lpage><pub-id pub-id-type="doi">10.1001/jamainternmed.2024.0084</pub-id><pub-id pub-id-type="medline">38526472</pub-id></nlm-citation></ref><ref id="ref11"><label>11</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Schwabe</surname><given-names>K</given-names> </name><name name-style="western"><surname>Ferizaj</surname><given-names>D</given-names> </name><name name-style="western"><surname>Neumann</surname><given-names>S</given-names> </name></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Yurish</surname><given-names>SY</given-names> </name></person-group><article-title>Reducing nurses&#x2019; workload with an AI speech assistant for documentation</article-title><year>2025</year><conf-name>First International Conference on AI in Medicine and Healthcare (AiMH&#x2019; 2025)</conf-name><conf-date>Apr 8-10, 2025</conf-date><pub-id pub-id-type="doi">10.13140/RG.2.2.20387.77606</pub-id></nlm-citation></ref><ref id="ref12"><label>12</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Ferizaj</surname><given-names>D</given-names> </name><name name-style="western"><surname>Neumann</surname><given-names>S</given-names> </name></person-group><article-title>Assessing perceptions and experiences of an AI-driven speech assistant for nursing documentation: a qualitative study in german nursing homes</article-title><year>2024</year><conf-name>Human-Computer Interaction: Thematic Area, HCI 2024, Held as Part of the 26th HCI International Conference</conf-name><conf-date>Jun 29 to Jul 4, 2024</conf-date><conf-loc>Washington, DC, USA</conf-loc><fpage>17</fpage><lpage>34</lpage><pub-id pub-id-type="doi">10.1007/978-3-031-60449-2_2</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>Seibert</surname><given-names>K</given-names> </name><name name-style="western"><surname>Domhoff</surname><given-names>D</given-names> </name><name name-style="western"><surname>F&#x00FC;rstenau</surname><given-names>D</given-names> </name><name name-style="western"><surname>Biessmann</surname><given-names>F</given-names> </name><name name-style="western"><surname>Schulte-Althoff</surname><given-names>M</given-names> </name><name name-style="western"><surname>Wolf-Ostermann</surname><given-names>K</given-names> </name></person-group><article-title>Exploring needs and challenges for AI in nursing care &#x2013; results of an explorative sequential mixed methods study</article-title><source>BMC Digit Health</source><year>2023</year><volume>1</volume><issue>1</issue><pub-id pub-id-type="doi">10.1186/s44247-023-00015-2</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>von Gerich</surname><given-names>H</given-names> </name><name name-style="western"><surname>Moen</surname><given-names>H</given-names> </name><name name-style="western"><surname>Block</surname><given-names>LJ</given-names> </name><etal/></person-group><article-title>Artificial Intelligence -based technologies in nursing: a scoping literature review of the evidence</article-title><source>Int J Nurs Stud</source><year>2022</year><month>03</month><volume>127</volume><fpage>104153</fpage><pub-id pub-id-type="doi">10.1016/j.ijnurstu.2021.104153</pub-id><pub-id pub-id-type="medline">35092870</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>Feuerriegel</surname><given-names>S</given-names> </name><name name-style="western"><surname>Frauen</surname><given-names>D</given-names> </name><name name-style="western"><surname>Melnychuk</surname><given-names>V</given-names> </name><etal/></person-group><article-title>Causal machine learning for predicting treatment outcomes</article-title><source>Nat Med</source><year>2024</year><month>04</month><volume>30</volume><issue>4</issue><fpage>958</fpage><lpage>968</lpage><pub-id pub-id-type="doi">10.1038/s41591-024-02902-1</pub-id><pub-id pub-id-type="medline">38641741</pub-id></nlm-citation></ref><ref id="ref16"><label>16</label><nlm-citation citation-type="report"><article-title>State of the world&#x2019;s nursing 2025</article-title><year>2025</year><access-date>2026-05-08</access-date><publisher-name>World Health Organization</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://www.who.int/publications/i/item/9789240110236">https://www.who.int/publications/i/item/9789240110236</ext-link></comment></nlm-citation></ref><ref id="ref17"><label>17</label><nlm-citation citation-type="report"><article-title>EFN policy statement on improving frontline nurses&#x2019; time for direct patient care with digitalisation and responsible AI</article-title><year>2024</year><access-date>2026-05-08</access-date><publisher-name>European Federation of Nurses Association</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://efn.eu/wp-content/uploads/2024/10/EFN-PS-improving-frontline-nurses-time-for-direct-patient-care-with-digitalisation-responsible-AI-Oct.-2024.pdf">https://efn.eu/wp-content/uploads/2024/10/EFN-PS-improving-frontline-nurses-time-for-direct-patient-care-with-digitalisation-responsible-AI-Oct.-2024.pdf</ext-link></comment></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>Ball Dunlap</surname><given-names>PA</given-names> </name><name name-style="western"><surname>Michalowski</surname><given-names>M</given-names> </name></person-group><article-title>Advancing AI data ethics in nursing: future directions for nursing practice, research, and education</article-title><source>JMIR Nurs</source><year>2024</year><month>10</month><day>25</day><volume>7</volume><fpage>e62678</fpage><pub-id pub-id-type="doi">10.2196/62678</pub-id><pub-id pub-id-type="medline">39453630</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>Buchanan</surname><given-names>C</given-names> </name><name name-style="western"><surname>Howitt</surname><given-names>ML</given-names> </name><name name-style="western"><surname>Wilson</surname><given-names>R</given-names> </name><name name-style="western"><surname>Booth</surname><given-names>RG</given-names> </name><name name-style="western"><surname>Risling</surname><given-names>T</given-names> </name><name name-style="western"><surname>Bamford</surname><given-names>M</given-names> </name></person-group><article-title>Predicted influences of artificial intelligence on the domains of nursing: scoping review</article-title><source>JMIR Nurs</source><year>2020</year><month>12</month><day>17</day><volume>3</volume><issue>1</issue><fpage>e23939</fpage><pub-id pub-id-type="doi">10.2196/23939</pub-id><pub-id pub-id-type="medline">34406963</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>Akbarighatar</surname><given-names>P</given-names> </name><name name-style="western"><surname>Pappas</surname><given-names>I</given-names> </name><name name-style="western"><surname>Vassilakopoulou</surname><given-names>P</given-names> </name></person-group><article-title>A sociotechnical perspective for responsible AI maturity models: findings from a mixed-method literature review</article-title><source>Int J Inf Managment Data Insights</source><year>2023</year><month>11</month><volume>3</volume><issue>2</issue><fpage>100193</fpage><pub-id pub-id-type="doi">10.1016/j.jjimei.2023.100193</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>J&#x00F6;hnk</surname><given-names>J</given-names> </name><name name-style="western"><surname>Wei&#x00DF;ert</surname><given-names>M</given-names> </name><name name-style="western"><surname>Wyrtki</surname><given-names>K</given-names> </name><name name-style="western"><surname>Not</surname><given-names>AC</given-names> </name></person-group><article-title>Ready or not, AI comes&#x2014; an interview study of organizational AI readiness factors</article-title><source>Bus Inf Syst Eng</source><year>2021</year><month>02</month><volume>63</volume><issue>1</issue><fpage>5</fpage><lpage>20</lpage><pub-id pub-id-type="doi">10.1007/s12599-020-00676-7</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>Fountaine</surname><given-names>T</given-names> </name><name name-style="western"><surname>McCarthy</surname><given-names>B</given-names> </name><name name-style="western"><surname>Saleh</surname><given-names>T</given-names> </name></person-group><article-title>Building the AI-Powered Organization. Technology isn&#x2019;t the biggest challenge. Culture is</article-title><source>Harv Bus Rev</source><year>2019</year><access-date>2026-05-08</access-date><fpage>62</fpage><lpage>73</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://hbr.org/2019/07/building-the-ai-powered-organization">https://hbr.org/2019/07/building-the-ai-powered-organization</ext-link></comment></nlm-citation></ref><ref id="ref23"><label>23</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Becker</surname><given-names>J</given-names> </name><name name-style="western"><surname>Knackstedt</surname><given-names>R</given-names> </name><name name-style="western"><surname>P&#x00F6;ppelbu&#x00DF;</surname><given-names>J</given-names> </name></person-group><article-title>Developing maturity models for IT management</article-title><source>Bus Inf Syst Eng</source><year>2009</year><month>06</month><volume>1</volume><issue>3</issue><fpage>213</fpage><lpage>222</lpage><pub-id pub-id-type="doi">10.1007/s12599-009-0044-5</pub-id></nlm-citation></ref><ref id="ref24"><label>24</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Lasrado</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Vatrapu</surname><given-names>R</given-names> </name><name name-style="western"><surname>Andersen</surname><given-names>KN</given-names> </name></person-group><article-title>Maturity models development in IS research: a literature review</article-title><year>2015</year><access-date>2026-05-08</access-date><conf-name>System design for, with and by users</conf-name><conf-date>Aug 9-12, 2015</conf-date><comment><ext-link ext-link-type="uri" xlink:href="https://aisel.aisnet.org/iris2015/6/">https://aisel.aisnet.org/iris2015/6/</ext-link></comment></nlm-citation></ref><ref id="ref25"><label>25</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Pumplun</surname><given-names>L</given-names> </name><name name-style="western"><surname>Fecho</surname><given-names>M</given-names> </name><name name-style="western"><surname>Wahl</surname><given-names>N</given-names> </name><name name-style="western"><surname>Peters</surname><given-names>F</given-names> </name><name name-style="western"><surname>Buxmann</surname><given-names>P</given-names> </name></person-group><article-title>Adoption of machine learning systems for medical diagnostics in clinics: qualitative interview study</article-title><source>J Med Internet Res</source><year>2021</year><month>10</month><day>15</day><volume>23</volume><issue>10</issue><fpage>e29301</fpage><pub-id pub-id-type="doi">10.2196/29301</pub-id><pub-id pub-id-type="medline">34652275</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>Page</surname><given-names>MJ</given-names> </name><name name-style="western"><surname>McKenzie</surname><given-names>JE</given-names> </name><name name-style="western"><surname>Bossuyt</surname><given-names>PM</given-names> </name><etal/></person-group><article-title>The PRISMA 2020 statement: an updated guideline for reporting systematic reviews</article-title><source>BMJ</source><year>2021</year><month>03</month><day>29</day><volume>372</volume><fpage>n71</fpage><pub-id pub-id-type="doi">10.1136/bmj.n71</pub-id><pub-id pub-id-type="medline">33782057</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>Tong</surname><given-names>A</given-names> </name><name name-style="western"><surname>Sainsbury</surname><given-names>P</given-names> </name><name name-style="western"><surname>Craig</surname><given-names>J</given-names> </name></person-group><article-title>Consolidated Criteria for Reporting Qualitative Research (COREQ): a 32-item checklist for interviews and focus groups</article-title><source>Int J Qual Health Care</source><year>2007</year><month>12</month><volume>19</volume><issue>6</issue><fpage>349</fpage><lpage>357</lpage><pub-id pub-id-type="doi">10.1093/intqhc/mzm042</pub-id><pub-id pub-id-type="medline">17872937</pub-id></nlm-citation></ref><ref id="ref28"><label>28</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>O&#x2019;Cathain</surname><given-names>A</given-names> </name><name name-style="western"><surname>Murphy</surname><given-names>E</given-names> </name><name name-style="western"><surname>Nicholl</surname><given-names>J</given-names> </name></person-group><article-title>The quality of mixed methods studies in health services research</article-title><source>J Health Serv Res Policy</source><year>2008</year><month>04</month><volume>13</volume><issue>2</issue><fpage>92</fpage><lpage>98</lpage><pub-id pub-id-type="doi">10.1258/jhsrp.2007.007074</pub-id><pub-id pub-id-type="medline">18416914</pub-id></nlm-citation></ref><ref id="ref29"><label>29</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Seibert</surname><given-names>K</given-names> </name><name name-style="western"><surname>Domhoff</surname><given-names>D</given-names> </name><name name-style="western"><surname>Altona</surname><given-names>J</given-names> </name><etal/></person-group><person-group person-group-type="editor"><name name-style="western"><surname>Yurish</surname><given-names>SY</given-names> </name></person-group><article-title>ProKIP: rationale and development of the AI-nursing-care-readiness-assessment (AINCRA)</article-title><year>2025</year><access-date>2026-05-08</access-date><conf-name>In First International Conference on AI in Medicine and Healthcare (AiMH&#x2019; 2025)</conf-name><conf-date>Apr 8-10, 2025</conf-date><conf-loc>Innsbruck, Austria</conf-loc><fpage>8</fpage><lpage>10</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://sensorsportal.com/AIMH_2025/AIMH_2025_Proceedings.pdf">https://sensorsportal.com/AIMH_2025/AIMH_2025_Proceedings.pdf</ext-link></comment></nlm-citation></ref><ref id="ref30"><label>30</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Chang</surname><given-names>A</given-names> </name></person-group><article-title>Implementation of artificial intelligence in medicine, in intelligence-based medicine artificial</article-title><source>Artificial Intelligence and Human Cognition in Clinical Medicine and Healthcare</source><year>2020</year><publisher-name>Academic Press</publisher-name><fpage>397</fpage><lpage>412</lpage><pub-id pub-id-type="doi">10.1016/B978-0-12-823337-5.00009-3</pub-id></nlm-citation></ref><ref id="ref31"><label>31</label><nlm-citation citation-type="journal"><person-group person-group-type="author"><name name-style="western"><surname>Boren</surname><given-names>SA</given-names> </name><name name-style="western"><surname>Moxley</surname><given-names>D</given-names> </name></person-group><article-title>Systematically reviewing the literature: building the evidence for health care quality</article-title><source>Mo Med</source><year>2015</year><volume>112</volume><issue>1</issue><fpage>58</fpage><lpage>62</lpage><pub-id pub-id-type="medline">25812277</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>Ouzzani</surname><given-names>M</given-names> </name><name name-style="western"><surname>Hammady</surname><given-names>H</given-names> </name><name name-style="western"><surname>Fedorowicz</surname><given-names>Z</given-names> </name><name name-style="western"><surname>Elmagarmid</surname><given-names>A</given-names> </name></person-group><article-title>Rayyan-a web and mobile app for systematic reviews</article-title><source>Syst Rev</source><year>2016</year><month>12</month><day>5</day><volume>5</volume><issue>1</issue><fpage>210</fpage><pub-id pub-id-type="doi">10.1186/s13643-016-0384-4</pub-id><pub-id pub-id-type="medline">27919275</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>Palinkas</surname><given-names>LA</given-names> </name><name name-style="western"><surname>Horwitz</surname><given-names>SM</given-names> </name><name name-style="western"><surname>Green</surname><given-names>CA</given-names> </name><name name-style="western"><surname>Wisdom</surname><given-names>JP</given-names> </name><name name-style="western"><surname>Duan</surname><given-names>N</given-names> </name><name name-style="western"><surname>Hoagwood</surname><given-names>K</given-names> </name></person-group><article-title>Purposeful sampling for qualitative data collection and analysis in mixed method implementation research</article-title><source>Adm Policy Ment Health</source><year>2015</year><month>09</month><volume>42</volume><issue>5</issue><fpage>533</fpage><lpage>544</lpage><pub-id pub-id-type="doi">10.1007/s10488-013-0528-y</pub-id><pub-id pub-id-type="medline">24193818</pub-id></nlm-citation></ref><ref id="ref34"><label>34</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Willis</surname><given-names>GB</given-names> </name></person-group><source>Analysis of the Cognitive Interview in Questionnaire Design</source><year>2015</year><publisher-name>Oxford University Press</publisher-name><pub-id pub-id-type="other">978-0190262853</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>Doctor</surname><given-names>E</given-names> </name><name name-style="western"><surname>Eymann</surname><given-names>T</given-names> </name><name name-style="western"><surname>F&#x00FC;rstenau</surname><given-names>D</given-names> </name><etal/></person-group><article-title>A maturity model for assessing the digitalization of public health agencies</article-title><source>Bus Inf Syst Eng</source><year>2023</year><month>10</month><volume>65</volume><issue>5</issue><fpage>539</fpage><lpage>554</lpage><pub-id pub-id-type="doi">10.1007/s12599-023-00813-y</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>Elo</surname><given-names>S</given-names> </name><name name-style="western"><surname>Kyng&#x00E4;s</surname><given-names>H</given-names> </name></person-group><article-title>The qualitative content analysis process</article-title><source>J Adv Nurs</source><year>2008</year><month>04</month><volume>62</volume><issue>1</issue><fpage>107</fpage><lpage>115</lpage><pub-id pub-id-type="doi">10.1111/j.1365-2648.2007.04569.x</pub-id><pub-id pub-id-type="medline">18352969</pub-id></nlm-citation></ref><ref id="ref37"><label>37</label><nlm-citation citation-type="web"><article-title>AI nursing care readiness assessment (AINCRA): a tool for structured reflection and preparation of AI projects in nursing care</article-title><source>ProKIP</source><year>2026</year><access-date>2026-08-04</access-date><comment><ext-link ext-link-type="uri" xlink:href="https://aincra.prokip.care/en">https://aincra.prokip.care/en</ext-link></comment></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>Abuzaid</surname><given-names>MM</given-names> </name><name name-style="western"><surname>Elshami</surname><given-names>W</given-names> </name><name name-style="western"><surname>Tekin</surname><given-names>H</given-names> </name><name name-style="western"><surname>Issa</surname><given-names>B</given-names> </name></person-group><article-title>Assessment of the willingness of radiologists and radiographers to accept the integration of artificial intelligence into radiology practice</article-title><source>Acad Radiol</source><year>2022</year><month>01</month><volume>29</volume><issue>1</issue><fpage>87</fpage><lpage>94</lpage><pub-id pub-id-type="doi">10.1016/j.acra.2020.09.014</pub-id><pub-id pub-id-type="medline">33129659</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>Andersson</surname><given-names>J</given-names> </name><name name-style="western"><surname>Nyholm</surname><given-names>T</given-names> </name><name name-style="western"><surname>Ceberg</surname><given-names>C</given-names> </name><etal/></person-group><article-title>Artificial intelligence and the medical physics profession - a Swedish perspective</article-title><source>Phys Med</source><year>2021</year><month>08</month><volume>88</volume><fpage>218</fpage><lpage>225</lpage><pub-id pub-id-type="doi">10.1016/j.ejmp.2021.07.009</pub-id><pub-id pub-id-type="medline">34304045</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>Weinert</surname><given-names>L</given-names> </name><name name-style="western"><surname>M&#x00FC;ller</surname><given-names>J</given-names> </name><name name-style="western"><surname>Svensson</surname><given-names>L</given-names> </name><name name-style="western"><surname>Heinze</surname><given-names>O</given-names> </name></person-group><article-title>Perspective of information technology decision makers on factors influencing adoption and implementation of artificial intelligence technologies in 40 German hospitals: descriptive analysis</article-title><source>JMIR Med Inform</source><year>2022</year><month>06</month><day>15</day><volume>10</volume><issue>6</issue><fpage>e34678</fpage><pub-id pub-id-type="doi">10.2196/34678</pub-id><pub-id pub-id-type="medline">35704378</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>Alami</surname><given-names>H</given-names> </name><name name-style="western"><surname>Lehoux</surname><given-names>P</given-names> </name><name name-style="western"><surname>Denis</surname><given-names>JL</given-names> </name><etal/></person-group><article-title>Organizational readiness for artificial intelligence in health care: insights for decision-making and practice</article-title><source>J Health Organ Manag</source><year>2020</year><month>12</month><day>3</day><volume>ahead-of-print</volume><issue>ahead-of-print</issue><pub-id pub-id-type="doi">10.1108/JHOM-03-2020-0074</pub-id><pub-id pub-id-type="medline">33258359</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>Wiljer</surname><given-names>D</given-names> </name><name name-style="western"><surname>Hakim</surname><given-names>Z</given-names> </name></person-group><article-title>Developing an artificial intelligence-enabled health care practice: rewiring health care professions for better care</article-title><source>J Med Imaging Radiat Sci</source><year>2019</year><month>12</month><volume>50</volume><issue>4 Suppl 2</issue><fpage>S8</fpage><lpage>S14</lpage><pub-id pub-id-type="doi">10.1016/j.jmir.2019.09.010</pub-id><pub-id pub-id-type="medline">31791914</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>Jennett</surname><given-names>P</given-names> </name><name name-style="western"><surname>Yeo</surname><given-names>M</given-names> </name><name name-style="western"><surname>Pauls</surname><given-names>M</given-names> </name><name name-style="western"><surname>Graham</surname><given-names>J</given-names> </name></person-group><article-title>Organizational readiness for telemedicine: implications for success and failure</article-title><source>J Telemed Telecare</source><year>2003</year><volume>9 Suppl 2</volume><fpage>S27</fpage><lpage>30</lpage><pub-id pub-id-type="doi">10.1258/135763303322596183</pub-id><pub-id pub-id-type="medline">14728753</pub-id></nlm-citation></ref><ref id="ref44"><label>44</label><nlm-citation citation-type="confproc"><person-group person-group-type="author"><name name-style="western"><surname>Pumplun</surname><given-names>L</given-names> </name><name name-style="western"><surname>Tauchert</surname><given-names>C</given-names> </name><name name-style="western"><surname>Heidt</surname><given-names>M</given-names> </name></person-group><article-title>A new organizational chassis for artificial intelligence - exploring organizational readiness factors</article-title><year>2019</year><access-date>2026-05-08</access-date><conf-name>27th European conference on insformation systems (ECIS)</conf-name><comment><ext-link ext-link-type="uri" xlink:href="https://aisel.aisnet.org/ecis2019_rp/106/">https://aisel.aisnet.org/ecis2019_rp/106/</ext-link></comment></nlm-citation></ref><ref id="ref45"><label>45</label><nlm-citation citation-type="book"><person-group person-group-type="author"><name name-style="western"><surname>Someren</surname><given-names>MW</given-names> </name><name name-style="western"><surname>Barnard</surname><given-names>YF</given-names> </name><name name-style="western"><surname>Sandberg</surname><given-names>JAC</given-names> </name></person-group><source>The Think Aloud Method A Practical Guide to Modelling Cognitive Processes</source><year>1994</year><publisher-name>Academic Press</publisher-name><pub-id pub-id-type="other">&#x200E;978-0127142708</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>Wolcott</surname><given-names>MD</given-names> </name><name name-style="western"><surname>Lobczowski</surname><given-names>NG</given-names> </name></person-group><article-title>Using cognitive interviews and think-aloud protocols to understand thought processes</article-title><source>Curr Pharm Teach Learn</source><year>2021</year><month>02</month><volume>13</volume><issue>2</issue><fpage>181</fpage><lpage>188</lpage><pub-id pub-id-type="doi">10.1016/j.cptl.2020.09.005</pub-id><pub-id pub-id-type="medline">33454077</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>Peute</surname><given-names>LWP</given-names> </name><name name-style="western"><surname>de Keizer</surname><given-names>NF</given-names> </name><name name-style="western"><surname>Jaspers</surname><given-names>MWM</given-names> </name></person-group><article-title>The value of retrospective and concurrent think aloud in formative usability testing of a physician data query tool</article-title><source>J Biomed Inform</source><year>2015</year><month>06</month><volume>55</volume><fpage>1</fpage><lpage>10</lpage><pub-id pub-id-type="doi">10.1016/j.jbi.2015.02.006</pub-id><pub-id pub-id-type="medline">25733166</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>Helgesson</surname><given-names>YYL</given-names> </name><name name-style="western"><surname>H&#x00F6;st</surname><given-names>M</given-names> </name><name name-style="western"><surname>Weyns</surname><given-names>K</given-names> </name></person-group><article-title>A review of methods for evaluation of maturity models for process improvement</article-title><source>J Software Evolu Process</source><year>2012</year><month>06</month><access-date>2026-05-07</access-date><volume>24</volume><issue>4</issue><fpage>436</fpage><lpage>454</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://onlinelibrary.wiley.com/toc/20477481/24/4">https://onlinelibrary.wiley.com/toc/20477481/24/4</ext-link></comment><pub-id pub-id-type="doi">10.1002/smr.560</pub-id></nlm-citation></ref><ref id="ref49"><label>49</label><nlm-citation citation-type="report"><person-group person-group-type="author"><name name-style="western"><surname>Wolf-Ostermann</surname><given-names>K</given-names> </name><name name-style="western"><surname>F&#x00FC;rstenau</surname><given-names>D</given-names> </name><name name-style="western"><surname>Theune</surname><given-names>S</given-names> </name><etal/></person-group><article-title>Concept for embedding AI systems in nursing care: exploratory project on AI in nursing care (sokip)</article-title><access-date>2026-05-08</access-date><publisher-name>University of Bremen</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://media.suub.uni-bremen.de/entities/publication/7f4e91a6-6598-4b1c-bec7-fcbf513dd8eb">https://media.suub.uni-bremen.de/entities/publication/7f4e91a6-6598-4b1c-bec7-fcbf513dd8eb</ext-link></comment></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>Nystr&#x00F6;m</surname><given-names>ME</given-names> </name><name name-style="western"><surname>Karltun</surname><given-names>J</given-names> </name><name name-style="western"><surname>Keller</surname><given-names>C</given-names> </name><name name-style="western"><surname>Andersson G&#x00E4;re</surname><given-names>B</given-names> </name></person-group><article-title>Collaborative and partnership research for improvement of health and social services: researcher&#x2019;s experiences from 20 projects</article-title><source>Health Res Policy Syst</source><year>2018</year><month>05</month><day>30</day><volume>16</volume><issue>1</issue><fpage>46</fpage><pub-id pub-id-type="doi">10.1186/s12961-018-0322-0</pub-id><pub-id pub-id-type="medline">29843735</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>Greenhalgh</surname><given-names>T</given-names> </name><name name-style="western"><surname>Abimbola</surname><given-names>S</given-names> </name></person-group><article-title>The NASSS framework - a synthesis of multiple theories of technology implementation</article-title><source>Stud Health Technol Inform</source><year>2019</year><month>07</month><day>30</day><volume>263</volume><fpage>193</fpage><lpage>204</lpage><pub-id pub-id-type="doi">10.3233/SHTI190123</pub-id><pub-id pub-id-type="medline">31411163</pub-id></nlm-citation></ref></ref-list><app-group><supplementary-material id="app1"><label>Multimedia Appendix 1</label><p>Additional methods information and results.</p><media xlink:href="nursing_v9i1e84148_app1.pdf" xlink:title="PDF File, 968 KB"/></supplementary-material><supplementary-material id="app2"><label>Multimedia Appendix 2</label><p>Artificial intelligence nursing care readiness assessment full version.</p><media xlink:href="nursing_v9i1e84148_app2.pdf" xlink:title="PDF File, 1459 KB"/></supplementary-material><supplementary-material id="app3"><label>Multimedia Appendix 3</label><p>Artificial intelligence nursing care readiness assessment user manual.</p><media xlink:href="nursing_v9i1e84148_app3.pdf" xlink:title="PDF File, 6038 KB"/></supplementary-material><supplementary-material id="app4"><label>Checklist 1</label><p>PRISMA 2020 checklist.</p><media xlink:href="nursing_v9i1e84148_app4.pdf" xlink:title="PDF File, 68 KB"/></supplementary-material><supplementary-material id="app5"><label>Checklist 2</label><p>COREQ checklist.</p><media xlink:href="nursing_v9i1e84148_app5.pdf" xlink:title="PDF File, 297 KB"/></supplementary-material></app-group></back></article>