Precision dosing to avoid adverse drug reactions

Thomas M. Polasek, Carl M.J. Kirkpatrick, Amin Rostami-Hodjegan

Research output: Contribution to journalEditorial

2 Citations (Scopus)

Abstract

Adverse drug reactions (ADRs) have traditionally been managed by trial and error, adjusting drug and dose selection reactively following patient harm. With an improved understanding of ADRs, and the patient characteristics that increase susceptibility, precision medicine technologies enable a proactive approach to ADRs and support clinicians to change prescribing accordingly. This commentary revisits the famous pharmacology–toxicology continuum first postulated by Paracelsus 500 years ago and explains why precision dosing is needed to help avoid ADRs in modern clinical practice. Strategies on how to improve precision dosing are given, including more research to establish better precision dosing targets in the cases of greatest need, easier access to dosing instructions via e-prescribing, improved monitoring of patients with novel biomarkers of drug response, and further application of model-informed precision dosing.

Original languageEnglish
Pages (from-to)1-6
Number of pages6
JournalTherapeutic Advances in Drug Safety
Volume10
DOIs
Publication statusPublished - 11 Dec 2019
Externally publishedYes

Bibliographical note

Creative Commons Non Commercial CC BY-NC: This article is distributed under the terms of the Creative Commons Attribution-NonCommercial 4.0 License
(http://www.creativecommons.org/licenses/by-nc/4.0/) which permits non-commercial use, reproduction and distribution of the work without further permission provided the original work is attributed as specified on the SAGE and Open Access pages (https://us.sagepub.com/en-us/nam/open-access-at-sage).

Keywords

  • adverse drug reactions
  • medication safety
  • model-informed precision dosing
  • precision dosing
  • precision medicine

Fingerprint Dive into the research topics of 'Precision dosing to avoid adverse drug reactions'. Together they form a unique fingerprint.

Cite this