<!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-1256</article-id>
      <article-id pub-id-type="doi">10.51847/KDzAs5zVzk</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original research</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>Keeping the Patient Visible when Pharmacy Services Become Data-Driven</article-title>
      </title-group>
                    <contrib-group>
                      <contrib contrib-type="author">
              <name>
                <surname>Hariri</surname>
                <given-names>Youssef</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                                            <xref rid="cor1" ref-type="corresp" />
                          </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Nasser</surname>
                <given-names>Hassan</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Zahra</surname>
                <given-names>Fatima</given-names>
              </name>
                              <xref rid="aff2" ref-type="aff">2</xref>
                                        </contrib>
                  </contrib-group>
                  <aff id="aff1">
            <label>1</label>Department of Patient-Centered Pharmacy Informatics, Faculty of Pharmacy, Mohammed V University, Rabat, Morocco.
          </aff>
                  <aff id="aff2">
            <label>2</label>Department of Data-Driven Care and Patient Visibility, Faculty of Pharmacy, University of Casablanca, Casablanca, Morocco.
          </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="youssef.hariri@um5.ac.ma">youssef.hariri@um5.ac.ma</email>
                          </corresp>
          </author-notes>
                    <pub-date pub-type="epub">
        <day>30</day>
        <month>06</month>
        <year>2025</year>
      </pub-date>
      <volume>16</volume>
      <issue>2</issue>
      <fpage>53</fpage>
      <lpage>61</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>Data-driven pharmacy services can combine electronic medication records, patient-generated information, clinical decision support, and artificial intelligence to improve the organization and interpretation of medication-related data. However, a technically comprehensive record may still obscure the person whose treatment is being considered. Important explanations, preferences, practical capabilities, and social constraints may be absent, outdated, poorly interpreted, or disconnected from the eventual decision. This article develops an original Patient-Visibility Framework for examining whether the patient remains meaningfully represented when pharmacy services become data-driven. Patient visibility is proposed as a decision property arising when relevant context is captured with provenance, interpreted for the current medication task, open to patient correction, discussed when uncertainty or discordance exists, connected transparently to professional action, and updated over time. The framework organizes visibility through four interacting layers: narrative, preference, capability, and social context. These layers enter a sociotechnical pathway comprising context capture, interpretation, pharmacist–patient dialogue, medication action, follow-up, and accountability. Proposed failure modes include patient–record substitution, narrative flattening, preference freezing, capability misclassification, context staleness, unequal missingness, workflow bypass, and responsibility diffusion. Evaluation therefore requires more than model performance. Construct validity, representational fidelity, workflow feasibility, medication-safety consequences, patient experience, equity, governance, and temporal validity must be examined separately. The framework is a conceptual and evaluative contribution rather than a validated instrument, clinical protocol, or deployment standard. Its categories, relationships, transition gates, and proposed indicators require empirical testing across pharmacy tasks, populations, technologies, and care settings.</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>