LLOQ ≤5% of expected or observed Cmax? [Bioanalytics]

posted by Helmut Homepage – Vienna, Austria, 2018-10-18 10:28 (822 d 18:31 ago) – Posting: # 19468
Views: 2,999

Hi Beholder,

first of all congratulations for mastering the forum’s tricky syntax of nested lists. ;-)

» […] I have revealed that EEU BEQ GL has interesting note in validation chapter which is not presented in EU BEQ GL, namely:
» “[…] The LLOQ cannot be higher than 5% of Cmax (the minimum Cmax value from the entire sample of subjects) ).”

AFAIK, the Russian language leaves a lot of space for interpretation. Is the common meaning of »не должен« really equivalent to “cannot” or “must not”? Since I don’t speak Russian, I have to rely on A(un)I: Google, Yandex, and Bing translate it as “should not” – which is exactly the phrase used in the EMA’s GL.

If it is mandatory (your #1), very stupid. #2 is a show-stopper.

I can only tell you what is done in studies for the EMA. Use an estimate of the lowest expected Cmax and base the LLOQ on it. Depending on the expected variability CROs commonly opt for 2% or even 1% of the average Cmax. Nerds like me work with modeling, stuff like that (replace t½ with Cmax), or simulations. Of course, if individual data are available (pilot or other studies), better. Never saw revalidation. If you are cautious, exclude the subject. If that doesn’t occur too often, the loss in power is small.

Dif-tor heh smusma 🖖
Helmut Schütz
[image]

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

Complete thread:

Activity
 Admin contact
21,303 posts in 4,441 threads, 1,487 registered users;
online 4 (0 registered, 4 guests [including 4 identified bots]).
Forum time: Monday 05:00 UTC (Europe/Vienna)

I believe there is no philosophical high-road in science,
with epistemological signposts. No, we are in a jungle
and find our way by trial and error,
building our road behind us as we proceed.    Max Born

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