Loss of power etc. [Design Issues]

posted by ElMaestro  – Denmark, 2016-03-29 02:16 (3280 d 21:12 ago) – Posting: # 16151
Views: 23,831

Hi Astea,

❝ I understand clear that post-hoc power is set yours teeth on edge, but I'll take a chance to ask a question once more... There was a study with one drop-out. The results of that subject have not been included in the calculation. Recently the customers received a reply from regulatories to calculate aposteriory power and in the case of insufficient power present a plan for further clinical development of the drug.


It is an extremely unfortunate situation, and the regulators have clearly misunderstood the use of power, what it is and what it isn't. It is tempting to think that a study that passes the BE test must have a high power but this argument is just flawed. I am really sorry to hear you are caught in this mess.

❝ I estimated power with the help of power.TOST, based on obtained GMR and CV. The result is: power is less than 80% for AUC and more than 80% for Cmax. I remade the calculation including the drop-out: power for AUC is still less than 80%!


Very often companies that really do use posthoc power in their reporting do not use the observed GMR but rather plug in something like 0.95 or 1.00. This of course often give rise to higher power estimates, ones that arguably have little to do with anything. Perhaps that is your chance? Let me add, I do not in any way endorse such power calculation but then again I do not know what the regulator wants with a posthoc power calculation in the first place, so who knows?!?

Good luck, let us know how this ends, please.

Pass or fail!
ElMaestro

Complete thread:

UA Flag
Activity
 Admin contact
23,409 posts in 4,921 threads, 1,670 registered users;
17 visitors (0 registered, 17 guests [including 9 identified bots]).
Forum time: 22:29 CET (Europe/Vienna)

Facts are meaningless. You could use facts to prove
anything that’s even remotely true!    Homer Simpson

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