<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD with MathML3 v1.3 20210610//EN" "JATS-archivearticle1-3-mathml3.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink"
  dtd-version="1.3" xml:lang="en" article-type="research-article">
  <?DTDIdentifier.IdentifierValue -//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN?>
  <?DTDIdentifier.IdentifierType public?>
  <?SourceDTD.DTDName JATS-journalpublishing1.dtd?>
  <?SourceDTD.Version 1.2?>
  <?ConverterInfo.XSLTName jats2jats3.xsl?>
  <?ConverterInfo.Version 1?>
  <?properties open_access?>
  <front>
    <journal-meta>
      <journal-id journal-id-type="iso-abbrev">Arch Pharm Pract</journal-id>
      <journal-id journal-id-type="publisher-id">archivepp.com</journal-id>
      <journal-id journal-id-type="publisher-id">Arch Pharm Pract</journal-id>
      <journal-title-group>
        <journal-title>Archives of Pharmacy Practice</journal-title>
      </journal-title-group>
      <issn pub-type="epub">2320-5210</issn>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">archivepp.com-1250</article-id>
      <article-id pub-id-type="doi">10.51847/lgc8J2bCwU</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original research</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Where Should Automation Stop in Community Pharmacy? A Boundary Model for Delegating Medication Tasks</article-title>
      </title-group>
                    <contrib-group>
                      <contrib contrib-type="author">
              <name>
                <surname>Müller</surname>
                <given-names>Hans</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                                            <xref rid="cor1" ref-type="corresp" />
                          </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Schmidt</surname>
                <given-names>Anna</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Weber</surname>
                <given-names>Thomas</given-names>
              </name>
                              <xref rid="aff2" ref-type="aff">2</xref>
                                        </contrib>
                  </contrib-group>
                  <aff id="aff1">
            <label>1</label>Department of Pharmacy Automation and Task Delegation, Faculty of Pharmaceutical Sciences, University of Bonn, Bonn, Germany.
          </aff>
                  <aff id="aff2">
            <label>2</label>Department of Clinical Pharmacy and Digital Boundaries, Faculty of Pharmacy, LMU Munich, Munich, Germany.
          </aff>
                          <author-notes>
            <corresp id="cor1">
              <bold>Address for correspondence:</bold> Prof. Wael Abu Dayyih, Department of
              Pharmaceutical Chemistry, Faculty of Pharmacy, Mutah University, Al-Karak 61710, Jordan.
                              E-mail: <email xlink:href="hans.mueller@uni-bonn.de">hans.mueller@uni-bonn.de</email>
                          </corresp>
          </author-notes>
                    <pub-date pub-type="epub">
        <day>31</day>
        <month>03</month>
        <year>2025</year>
      </pub-date>
      <volume>16</volume>
      <issue>1</issue>
      <fpage>50</fpage>
      <lpage>59</lpage>
      <permissions>
        <copyright-statement>
          Copyright: &#x000a9; 2026 Archives of Pharmacy Practice
        </copyright-statement>
        <copyright-year>2026</copyright-year>
        <license>
          <ali:license_ref xmlns:ali="http://www.niso.org/schemas/ali/1.0/"
            specific-use="textmining" content-type="ccbyncsalicense">
            https://creativecommons.org/licenses/by-nc-sa/4.0/</ali:license_ref>
          <license-p>This is an open access journal, and articles are distributed under the terms of
            the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License, which allows
            others to remix, tweak, and build upon the work non-commercially, as long as appropriate
            credit is given and the new creations are licensed under the identical terms.</license-p>
        </license>
      </permissions>
      <abstract>
        <title>A<sc>BSTRACT</sc></title>
        <p>Automation in community pharmacy is often discussed as though medication tasks can be transferred to digital systems whenever adequate technical performance is demonstrated. This framing overlooks differences in clinical consequence, uncertainty, contextual dependence, patient vulnerability, error detectability, and the possibility of correcting an inappropriate action. This article develops an original, non-empirical delegation-boundary model for determining when automation may proceed, when professional review is required, and when delegation should stop. Delegability is defined as a conditional property of a specific medication-task instance rather than an inherent characteristic of an entire service, technology, or occupational role. The proposed model assesses six interacting dimensions: clinical consequence, ambiguity, reversibility, contextual dependence, patient vulnerability, and detectability of error. These dimensions inform three conditional states. Proceed permits bounded automated execution under defined safeguards; Escalate requires review by an authorized professional before action; and Stop retains human control because necessary context, recovery capacity, accountability, or safety conditions are insufficient. The architecture also includes task specification, uncertainty communication, professional authority, monitoring, incident review, and boundary reassessment. Application is intended to distinguish automatable components from judgment-dependent components within dispensing, verification, counselling, and follow-up rather than classify whole services as automatable or non-automatable. Empirical evaluation would require task-specific technical validation, workflow simulation, human-factors assessment, medication-safety analysis, patient and equity evaluation, external validation, and lifecycle monitoring. The model is a proposed conceptual synthesis, not a clinical recommendation, legal standard, validated scoring system, or deployment-ready framework. Its principal contribution is to reposition pharmacy automation as a conditional delegation decision requiring evidence about both system performance and the consequences of transferring professional work.</p>
      </abstract>
      <kwd-group>
                <kwd>Digital pharmacy</kwd>
                <kwd>Artificial intelligence</kwd>
                <kwd>Pharmacy practice</kwd>
                <kwd>Medication safety</kwd>
                <kwd>Human–AI collaboration</kwd>
                <kwd>Clinical decision support</kwd>
              </kwd-group>
    </article-meta>
  </front>
</article>