nvs
☆    

India,
2007-11-30 08:24
(6779 d 17:05 ago)

Posting: # 1345
Views: 4,638
 

 QCs in a run [Bioanalytics]

Dear all forum members and HS

Goodmorning.

I have some doubts regarding the IS variation in QC samples.

If the specification for the sampels in the run is, the IS response should be with in 50% of the average IS repsonse of the accepted calibration curve standards.

The specification for the QCs in a run is, 50% of QCs at each level should pass the accuracy specification (+/- 15%)

1) In a run one of the QC has failed in the accuracy acceptence i.e., out of 15% accuracy, and the other is meeting the accuracy specification, but the IS response of the QC is not within the +/- 50% specification.

Now , whether the run can be accepted, since one of the QC is meeting the specification. Or, since the passed QC is not meeting the IS acceptance limit, the run has to be declered as failed run?

2) What is the best practice for the IS variation specification.

Means, considering the IS responses only from the accepted CCs, or from the aceepted CCs and all the QCs in a run.

Thanks in advance, :-)

nvs.
Helmut
★★★
avatar
Homepage
Vienna, Austria,
2007-11-30 13:54
(6779 d 11:35 ago)

@ nvs
Posting: # 1346
Views: 3,622
 

 IS variation

Dear nvs!

❝ If the specification for the sampels in the run is, the IS response should

❝ be with in 50% of the average IS repsonse of the accepted calibration curve

❝ standards.


Interesting approach; did you follow one of Ohlbe's suggestions?

❝ The specification for the QCs in a run is, 50% of QCs at each level should

❝ pass the accuracy specification (+/- 15%)


OK, this point is the commonly accepted procedure according to FDA's guideline and the consensus papers of the 'Arlington Conferences I-III' (for references: I-II and III).

❝ 1) In a run one of the QC has failed in the accuracy acceptence i.e.,

❝ out of 15% accuracy, and the other is meeting the accuracy specification,

❝ but the IS response of the QC is not within the +/- 50% specification.

❝ Now, whether the run can be accepted, since one of the QC is meeting the

❝ specification. Or, since the passed QC is not meeting the IS acceptance

❝ limit, the run has to be declered as failed run?


IS variation is not a topic in the guideline. But since you have set a limit in your method, both QCs at the same level are rejected - and therefore the run is not valid.

❝ 2) What is the best practice for the IS variation specification.

❝ Means, considering the IS responses only from the accepted CCs, or from

❝ the aceepted CCs and all the QCs in a run.


First have a look at this thread.
Personally I still don't get the point, because the IS should protect the analyst against errors in volume transfers. If e.g., 50% of the solution are spilled in one of the sample preparation steps (after IS addition), the analyte/IS ratio will not change anyway.
Of course Ohlbe's argument about laking sensitivity close to the LLOQ are strong ones. One the other hand I have some doubts whether such a cut-off (50% of whatsoever) really would improve the credibility of our analyses.
Nobody would bother if e.g., a vial was broken at centrifugation and the sample simply is missing. AUC is pretty robust, and if the sample is close to tmax for sure a couple of others in the same section of the profile are available. ;-)
IMHO once you set a limit on the IS response - agreeing with Ohlbe - you must apply this rule for all samples (calibrators, QCs, and unknowns). Most likely you will have to face repeated runs - but what for?

Dif-tor heh smusma 🖖🏼 Довге життя Україна! [image]
Helmut Schütz
[image]

The quality of responses received is directly proportional to the quality of the question asked. 🚮
Science Quotes
UA Flag
Activity
 Admin contact
23,655 posts in 4,993 threads, 1,570 registered users;
138 visitors (0 registered, 138 guests [including 52 identified bots]).
Forum time: 02:30 CEST (Europe/Vienna)

Competence, like truth, beauty and contact lenses,
is in the eye of the beholder.    Laurence J. Peter

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