31 - GLP Protocols and Standard Operating Procedures (S17E5)

Hey there, welcome back for another deep dive
with us. Looks like we're getting into some seriously
detailed stuff this time around. You've brought
us a ton of information about GLP protocols and
standard operating procedures. FOPs, right? Those
are important in lab studies, from what I remember.
Yeah, you're right on the money there. And you've
given us some really interesting sources to work
with, too. I mean, we've got everything from
those official regulatory documents, like CFR
titles 21 and 58, which, you know, lay down the
law, so to speak, all the way to these super
practical YouTube videos that break down GMP
and GLP. Plus, we've even got some excerpts from
books on pharmaceutical manufacturing and just
quality management in general. It's a really
fascinating mix. It is. want to get into today
is how all these detailed protocols and procedures,
I mean, they get pretty intense, actually work
in practice. I'm especially interested in how
they guarantee that experiments are done the
same way every time, you know, consistently,
and that the data coming out of labs is solid
and reliable. And that's especially crucial in
fields where, like, messing up even a little
bit can have huge consequences. Absolutely. And
for you listening in, this isn't just some theoretical
exercise, right? This is about understanding
the very foundation of how we create trustworthy
scientific data, particularly in critical areas
like developing new drugs and making sure those
medicines are manufactured safely and effectively.
So we're going to break down these potentially
complex, maybe even intimidating topics and show
you why they matter so much. OK, so let's jump
right in. Why are these GLP protocols and SOPs
so incredibly detailed? Like seriously, when
you first lay eyes on them, it could be a little
overwhelming, right? Oh, I totally get it. They
can be a bit much at first glance, but there's
a very, very good reason for all that detail.
Think of it this way. These protocols and SOPs
are like. As one of the videos you provided put
it, written recipes, but super, super precise
ones. These aren't just loose guidelines, they're
like step -by -step instructions that dictate
exactly how every single part of the lab work
needs to be carried out. No room for interpretation.
So it's all about making sure that no matter
who's doing the experiment or even where they're
doing it, the process is always exactly the same.
Like down to the tiniest detail. Exactly. You
got it. That unwavering consistency in how things
are done is the absolute bedrock of generating
reliable data. You see, if you let even small
variations creep into the procedures, it can
throw off the results and then it becomes really
hard to be confident in what those results actually
mean. For someone like you, though, who really
wants to get a deep understanding, looking at
these super detailed procedures as a structured
approach to what can be incredibly complex tasks.
Well, that can actually make the whole thing
less daunting. It's like having a super detailed
roadmap to guide you through all those intricate
steps in the scientific process. That's a great
way to look at it. Like it's kind of like following
a precise set of instructions to build, I don't
know, a really complex piece of machinery. If
you skip steps or try to do things out of order,
the whole thing could malfunction or even, you
know, become dangerous. So what are the key building
blocks, the must haves when you're creating these
detailed blueprints? doing lab work. Well, creating
these protocols is a pretty involved process,
but if you look across all the sources you've
provided, a few key elements pop up again and
again. First up, and it's a big one, is method
validation. It's all about making absolutely
sure that the tests they're using in the lab
are scientifically sound and will give accurate
and reliable results consistently. So you can't
just like come up with a test in the lab and
start using it. There needs to be proof that
it actually does what it's supposed to do. Exactly,
you hit the nail on the head. Your sources highlight
several characteristics that are really important
when defining a validated method. First, you
need accuracy. That's how close the result you
get from the test is to the real true value of
what you're actually measuring. Scientists often
check this by adding a known amount of a substance
to a sample that's called fortification or spiking.
They see how well the test can detect and measure
that added substance. Then there's precision.
That's all about how consistent the results are
when you test the the same sample multiple times,
using the same conditions each time. It's usually
expressed as something called a percentage relative
standard deviation. We shorten that to percent
RSD. Got it. So accuracy is like hitting the
bullseye on a target. And precision is about
having all your shots land close together, even
if they're not all right in the center. Yeah,
that's a great analogy. But it doesn't stop there.
You also need specificity. What that means is
the method should only measure the specific thing
you're interested in and not be thrown off by
other stuff that might be present in the sample.
It shouldn't be influenced by the equipment itself
either. And last but not least, there's ruggedness.
This is about how well the method holds up and
continues to give reliable results even when
there are small intentional changes in the experimental
conditions. This might involve things like having
different people run the test, using different
equipment, or even doing the tests on different
days. It's all about making sure the method is
dependable in the real world of a busy lab. Wow,
those are some pretty strict criteria. So where
do labs even get these validated methods? Do
they have to invent them all from scratch? Luckily,
no. They don't have to reinvent the wheel every
time. The EAS consulting group video you gave
us actually mentioned several well -known organizations
that publish these tried and tested, fully validated
methods that labs can use. For example, there's
the United States Pharmacopeia, or USP. They
focus on setting standards for medicines and
dietary supplements. Then there's AOAC International.
They provide standards for analytical science
that are accepted around the world. And the Food
Chemicals Codex, or FCC, standards specifically
for food ingredients and let's not forget the
bacteriological analytical manual Bay Beam which
is from the FDA. It lays out procedures for detecting
those nasty pathogens in food. Labs can often
just take these established methods and use them
as is or they might adapt them slightly to fit
their specific needs. Right and it's not just
about the test methods themselves is it? The
equipment used to actually perform those tests
has to be in tip -top shape and giving accurate
readings too, right? You are absolutely right.
And that brings us to equipment qualification.
Your sources talk about this in some detail,
breaking it down into different stages. There's
DQ. Design qualification, that's confirming that
the way the equipment is designed meets all the
specific requirements. Then there's IQ, installation
qualification, where they double check that the
equipment was installed correctly, you know,
following the manufacturer's instructions to
the letter. And then there's OQ, operational
qualification. That step is all about checking
that the equipment actually works the way it's
supposed to across its full operating range.
And finally, PQ, performance qualification. This
is the big one where they show that the equipment
consistently performs as expected in the actual
lab environment, where it'll be used day in and
day out. It makes sense to have all those checks
in place, especially when you consider how sensitive
some of this lab equipment can be. Even something
as seemingly small as a change in room temperature
could potentially mess with the results. Oh,
absolutely. Even something as simple as moving
a piece of equipment to a different spot in the
lab could affect how it performs. Maybe it ends
up closer to event or in spot with more vibrations.
It can be that sensitive. That's why they often
have to requalify equipment after any major repairs
if they've changed the equipment's configuration
significantly or if they've had to move it to
a new location. And all this qualification work
needs to be meticulously documented in, you guessed
it, qualification protocols and reports. And
on top of making sure the equipment is qualified,
there's also calibration. How does that fit in
with everything else? Good point. Calibration
is about making sure that the equipment is giving
you accurate and precise measurements. You see,
regulations require all equipment to be calibrated
before it's ever used and then at regular intervals
after that. Those intervals can be based on the
manufacturer's recommendations or the lab might
set their own schedule based on how often the
equipment is used and for what purpose. The main
goal is to make sure those measurements stay
accurate and precise over time. They'll often
figure out the initial calibration settings during
the performance qualification, that PQ phase
we talked about, but some instruments, you know,
the ones that give you direct measurements like
pH meters or those analytical balances, those
might need to be checked way more often, maybe
even daily, just to make sure they still want
a point. And just like with qualification, all
those calibration activities need to be logged
in detail, including the dates, the methods used,
and of course, the results. So if I'm understanding
this right, qualification is kind of like making
sure the instrument is fundamentally sound and
set up the right way, while calibration is like
fine -tuning it to ensure those numbers it spits
out are actually correct. Yeah, that's a really
clear way to think about it. So we've talked
about validating those test methods and making
sure the equipment is reliable. What else is
essential when you're developing these really
robust GLP protocols? I'm all ears. Well, another
crucial piece of the puzzle is risk assessment.
They often call this quality risk management.
It's all about identifying and evaluating potential
problems, you know, risks that could compromise
the quality and integrity of the work being done
in the lab. And they do this up front. Risk -based
thinking seems to be a big deal across many industries
now. So how does that apply to lab protocols
specifically? Well, like those books on quality
risk management you provided explained and the
ICHQB guideline to a risk based approach allows
organizations to sort of anticipate potential
issues that might pop up during lab operations.
And then even more importantly, to put preventative
measures in place to minimize or completely eliminate
those risks. It's about being proactive, not
reactive, you know, trying to foresee what could
go wrong and then taking steps to prevent it
from happening in the first place. So instead
of waiting for a mistake to happen and then scrambling
to fix it, you're looking for those potential
weak points in the system beforehand and trying
to reinforce them. Precisely, and they have specific
tools to help with this. One is called failure
mode and effects analysis. That's FMEA. They
use that to systematically analyze each step
in a process, looking for points where it could
fail. Then they figure out how likely those failures
are, how bad they could be if they did happen,
and what the consequences might be. This way,
labs can prioritize risks and figure out the
best ways to control them. Then there's fault
tree analysis, or FTA. It's more of a reactive
tool used when something has already gone wrong.
It's a structured way to investigate how a specific
failure happened, especially if there are multiple
factors that contributed to it. It helps you
trace things back to the root cause. So FMEA
is like preventative maintenance, trying to stop
those problems before they occur, and FTA is
more like a postmortem when something's already
broken down. Got it. So is there a final piece
to this puzzle, something that ensures these
protocols stay effective over time? Yes, absolutely,
and that would be periodic review. These GLP
protocols and SOPs aren't meant to be written
in stone, you know, never to be changed. They
need to be looked at regularly and updated if
necessary. That way they stay accurate and effective
and they keep up with any changes in regulations,
new technology, or even just better ways of doing
things in the field. It's like a continuous improvement
cycle, constantly looking for ways to refine
and improve these recipes for how lab work is
done, right? Exactly. You got it. And one of
the videos you shared mentioned a really important
regulatory requirement. You need to have written
procedures for conducting evaluations at least
once a year. And these evaluations need to cover
things like complaints, any recalls that have
happened, and any findings from internal investigations.
This ongoing assessment helps identify areas
where they might need to revise the protocols
or maybe and develop brand new ones to maintain
quality and stay compliant. Okay, so we've got
these incredibly detailed protocols. They've
been developed with this rigorous method validation,
proactive risk assessment, and they're committed
to reviewing them regularly. But just having
these documents sitting around isn't enough,
right? People in the lab actually have to follow
them and follow them consistently. You're absolutely
right. Implementation and consistent execution
are critical. In good manufacturing practice,
or GMP, which is closely related to GLP, there's
a really important principle that says if it
wasn't documented, it didn't happen. really highlights
how essential it is to keep detailed records
of everything that happens in the lab. So seriously,
every single step, every observation, every result,
it all needs to be carefully recorded. Yes. every
bit of it. And it doesn't matter if it's written
down on paper or logged in an electronic system.
The documentation needs to be thorough, capturing
all the important information, but also concise
and easy to understand. And it needs to be recorded
right when the activity takes place. If it's
handwritten, it's got to be legible, signed by
the person who did the work, and dated. And if
they make a mistake, they have to correct it
the right way by drawing a single line through
what's wrong, initialing it, dating it and writing
a short explanation for the change. No erasing
or scribbling it out so you can't read it. Electronic
systems have similar rules. They often have what
they call audit trails that track every change
to the data, including who made the change and
when. Wow, that is a lot of record keeping. Is
there any way to make sure all this documentation
is? Accurate and complete? Yes there is. A really
important part of making sure the data is reliable
is that they have to have peer review of all
the original records. That means a second qualified
person looks over all the documentation, double
-checking that it's accurate, complete, and follows
all the established protocols. And of course
that review process itself needs to be documented
too, particularly in electronic record -keeping
systems. So where does all the documentation
actually live? What are the main types of records
they keep in a lab that's operating under GLP.
Your sources mention a few key types. First,
there are the standard operating procedures,
the SOPs themselves. Those are a primary record,
laying out those detailed instructions we talked
about earlier. Then there are lab notebooks,
which can be electronic or the traditional paper
kind. They use those to document the details
of specific experiments and any controlled processes
they're running. And we've already talked about
the equipment log books, which are crucial for
keeping track of each piece of equipment, including
any maintenance, repairs, or calibrations. Labs
often use a combination of all these types of
documentation to make sure they have a comprehensive
record of everything they do. So the SOPs are
like the official playbook, the standard way
of doing things. What happens if someone decides
to go rogue and deviate from the SOP? Well, as
one of those videos pointed out, any time someone
veers off course from an established SOP, even
if it seems like a minor thing, they need to
follow up formally. That usually means they have
to investigate to figure out why the deviation
happened, assess what impact it might have had
on the quality and integrity of the data, and
then put corrective and preventative actions
in place to ensure it doesn't happen again. The
rule is, stick to the SOPs. Any departure from
them has to be justified and addressed. They
take this stuff seriously. It all sounds very
tightly controlled, which makes sense. How does
all this meticulous protocol development and
implementation tie into the bigger picture of
regulatory compliance. Following those GLP protocols
and SOPs is absolutely essential if they want
to meet the requirements set by regulatory agencies.
Your sources actually provided specific examples,
like 21 CFR Part 111 Subpart J. That section
lays out the specific requirements for lab operations
in the world of dietary supplement manufacturing.
Then you've got 21 CFR Part 58, which focuses
specifically on the good laboratory practice
regulations for those non -clinical lab studies.
So we're not talking about suggestions or best
practices here, but actual rules and regulations
that labs operating in these areas have to follow
by law. Exactly. And like we mentioned earlier,
GLP and GMP, good manufacturing practices are
closely related. GLP is really focused on the
lab side of things, like research and testing,
while GMP covers the whole manufacturing process
for things like pharmaceuticals, with the main
goal of ensuring those products are high quality,
safe, and effective. And one of the videos really
emphasized that for any GMP activities, which
would definitely include work done under GLP,
the people doing those tasks have to be properly
trained and demonstrate that they can do the
job correctly. It sounds like there are several
layers of oversight and accountability baked
into the system. Absolutely. The quality control
unit within a company plays a huge role in all
of this. As they explain in 21 CFR Part 211,
that unit has the final say on approving or rejecting
any procedures or specifications that could affect
the quality of the drug product. And their responsibilities
have to be clearly spilled out in written procedures.
And crucially, those written procedures need
to be followed to the letter by everyone involved.
So from the very beginning, when they're designing
those protocols all the way through to putting
them into practice and keeping those meticulous
records of every single step, it's all geared
towards guaranteeing product quality and meeting
those strict standards set by the regulatory
agencies. Makes sense. Exactly. And remember,
this isn't a static system. It's designed to
be continuously improved. That whole cycle of
developing the protocols, implementing them,
and then reviewing them regularly, it's all part
of an ongoing effort to refine and enhance how
things are done in the lab. And that includes
when things don't quite go according to plan,
like when a test gives you a result that's out
of spec. Especially then. When they get those
unexpected results, the focus isn't on pointing
fingers and blaming someone. It's about thoroughly
investigating to understand what caused it. They
want to figure out exactly what went wrong and
then put things in place to prevent it from happening
again in the future. One of those season one
transcripts you provided actually made a really
good point. If you investigate them properly,
failures can be incredibly valuable learning
opportunities, and they can help make the whole
system even stronger. So all this incredibly
detailed stuff in GOP protocols and SOPs, even
though it might seem a bit overwhelming at first,
it's all about building trust in the scientific
data they're generating, right? And ultimately,
it's about making sure that the products that
can really impact people's lives are safe and
high quality. So for you, listening, understanding
this whole framework can really help you appreciate
just how much rigor and care goes into scientific
research and development. It's not just people
messing around in a lab. I couldn't agree more.
These protocols and procedures aren't just bureaucratic
heaps to jump through. They are the fundamental
tools that make it possible to generate reliable
and trustworthy scientific data. And they do
a lot. They ensure consistency, they help labs
comply with those crucial regulations, and they
drive that constant improvement that's so important
in any lab environment. So for those of you listening
out there, think about this for a minute. In
your own field, whatever you're working on, or
even just your own interests, are there complex
processes where having these detailed protocols
and standardized procedures could be helpful?
Could they help you be more accurate and consistent?
Maybe a more structured approach could help you
make fewer errors and have more confidence in
the results? Something to consider. And if you
want to go even deeper, you could look into those
specific regulations that might apply to your
work or your interests. You know, if you're involved
in preclinical research, you could check out
21 CFR part 58. Or if you're in the world of
dietary supplements, part 111 is the one to look
at. And for a broader international perspective
on those quality standards in the pharmaceutical
industry, you could look into those ICH guidelines
from the International Council for Harmonization.
Lots of good stuff out there. And if you've got
any feedback or any other questions you'd like
us to explore, let us know. We could always do
another deep dive focused on specific parts of
GLP or GMP, getting into even more detail. Thanks
so much for joining us today. We had a great
time digging into this fascinating world of lab
protocols and procedures with you. Until next
time.