About this event
Foundations of a Sustainable, High-Performing QA Program
Learn how to build a sustainable quality assurance program that strengthens confidence in laboratory data. This session explores method performance, analyst competency, precision, accuracy, control charting, trending, root cause analysis, and certified reference materials. Discover practical strategies to identify issues early, improve consistency, and support long term analytical performance.
Download
Presented by
Christy Abbas, PhD
Sr. Product Marketing Manager
Waters ERA
Key Learning Topics
- Build a more effective and sustainable laboratory QA program.
- Use precision, accuracy, and control charting to improve data quality and identify issues early.
- Apply root cause analysis and certified reference materials to strengthen performance and corrective actions.
Who should watch
- Quality Assurance Managers
- Quality Control (QC) Managers
- Analytical Chemists
- Laboratory Scientosts, Supevisors, and Managers
Coming Soon.
Question 1:
I have a method that requires a spike sample for calculation in addition to the unspiked sample for accuracy validation. We are spiking a placebo. Do we need to perform a double spike to align with the sample prep?
Answer 1:
I would say no. You generally do not need to perform a double spike on a placebo, provided your calculation accounts for that matrix background. And that is with the caveat of unless your standard SOP specifically mandates replicating every volume, that additional step, regardless of the matrix analyte, a standard single spike will do the job.
Question 2:
Do you have a reference that refers to the frequency of the ICV or check standards? Are there different intervals for these?
Answer 2:
That's a great question. The frequency really depends on the method and any requirements your lab operates under. There isn't one universal document that says run an ICV or check standard every X samples. I'd start by looking at your method and your lab's QA/QC program and any project-specific requirements. In some cases, those documents will be very specific about how often checks need to be run. As a general example, many labs run check standards at the beginning and end of a batch and then periodically throughout the run. And so, I guess the short answer is that the frequency is usually driven by the method, your quality system, or any regulatory or project requirements. And that's the best place to look when determining what's appropriate for your situation.