<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.0 20040830//EN" "http://dtd.nlm.nih.gov/publishing/2.0/journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.0" xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher-id">JMI</journal-id>
      <journal-id journal-id-type="nlm-ta">JMIR Med Inform</journal-id>
      <journal-title>JMIR Medical Informatics</journal-title>
      <issn pub-type="epub">2291-9694</issn>
      <publisher>
        <publisher-name>JMIR Publications</publisher-name>
        <publisher-loc>Toronto, Canada</publisher-loc>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">v14i1e94376</article-id>
      <article-id pub-id-type="pmid"/>
      <article-id pub-id-type="doi">10.2196/94376</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original Paper</subject>
        </subj-group>
        <subj-group subj-group-type="article-type">
          <subject>Original Paper</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Adoption Strategies and Workarounds in the Evolution of Information Infrastructures Integrating Health and Social Care Providers in Scotland: Multimethod Qualitative Case Study of the Key Information Summary</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="editor">
          <name>
            <surname>Steenstra</surname>
            <given-names>Ivan</given-names>
          </name>
        </contrib>
        <contrib contrib-type="editor">
          <name>
            <surname>Benis</surname>
            <given-names>Arriel</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Cather</surname>
            <given-names>Corrine</given-names>
          </name>
        </contrib>
        <contrib contrib-type="reviewer">
          <name>
            <surname>Nabiolahi</surname>
            <given-names>Abdolahd</given-names>
          </name>
        </contrib>
      </contrib-group>
      <contrib-group>
        <contrib id="contrib1" contrib-type="author" corresp="yes">
          <name name-style="western">
            <surname>Sai</surname>
            <given-names>Varun</given-names>
          </name>
          <degrees>BTECH, MA, MSc</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <address>
            <institution/>
            <institution>Usher Institute</institution>
            <institution>University of Edinburgh</institution>
            <addr-line>5 Little France Road</addr-line>
            <addr-line>Edinburgh EH16 4UX</addr-line>
            <addr-line>Edinburgh, Scotland, EH16 4UX</addr-line>
            <country>United Kingdom</country>
            <phone>44 0131 651 7869</phone>
            <email>v.sai@sms.ed.ac.uk</email>
          </address>
          <ext-link ext-link-type="orcid">https://orcid.org/0009-0003-8708-1260</ext-link>
        </contrib>
        <contrib id="contrib2" contrib-type="author">
          <name name-style="western">
            <surname>Williams</surname>
            <given-names>Robin</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff2" ref-type="aff">2</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0002-9044-4611</ext-link>
        </contrib>
        <contrib id="contrib3" contrib-type="author">
          <name name-style="western">
            <surname>Cresswell</surname>
            <given-names>Kathrin</given-names>
          </name>
          <degrees>PhD</degrees>
          <xref rid="aff1" ref-type="aff">1</xref>
          <ext-link ext-link-type="orcid">https://orcid.org/0000-0001-6634-9537</ext-link>
        </contrib>
      </contrib-group>
      <aff id="aff1">
        <label>1</label>
        <institution>Usher Institute</institution>
        <institution>University of Edinburgh</institution>
        <addr-line>Edinburgh, Scotland</addr-line>
        <country>United Kingdom</country>
      </aff>
      <aff id="aff2">
        <label>2</label>
        <institution>Institute for the Study of Science, Technology and Innovation</institution>
        <institution>University of Edinburgh</institution>
        <addr-line>Edinburgh, Scotland</addr-line>
        <country>United Kingdom</country>
      </aff>
      <author-notes>
        <corresp>Corresponding Author: Varun Sai <email>v.sai@sms.ed.ac.uk</email></corresp>
      </author-notes>
      <pub-date pub-type="collection">
        <year>2026</year>
      </pub-date>
      <pub-date pub-type="epub">
        <day>20</day>
        <month>10</month>
        <year>2026</year>
      </pub-date>
      <volume>14</volume>
      <elocation-id>e94376</elocation-id>
      <history>
        <date date-type="received">
          <day>28</day>
          <month>2</month>
          <year>2026</year>
        </date>
        <date date-type="rev-request">
          <day>14</day>
          <month>6</month>
          <year>2026</year>
        </date>
        <date date-type="rev-recd">
          <day>14</day>
          <month>9</month>
          <year>2026</year>
        </date>
        <date date-type="accepted">
          <day>16</day>
          <month>9</month>
          <year>2026</year>
        </date>
      </history>
      <copyright-statement>©Varun Sai, Robin Williams, Kathrin Cresswell. Originally published in JMIR Medical Informatics (https://medinform.jmir.org), 20.10.2026.</copyright-statement>
      <copyright-year>2026</copyright-year>
      <license license-type="open-access" xlink:href="https://creativecommons.org/licenses/by/4.0/">
        <p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (https://creativecommons.org/licenses/by/4.0/), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work, first published in JMIR Medical Informatics, is properly cited. The complete bibliographic information, a link to the original publication on https://medinform.jmir.org/, as well as this copyright and license information must be included.</p>
      </license>
      <self-uri xlink:href="https://medinform.jmir.org/2026/1/e94376" xlink:type="simple"/>
      <abstract>
        <sec sec-type="background">
          <title>Background</title>
          <p>Summary care records are digital technologies designed to support information sharing and care coordination across fragmented health and social care systems. However, adoption and use of these technologies can vary across diverse health and care settings, with users using workarounds and other strategies to meet their specific information needs. In Scotland, the Key Information Summary (KIS) has been in use for over 13 years, sharing key patient information from general practitioners (GPs) with other health and care providers for future care planning.</p>
        </sec>
        <sec sec-type="objective">
          <title>Objective</title>
          <p>Using the KIS as a case study, this study examines how various adoption strategies and workarounds have shaped the evolution of regional information infrastructures integrating health and social care in Scotland over time.</p>
        </sec>
        <sec sec-type="methods">
          <title>Methods</title>
          <p>This multimethod qualitative study examined the various contextual factors influencing adoption and use of the KIS across diverse health and care settings. Data collection included interviews with KIS users from health and care settings, implementers, and vendors; documentary analysis of user guides, websites, reports, and policies; and observation of multidisciplinary team meetings and technology use. Data analysis involved a hybrid approach. The technology-people-organization-macroenvironment framework was applied to code interview, documentary, and observational data, followed by an inductive analysis informed by science and technology studies theories of information infrastructures, domestication, and workarounds to examine strategies and workarounds for adapting the KIS to local contexts and evolving needs.</p>
        </sec>
        <sec sec-type="results">
          <title>Results</title>
          <p>Data comprised 54 qualitative interviews, 59 documents, 2 websites, and 20 hours of observational field notes collected between April 2024 and March 2025. Findings indicate that adoption of the KIS varied across settings and over time due to misalignment between system design, evolving expectations of integrated care, and national initiatives during the COVID-19 pandemic that repurposed its use. Professional roles and associated information needs shaped differing expectations of what constituted useful information, generating tensions between users who relied on the KIS and GPs responsible for maintaining it. Formal workarounds enabled the extension of the health care–centric infrastructure into nonclinical settings to facilitate information sharing with GPs and, in some cases, supported clinician access to the KIS during system outages. Across settings, informal user-driven repair practices enabled diverse professionals to adopt and realign the KIS with its intended use.</p>
        </sec>
        <sec sec-type="conclusions">
          <title>Conclusions</title>
          <p>This study demonstrates how regional information infrastructures integrating health and care evolve incrementally as they become embedded within local routines, practices, and existing systems. Adoption was shaped by professional roles, information needs, and users’ capabilities, with formal workarounds extending infrastructures into new settings and informal, user-driven repair practices supporting ongoing use and maintenance. Policymakers and vendors must recognize that workarounds and user-driven repair practices are central to infrastructural growth and sustainability, and understanding these strategies can inform future technology development and innovation.</p>
        </sec>
      </abstract>
      <kwd-group>
        <kwd>health information exchange</kwd>
        <kwd>information systems</kwd>
        <kwd>intersectoral collaboration</kwd>
        <kwd>delivery of health care</kwd>
        <kwd>integrated</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec sec-type="introduction">
      <title>Introduction</title>
      <p>Summary care records are digital technologies designed to facilitate information exchange across organizations, supporting collaboration and cooperative working between care settings and thereby contributing to the integration of fragmented health and care services [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref2">2</xref>]. These records entail information that diverse health and care professionals can draw upon to inform action within their respective organizational and professional contexts [<xref ref-type="bibr" rid="ref1">1</xref>].</p>
      <p>Information infrastructures are sociotechnical arrangements that support information exchange and collaborative work across organizations over extended periods [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. They consist of interconnected information systems, standards, organizational arrangements, and work practices that become embedded within an installed base of existing technologies and routines [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. As new digital technologies, like summary care records, are introduced, they must integrate with this installed base [<xref ref-type="bibr" rid="ref3">3</xref>]. Consequently, in complex health and social care settings, summary care records are enacted differently across organizations to accommodate local workflows, professional roles, and information needs, often creating tensions around collaboration, standards, and information use [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>]. In different settings, digital technologies are embedded within an installed base of work practices and information sharing mechanisms, making information infrastructures “systems of systems” composed of entrenched workflows, information systems, organizational arrangements, and diverse user information needs [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>]. In complex and variable health and social care processes, summary care records are enacted differently across settings to accommodate local workflows, systems, and professional needs, which can create tensions among stakeholders with differing expectations of collaboration, standards, and information use [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>Adoption of such digital solutions can vary across different health and care settings; in some instances, often to address usability issues and the difficulty of designing information systems that support diverse roles and activities, users use workarounds, develop shortcuts to save time, or bypass tasks [<xref ref-type="bibr" rid="ref8">8</xref>-<xref ref-type="bibr" rid="ref11">11</xref>]. According to Alter [<xref ref-type="bibr" rid="ref10">10</xref>], a workaround occurs when someone modifies the usual way a system is intended to be used to overcome problems, obstacles, or inefficiencies that prevent them from achieving their goals; it is primarily shaped by the system’s design, though organizational norms may also influence its use. Workarounds are practical, goal-oriented solutions that may bypass rules, standard procedures, or limitations to get work done more effectively or efficiently [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref12">12</xref>]. Cresswell et al [<xref ref-type="bibr" rid="ref11">11</xref>] highlight that formal workarounds are organizationally sanctioned methods for addressing known system shortcomings, such as usability issues, whereas informal workarounds are user-initiated adaptations aimed at achieving goals with the available systems and information, for example, to complete tasks, reduce time pressures, or compensate for system defects. While these theoretical concepts acknowledge that users use workarounds in response to infrastructural breakdown [<xref ref-type="bibr" rid="ref10">10</xref>], the relationship between infrastructural evolution and the emergence of workarounds remains largely unexamined.</p>
      <p>Many countries around the world are pursuing a variety of strategies aimed at integrating health and care providers using digital technologies. Scotland has followed a coherent and long-term path, particularly through the establishment of Integrated Joint Boards (IJBs) to facilitate integrated and collaborative working following the Public Bodies (Joint Working) (Scotland) Act 2014 [<xref ref-type="bibr" rid="ref13">13</xref>,<xref ref-type="bibr" rid="ref14">14</xref>]. The Key Information Summary (KIS) in Scotland is a summary care record, used to share key patient information from general practice (GP) records with other health and care providers involved in an individual’s care [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref15">15</xref>].</p>
      <p>Scotland has a nationally shared electronic health record (EHR), the Emergency Care Summary (ECS), which was introduced to make core information from GP records available across the National Health Service (NHS) [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. The ECS contains demographic information, medications prescribed by the GP, allergies, and adverse reactions, and is accessible to authorized health care professionals involved in a patient’s care. Introduced in 2012, the KIS was developed as an extension of the ECS to support the recording and sharing of future care planning information across health care settings. In addition to the information available through the ECS, the KIS includes emergency contact and next-of-kin details, documented care preferences, baseline clinical and functional status, active care and escalation plans, resuscitation decisions, medication history, and a special notes section containing anticipatory and future care information.</p>
      <p>The KIS was designed to facilitate communication between GPs and a broad range of professionals involved in community and unscheduled care, including hospital clinicians, out-of-hours (OOH) services, the Scottish Ambulance Service (SAS), community nurses, social workers, care home staff, and other professionals involved in coordinating care. GPs acted as custodians of the KIS and were the only users with administrative rights to create and update records through GP clinical systems. Information contained within the KIS was transferred electronically twice daily from GP systems to a central NHS data center [<xref ref-type="bibr" rid="ref7">7</xref>]. Hospital clinicians, OOH services, and the SAS could access the KIS in a read-only format through their respective clinical information systems [<xref ref-type="bibr" rid="ref15">15</xref>]. In contrast, social workers and social care providers, including care home staff, were not initially provided with digital access to the KIS during its early implementation and instead relied on indirect communication with health care professionals [<xref ref-type="bibr" rid="ref7">7</xref>].</p>
      <p>As an extension of the ECS, the KIS became an integral part of Scotland’s wider information infrastructure, supporting information sharing across health and social care providers [<xref ref-type="bibr" rid="ref7">7</xref>]. Used across multiple settings and care pathways for future care planning, the KIS functions as a shared artifact that supports coordination across organizational and professional boundaries. Initially, GPs used the REDMAP (Ready, Expect, Diagnosis, Matters, Actions, and Plans) approach, together with clinical judgment, to identify patients who would benefit from a KIS, primarily those with long-term conditions and complex care needs requiring anticipatory or future care planning [<xref ref-type="bibr" rid="ref15">15</xref>,<xref ref-type="bibr" rid="ref16">16</xref>]. Over time, the use of the KIS expanded to additional care pathways, including dementia, frailty, end-of-life, and reablement, reflecting changing clinical priorities and service needs [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref15">15</xref>]. During the COVID-19 pandemic, the Scottish government further repurposed the KIS to identify and share information on individuals considered clinically vulnerable to COVID-19. This was facilitated by using the KIS, particularly the special notes section, which enabled clinicians to rapidly record and communicate relevant information across health and care settings. We have previously examined the evolution of information infrastructures for integrating health and social care providers, using the KIS as a case study to demonstrate how successive waves of infrastructural development enabled the interlinking of previously fragmented health and care systems [<xref ref-type="bibr" rid="ref7">7</xref>]. This work showed how integration was achieved through extending existing health care–centric infrastructures into social care settings, often requiring formal workarounds in the absence of shared data standards. While previous studies have examined how infrastructures evolve through policy initiatives, technical integration, and organizational arrangements, less attention has been given to how these infrastructures are enacted after implementation, when users encounter the technology within diverse professional practices and local contexts. In particular, limited attention has been given to how users interpret and negotiate the purpose and value of shared information artifacts within situated practices of use and how workarounds and repair practices contribute to the continued evolution of digital infrastructures.</p>
      <p>This paper draws on a broader longitudinal study examining the long-term evolution of information infrastructures supporting health and social care integration in Scotland. By examining the KIS as a shared information artifact within a broader information infrastructure, this study provides insights into how digital technologies integrating health and care providers are domesticated, maintained, and transformed through ongoing interactions between technologies, users, organizational arrangements, and wider health and care contexts. Specifically, it examines how processes of domestication, workaround, and repair contribute to the ongoing maintenance and transformation of infrastructures through interactions between technologies, users, organizational arrangements, and wider health and care contexts.</p>
    </sec>
    <sec sec-type="methods">
      <title>Methods</title>
      <sec>
        <title>Study Setting</title>
        <p>The adoption and use of the KIS vary across regions in Scotland. Lothian, a region of Scotland, serves as an exemplar of how the KIS can be used for future care planning, linking multiple health and care providers through distinct locally developed mechanisms. In Lothian, the KIS is used across multiple care pathways to share key information concerning an individual’s care needs, resuscitation status, and medication history. While most of the information in the KIS is automatically updated from the electronic records held in GP practices, the special notes section in the KIS requires periodic review and manual entry of care needs and plans by the GP. In Lothian, health and social care partnerships, specifically the Edinburgh Health and Social Care Partnership (EHSCP), use customized templates that enable community workers, social workers, and care home carers to share updates with GP practices. GP practices also share the KIS as a PDF file with social workers involved in care pathways and provide paper-based versions to carers and residents in care homes. The KIS thus functions as an artifact shared across multiple health and care providers, with different actors using it in distinct ways to address their respective information needs. Its use in Lothian offered a valuable case for examining digitally mediated collaborative work and integration efforts, in which actors from diverse professional backgrounds adopted and domesticated a standardized digital technology embedded within the information infrastructure to meet varied informational needs and support the delivery of integrated care.</p>
      </sec>
      <sec>
        <title>Study Design</title>
        <p>Using the biography of artifacts and practices (BoAP) [<xref ref-type="bibr" rid="ref17">17</xref>], and the technology-people-organization-macroenvironment technology people organization and macroenvironment (TPOM) framework [<xref ref-type="bibr" rid="ref18">18</xref>], this multisited ethnographic study aimed to explore the adoption and contextual use of the KIS in different health and care settings. Multisited ethnography as a methodological approach allows the researcher to explore the diverse settings of technology development, adoption, and use [<xref ref-type="bibr" rid="ref19">19</xref>]. BoAP, as a methodological tool, enabled navigation across different times and spaces, exemplified phases of technology adoption and use, and supported reflection on the choice of setting, time, and focus of enquiry [<xref ref-type="bibr" rid="ref16">16</xref>,<xref ref-type="bibr" rid="ref18">18</xref>]. TPOM is an evaluation framework designed to capture technological (eg, usability and performance), socio-organizational (eg, leadership and management practices over time and organizational routines), sociotechnical (eg, user satisfaction, engagement, and work processes), and macroenvironmental factors (eg, political and economic contexts and vendor management) that shape the real-time implementation, adoption, and use of digital technologies [<xref ref-type="bibr" rid="ref18">18</xref>]. While BoAP helped examine various stages of technology adoption and use over time, providing a longitudinal view, TPOM supported contextual enquiry into how the KIS was adopted and used across different health and care settings.</p>
      </sec>
      <sec>
        <title>Ethical Considerations</title>
        <p>Ethics approval for this study was granted by the Edinburgh Medical School Research Ethics Committee (EMREC). Approval for interviews with participants in Scotland was obtained on April 17, 2024 (24-EMREC-012), and approval for observations of meetings, events, and training sessions involving technology use was granted on June 17, 2024 (24-EMREC-043). The study also received approval from the NHS Lothian Quality Improvement (QI) team. Informed consent was obtained from all participants prior to their participation in interviews and observations. Participants were informed of the purpose of the study, their right to withdraw, and how their data would be used. No prior relationship was established between the researchers and participants before recruitment. The researchers did not have a role in the implementation or operational delivery of the KIS. Participant data were deidentified and anonymized in the analysis and reporting, and identifying information was removed or omitted to protect participant confidentiality. Participants were not compensated for their participation.</p>
      </sec>
      <sec>
        <title>Sampling</title>
        <p>BoAP and TPOM guided the sampling strategy, enabling the identification of technology developers, users across various health and care settings, social workers from local councils, social care workers, policymakers, and academics. Recruiting participants informing various stages of technology development, adoption, and use, across various time frames and settings, enabled a longitudinal view of KIS’s adoption and factors affecting contextual use. Here, BoAP was used to identify participants with experience across different stages of KIS’s conception, adoption, and use in various time frames and settings, allowing the capture of a longitudinal view of its adoption. TPOM’s focus on technological, sociotechnical, socio-organizational, and macroenvironmental contexts guided the recruitment of diverse stakeholders. This enabled the inclusion of participants who could provide insights into factors shaping adoption and use at the macro-, meso-, and microlevels, including usability challenges, organizational and professional practices, and the influence of national policies [<xref ref-type="bibr" rid="ref18">18</xref>].</p>
        <p>Snowballing and purposive sampling methods were used to recruit participants for the study. Purposive sampling enabled the recruitment of participants capable of providing context-rich insights from multiple settings, based on their involvement in the development, implementation, adoption, and use of the KIS at different points in time. QI teams of NHS Lothian and Lothian Unscheduled Care Services acted as gatekeepers for the study, assisting in identifying participants from across different health and care settings. Recruitment proceeded iteratively through purposive and snowball sampling until sufficient depth and breadth of perspectives had been obtained and saturation was achieved. Gatekeepers supported purposive sampling by identifying relevant stakeholder groups, multidisciplinary team (MDT) meetings, and care settings where the KIS was used for future care planning. They facilitated access to observations of MDT meetings and training sessions involving KIS use across different health and care contexts. The sampling strategy aimed to capture variation in perspectives and experiences of KIS adoption across professional roles and organizational settings. MDTs constituted GPs, OOH staff, clinicians and specialists from hospitals, community nurses and workers, social workers from various care pathways, and care workers from social care homes.</p>
        <p>With respect to interviews, participants were sampled to represent a range of health and social care settings, including all 4 Lothian councils. Policymakers working in the domain of health and social care were purposively identified through national policy documents to understand how the policy landscape has evolved since the KIS was first developed and implemented. These documents were identified from the NHS and Scottish government websites via Google using the search term “Key Information Summary in Lothian and Scotland.” National and international technology vendors were also purposively included to examine the factors influencing technological development, implementation, and adoption, as well as to gather insights into user support provided over time. In addition, a snowball sampling approach was used, whereby participants were invited to suggest others involved in the development, implementation, adoption, or use of the KIS.</p>
      </sec>
      <sec>
        <title>Researcher Characteristics</title>
        <p>VS (male) is trained as an IT engineer, with research experience in medical informatics, health and social care information systems, and qualitative research. KC (female) and RW (male) have research experience evaluating large-scale digital transformation initiatives across the NHS, including the Global Digital Exemplar program, which supported digital transformation across acute hospital settings in England, and NHS AI Lab programs.</p>
      </sec>
      <sec>
        <title>Data Collection</title>
        <p>Data collection was undertaken by VS between April 2024 and March 2025 under the supervision of KC and RW, using multiple qualitative methods, including semistructured interviews, ethnographic observations of KIS use in practice, and documentary analysis of materials related to KIS implementation, training, and operational processes. These methods were integrated within a qualitative case study design to develop an in-depth understanding of the technological, sociotechnical, socio-organizational, and macroenvironmental factors shaping the adoption and use of the KIS within its real-world context.</p>
        <p>One-to-one, semistructured interviews were carried out with a range of stakeholders, including users, policy leads, data scientists, academics, technology developers, and health and social care providers, to explore their perspectives on the development, implementation, adoption, and use of the KIS. Interviews lasted between 40 and 60 minutes, were conducted online via Microsoft Teams, audio-recorded, and transcribed verbatim. For a small number of participants, follow-up interviews were conducted, where participants were willing to engage further, and additional discussion was needed during the analysis. These conversations were used to clarify points raised in the initial interviews and to explore emerging questions from the ongoing analysis.</p>
        <p>Topic guides for the interviews, informed by the TPOM framework [<xref ref-type="bibr" rid="ref18">18</xref>], explored how system usability and performance, leadership and governance practices, organizational routines, user engagement and everyday work practices, and wider political-economic and vendor-related conditions shaped the adoption and domestication of KIS across health and social care settings. Tailored topic guides were developed for users from different settings, vendors, academics, and policy leads to capture insights regarding their role in the conception, adoption, and use of the KIS (<xref ref-type="supplementary-material" rid="app1">Multimedia Appendix 1</xref>).</p>
        <p>Nonparticipant observations were undertaken to examine how MDTs and national planning groups engaged with the KIS to support future care planning. Observations included MDT meetings involving NHS Lothian and the EHSCP, as well as national planning group meetings, to explore interprofessional collaboration across health and care organizations at both regional and national levels. Use of the KIS by different users was also observed to understand how its adoption and use varied across settings. Observation sessions lasted between 1 and 2 hours. Meetings and patterns of technology use were observed online via Microsoft Teams. In addition, in-person training sessions delivered by the EHSCP in care homes were also observed. Field notes were systematically documented using a structured observation protocol (<xref ref-type="supplementary-material" rid="app2">Multimedia Appendix 2</xref>).</p>
        <p>Study participants were also asked to provide relevant documents regarding the implementation, adoption, and use of the KIS. Internal case studies, user guides for different professionals, contingency plans during technology breakdown, and software update notifications were shared by participants. Documents were purposively selected based on their relevance to understanding the evolution of the KIS as an information infrastructure. Selection focused on materials describing the development, implementation, and use of the KIS in Scotland and Lothian; health and social care integration initiatives; the intended functions and uses of the KIS; related health and social care information systems supporting KIS access; and implementation strategies and anticipated benefits at local and national levels (<xref ref-type="supplementary-material" rid="app3">Multimedia Appendix 3</xref>). Historical documents were treated as empirical artifacts that provided insights into how standards, practices, and infrastructural arrangements were developed, negotiated, and embedded over time. These documents were examined qualitatively to understand challenges surrounding the adoption and use of KIS in different settings over time and to explore the similarities and differences between national goals, technological claims, and regional narratives.</p>
      </sec>
      <sec>
        <title>Data Analysis</title>
        <p>NVivo (version 14; Lumivero) was used to code the interview transcripts, observation notes, and documentary materials. Data analysis was conducted by VS under the supervision of KC and RW. VS was the primary and sole data coder, while KC and RW provided ongoing oversight of the analytical process and contributed to discussions of coding, emerging themes, and interpretations. The analysis adopted an interpretive approach that recognized the researcher’s positionality and subjectivity. Credibility was strengthened through the search for disconfirming evidence and the use of data triangulation. Triangulation involved integrating insights from all qualitative data sources to situate the case study within the broader context of integrating health and social care through digitalization while also capturing the microlevel practices of individual users and the mesolevel organizational processes and interactions that shaped the adoption and use of the KIS.</p>
        <p>Data analysis followed a hybrid approach, that is, a combination of inductive and deductive approaches [<xref ref-type="bibr" rid="ref20">20</xref>]. Deductive thematic analysis, informed by the TPOM framework, was applied to interviews, documents, and observational notes to examine the challenges around technology usability, user and organizational practices, as well as the wider macroenvironmental factors influencing the adoption and use of the KIS across different settings [<xref ref-type="bibr" rid="ref18">18</xref>]. Related codes that emerged were clustered into themes and compared across sites, professional roles, and time periods to identify relevant subthemes following an inductive analysis. Concepts and theories from science and technology studies, including information infrastructures [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref6">6</xref>,<xref ref-type="bibr" rid="ref21">21</xref>-<xref ref-type="bibr" rid="ref23">23</xref>] and domestication [<xref ref-type="bibr" rid="ref24">24</xref>,<xref ref-type="bibr" rid="ref25">25</xref>], alongside theories and concepts on workarounds [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>], were used to further interpret how the KIS was adopted across different settings over time as the regional information infrastructure evolved. These approaches enabled a systematic analysis of KIS’s adoption and use over time, the tensions emerging during its adoption across diverse settings, and the various adoption strategies and workarounds enacted by users and organizations to mitigate constraints imposed by the system. The coding process involved organizing codes into second-order and aggregate themes, with the resulting coding structure provided in <xref ref-type="supplementary-material" rid="app4">Multimedia Appendix 4</xref>.</p>
      </sec>
      <sec>
        <title>Reporting Guidelines</title>
        <p>This study was reported in accordance with the COREQ (Consolidated Criteria for Reporting Qualitative Research) guidelines [<xref ref-type="bibr" rid="ref26">26</xref>]. The completed COREQ checklist is provided in <xref ref-type="supplementary-material" rid="app5">Multimedia Appendix 5</xref>.</p>
      </sec>
    </sec>
    <sec sec-type="results">
      <title>Results</title>
      <sec>
        <title>Overview</title>
        <p>Data consisted of 54 interviews; notes from observing technology use, MDT meetings, and national-level meetings regarding the use of KIS for future care planning (20 hours); and documentary analysis of 59 documents and 2 archived websites (<xref ref-type="table" rid="table1">Table 1</xref>).</p>
        <table-wrap position="float" id="table1">
          <label>Table 1</label>
          <caption>
            <p>Dataset.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="30"/>
            <col width="30"/>
            <col width="830"/>
            <col width="0"/>
            <col width="110"/>
            <thead>
              <tr valign="top">
                <td colspan="4">Method, dataset, and description</td>
                <td>Values, n</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td colspan="5">
                  <bold>Interviews</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="4">
                  <bold>54 interviews (lasting 40-60 minutes each)</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>GPs<sup>a</sup> from daytime practices</td>
                <td colspan="2">14</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Social workers and social care workers</td>
                <td colspan="2">13</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Out-of-hours service</td>
                <td colspan="2">5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Data analysts from Public Health Scotland</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Clinical informatics and population health experts</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Technology vendors and software developers</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Academics and implementation scientists</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Government representatives for digital health and social care</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>GP administrative staff</td>
                <td colspan="2">2</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Observations</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="4">
                  <bold>12 meetings (1-2 hours each) lasting 20 hours in total</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Observing national-level collaborative meetings to use digital technologies for future care planning from May 2024 to December 2024</td>
                <td colspan="2">8 hours</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Observing events hosted by social care organizations</td>
                <td colspan="2">8 hours</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Observing technology use by clinicians</td>
                <td colspan="2">4 hours</td>
              </tr>
              <tr valign="top">
                <td colspan="5">
                  <bold>Documents</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td colspan="4">
                  <bold>59 documents and 2 websites</bold>
                </td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Meeting notes from care home meeting with GP practices for service improvement of future care planning</td>
                <td colspan="2">12</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>The KIS<sup>b</sup> user guide for GPs, nurses, social workers, and social care workers</td>
                <td colspan="2">11</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Information leaflets issued by various departments promoting the KIS</td>
                <td colspan="2">8</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>User guides and contingency plan for information systems used in different health and care settings</td>
                <td colspan="2">8</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>National and regional information sharing guidelines, regulations, and policies</td>
                <td colspan="2">5</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Economic impact measurement plans and assessments</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Documents pertaining to 7 steps to ACP<sup>c</sup> for care home staff</td>
                <td colspan="2">4</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Digital health and care strategies in Scotland</td>
                <td colspan="2">3</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Internal case studies were around the introduction of the KIS in care homes in the northeast of Edinburgh</td>
                <td colspan="2">2</td>
              </tr>
              <tr valign="top">
                <td>
                  <break/>
                </td>
                <td>
                  <break/>
                </td>
                <td>Internal case studies about the use of the KIS by Alzheimer Scotland Post Diagnostic Dementia Service in Edinburgh and by Reablement and End of Life Care in the northwest of Edinburgh</td>
                <td colspan="2">2</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table1fn1">
              <p><sup>a</sup>GP: general practitioner.</p>
            </fn>
            <fn id="table1fn2">
              <p><sup>b</sup>KIS: Key Information Summary.</p>
            </fn>
            <fn id="table1fn3">
              <p><sup>c</sup>ACP: anticipatory care planning.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>The KIS was designed to enable the sharing of key patient information from GP with other service providers to support continuity of care and provide an overview of patients’ health status and care plans. However, expectations regarding the content and level of detail required varied across professional groups and care settings, and the functionality and design of KIS did not accommodate the full range of tasks it was expected to support. Consequently, tensions emerged between different user groups (such as OOH and hospital staff) and those responsible for maintaining and governing the information recorded in the KIS (GPs). These tensions were exemplified following top-down policy initiatives by the government that repurposed the KIS to identify vulnerable patient groups during the COVID-19 pandemic. As a result, many KISs were created without substantive information on future care plans and were instead flagged as having been generated as part of COVID-19 protocols. In turn, formal workarounds were used by health boards to provide social workers and carers access to the KIS and to ensure that relevant and updated information regarding future care is shared with the GP practices. Informal user-driven repair strategies were used in different health and care settings to update the KIS with relevant information and realign the KIS with its intended use. Here, repair work was conceptualized as the ongoing, often invisible labor through which users maintain, adapt, and render technologies usable in practice. <xref rid="figure1" ref-type="fig">Figure 1</xref> provides an overview of identified themes.</p>
        <p>The analysis identified several interconnected challenges that influenced the adoption, use, and ongoing maintenance of the KIS across health and social care settings. These challenges related to information quality, interoperability, professional responsibilities, and organizational capacity. Rather than representing discrete implementation failures, these challenges reflected tensions that emerged as the KIS evolved from a health care–focused summary record into an information artifact supporting wider health and social care integration. Users and organizations responded to these challenges through formal workarounds and informal repair practices that sought to maintain information quality, extend access, and align the KIS with changing care needs.</p>
        <fig id="figure1" position="float">
          <label>Figure 1</label>
          <caption>
            <p>Themes emerging from the analysis. GP: general practitioner; KIS: Key Information Summary.</p>
          </caption>
          <graphic xlink:href="medinform_v14i1e94376_fig1.png" alt-version="no" mimetype="image" position="float" xlink:type="simple"/>
        </fig>
      </sec>
      <sec>
        <title>Intended Use of the KIS and the Information Required for Continuity of Care</title>
        <p>GPs were regarded as the main point of care for residents in Scotland, and the KIS was developed to share key information regarding a person’s future care plan to other primary, secondary, and community care providers. GPs identified individuals who would benefit from a KIS within their practice and documented their care plans and preferences. Consequently, the KIS enabled GPs to share information concerning a person’s medication, resuscitation status, and care plans with other health and care providers, who may not have had regular or long-term contact with the individual. Clinicians in OOH settings, who served a broader patient population than GPs and provided care outside regular GP hours, reported that the KIS gave them access to information they would not otherwise have, allowing them to understand the GP’s assessment of a patient’s condition and to make informed clinical decisions:</p>
        <disp-quote>
          <p>In an out-of-hours environment, you don’t know the patient; all I’m seeing is their KIS, and only if the GP has uploaded one. If you work in Edinburgh out of hours, you’re covering most of the city of Edinburgh. The information that the KIS summary can provide is really valuable because it helps to just get a sense of what the GPs are doing, what they’re worried about regarding a person, and what their care needs are. Those things are sort of there to help you make those decisions when it’s an emergency, night-time or evening.</p>
          <attrib>Clinician, OOH (1), Lothian</attrib>
        </disp-quote>
        <p>The KIS was developed to support GPs in engaging with individuals about their future care with primary, secondary, and community care providers. However, as the KIS was adopted across different care settings, expectations regarding the type, completeness, and level of detail required varied between professional groups. While GPs viewed the KIS primarily as a mechanism for documenting future care preferences, clinicians in other settings increasingly relied on it as a broader source of information to support decision-making. Conversations regarding future care between the GP and the individual were regarded as an ongoing, dynamic, and iterative process aimed at capturing an individual’s care preferences, as their conditions and care needs changed. GPs, acting as custodians of KIS data, were responsible for updating patients’ care preferences and future care needs, making the KIS a dynamic record, whose completeness and accuracy varied according to the extent to which individual GPs maintained it. However, this model of data stewardship also created a key challenge, as maintaining the accuracy and completeness of KIS information depended heavily on the capacity, time, and willingness of individual GP practices.</p>
        <disp-quote>
          <p>The KIS is a living document. To me, once a KIS is in place, it should be a dialogue to know when you’ve got a new condition or if something new happens. Lives are fluid, and there will be new bits of information, and it should be an ongoing document.</p>
          <attrib>Clinician, GP (3), Lothian</attrib>
        </disp-quote>
        <p>However, some GPs noted that they did not always maintain such long-term engagement with patients whose health and care needs had become complex, requiring them to gather relevant information from other sources to update the KIS. This variability represented an important challenge, as the usefulness of the KIS depended on sustained processes of information maintenance that were influenced by individual practice capacity, workload, and access to information from other care providers. In some cases, individuals required long-term care that could not be delivered in community settings and instead depended on ongoing support from hospitals, nursing homes, or care homes. To ensure the KIS reflected up-to-date information, GPs had to draw on multiple information sources, including updates provided by other health care professionals, social workers, and carers. For instance, discharge letters were provided by hospital-based clinicians to GPs after an individual’s discharge following hospital admission, which the GPs had to review to update the KIS. However, not all GPs adopted a systematic approach to reviewing documentation on patients’ future care needs, and maintaining these records required ongoing effort. Access to up-to-date information was particularly valuable for clinicians in hospital and OOH settings.</p>
        <disp-quote>
          <p>So we’ve got 150 to 200 housebound patients in my practice, quite high. So, we did a project around making sure all housebound patients had a KIS, and you see that sometimes you haven’t seen the patient all year, or they’ve just been seen in secondary care. But no one has thought about updating it from the secondary care letters.</p>
          <attrib>Clinician, GP (6), Lothian</attrib>
        </disp-quote>
      </sec>
      <sec>
        <title>Tensions Between Controllers and Users of Information</title>
        <sec>
          <title>Overview</title>
          <p>The variations in how GPs and GP practices updated the KIS differences reflected the evolving organization of general practice over time, resulting in uneven distributions of resources and capacity across practices. While GPs bore primary responsibility for ensuring that KIS information remained up-to-date and clinically relevant, other users largely benefited from the availability of this information, thereby generating tensions between different user groups. The demand for up-to-date information was further intensified by national initiatives that repurposed the KIS to identify vulnerable patient groups. The following sections examine these issues in detail.</p>
        </sec>
        <sec>
          <title>Shifts in GP Service Provision and Data Control</title>
          <p>The organization of GP services in Lothian was such that not all GP practices had the responsibility of providing medical services to care homes, nor were they equally resourced or willing to update the KIS. In some cases, GPs expressed the need to have control over the data collected and shared using the KIS and had the resources to ensure this. Whereas in other practices, they had no spare capacity to review and periodically update the KIS, leading to variability in the way the notes were recorded and updated.</p>
          <disp-quote>
            <p>All the onus is on the GP practice to add the information into the KIS, so it’s very much dependent on the capacity and availability of staff who are allocated that role to update the KIS. It’s different across each GP practice. You’ll have a GP practice that will very much want to keep control and be responsible for updating the KIS. Not all GP practices cover care homes; if they do, then they’ll go out, do the visit, and quite often they’ll keep that to themselves. They don’t want to share it out, not quite gatekeeping, but there is that element of them wanting to kind of have some oversight of that responsibility and the cheques.</p>
            <attrib>Social work, EHSCP, Lothian</attrib>
          </disp-quote>
          <disp-quote>
            <p>It depends on how pressurized the practices are and the amount of capacity they have. I think if a practice has no spare capacity, then people don’t dedicate the necessary time to update the KIS. Whereas another practice or another GP who has got a bit of capacity will actually spend time updating the information to make sure it’s current, so there’s a huge variability, which has been one of the frustrations.</p>
            <attrib>Clinician, Hospital (1), Lothian</attrib>
          </disp-quote>
          <p>The introduction of the General Medical Services (GMS) contract in 2018 led to the establishment of MDTs intended to reduce pressures on GP practices and to provide integrated care. The GMS contract of 2018 also placed GPs as controllers of patient data for integrated care services. Since the earlier GMS contract of 2004, GP practices have not operated as NHS-managed services but as independent businesses contracted to deliver services on behalf of the health board. Before this restructuring, many practices were directly funded and managed by health boards; under the GMS contract of 2004, GPs functioned as independent contractors, and a pay-for-performance scheme was introduced. As a part of the GMS contract of 2018, practices that are geographically close formed clusters to work together with regional health and social care partnerships to provide integrated care. Although the 2018 contract sought to alleviate workload by positioning GPs as clinical experts supported by wider MDTs, documentary evidence and participant accounts indicated that, in practice, these changes often increased rather than reduced the workload placed on GP practices. Some of the GP practices were struggling to recruit new GPs, whereas some had the resources to recruit more staff and run integrated care services through MDTs. However, a few GPs noted that insufficient systemic and organizational support for running GP practices adversely affected their capacity to maintain high-quality and up-to-date data in the KIS. Together, these findings demonstrate how organizational capacity, workforce constraints, and variation between GP practices affected the consistent embedding and maintenance of KIS-related activities across settings. These challenges were not simply related to user willingness to adopt the KIS but reflected broader organizational conditions that shaped the capacity of practices to sustain information-sharing activities over time. While there was increased recognition of the need to provide up-to-date information for population health management and preventative care among GPs, they also questioned the misalignment of national-level priorities regarding care provisioning and delivery.</p>
        </sec>
        <sec>
          <title>Impact of Top-Down Policies on Information Quality</title>
          <p>The need for reliable and up-to-date patient information became increasingly critical after the KIS was repurposed during the COVID-19 pandemic to identify vulnerable groups of patients by the government. This was achieved by using the special notes section in the KIS to indicate that the record had been created in response to the pandemic. However, this “top-down” approach diverged from the KIS’s primary purpose as a tool to record and share an individual’s care preferences and needs. This affected the usefulness of the information available to professionals using the KIS for clinical decision-making, particularly in settings where clinicians relied on shared information to understand an individual’s current health status and care requirements. Thus, a key challenge emerged when national policy priorities expanded the expected function of the KIS without corresponding changes to the information structure, workflows, or responsibilities associated with maintaining the record. One clinician in the OOH service highlighted how the repurposing of the KIS during the pandemic affected the information available through the system:</p>
          <disp-quote>
            <p>There was a mandate during the pandemic that every patient should have a KIS summary. But the pragmatic reality was that much of what was included was focused on COVID status. It often did not capture other medical problems they might have, such as diabetes, involvement with mental health services, or multiple medications. So, it was quite patchy in terms of what up-to-date information was actually coming through to the clinician looking at the case through the ECS.</p>
            <attrib>Clinician, OOH (1), Lothian</attrib>
          </disp-quote>
          <p>The consequences of this policy-driven repurposing were therefore not limited to information quality but also generated additional maintenance work for users attempting to restore the original purpose of the KIS. Consequently, GPs were required to undertake additional work to identify individuals who would benefit from a KIS containing up-to-date information relating to future care planning and to restore the intended purpose of the record. This illustrates how repurposing an existing information infrastructure for new policy objectives can unintentionally reshape information practices, alter the content generated within the infrastructure, and create additional maintenance work for users responsible for sustaining its intended function.</p>
          <p>While users in OOH services and the ambulance service benefited from having up-to-date information in the KIS, maintaining this accuracy required GP practices to collate information from multiple sources and manually enter updates. Clinicians in OOH settings shared that recent and relevant information in KIS aided in decision-making and provided an improved understanding of the individual’s condition and care plans in place. Accordingly, clinicians from OOH services and hospitals emphasized the importance of involving social workers and social care workers from MDTs (such as the Care at Home, End of Life care, Post-Diagnostic Dementia Service, and Reablement teams) in updating the KIS, both to reduce the burden on GP practices and to support a more integrated approach to care.</p>
          <disp-quote>
            <p>I think sometimes the frustration is that updating the KIS feels like it is a GP’s job and it’s quite time-consuming. You have to click a lot of buttons, copy the information, and make sure it is shared. Sometimes, GPs can feel like we’re doing all this work to help other services more than to help ourselves. I don’t think that is true because it helps with continuity, and if different doctors were seeing a patient, then they would have a better understanding. It would be great if more people could get involved with creating and updating the KIS, for example, the re- enablement team or the care home teams, making it a collective joint effort rather than it always coming back to daytime GPs to do.</p>
            <attrib>Clinician, OOH (3), Lothian</attrib>
          </disp-quote>
          <p>In some instances, when clinicians in OOH settings identified that a patient could benefit from a KIS, they would email the GP with relevant information extracted from OOH-based information systems. Although OOH staff found this process time-consuming—requiring them to gather information from multiple systems—they often did not receive any feedback from GPs regarding updates to the KIS.</p>
          <disp-quote>
            <p>There’s a bit of work involved because you’ve got to obviously do the e-mail, fill in the paperwork and the name, address the pile, put all that we have been doing, and any other information that we might have on our system about them. So, to update it is a wee bit time-consuming, but we never ever get a response back to see that it’s updated.</p>
            <attrib>Clinician, OOH (2), Lothian</attrib>
          </disp-quote>
        </sec>
      </sec>
      <sec>
        <title>Formal Workarounds to Access and Use the KIS</title>
        <sec>
          <title>Overview</title>
          <p>In response to challenges related to information access, interoperability, and information quality, organizations and information system vendors developed formal workarounds to extend and sustain the use of the KIS. These were designed both to extend access to KISs to nonclinical settings and to ensure continued access to the KIS during system outages. The following sections examine these subthemes in detail.</p>
        </sec>
        <sec>
          <title>Formal Workarounds to Extend the Information Infrastructure</title>
          <p>Understanding the need to update relevant information and to provide integrated care, a few GP practices in Lothian involved social workers and social care workers from MDTs and care pathways to update the KIS. However, as the information systems used by social workers and care providers were not interoperable with the information systems used by GPs, formal workarounds were used to provide social workers and care providers access to the KIS. These workarounds were formal insofar, as they were agreed and promoted by various stakeholders like the health board, technology vendor, and the EHSCP. Formal workarounds included creating proxy access for social workers and care providers involved in MDTs (Reablement, End-of-Life Care, and Post-Diagnostic Dementia Services) to view a read-only version of the KIS through hospital information systems on behalf of the NHS. Functionally, this constituted a semilegal extension of the technology, permitted through formal organizational and vendor sanctions. The boundary between formal and informal use was blurred, as access was generally limited to viewing the KIS rather than updating it, thereby avoiding potential breaches of professional jurisdiction or liability. Here, communities of practice, such as the regional health and social care partnership (EHSCP), organized training sessions for social care workers in care homes and for social workers involved in MDTs and care pathways. These training sessions helped in building a sense of ownership among nonclinical users (social workers and social care workers). EHSCP created templates for social workers and care providers to understand who would benefit from a KIS, as well as to share updates regarding future care plans with the GP practices.</p>
          <p>Formal workarounds in providing social care workers from MDTs access to the information infrastructure also involved issuing NHS email accounts to a limited number of social care providers operating care homes. Care home managers, due to their involvement in MDTs and seniority, were provided with NHS email accounts on behalf of the NHS. This arrangement provided nonclinical entities, with access to the secure emailing system used by health care providers to share updates with GPs. Documentary evidence from NHS Lothian demonstrated that this approach was formally supported, with care homes encouraged to establish secure email connections with NHS services to facilitate the exchange of person-identifiable and sensitive information. Observations of MDT discussions and training sessions, alongside documentary evidence from EHSCP materials, demonstrated that standardized templates were developed to support care providers in identifying individuals who may benefit from a KIS and communicating relevant updates to GP practices. However, because access was limited to selected individuals within care homes, managers often acted as intermediaries, sharing information with GP practices on behalf of other members of the care team who did not have direct access to the information infrastructure.</p>
        </sec>
        <sec>
          <title>Formal Workarounds to Access the Information Infrastructure During System Outages</title>
          <p>Formal workarounds were also used and promoted by health boards and vendors when technical barriers impeded access to the KIS through various information systems used by the different users. Contingency plans were developed and shared, detailing alternative communication channels that clinicians could use to maintain continuity of care by accessing relevant information. For instance, during system outages that made the KIS temporarily unavailable, clinicians were able to obtain relevant information through telephone referrals or secure email by contacting designated support teams within the health board. These teams, such as the Flow center (a digital navigation center for assisting clinical users), coordinated the distribution of information as well as contingency plans to GP practices, OOH services, and hospital-based clinicians, ensuring continued information access during planned and unplanned system downtime.</p>
          <p>Similarly, unanticipated impact or issues demanded the use of formal workarounds to provide temporary access to information systems to ensure continuity of care. For instance, after Adastra had a security outage in 2022, users in OOH settings had to learn and start using TrakCare (Scotland’s hospital-based information system) until Adastra was restored. Formal workarounds involved the health board and the vendor of TrakCare agreeing to provide OOH entity access to information systems used in hospitals. As part of the workaround to provide access, the OOH service was listed as a new hospital to be identified as a trusted entity with administrative rights. These workarounds ensured that staff from OOH settings could share clinical information with other entities like GPs, as well as view the KIS. However, OOH staff were required to familiarize themselves with TrakCare, a system designed for hospital-based workflows. This imposed additional learning demands and disrupted established clinical workflows for clinicians unfamiliar with hospital-based information systems.</p>
          <disp-quote>
            <p>When we had that ransomware attack, they had to quickly get everyone a proper TrakCare account so that they could write up and share the case notes. That was a huge piece of work, and they had to set up OOH as a clinic, like an outpatient clinic. So, we could at least write the GP a letter, and we could access the KIS. TrakCare wasn’t a bad option; there weren’t any problems with it necessarily. It’s just the fact that everyone had to learn it, because most of us hadn’t been working in hospitals particularly, and we would look stuff up, but we wouldn’t have to interact with the system, particularly often.</p>
            <attrib>Clinician, OOH (2), Lothian</attrib>
          </disp-quote>
          <p>Vendors provided users with documents promoting temporary workarounds to ensure interoperability across information systems used to access the KIS. Clinicians routinely relied on multiple interconnected systems, meaning that updates to any one software created misalignments with established workflows. In response to such issues, vendors issued detailed user guides describing interim procedures to support continued use. For example, Vision, the information system used by GPs, and the Scottish Care Information (SCI) Gateway, a national platform for clinical referrals, were software applications that allow GPs to access and share information with other clinicians. A security update to the SCI Gateway restricted users to a single active session and prevented simultaneous access through multiple browsers or devices. For Vision users, however, each patient consultation triggered a new login instance (parallel active session), causing active SCI Gateway sessions to be terminated automatically. To manage this incompatibility, vendors provided Vision users with revised login procedures intended to preserve interoperability with the updated SCI Gateway. These procedures required GPs to log in and out of the system after each consultation, thereby inadvertently disrupting routine practice.</p>
        </sec>
      </sec>
      <sec>
        <title>Repair Work to Adopt and Use the KIS</title>
        <sec>
          <title>Overview</title>
          <p>Following the COVID-19 pandemic, maintaining adoption of the KIS required users to undertake additional repair work to address challenges related to information quality, relevance, and interoperability. First, to restore information quality in the KIS, users adopted new strategies that functioned as repair work to maintain information quality. Across settings, users engaged in informal repair practices to obtain relevant information from alternative sources and to update the KIS. These practices varied by site and were influenced by users’ roles, digital skills, and access to specific information systems. Second, adoption also varied across health and social care settings. In nonclinical settings, carers and social workers acted as human nodes for information gathering and sharing, as the information systems used were not interoperable. The following sections illustrate how professionals in different settings adopted different strategies, including repair work, to realign the KIS with its intended purpose and update its information.</p>
        </sec>
        <sec>
          <title>User-Driven Repair Work in Clinical Settings</title>
          <p>As the quality of information in the KIS declined after COVID-19, users had to use different mechanisms to improve the quality of information in the KIS. In GP settings, these repair strategies were developed by GPs with analytical expertise and were shared informally with colleagues. In some GP practices, GPs with access to the Scottish Patients at Risk of Readmission and Admission (SPARRA) dataset used risk scores to identify patients who might benefit from a KIS and to determine whether existing KISs required updating. The SPARRA dataset identified individuals at risk of hospital admission by assigning a risk score derived from analyzing an individual’s chronic health conditions, prior unplanned hospital admissions, mental health diagnoses, and alcohol or drug-related admissions. However, a few GPs highlighted that reliance on SPARRA data was restrictive, as it drew predominantly on hospital-based data. Additionally, the high prevalence of multimorbidity within the dataset complicated efforts to determine which individuals would meaningfully benefit from a KIS.</p>
          <disp-quote>
            <p>The solution I’m finding at my practice is that I’m trying to use the SPARRA data, and I’m trying to get just my work through it. Okay, now who has just got the COVID phrase and who’s got a meaningful KIS? I get the SPARRA data, and then I build a group and code all of those. So, you could look at who’s coded for high SPARRA data and has a KIS and who doesn’t have a KIS and identify them. But that is really difficult now because everyone’s got cancer, even if there’s nothing in that, that’s quite difficult.</p>
            <attrib>Clinician, GP (2), Lothian</attrib>
          </disp-quote>
          <disp-quote>
            <p>SPARRA is not unhelpful, but if my recollection is right, it’s skewed by hospital admission. So it’s quite good at telling you who’s currently sick. Which is not quite the same as predicting who might become sick, and you might have something you could do about it as a GP.</p>
            <attrib>Clinician, GP (5), Lothian</attrib>
          </disp-quote>
          <p>A few other GP practices, which were involved in MDTs tackling issues around frailty and multimorbidity, used local datasets to identify who would benefit from a KIS. These GP practices, forming a cluster under the GMS contract of 2018, ran special services to identify frail patients in a region and support their care plans and preferences. GP practices used local datasets to identify frail patients and to identify if they had a KIS in place. These informal repair strategies, developed and used in different practices, were later shared by communities of practice like Scottish Clinical Information Management in Primary Care and EHSCP. As a result, networks of GP practices, in different clusters, had started to use SPARRA datasets, alongside other local datasets capturing details regarding polypharmacy, multimorbidity, and frailty.</p>
          <p>Clinicians working in OOH settings reported that many other sources of information could help GPs understand an individual’s current care needs, but these were stored in various formats across different information systems. This information included records from community nurses and care home staff, maintained across multiple digital systems as well as physical documents, to capture a person’s health and care needs. OOH clinicians noted that nurses and care home staff, who knew the patient and their family well, provided valuable information about next of kin, recent hospitalizations, current functional status, and any gradual health decline over time. Nurses and carers visiting house-bound individuals documented residents’ mobility, recent hospital visits or admissions, and care plans using disparate information systems—and sometimes physical copies. Because information systems across organizations were not interoperable, OOH clinicians visiting care home residents often relied on verbal reports from nurses as well as carers and shared them with GP practices via secure email, with the extent of sharing and GPs’ incorporation of updates both depending on individual capacity and willingness.</p>
          <disp-quote>
            <p>So if it’s district nurses in hospital-based complex care settings or home care for house-bound patients, it would usually be verbal communication. You would take a handover from the nurse or carer who contacted our service to know what they’re concerned about, and usually, they know the patient well and know the family, which can be an excellent source of information. Like, who is the patient’s next of kin, or say that the person has been in the hospital for a problem last month. I think the care home staff are a really valuable source of information because they can tell you about the level of function of the person, whether they have been sick for a while, or are normally quite mobile and independent but currently bed-bound or needs help, if this patient’s been on a downward trajectory over the last six months and they’ve been declining steadily. That is really useful information, and I would type up my notes and share them with the registered GP afterwards.</p>
            <attrib>Clinician, OOH (2), Lothian</attrib>
          </disp-quote>
        </sec>
        <sec>
          <title>Maintenance and Repair Work in Nonclinical Settings</title>
          <p>While formal workarounds enabled social care providers to access the secure emailing networks to receive a digital copy of the KIS from GP practices, care providers also maintained a physical copy. A few care managers highlighted that in social care settings, physical copies of care plans and the KIS were stored to ensure continuity of care and as a contingency mechanism. These contingency mechanisms were in place, recognizing the vulnerability of digital technologies to occasional breakdown, and due to epistemic practices around record keeping in care settings. The different material forms of the KIS also served as a medium to share information with clinical staff providing emergency care, like the ambulance service. Ambulance services visiting care homes often relied on multiple sources of information present at care settings while attending a patient, which required care staff to maintain physical records as well.</p>
          <disp-quote>
            <p>Yeah. I think it is good practice to have everything on the electronic platform, but like any electronic device, as you do rely on the internet and electricity working, and you know if all that went down, you are left with nothing, which I don’t feel is really good practice. This resident has to be cared for regardless of whether we have electricity, Wi-Fi, or Internet. So, we have a folder for each person that contains these very important documents. If anything were to happen to this system, or let’s say you know, like the NHS system that has been hacked several times, you don’t know what will happen in life. But I still have to provide the most important care to my resident. So, I feel we should have a paper copy just in case things happen, and we can’t access it digitally.</p>
            <attrib>Social care (3), Lothian</attrib>
          </disp-quote>
          <p>A few GPs reported that extending the health care–centric information infrastructure to social workers and care providers to access and share information regarding future care planning was beneficial. Although this access to the information infrastructure enabled a few care workers and social workers to share information with clinicians, they functioned as human nodes who shared information with the GP practices to update the KIS. For instance, charity and voluntary organizations engaged in frailty assessments had to manually collect information regarding a person’s contact information, care plans in place, mobility status, and available resources at their residence to support home-based care. Voluntary organizations then had to share the assessment with GPs, where GPs or GP admin staff would enter the details into the KIS.</p>
          <p>Internal implementation reports by EHSCP also highlighted the development of local forms and documentation processes across different reablement pathways to facilitate information collection and sharing between community organizations and GP practices. However, despite these efforts to support information exchange, challenges remained as different professional groups operated with distinct epistemic approaches to documentation, information recording, and care practices. These differences influenced how information was generated, interpreted, and incorporated into the KIS, requiring ongoing negotiation and coordination among stakeholders.</p>
          <disp-quote>
            <p>There are some local initiatives, like the long-term conditions team, where community teams will collect the data in a structured way and then email it to the GP practice so that it’s kind of easier for the GP. You can just copy and paste aspects of that record to share in the KIS as opposed to having to, you know, originate it and type it up yourself.</p>
            <attrib>Clinician, GP (2), Lothian</attrib>
          </disp-quote>
        </sec>
      </sec>
    </sec>
    <sec sec-type="discussion">
      <title>Discussion</title>
      <sec>
        <title>Summary of Findings</title>
        <p>Findings illustrate how the KIS, as a shared object of collaboration across diverse health and care professionals within an information infrastructure, was adopted differently in various settings over time. Diverse health and care providers benefited differently from the information held in the KIS, with varying expectations regarding what constituted useful information based on their professional roles. These expectations varied, shaped by users’ professional roles as well as information needs, and only became evident as the KIS was adopted across different settings. They revealed how various providers’ specific requirements and perspectives influenced their expectations and use of the KIS. These expectations evolved as the expectations of integrated care evolved and more significantly after national initiatives diverted the use of KIS to new missions, necessitating workarounds and repair work to extend the health care–centric information infrastructure to new settings and to realign the KIS with its intended purposes.</p>
        <p>Formal workarounds were used to extend the health care–centric information infrastructure to social care settings and to ensure access to the KIS during system outages. These workarounds included creating proxy access for a few nonclinical professionals (eg, social workers from councils and social care providers) involved in MDTs to view the KIS using hospital-based information systems. This allowed social workers and carers to access the KIS in a digital format and communicate with GPs using the secure emailing network. Formal workarounds also involved the development and sharing of contingency plans by vendors, health boards, and organizations with users to address unexpected technical barriers that hindered access to the KIS.</p>
        <p>While formal workarounds facilitated access for new users and the development and sharing of contingency plans, informal user-driven repair work was used to gather and share relevant information from alternative sources to update the KIS. These user-driven repair works were subject to the affordances of the users, that is, their role and consequent level of access to the existing information infrastructure, digital skills, willingness, subjective perceptions of integrated care, organizational practices, and leadership. Users leveraged various interconnected systems within the information infrastructure, such as local datasets, other EHRs, and care plans, to fulfill their information needs, even though these systems were originally designed for different purposes. Over time, these locally developed repair strategies became embedded within practice, influenced patterns of the KIS’s adoption across settings, and contributed to shaping the evolution of the regional information infrastructure.</p>
      </sec>
      <sec>
        <title>Integration With the Literature</title>
        <p>This research aligns with existing literature, showing that information infrastructures evolve over long periods, gradually embedding new technologies within user groups and becoming shaped by established organizational practices, information needs, and existing information systems [<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref4">4</xref>,<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref21">21</xref>,<xref ref-type="bibr" rid="ref27">27</xref>]. Previous evaluations of summary care records have highlighted challenges associated with information quality, interoperability, and aligning shared records with the information needs and workflows of different professional groups [<xref ref-type="bibr" rid="ref1">1</xref>,<xref ref-type="bibr" rid="ref3">3</xref>,<xref ref-type="bibr" rid="ref5">5</xref>,<xref ref-type="bibr" rid="ref7">7</xref>]. However, these evaluations have often examined summary care records at particular points in time, providing limited insight into how such technologies evolve as part of broader information infrastructures [<xref ref-type="bibr" rid="ref1">1</xref>]. Our previous research examined how the KIS and associated infrastructures developed through successive waves of infrastructural growth [<xref ref-type="bibr" rid="ref7">7</xref>]. This study extends that work by examining what happens after infrastructural expansion, focusing on how users domesticate, maintain, and transform established infrastructures through everyday practices of repair and workaround. Building on this perspective, this study illustrates how the KIS continued to evolve as it became embedded across diverse health and care settings, where different professional groups developed context-specific interpretations of its purpose, functionality, and information requirements. Jarrahi et al [<xref ref-type="bibr" rid="ref27">27</xref>] further emphasize that information infrastructures are open and generative, developing through interaction with new settings where they combine with existing practices and information needs. By examining a digital technology used for collaborative work [<xref ref-type="bibr" rid="ref5">5</xref>-<xref ref-type="bibr" rid="ref7">7</xref>], this study illustrates how the KIS was translated across different settings over time and embedded within the installed base, highlighting the generative nature of the information infrastructure as it evolved to support health and social care integration. Across these settings, user groups differed in their understanding of the usability of the KIS, which changed over time, as they started to adopt the KIS. For instance, the KIS was designed to share information from GP records with other people involved in delivering care. However, as the KIS was implemented and adopted across settings over time, user groups developed differing interpretations of what constituted key information. OOH staff, for instance, benefited from having up-to-date future care plans recorded in the KIS, but this required GPs to collate information from various information sources to update the KIS. Consequently, their views on how the KIS should be updated and what it should contain varied according to the users’ professional roles and information needs, informing the repair work they used, such as referring to other EHRs and datasets to which they had access. Findings from the study illustrate the range of strategies organizations and users used to update information in the KIS, including formal workarounds to extend the KIS into new settings and informal, user-driven repair work to access and update with relevant information. These findings demonstrate that information infrastructures integrating health and care providers are open and evolve generatively over extended periods, with workarounds and user-driven repair practices shaping their extension and adoption across settings [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref27">27</xref>].</p>
        <p>This study also aligns with the literature highlighting that workarounds are an integral part of technology implementation and adoption [<xref ref-type="bibr" rid="ref10">10</xref>,<xref ref-type="bibr" rid="ref11">11</xref>]. Several workarounds observed in this study are consistent with the literature describing formal, interim measures used to address limitations around technology usability [<xref ref-type="bibr" rid="ref11">11</xref>]. Formal workarounds identified in the study included the development of contingency plans and the provision of interim user guides by vendors, offering temporary instructions to support users in navigating the technology during periods of limited system functionality. Contingency plans involved using alternative information systems and paper-based records as intermediaries to maintain continuity of care in the event of system failures. Finally, formal workarounds were also used to extend the health care–centric information infrastructure to nonclinical settings. These findings illustrate that workarounds are strategies used by individuals and organizations to navigate technological or procedural constraints, and that they play a critical role not only in technology implementation and adoption but also in the evolution of information infrastructures [<xref ref-type="bibr" rid="ref8">8</xref>,<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>].</p>
        <p>Information infrastructure and the repair work it entails have been examined from various perspectives. Scholars note that information infrastructures are prone to breakdown and require repair as part of their maintenance [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. However, existing studies focus on visible and invisible repair activities, the use of material tools, and the power dynamics during infrastructural failure, but pay limited attention to repair work in the context of the long-term evolution of infrastructures for integrating health and care providers [<xref ref-type="bibr" rid="ref28">28</xref>,<xref ref-type="bibr" rid="ref29">29</xref>]. This study contributes to the literature by highlighting that the evolution of information infrastructures for integrating health and social care providers necessitates user-driven repair work for its maintenance. User-driven repair work involved drawing on local datasets and other EHRs—containing overlapping information but designed for different purposes—to identify and share relevant information for updating the KIS. These datasets and information present in different systems can be conceptualized as digital assemblages or personal information infrastructures, which users engaged with to support their information needs [<xref ref-type="bibr" rid="ref30">30</xref>]. A digital assemblage is a combination of digital and physical resources that users interact with to achieve specific objectives [<xref ref-type="bibr" rid="ref27">27</xref>,<xref ref-type="bibr" rid="ref30">30</xref>,<xref ref-type="bibr" rid="ref31">31</xref>]. By analyzing how users engaged with digital assemblages during infrastructural breakdowns to meet their information needs, this study shows that infrastructural growth is also driven by bottom-up strategies and enacted through user-driven repair work.</p>
        <p>Finally, this research contributes to the theory of workarounds by further elucidating the relationships between environment, strategies, and infrastructure [<xref ref-type="bibr" rid="ref10">10</xref>-<xref ref-type="bibr" rid="ref12">12</xref>]. The theory of workarounds seeks to classify the different types of workarounds used by users, identify the conditions under which workarounds emerge, and explain how sociotechnical systems evolve through the continued use of workarounds [<xref ref-type="bibr" rid="ref10">10</xref>]. Central to this theoretical perspective is the argument that the enactment of workarounds by users, organizations, developers, and implementers arises from the dynamic interplay between environment, strategies, and infrastructure. According to Alter [<xref ref-type="bibr" rid="ref10">10</xref>], environment refers to the broader organizational, cultural, technical, and regulatory context in which a technology is implemented, whereas strategies denote organizational- and vendor-level approaches to technology development, implementation, and customization. While the theory of workarounds emphasizes the relationship among these elements, subsequent studies have largely focused on the interplay between environment and strategies [<xref ref-type="bibr" rid="ref11">11</xref>,<xref ref-type="bibr" rid="ref12">12</xref>], giving limited attention to infrastructure. This study demonstrates that access to the information infrastructure enabled users to undertake repair work aligned with their specific information needs, thereby generating new affordances. For instance, access to the information infrastructure allowed clinical users to draw on multiple information sources that contained information analogous to the KIS. Examples include hospital staff accessing other EHRs and local datasets to retrieve information related to multimorbidity, polypharmacy, and risk of hospital readmission, which were then used to inform their clinical decision-making needs. Similarly, access to the information infrastructure enabled nonclinical (social workers and social care workers) users to leverage the infrastructure to access the KIS and communicate relevant updates to GPs via the secure email system. These cases demonstrate how users used the information infrastructure to undertake diverse repair work across different settings, thereby creating affordances. In turn, this contributes to theorizing how users leverage the infrastructure to implement different types of workarounds and repair work within specific contexts, where organizations and vendors pursue distinct approaches to technology development, customization, and adoption.</p>
      </sec>
      <sec>
        <title>Strengths and Limitations</title>
        <p>This study offers a methodological contribution by demonstrating the value of combining longitudinal and contextual analytical approaches with a multimethod qualitative case study design to examine the evolution of information infrastructures. The integration of the BoAP and TPOM frameworks enabled examination of both the historical trajectory of the KIS and the contextual factors shaping its adoption and use across different settings. While BoAP supported reconstruction of the KIS’s development and evolution over time, TPOM facilitated analysis of the technological, sociotechnical, organizational, and macroenvironmental conditions influencing its adoption in practice. By triangulating historical and contemporary documentary evidence with interviews and ethnographic observations, the study further strengthened this longitudinal perspective by reconstructing the development, adoption, and use of the KIS across multiple settings and time periods.</p>
        <p>This approach enabled examination of how contextual factors, historical trajectories, organizational dynamics, and evolving understandings of integrated care shaped technology adoption over time, while capturing long-term trends that are difficult to observe through cross-sectional or short-term implementation studies [<xref ref-type="bibr" rid="ref3">3</xref>-<xref ref-type="bibr" rid="ref5">5</xref>]. Combining documentary evidence with participants’ retrospective accounts and observations of contemporary practice allowed different sources of evidence to be compared and contextualized, providing a richer understanding of how information infrastructures evolve through successive phases of development, implementation, domestication, and everyday use. This perspective made it possible to examine how challenges relating to usability, organizational practices, and macroenvironmental conditions changed over time and across settings, dynamics that are often overlooked in snapshot evaluations of digital technologies [<xref ref-type="bibr" rid="ref19">19</xref>].</p>
        <p>However, reconstructing longitudinal processes primarily through retrospective accounts and documentary evidence, rather than prospective longitudinal ethnography, constitutes a limitation. Although triangulation with observations strengthened the analysis, the study could not fully capture the granular, real-time negotiations, decision-making processes, and implementation activities that occurred during the early phases of KIS development and adoption. Additionally, while BoAP enabled examination of historical trajectories and TPOM supported contextual analysis across settings, the use of retrospective data meant that changes in workforce digital skills, organizational practices, and technological arrangements could not be systematically observed as they unfolded.</p>
        <p>Adoption strategies mentioned in the study are specific to users in the Lothian region, and this contextual specificity also limits the generalizability of the findings. The various care pathways, health and care professionals involved, and technological arrangements may differ in other regions of Scotland. Studying adjacent contexts would enable comparative insights into how local contingencies shape both processes and outcomes and would also allow the findings to be situated more robustly within the broader context of integration. Finally, responsibilities for care provision and approaches to digital integration vary internationally, limiting the direct transferability of these insights to health system contexts beyond Scotland. However, the study offers valuable and transferable theoretical contributions: it demonstrates how the domestication of digital technologies evolved over time and highlights the ongoing repair work and workarounds required to maintain and extend information infrastructures.</p>
      </sec>
      <sec>
        <title>Implications for Policy and Practice</title>
        <p>Adoption of digital technologies for integrating health and care providers is a dynamic process, shaped by broader macroenvironmental conditions, evolving user needs, and organizational practices. Consequently, policies aimed at supporting digital technologies in integrated care must incorporate mechanisms for continuous feedback and periodic evaluation, particularly following major changes relating to their use. Such iterative assessments enable implementers, policymakers, and vendors to identify emerging challenges, understand the strategies that users develop in practice, and adjust technologies or implementation approaches accordingly. Findings from the study highlight a range of user-driven repair practices undertaken to maintain the infrastructure. Identifying such local practices is useful, as it provides insight into shortcomings in design and can support further iterations of technology development and infrastructural growth, as well as the streamlining and regulation of these practices. These repair practices can also serve as indicators of implementation and adoption barriers, highlighting where additional resources, training, governance mechanisms, or changes to existing workflows may be required.</p>
        <p>The findings suggest that continuous quality improvement should not focus solely on increasing user adoption, but also on identifying where repair work and workarounds emerge during routine use. These practices provide valuable indicators of mismatches between the intended use of digital technologies and evolving expectations of integrated care, organizational arrangements, and users’ information needs over time [<xref ref-type="bibr" rid="ref7">7</xref>,<xref ref-type="bibr" rid="ref32">32</xref>]. Rather than viewing repair practices simply as deviations from intended implementation, they can be used to identify challenges, reveal areas where technologies no longer align with everyday practice, and inform iterative improvements of digital infrastructures. <xref ref-type="table" rid="table2">Table 2</xref> summarizes the key implementation and adoption challenges identified in this study, their impact on KIS use, the formal workarounds and user-driven repair practices that emerged in response, and the associated implications for policy and practice.</p>
        <table-wrap position="float" id="table2">
          <label>Table 2</label>
          <caption>
            <p>Recommendations for policy and practice.</p>
          </caption>
          <table width="1000" cellpadding="5" cellspacing="0" border="1" rules="groups" frame="hsides">
            <col width="210"/>
            <col width="190"/>
            <col width="220"/>
            <col width="380"/>
            <thead>
              <tr valign="bottom">
                <td>Implementation and adoption challenges</td>
                <td>Impact on KIS<sup>a</sup> use</td>
                <td>Formal workaround or repair response</td>
                <td>Recommendations for policy and practice</td>
              </tr>
            </thead>
            <tbody>
              <tr valign="top">
                <td>Variation in GP<sup>b</sup> capacity and responsibility for maintaining records</td>
                <td>Inconsistent updating and completeness of KIS information</td>
                <td>Local prioritization approaches, MDT<sup>c</sup> involvement, structured information sharing from community teams</td>
                <td>Distribute responsibility for maintaining shared records across multidisciplinary teams, supported by dedicated time, organizational support, and clear governance arrangements.</td>
              </tr>
              <tr valign="top">
                <td>Repurposing of KIS during COVID-19</td>
                <td>Increased number of records with limited future care planning information</td>
                <td>GP-led review and restoration of KIS information quality</td>
                <td>Ensure that future policy changes align with the intended function of shared records and include plans for maintaining information quality during and after implementation.</td>
              </tr>
              <tr valign="top">
                <td>Limited interoperability across health and social care systems</td>
                <td>Reduced ability of social care providers to directly contribute information</td>
                <td>Proxy access, secure email, templates, and intermediary roles</td>
                <td>Strengthen interoperability across semantic, organizational, and legal levels by addressing existing barriers and learning from user-developed workarounds. Develop structured mechanisms for extending information infrastructures that enable social care professionals to contribute information while maintaining appropriate governance and accountability.</td>
              </tr>
              <tr valign="top">
                <td>Differences in professional information needs and documentation practices</td>
                <td>Variation in what information was considered relevant across settings</td>
                <td>Negotiation between professional groups and development of local documentation processes</td>
                <td>Engage different user groups when designing and revising shared records to understand their distinct roles, information needs, and workflows, ensuring that records support the diverse requirements of clinical and care settings.</td>
              </tr>
              <tr valign="top">
                <td>Technical limitations and system outages</td>
                <td>Temporary disruption to access and established workflows</td>
                <td>Contingency plans, alternative systems, vendor-supported workarounds</td>
                <td>Develop resilient contingency arrangements and involve users in testing workflow changes before implementation.</td>
              </tr>
            </tbody>
          </table>
          <table-wrap-foot>
            <fn id="table2fn1">
              <p><sup>a</sup>KIS: Key Information Summary.</p>
            </fn>
            <fn id="table2fn2">
              <p><sup>b</sup>GP: general practitioner.</p>
            </fn>
            <fn id="table2fn3">
              <p><sup>c</sup>MDT: multidisciplinary team.</p>
            </fn>
          </table-wrap-foot>
        </table-wrap>
        <p>Importantly, improvement efforts should not seek to eliminate all workarounds, as some locally developed practices enabled users to overcome limitations within the existing infrastructure and supported continued use of the KIS in different settings. Instead, organizations should identify which workarounds represent valuable context-specific solutions and which indicate persistent system limitations requiring intervention. This requires balancing standardization of digital infrastructures with flexibility to accommodate differences in organizational contexts, professional roles, and local workflows.</p>
        <p>Moreover, national and regional initiatives must aim to strengthen the digital competencies of health and care professionals and establish networks for knowledge exchange, which are crucial to sustaining adoption and use at different settings over time. These initiatives must recognize the heterogeneity of stakeholders: different organizations vary considerably in their digital maturity, resource availability, and leadership capacity. Therefore, policy interventions should avoid uniform approaches and instead provide long-term support tailored to organizational contexts. This includes ensuring that sufficient workforce capacity, training, and organizational support are available to sustain information-sharing practices over time. The analysis also demonstrates the importance of communities of practice and intermediary organizations in sharing locally developed strategies and supporting wider adoption across settings.</p>
        <p>Findings from the study also illustrate how users relied on multiple digital assemblages to meet their information needs when existing infrastructures did not fully support their activities. Future adoption strategies should therefore anticipate how emerging sources of information, such as AI-supported documentation tools or patient-generated data from wearable devices, may interact with existing information infrastructures. Policies must consider how these sources can be incorporated while maintaining appropriate governance arrangements, interoperability, and alignment with the needs of diverse users.</p>
      </sec>
      <sec>
        <title>Conclusions</title>
        <p>Using the KIS in Scotland as a case, this study illustrates how regional information infrastructures for integrating health and care providers evolved over time, embedding technologies within local routines, practices, and existing systems, while being shaped by professional roles and information needs. Adoption occurs incrementally, with formal workarounds extending health care–centric infrastructure to new settings and informal user-driven practices facilitating adaptation across diverse local contexts and supporting ongoing infrastructural maintenance. The study offers theoretical insights into how users domesticate digital technologies across diverse health and care settings over time and how infrastructural growth is facilitated through workarounds and user-driven repair work. Importantly, policymakers and technology vendors must recognize that technology deployment alone is insufficient; they need to account for evolving user needs and the diverse strategies users use to make technologies functional in practice. This requires continuous evaluation of implementation challenges, including resource constraints, interoperability limitations, and changing information needs, while supporting locally developed solutions that enable technologies to remain useful across diverse settings. Understanding these practices can inform how technologies become embedded within the infrastructure, identify and manage workarounds as well as user-driven strategies that support infrastructural growth, and guide future innovation.</p>
      </sec>
    </sec>
  </body>
  <back>
    <app-group>
      <supplementary-material id="app1">
        <label>Multimedia Appendix 1</label>
        <p>Topic guide for interviews.</p>
        <media xlink:href="medinform_v14i1e94376_app1.docx" xlink:title="DOCX File , 25 KB"/>
      </supplementary-material>
      <supplementary-material id="app2">
        <label>Multimedia Appendix 2</label>
        <p>Protocol for observation.</p>
        <media xlink:href="medinform_v14i1e94376_app2.docx" xlink:title="DOCX File , 16 KB"/>
      </supplementary-material>
      <supplementary-material id="app3">
        <label>Multimedia Appendix 3</label>
        <p>Selection criteria for documents.</p>
        <media xlink:href="medinform_v14i1e94376_app3.docx" xlink:title="DOCX File , 15 KB"/>
      </supplementary-material>
      <supplementary-material id="app4">
        <label>Multimedia Appendix 4</label>
        <p>Codes and themes emerging from the data.</p>
        <media xlink:href="medinform_v14i1e94376_app4.docx" xlink:title="DOCX File , 20 KB"/>
      </supplementary-material>
      <supplementary-material id="app5">
        <label>Multimedia Appendix 5</label>
        <p>COREQ checklist.</p>
        <media xlink:href="medinform_v14i1e94376_app5.pdf" xlink:title="PDF File  (Adobe PDF File), 456 KB"/>
      </supplementary-material>
    </app-group>
    <glossary>
      <title>Abbreviations</title>
      <def-list>
        <def-item>
          <term id="abb1">BoAP</term>
          <def>
            <p>biography of artifacts and practices</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb2">COREQ</term>
          <def>
            <p>Consolidated Criteria for Reporting Qualitative Research</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb3">ECS</term>
          <def>
            <p>Emergency Care Summary</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb4">EHR</term>
          <def>
            <p>electronic health record</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb5">EHSCP</term>
          <def>
            <p>Edinburgh Health and Social Care Partnership</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb6">EMREC</term>
          <def>
            <p>Edinburgh Medical School Research Ethics Committee</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb7">GMS</term>
          <def>
            <p>General Medical Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb8">GP</term>
          <def>
            <p>general practitioner</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb9">KIS</term>
          <def>
            <p>Key Information Summary</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb10">MDT</term>
          <def>
            <p>multidisciplinary team</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb11">NHS</term>
          <def>
            <p>National Health Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb12">OOH</term>
          <def>
            <p>out-of-hour</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb13">QI</term>
          <def>
            <p>Quality Improvement</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb14">REDMAP</term>
          <def>
            <p>Ready, Expect, Diagnosis, Matters, Actions, and Plans</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb15">SAS</term>
          <def>
            <p>Scottish Ambulance Service</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb16">SCI</term>
          <def>
            <p>Scottish Care Information</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb17">SPARRA</term>
          <def>
            <p>Scottish Patients at Risk of Readmission and Admission</p>
          </def>
        </def-item>
        <def-item>
          <term id="abb18">TPOM</term>
          <def>
            <p>technology-people-organization-macroenvironment</p>
          </def>
        </def-item>
      </def-list>
    </glossary>
    <ack>
      <p>ChatGPT was used to assist with proofreading and language refinement of the manuscript.</p>
    </ack>
    <notes>
      <title>Data Availability</title>
      <p>The datasets generated or analyzed during this study are available from the corresponding author on reasonable request.</p>
    </notes>
    <notes>
      <title>Funding</title>
      <p>This study was supported by the University of Edinburgh and was undertaken as part of VS’s doctoral research.</p>
    </notes>
    <fn-group>
      <fn fn-type="con">
        <p>This study was conducted as part of VS’s doctoral research under the supervision of KC and RW. VS conceptualized the study with significant contributions from KC and RW. VS conducted data collection, analysis, and wrote the first draft of the manuscript. KC and RW provided supervision, contributed to theoretical development, and critically reviewed and edited multiple versions of the manuscript. All authors read and approved the final manuscript.</p>
      </fn>
      <fn fn-type="conflict">
        <p>None declared.</p>
      </fn>
    </fn-group>
    <ref-list>
      <ref id="ref1">
        <label>1</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>Morris</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Thomas</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Gunning</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Introducing a nationally shared electronic patient record: case study comparison of Scotland, England, Wales and Northern Ireland</article-title>
          <source>Int J Med Inform</source>
          <year>2013</year>
          <volume>82</volume>
          <issue>5</issue>
          <fpage>e125</fpage>
          <lpage>e138</lpage>
          <pub-id pub-id-type="doi">10.1016/j.ijmedinf.2013.01.002</pub-id>
          <pub-id pub-id-type="medline">23434362</pub-id>
          <pub-id pub-id-type="pii">S1386-5056(13)00013-0</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>Morris</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Brown</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Williamson</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Wyatt</surname>
              <given-names>J</given-names>
            </name>
          </person-group>
          <article-title>The Scottish Emergency Care Summary—an evaluation of a national shared record system aiming to improve patient care: technology report</article-title>
          <source>Inform Prim Care</source>
          <year>2012</year>
          <volume>20</volume>
          <issue>1</issue>
          <fpage>41</fpage>
          <lpage>49</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.14236/jhi.v20i1.46"/>
          </comment>
          <pub-id pub-id-type="doi">10.14236/jhi.v20i1.46</pub-id>
          <pub-id pub-id-type="medline">23336834</pub-id>
          <pub-id pub-id-type="pii">46</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref3">
        <label>3</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Aanestad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Grisot</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Hanseth</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Vassilakopoulou</surname>
              <given-names>P</given-names>
            </name>
          </person-group>
          <source>Information Infrastructures within European Health Care. 1st Edition</source>
          <year>2017</year>
          <publisher-loc>Cham</publisher-loc>
          <publisher-name>Springer</publisher-name>
        </nlm-citation>
      </ref>
      <ref id="ref4">
        <label>4</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Star</surname>
              <given-names>SL</given-names>
            </name>
            <name name-style="western">
              <surname>Ruhleder</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Steps toward an ecology of infrastructure: design and access for large information spaces</article-title>
          <source>Inform Syst Res</source>
          <year>1996</year>
          <fpage>111</fpage>
          <lpage>134</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://pubsonline.informs.org/doi/10.1287/isre.7.1.111"/>
          </comment>
          <pub-id pub-id-type="doi">10.1287/isre.7.1.111</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref5">
        <label>5</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Bowker</surname>
              <given-names>GC</given-names>
            </name>
            <name name-style="western">
              <surname>Star</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <source>Sorting Things Out: Classification and Its Consequence</source>
          <year>1999</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>Mit Press, Ca</publisher-name>
        </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>Star</surname>
              <given-names>SL</given-names>
            </name>
          </person-group>
          <article-title>This is not a boundary object: reflections on the origin of a concept</article-title>
          <source>Sci Technol Hum Values</source>
          <year>2010</year>
          <volume>35</volume>
          <issue>5</issue>
          <fpage>601</fpage>
          <lpage>617</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/25746386"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/0162243910377624</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>Sai</surname>
              <given-names>V</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Cresswell</surname>
              <given-names>K</given-names>
            </name>
          </person-group>
          <article-title>Evolution of regional information infrastructures integrating health and social care in Scotland: qualitative study</article-title>
          <source>J Med Internet Res</source>
          <year>2026</year>
          <volume>28</volume>
          <fpage>e90997</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2026//e90997/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/90997</pub-id>
          <pub-id pub-id-type="medline">42430230</pub-id>
          <pub-id pub-id-type="pii">v28i1e90997</pub-id>
          <pub-id pub-id-type="pmcid">PMC13353405</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref8">
        <label>8</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Ser</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Robertson</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>A qualitative exploration of workarounds related to the implementation of national electronic health records in early adopter mental health hospitals</article-title>
          <source>PLoS One</source>
          <year>2014</year>
          <volume>9</volume>
          <issue>1</issue>
          <fpage>e77669</fpage>
          <pub-id pub-id-type="doi">10.1371/journal.pone.0077669</pub-id>
          <pub-id pub-id-type="medline">24454678</pub-id>
          <pub-id pub-id-type="pii">PONE-D-12-12587</pub-id>
          <pub-id pub-id-type="pmcid">PMC3894172</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref9">
        <label>9</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Coiera</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Technology, cognition and error</article-title>
          <source>BMJ Qual Saf</source>
          <year>2015</year>
          <volume>24</volume>
          <issue>7</issue>
          <fpage>417</fpage>
          <lpage>422</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://qualitysafety.bmj.com/lookup/pmidlookup?view=long&amp;pmid=26092566"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2014-003484</pub-id>
          <pub-id pub-id-type="medline">26092566</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2014-003484</pub-id>
          <pub-id pub-id-type="pmcid">PMC4484254</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>Alter</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Theory of workarounds</article-title>
          <source>CAIS</source>
          <year>2014</year>
          <volume>34</volume>
          <issue>1041-66</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.17705/1CAIS.03455"/>
          </comment>
          <pub-id pub-id-type="doi">10.17705/1cais.03455</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref11">
        <label>11</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Cresswell</surname>
              <given-names>KM</given-names>
            </name>
            <name name-style="western">
              <surname>Mozaffar</surname>
              <given-names>H</given-names>
            </name>
            <name name-style="western">
              <surname>Lee</surname>
              <given-names>L</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Workarounds to hospital electronic prescribing systems: a qualitative study in English hospitals</article-title>
          <source>BMJ Qual Saf</source>
          <year>2017</year>
          <volume>26</volume>
          <issue>7</issue>
          <fpage>542</fpage>
          <lpage>551</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="http://hdl.handle.net/20.500.11820/614a5881-c57e-4faa-883a-1032f084c742"/>
          </comment>
          <pub-id pub-id-type="doi">10.1136/bmjqs-2015-005149</pub-id>
          <pub-id pub-id-type="medline">27129493</pub-id>
          <pub-id pub-id-type="pii">bmjqs-2015-005149</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref12">
        <label>12</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Wibisono</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Sammon</surname>
              <given-names>D</given-names>
            </name>
            <name name-style="western">
              <surname>Heavin</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>Opening the workaround black box: an organisational routines perspective</article-title>
          <source>J Decis Syst</source>
          <year>2022</year>
          <volume>31</volume>
          <issue>sup1</issue>
          <fpage>270</fpage>
          <lpage>281</lpage>
          <pub-id pub-id-type="doi">10.1080/12460125.2022.2073647</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>Correia de Matos</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>do Nascimento</surname>
              <given-names>G</given-names>
            </name>
            <name name-style="western">
              <surname>Campos Fernandes</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Matos</surname>
              <given-names>C</given-names>
            </name>
          </person-group>
          <article-title>The integration of social and health sectors in Scotland: an analysis from the prism of different public policy models</article-title>
          <source>J Mark Access Health Policy</source>
          <year>2025</year>
          <volume>13</volume>
          <issue>1</issue>
          <fpage>8</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.mdpi.com/resolver?pii=jmahp-13-00008"/>
          </comment>
          <pub-id pub-id-type="doi">10.3390/jmahp13010008</pub-id>
          <pub-id pub-id-type="medline">40144194</pub-id>
          <pub-id pub-id-type="pii">jmahp-13-00008</pub-id>
          <pub-id pub-id-type="pmcid">PMC11942909</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>Donaldson</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Knight</surname>
              <given-names>P</given-names>
            </name>
            <name name-style="western">
              <surname>Noble</surname>
              <given-names>A</given-names>
            </name>
            <name name-style="western">
              <surname>Strathearn</surname>
              <given-names>S</given-names>
            </name>
          </person-group>
          <article-title>Health and social care integration in Scotland: evidence vs rhetoric</article-title>
          <source>Int J Integr Care</source>
          <year>2024</year>
          <volume>24</volume>
          <issue>1</issue>
          <fpage>4</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://europepmc.org/abstract/MED/38312476"/>
          </comment>
          <pub-id pub-id-type="doi">10.5334/ijic.7759</pub-id>
          <pub-id pub-id-type="medline">38312476</pub-id>
          <pub-id pub-id-type="pmcid">PMC10836158</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref15">
        <label>15</label>
        <nlm-citation citation-type="web">
          <article-title>Guidance and top tips for updating and reviewing Key Information Summaries for GP practices</article-title>
          <source>Health Improvement Scotland</source>
          <year>2021</year>
          <access-date>2026-09-18</access-date>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://docslib.org/doc/2222440/guidance-and-top-tips-for-updating-and-reviewing-key-information-summaries-for-gp-practices">https://docslib.org/doc/2222440/guidance-and-top-tips-for-updating-and-reviewing-key-information-summaries-for-gp-practices</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref16">
        <label>16</label>
        <nlm-citation citation-type="web">
          <person-group person-group-type="author">
            <collab>NHS Education for Scotland</collab>
          </person-group>
          <article-title>Anticipatory care planning (REDMAP)</article-title>
          <source>Turas Learn</source>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://learn.nes.nhs.scot/60447/realistic-medicine/anticipatory-care-planning-redmap/treatment-escalation-planning-tep-redmap-masterclass-toolkit">https://learn.nes.nhs.scot/60447/realistic-medicine/anticipatory-care-planning-redmap/treatment-escalation-planning-tep-redmap-masterclass-toolkit</ext-link>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref17">
        <label>17</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Pollock</surname>
              <given-names>N</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>e-infrastructures: how do we know and understand them? Strategic ethnography and the biography of artefacts</article-title>
          <source>Comput Support Cooperative Work (CSCW)</source>
          <year>2010</year>
          <volume>19</volume>
          <issue>6</issue>
          <fpage>521</fpage>
          <lpage>556</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://link.springer.com/article/10.1007/s10606-010-9129-4"/>
          </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>Cresswell</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Sheikh</surname>
              <given-names>A</given-names>
            </name>
          </person-group>
          <article-title>Developing and applying a formative evaluation framework for health information technology implementations: qualitative investigation</article-title>
          <source>J Med Internet Res</source>
          <year>2020</year>
          <volume>22</volume>
          <issue>6</issue>
          <fpage>e15068</fpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jmir.org/2020/6/e15068/"/>
          </comment>
          <pub-id pub-id-type="doi">10.2196/15068</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>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Pollock</surname>
              <given-names>N</given-names>
            </name>
          </person-group>
          <article-title>Research commentary—Moving beyond the single site implementation study: how (and why) we should study the biography of packaged enterprise solutions</article-title>
          <source>Inform Syst Res</source>
          <year>2012</year>
          <volume>23</volume>
          <issue>1</issue>
          <fpage>1</fpage>
          <lpage>22</lpage>
          <pub-id pub-id-type="doi">10.1287/isre.1110.0352</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>Fereday</surname>
              <given-names>J</given-names>
            </name>
            <name name-style="western">
              <surname>Muir-Cochrane</surname>
              <given-names>E</given-names>
            </name>
          </person-group>
          <article-title>Demonstrating rigor using thematic analysis: a hybrid approach of inductive and deductive coding and theme development</article-title>
          <source>Int J Qual Methods</source>
          <year>2006</year>
          <volume>5</volume>
          <issue>1</issue>
          <fpage>80</fpage>
          <lpage>92</lpage>
          <pub-id pub-id-type="doi">10.1177/160940690600500107</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>Aanestad</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Jensen</surname>
              <given-names>T</given-names>
            </name>
          </person-group>
          <article-title>Building nation-wide information infrastructures in healthcare through modular implementation strategies</article-title>
          <source>J Strateg Inform Syst</source>
          <year>2011</year>
          <volume>20</volume>
          <issue>2</issue>
          <fpage>161</fpage>
          <lpage>176</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/S0963868711000229?via%3Dihub"/>
          </comment>
          <pub-id pub-id-type="doi">10.1016/j.jsis.2011.03.006</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>Sahay</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Monteiro</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Aanestad</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Configurable politics and asymmetric integration: health e-infrastructures in India</article-title>
          <source>J Assoc Inform Syst</source>
          <year>2009</year>
          <volume>10</volume>
          <issue>5</issue>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://aisel.aisnet.org/jais/vol10/iss5/4"/>
          </comment>
          <pub-id pub-id-type="doi">10.17705/1jais.00198</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref23">
        <label>23</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Hanseth</surname>
              <given-names>O</given-names>
            </name>
            <name name-style="western">
              <surname>Monteiro</surname>
              <given-names>E</given-names>
            </name>
            <name name-style="western">
              <surname>Hatling</surname>
              <given-names>M</given-names>
            </name>
          </person-group>
          <article-title>Developing information infrastructure: the tension between standardization and flexibility</article-title>
          <source>Sci Technol Hum Values</source>
          <year>1996</year>
          <volume>21</volume>
          <issue>4</issue>
          <fpage>407</fpage>
          <lpage>426</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.jstor.org/stable/690088"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref24">
        <label>24</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Williams</surname>
              <given-names>R</given-names>
            </name>
            <name name-style="western">
              <surname>Edge</surname>
              <given-names>D</given-names>
            </name>
          </person-group>
          <article-title>The social shaping of technology</article-title>
          <source>Res Policy</source>
          <year>1996</year>
          <volume>25</volume>
          <issue>6</issue>
          <fpage>865</fpage>
          <lpage>899</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://www.sciencedirect.com/science/article/pii/0048733396008852"/>
          </comment>
        </nlm-citation>
      </ref>
      <ref id="ref25">
        <label>25</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Lie</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sørensen</surname>
              <given-names>KH</given-names>
            </name>
          </person-group>
          <source>Making Technology Our Own? Domesticating Technology into Everyday Life</source>
          <year>1996</year>
          <publisher-loc>Oslo, Norway</publisher-loc>
          <publisher-name>Scandinavian University Press</publisher-name>
        </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>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>
          <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>
          <pub-id pub-id-type="pii">mzm042</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>Jarrahi</surname>
              <given-names>M</given-names>
            </name>
            <name name-style="western">
              <surname>Sawyer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Erickson</surname>
              <given-names>I</given-names>
            </name>
          </person-group>
          <article-title>Digital assemblages, information infrastructures, and mobile knowledge work</article-title>
          <source>J Inform Technol</source>
          <year>2021</year>
          <volume>37</volume>
          <issue>3</issue>
          <fpage>230</fpage>
          <lpage>249</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1177/02683962211050943"/>
          </comment>
          <pub-id pub-id-type="doi">10.1177/02683962211050943</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref28">
        <label>28</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Henke</surname>
              <given-names>C</given-names>
            </name>
            <name name-style="western">
              <surname>Sims</surname>
              <given-names>B</given-names>
            </name>
          </person-group>
          <source>Repairing Infrastructures: The Maintenance of Materiality and Power</source>
          <year>2020</year>
          <publisher-loc>Cambridge, MA</publisher-loc>
          <publisher-name>The Mit Press</publisher-name>
        </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>Jackson</surname>
              <given-names>SJ</given-names>
            </name>
            <name name-style="western">
              <surname>Kang</surname>
              <given-names>L</given-names>
            </name>
          </person-group>
          <article-title>Breakdown, obsolescence and reuse</article-title>
          <year>2014</year>
          <conf-name>CHI '14: Proceedings of the SIGCHI Conference on Human Factors in Computing Systems</conf-name>
          <conf-date>April 26-May 1, 2014</conf-date>
          <conf-loc>Toronto, Ontario, Canada</conf-loc>
          <fpage>449</fpage>
          <lpage>458</lpage>
          <pub-id pub-id-type="doi">10.1145/2556288.2557332</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref30">
        <label>30</label>
        <nlm-citation citation-type="journal">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Sawyer</surname>
              <given-names>S</given-names>
            </name>
            <name name-style="western">
              <surname>Crowston</surname>
              <given-names>K</given-names>
            </name>
            <name name-style="western">
              <surname>Wigand</surname>
              <given-names>R</given-names>
            </name>
          </person-group>
          <article-title>Digital assemblages: evidence and theorising from the computerisation of the US residential real estate industry</article-title>
          <source>New Technol Work Employ</source>
          <year>2014</year>
          <volume>29</volume>
          <issue>1</issue>
          <fpage>40</fpage>
          <lpage>56</lpage>
          <comment>
            <ext-link ext-link-type="uri" xlink:type="simple" xlink:href="https://doi.org/10.1111/ntwe.12020"/>
          </comment>
          <pub-id pub-id-type="doi">10.1111/ntwe.12020</pub-id>
        </nlm-citation>
      </ref>
      <ref id="ref31">
        <label>31</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Marchionini</surname>
              <given-names>G</given-names>
            </name>
          </person-group>
          <article-title>Foundations for personal information infrastructures: information-seeking knowledge, skills, and attitudes</article-title>
          <source>Information Seeking in Electronic Environments</source>
          <year>1995</year>
          <publisher-loc>Cambridge, UK</publisher-loc>
          <publisher-name>Cambridge University Press</publisher-name>
          <fpage>61</fpage>
          <lpage>75</lpage>
        </nlm-citation>
      </ref>
      <ref id="ref32">
        <label>32</label>
        <nlm-citation citation-type="book">
          <person-group person-group-type="author">
            <name name-style="western">
              <surname>Norman</surname>
              <given-names>DA</given-names>
            </name>
          </person-group>
          <source>Things that Make Us Smart: Defending Human Attributes in the Age of the Machine</source>
          <year>1993</year>
          <publisher-loc>Reading, MA</publisher-loc>
          <publisher-name>Addison-Wesley Pub Co</publisher-name>
        </nlm-citation>
      </ref>
    </ref-list>
  </back>
</article>
