<!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">Pharmacophore</journal-id>
      <journal-id journal-id-type="publisher-id">pharmacophorejournal.com</journal-id>
      <journal-id journal-id-type="publisher-id">Pharmacophore</journal-id>
      <journal-title-group>
        <journal-title>Pharmacophore</journal-title>
      </journal-title-group>
      <issn pub-type="epub">2229-5402</issn>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="publisher-id">pharmacophorejournal.com-6964</article-id>
      <article-id pub-id-type="doi">10.51847/eFLYQytugp</article-id>
      <article-categories>
        <subj-group subj-group-type="heading">
          <subject>Original research</subject>
        </subj-group>
      </article-categories>
      <title-group>
        <article-title>A Pharmaceutical Data Mesh That Preserves Ownership while Enabling Semantic Interoperability, Model Development, and Evidence Reuse</article-title>
      </title-group>
                    <contrib-group>
                      <contrib contrib-type="author">
              <name>
                <surname>Davis</surname>
                <given-names>William</given-names>
              </name>
                              <xref rid="aff1" ref-type="aff">1</xref>
                                                            <xref rid="cor1" ref-type="corresp" />
                          </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Kowalski</surname>
                <given-names>Anna</given-names>
              </name>
                              <xref rid="aff2" ref-type="aff">2</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Brown</surname>
                <given-names>Hannah</given-names>
              </name>
                              <xref rid="aff3" ref-type="aff">3</xref>
                                        </contrib>
                      <contrib contrib-type="author">
              <name>
                <surname>Collins</surname>
                <given-names>Jeffrey</given-names>
              </name>
                              <xref rid="aff4" ref-type="aff">4</xref>
                                        </contrib>
                  </contrib-group>
                  <aff id="aff1">
            <label>1</label>Department of Pharmaceutical Data Mesh and Ownership, College of Pharmacy, Pennsylvania State University, University Park, United States.
          </aff>
                  <aff id="aff2">
            <label>2</label>Department of Semantic Interoperability and Model Development, Faculty of Pharmaceutical Sciences, University of Wrocław, Wrocław, Poland.
          </aff>
                  <aff id="aff3">
            <label>3</label>Department of Evidence Reuse and Data Governance, Faculty of Pharmacy, McGill University, Montreal, Canada.
          </aff>
                  <aff id="aff4">
            <label>4</label>Department of Federated Data Architecture, Faculty of Pharmacy, University of Sydney, Sydney, Australia.
          </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="william.davis@psu.edu">william.davis@psu.edu</email>
                          </corresp>
          </author-notes>
                    <pub-date pub-type="epub">
        <day>28</day>
        <month>06</month>
        <year>2026</year>
      </pub-date>
      <volume>16</volume>
      <issue>3</issue>
      <fpage>96</fpage>
      <lpage>105</lpage>
      <permissions>
        <copyright-statement>
          Copyright: &#x000a9; 2026 Pharmacophore
        </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>Pharmaceutical research increasingly depends on the combined interpretation of chemical, biological, preclinical, clinical, safety, manufacturing, and real-world evidence. These data are commonly distributed across scientific functions, technology platforms, legal jurisdictions, and stages of the product lifecycle. Centralized architectures attempt to overcome this fragmentation by consolidating data into shared repositories, but consolidation alone does not preserve scientific context, resolve semantic incompatibility, establish fitness for reuse, or reconcile competing ownership and access obligations. This original pharmaceutical data architecture article develops a proposed ownership-preserving pharmaceutical data mesh in which scientific domains remain accountable for versioned data products while participating in federated semantic, lineage, access, computational, and governance services. The approach integrates evidence from pharmaceutical data science, FAIR data practice, biomedical interoperability, distributed computation, provenance engineering, model governance, and translational implementation. Its principal contribution is a conceptual architecture that distinguishes physical data location from semantic interoperability and separates data availability from scientific suitability. Domain-owned data products are connected through explicit semantic contracts, distributed evidence-lineage records, federated stewardship, policy-aware access control, governed compute-to-data services, and qualified model-reuse mechanisms. The architecture is evaluated through multiple dimensions rather than a single performance measure, including semantic validity, lineage completeness, policy correctness, reproducibility, model transportability, evidence-reuse fidelity, and organizational sustainability. The proposal remains conceptual: it does not establish privacy guarantees, empirical superiority, regulatory acceptability, clinical utility, or deployment readiness. Its value lies in organizing the scientific and governance conditions under which pharmaceutical evidence may become reusable without being detached from its ownership, provenance, uncertainty, and intended context.</p>
      </abstract>
      <kwd-group>
                <kwd>Pharmaceutical data architecture</kwd>
                <kwd>Data mesh</kwd>
                <kwd>Domain ownership</kwd>
                <kwd>Data products</kwd>
                <kwd>Semantic interoperability</kwd>
                <kwd>Evidence lineage</kwd>
              </kwd-group>
    </article-meta>
  </front>
</article>