ER vs. IR [Design Issues]

posted by Helmut Homepage – Vienna, Austria, 2019-12-18 16:33 (1762 d 20:54 ago) – Posting: # 20994
Views: 3,895

Hi Dan,

nice that you post again. ;-)

❝ if the recommended dosage regimen of the IR as per product monograph IR is to be given every 4 hrs then this means that higher doses have either a safety issue or the dose/effect relationship is in disfavor of higher doses. In this case AUC alone does not matter. Consequently, a regulatory body will reject the study


I disagree. John was asking for ER (once a day) vs. IR (twice a day with τ 4 hours). In Europe that’s a hybrid application (dunno the US term; 505(b)2?). Quite common, if no ER exists and should be development for various reasons (better compliance, convenience for the patient).
Say the single IR doses are 10 mg and the ER 20 mg. It might well be that the originator’s IR is approved for up to 40 mg given a single doses.1
In the comparison AUC is primary. Whether the first/second peak of the ER has to match the Cmax-values of the IR administrations (and to which degree) is another story. I have seen assessing both but with expanded limits, non-superiority2 (to assess potential dose-dumping), only the global Cmax, and even just a descriptive analysis. Which one is the right approach depends on the drug, of course.


  1. Real example. Don’t ask me for the drug.
  2. Preferred in the EMA’s MR-GL (together with non-inferiority of Cτ = the bracketing approach). See an example in the vignette of PowerTOST.

Dif-tor heh smusma 🖖🏼 Довге життя Україна! [image]
Helmut Schütz
[image]

The quality of responses received is directly proportional to the quality of the question asked. 🚮
Science Quotes

Complete thread:

UA Flag
Activity
 Admin contact
23,258 posts in 4,886 threads, 1,671 registered users;
74 visitors (0 registered, 74 guests [including 7 identified bots]).
Forum time: 14:27 CEST (Europe/Vienna)

Tortured data will confess to anything.    Fredric Menger

The Bioequivalence and Bioavailability Forum is hosted by
BEBAC Ing. Helmut Schütz
HTML5