Appropriate wording for a protocol [Two-Stage / GS Designs]

posted by Helmut Homepage – Vienna, Austria, 2019-09-09 23:27 (441 d 21:07 ago) – Posting: # 20567
Views: 4,977

Hi ElMaestro,

» » 1. Should we include the information that evaluation after stage 1 completion should be performed assuming GMR=0.95?
» I would do so.

So would I.

» » 2. Should we describe the maximum number of subjects who can be included in whole or in stage 2?
» I would only put a cap on it if you can refer to simulations having done exactly so (having done so in exactly your way of capping).

From a regulatory perspective this is not necessary. Any futility rule (like max. n2) decreases the chance to show BE if compared to a published method without one. Hence, if the type I error was controlled in a method without a futility rule, the TIE will always be lower with a futility rule. However, if a futility rule is too strict, you may shoot yourself in the foot since power might be compromised. To check that, sim’s are a good idea indeed.

» » 3. Any other information that should be clearly stated in order to be accurate and to satisfy regulatory authorities?
» Exact decision tree, and exact values for alphas, desired power level, and power being calculated using GMR=0.95.


» » 4. What if BE criteria are met after stage 1, but estimated power is too low (e.g. 30%)?
» It is not a crime to be lucky.

Absolutely. As one of the grumpy old men: Forget power, doesn’t matter.

Dif-tor heh smusma 🖖
Helmut Schütz

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

Complete thread:

 Admin contact
21,206 posts in 4,425 threads, 1,481 registered users;
online 5 (0 registered, 5 guests [including 4 identified bots]).
Forum time: Tuesday 19:35 CET (Europe/Vienna)

All we know about the world teaches us that the effects of A and B
are always different—in some decimal place—for any A and B.
Thus asking “are the effects different?” is foolish.    John W. Tukey

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