alpha... where is omega? [Power / Sample Size]

posted by Astea – Russia, 2018-02-02 22:45 (2634 d 13:25 ago) – Posting: # 18335
Views: 21,995

Dear Smart People!

I am suffering trying to understand the problems and perspectives of alpha-adjustment.
Wherever I look I see TIE inflation...
For HVD:For well-known adaptive designs (Potvin, Xu...) TIE also behaves badly...
TIE may be also inflated by evaluating different methods for PK metrics (when one of them turns to be overpowered - as in the case of adaptive design or different CI for two Cmax and AUC).
I suspect TIE will be also inflated in studies of NTDs also (by using FDA approach or by using different confidence limits for two metrics).
Now you talk about higher-order design and dose-proportional studies...

So... Are there any ways to deal with it excepting the bright idea of iteratively adjusted alpha? While looking through the literature I've found only some suggestions of modificating ABE (with new procedures or nonlinear CI limits) or alternatives for ABE (like GSD or Two-stage designs)...

  1. Knahl SIE, Lang B, Fleischer F, Kieser M., A comparison of group sequential and fixed sample size designs for bioequivalence trials with highly variable drugs, J Clin Pharmacol, 2018, doi:10.1007/s00228-018-2415-7.
  2. Molins E., Cobo E., Ocaña J. Two-stage designs versus European scaled average designs in bioequivalence studies for highly variable drugs: Which to choose? Statistics in Medicine, V. 36, I. 30, pp 4777–4788, 2017 doi:10.1002/sim.7452.

"Being in minority, even a minority of one, did not make you mad"

Complete thread:

UA Flag
Activity
 Admin contact
23,424 posts in 4,927 threads, 1,671 registered users;
31 visitors (0 registered, 31 guests [including 10 identified bots]).
Forum time: 13:10 CEST (Europe/Vienna)

The combination of some data and an aching desire
for an answer does not ensure that a reasonable answer
can be extracted from a given body of data.    John W. Tukey

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