Hackin' the GDPR

Trying to comply with the GDPR got you down?
Maybe our parody will cheer you up.

(Sung to the tune of Lennon-McCartney's "Back in the U.S.S.R.")

eSource Terminology Untangled

True or False:

(1) eSource in clinical trials means eliminating the possibility for transcription errors.

(2) Data collected in Electronic Data Capture (EDC) systems is eSource.

Strictly speaking, both statements are false. If that surprises you, it’s probably because many casual uses of the term “eSource” actually differ from the formal definition laid out by FDA. If the participants in any discussion share the same interpretation of “eSource”, or if it’s clear from context how “eSource” is being used, then no harm, no foul. (Contemporary translation: “Meh.”) BUT…and you know where we’re going with this…when a term can be interpreted in multiple ways, there’s always a possibility for miscommunication and cross talk.

Delegation of Authority Log: Tips for Monitors

We may call them “site inspections”, but it’s not the site that’s being inspected when a regulator visits; it’s the Principal Investigator. Though a PI typically delegates study tasks to other staff members, he or she remains solely responsible for the conduct of the study. In fact, the ICH E6(R2) addendum adds two new sections to the international guidance that emphasize PI supervision.

That’s what makes the Delegation of Authority (DoA) log so important and why regulatory inspectors care about it so much. A DoA log serves as evidence that a PI has assigned study tasks only to those staff members with the education, training, and experience to carry them out. If delegates are unqualified to perform their tasks, subject safety could be at risk and it’s highly likely that the study data would be unusable.

Study Sites: Show 'Em Your QC!

Sites frequently want to know how they can stand out to Sponsors and CROs to win more studies.
Our advice: Implement internal QC procedures.

Sponsors and CROs we work with consider a tight quality control program to be evidence that a site can be counted on to produce reliable data. It shows that managing quality at your site is a continual process, and doesn’t wait for monitors to arrive. In a risk-based monitoring environment, this is an increasingly compelling attribute.

Where to Start: The Usual Suspects
It makes sense for you to focus your QC efforts on those areas where you’ve historically had the most problems. If the phrase “trend analysis” makes you want to jump through a window -- it's okay -- you can climb back inside. You don't have to do a trend analysis. We've identified 3 areas in which audit findings are common and how you can avoid them.

Love at First "Site": Early Signs of Strong PI Oversight

When I was a teenager, my grandfather would invite my new boyfriends to run short, pointless errands with him, just so he could watch them drive. He said he could tell a lot about a boy’s character simply by observing his actions behind the wheel. Did he stay under the speed limit? Did he use his signal when he was switching lanes? Did he slow down when children were playing near the road? If so, it was a good sign that the boy was generally a careful and attentive fellow. If not, it was an early indication of reckless tendencies, and I would do well to be on my guard.

What does this have to do with PI oversight?

Anticipating Tensions Between Clinical Care and Study Protocol

Protocol trumps practice. This principle seems clear enough, but complying with it is not always as straight-forward as it sounds. Years of practicing medicine has reinforced the way a physician responds to medical situations. But do these responses run counter to the investigational plan? Can a site’s commitment to standard of care affect its ability to meet enrollment targets?


There’s a lot to consider.

Coping with Scoping Your CSV/Part 11 Audit

You know you need a computer systems audit, but that’s literally the extent of what you know.
Has this ever been you?

Yes, you use computers on a daily basis, and you may even use the system that needs to be audited. But you don’t spend your day thinking about where all the system components are located, how services and software are combined, and what Part 11 requirements apply. Terms like “cloud computing” make you feel slightly queasy. You’d rather get a root canal than discuss “distributed processing.” Your expertise is in manufacturing. Or clinical research. Or non-clinical lab operations. And somehow it’s your job to make sure an effective and properly-sized system audit is conducted. Great.