How to understand what is guilty? [Study As­sess­ment]

posted by ElMaestro  – Denmark, 2016-07-31 01:15 (3612 d 01:42 ago) – Posting: # 16530
Views: 9,960

Hi BE-Proff,

❝ Saying, I have conducted a BE-study which doesn't show bioequivalence.


Yes that can happen.

❝ Is it possible to understand what was the reason of this failure - poor formulation or incorrect time points in the protocol?


In practice, you often can't directly tell what caused the problem.

A few rules of thumb:
1. If the CI is completely outside the acceptance range (e.g. 54.66% - 77.19%) then you can say you have shown bioinequivalence. In this case it is statistically a formulation problem. At least.
2. If the CI is not within the acceptance range but the point estimate is "close" to 1.0, then your trial was most likely underpowered, and you would in this case be justified in repeating it.
3. If your CI is not within the acceptance range and point estimate is far from one, then there is really no good way of telling what has happened or how to remedy it. Perhaps you can repeat it, perhaps you shouldn't, it will always be a difficult discussion.

It is pt. 3 that often happens, unfortunately.

Look also at predose concentrations, subjects lacking AUCinf values, protocol deviations, failed analytical runs. These may indicate a practical issue. I believe there are people much more experienced than I who can write entire books about what to do when a study fails and when to repeat it.
I hope the few points above are helpful.

Let's hear your numbers and some background of your failure, please.

Pass or fail!
ElMaestro

Complete thread:

UA Flag
Activity
 Admin contact
23,655 posts in 4,993 threads, 1,570 registered users;
160 visitors (0 registered, 160 guests [including 33 identified bots]).
Forum time: 02:58 CEST (Europe/Vienna)

Science is simply common sense at its best that is,
rigidly accurate in observation, and
merciless to fallacy in logic.    Thomas Henry Huxley

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