Tools in Clinical Research

On weekends, I try my best to disengage my brain from work and be present in the moment. However, my brain fights against that and manages to continue working and it’s on the weekends that I have some of my most creative moments.

This past weekend wasn’t a particularly creative one, but I was thinking about tools.

As a photographer I often receive comments that “you must have a great camera to take such great photos”. The comment makes me wince a little every time I hear it. Yes, I have some nice camera gear, but a camera is just a tool. It takes years of study for a great photographer to really understand how best to use the tool they have. I’m still learning on that front. The camera and lenses also need to be designed with the photographer in mind. Makes common sense, right?  

This brings me to the topic of today. Tools in clinical research. There is a plethora of tools for clinical researchers. Sites are forced to use them every day. (e-PRO, eCOA, e-consent…)

Most sites are not incredibly sophisticated tech users. It makes sense, their focus is clinical research, not tech design or software engineering.

Unfortunately, most tools a clinical investigator or clinical research coordinator use were never designed with them in mind as a priority. The tools we use every day were designed to collect data required for a clinical trial.

Very little work is done during the development of those tools to ensure they will be useful for the end user.

Bold statement – how can I possibly know that?

It’s because sites use the end product. That end product frequently doesn’t work properly when you’re trying to conduct an assessment with a study participant. It typically makes the study visit less efficient and increases study costs.

So, what’s the solution? Tech developers and pharmaceutical companies need to examine their process for development and whatever level of engagement of sites has been in the past, it needs to change and increase (significantly).

My critics will say that it’s not that simple, but I would push back by saying why not try and see if together we can build a better tool? After all, the current process isn’t working so what do we have to lose?