TRV-2026-1794Certified recordPeer-reviewed

Artificial intelligence in pharmacy and pharmaceutical sciences: Research output, trends, and thematic priorities - A descriptive analysis of web of science-indexed publications (2010-2025)

Background: Artificial intelligence (AI) is rapidly transforming pharmacy and pharmaceutical sciences (PPS), yet the evolution, research priorities, and global landscape of AI-related research within this field have not been comprehensively characterized. Methods: A descriptive bibliometric analysis of publications indexed in the Web of Science Core Collection was conducted for studies published between 2010 and November 9, 2025. Publication trends, document characteristics, journals, publishers, countries, auth…

Science · Problem Space — documented harm · certified 2026-10-18 · v1 · article view · machine-readable

Current reading — problem

Research on AI in pharmacy is heavily weighted toward computational drug design, leaving clinical decision support, pharmacovigilance, and manufacturing comparatively underrepresented.

What this doesn’t fix

The study is a descriptive bibliometric analysis of one database's publications and characterizes research output, not the real-world clinical effectiveness of AI in pharmacy.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1794, v1: “Artificial intelligence in pharmacy and pharmaceutical sciences: Research output, trends, and thematic priorities - A descriptive analysis of web of science-indexed publications (2010-2025).” Truvace, 2026-10-18. /record/TRV-2026-1794 (accessed at citation time). sha256 8fd76220bf138353…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv18fd76220bf13…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1794 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.