สำเนาบทสนทนา 🔗
WEBVTT
00:00:07.709 --> 00:00:12.720
Welcome to SCRS talks provided by the Society for Clinical Research Sites.
00:00:12.929 --> 00:00:19.379
Thank you for joining us as we explore the latest insights, trends, and innovations shaping clinical research today.
00:00:19.710 --> 00:00:27.730
I'm Jimmy Bechtel, the Vice President of Site Engagement with the Society, and today I'm joined by Rick Ward, the Chief Commercial Officer with CRIO.
00:00:27.899 --> 00:00:38.009
Rick's here to talk with us about the concept of central eSource and how eSource is really changing and evolving as the industry continues to evolve.
00:00:38.009 --> 00:00:39.674
Rick, great to have you.
00:00:39.795 --> 00:00:48.304
Really excited to talk about this relatively novel concept on a longstanding piece of technology we've had in the industry.
00:00:48.515 --> 00:00:55.244
But before we jump into that if you wouldn't mind, deepen your introduction for us and love to learn a little bit more about you and CRIO.
00:00:55.902 --> 00:00:56.712
Absolutely, Jimmy.
00:00:56.712 --> 00:00:57.521
Thanks for having me.
00:00:57.521 --> 00:00:58.661
I appreciate the time.
00:00:58.661 --> 00:00:59.981
Look forward to the conversation.
00:01:00.262 --> 00:01:02.692
As you mentioned, I'm Chief Commercial Officer at CRIO.
00:01:03.036 --> 00:01:09.167
Actually joined the organization just about six months ago, but I've been working in the clinical trial space for..
00:01:09.637 --> 00:01:10.852
little over two decades.
00:01:10.882 --> 00:01:20.311
Last 10 plus years really helping to drive commercial growth and spread the word for various leading eClinical solutions.
00:01:20.311 --> 00:01:23.861
So I know many of your listeners are probably familiar with Green Fire.
00:01:24.001 --> 00:01:30.001
I was one of the very early employees at Green Fire, and that's back when I also first was introduced to SCRS.
00:01:30.352 --> 00:01:37.052
Also worked for a few other companies, CluePoints, Trifecta Clinical before I joined CRIO this past fall.
00:01:37.382 --> 00:01:56.507
And that's provided me a nice view of what it takes in this industry to take a good idea, a concept, especially one that's technology based and help socialize it across the industry, hopefully with the intent of improving clinical research and making some of our jobs a little more enjoyable or a little less burdensome.
00:01:56.846 --> 00:02:02.436
I wasn't super familiar with CRIO prior to joining, but I had seen them at the SCRS summits.
00:02:02.656 --> 00:02:06.706
Knew that they were well known, especially among leading investigators.
00:02:06.947 --> 00:02:15.445
But when I learned about their plans to expand eSource to provide this concept of Central eSource, I wanted to learn what that was and the impact it could have.
00:02:15.746 --> 00:02:19.015
That was kinda all it took for me to get excited and join the organization.
00:02:19.670 --> 00:02:30.040
Yeah, it's great Rick and you have been a long time friend of SCRS in your various roles previously, and it's great to see you with such an awesome and supportive organization as CRIO.
00:02:30.040 --> 00:02:34.161
CRIOle's been along for the ride with SCRS as well for, several years now, Raymond and the team.
00:02:34.320 --> 00:02:50.830
So congratulations and really excited to talk about this because as you have stated, and as we've observed, CRIO has really been one of the leaders in the eSource space for a long time, but this concept of central eSource is gonna be probably something none have heard before on the line.
00:02:50.830 --> 00:02:55.091
And there's probably already a lot of speculation when I mention that word as to what that could mean.
00:02:55.121 --> 00:03:03.580
But why don't you as kind of the SMEs in this space here, break down what that is and how it might differ a little bit from sort of the traditional eSource model.
00:03:04.316 --> 00:03:04.705
Sure.
00:03:04.705 --> 00:03:05.455
Absolutely.
00:03:05.506 --> 00:03:09.181
And I know a lot of folks are familiar with the concept of eSource.
00:03:09.181 --> 00:03:23.390
It certainly is something that the majority of your leading investigators have evolved beyond sort of the paper source and paper process days, and recognizing that by leveraging an eSource tool it assists with protocol compliance.
00:03:23.390 --> 00:03:33.626
It allows to, sort of streamline the process, foresight staff generally leads to fewer protocol deviations and a, a better audit trail and lots of advantages from the site's perspective.
00:03:33.786 --> 00:03:39.256
Also some advantages to study sponsors and CROs that maybe were not quite as visible to them.
00:03:39.756 --> 00:03:54.656
What occurred in the industry over the last couple of years were sponsors recognizing that as the CRIO eSource had sort of been adopted as the standard in the industry, there was a lot of feedback from sponsors saying, we recognize the value that's being brought here.
00:03:54.705 --> 00:04:00.915
Is there anything else we can do, or how might we partner with sites to leverage this technology in an even more effective way?
00:04:00.915 --> 00:04:33.403
Because they recognize that for most of their studies, they might have a large swath of their sites that were using CRIO eSource to collect data, but there were also sites that were still perhaps using paper methods or some other eSource tool and they looked at it and saw an opportunity to build some standardization and gain some efficiencies by having a centrally designed source document that could be built and then provided to their sites to further enhance and be consistent with how the data is being collected across their trial.
00:04:33.903 --> 00:04:39.153
As they explored that and we partnered with a couple of sponsors to further explore exactly how that could be deployed.
00:04:39.432 --> 00:04:45.192
We've come up with a few meaningful additional values that can be provided to the sponsor.
00:04:45.523 --> 00:04:52.452
Load full transcript
And what's gonna be important to your audience is some enhancements to the experience at the site level that they may have never experienced before.
00:04:52.452 --> 00:04:54.343
That I think they're gonna be quite excited about.
00:04:54.983 --> 00:05:08.774
That's cool, Rick and I think it is a really interesting concept because you're potentially augmenting the work that the site is doing by giving them an additional resource and a head start I guess with the source collection aspect of things.
00:05:08.774 --> 00:05:12.798
And I know there's been past attempts to centralize this at the sponsor level.
00:05:12.798 --> 00:05:17.119
But I'm sure some of the sites on the line have probably also said, huh, that does sound familiar.
00:05:17.119 --> 00:05:18.439
Or maybe they've seen that before.
00:05:18.488 --> 00:05:22.269
It hasn't gained a lot of adoption, and I know you guys are taking a different approach.
00:05:22.269 --> 00:05:24.189
So can you share what's different this time?
00:05:24.189 --> 00:05:29.689
Why is what CRIO is doing any different or, better than what we've tried to do in the past?
00:05:30.853 --> 00:05:32.113
Yeah, that's a great question, Jimmy.
00:05:32.113 --> 00:05:44.033
And it's really important to look at the historical perspective because yes, there have been attempts to leverage this approach in the past that haven't quite taken foot and I think that there's a few important reasons for it.
00:05:44.033 --> 00:05:46.163
You mentioned one of our founders, Raymond.
00:05:46.399 --> 00:05:51.079
It's probably worth noting that CRIO was founded as a site facing solution.
00:05:51.079 --> 00:05:59.244
It was founded to support the needs of sites and the eSource solution was designed with sites in mind.
00:05:59.463 --> 00:06:13.934
The most important difference in what CRIO is doing to what has been tried in the past is we're starting with a solution that has been embraced by sites and has been designed to meet the flexible needs of the many different types of investigators out there.
00:06:14.173 --> 00:06:24.584
First and foremost, starting with a technology solution that is designed for sites is the biggest differentiator in terms of why we believe that this is going to work much more effectively.
00:06:25.033 --> 00:06:27.553
But there, are a couple of other really important pieces.
00:06:27.613 --> 00:06:41.264
One of the challenges that was recognized was that although clinical trials are a process that requires standardization, when you look at an EDC template, that EDC template is the same for every single site.
00:06:41.264 --> 00:06:52.144
There's certain data that just needs to be collected and reported back to the sponsor, but the way in which patients are visiting sites and the way assessments are delivered within the confines of the protocol.
00:06:52.144 --> 00:06:55.264
There are still various different ways that sites operate.
00:06:55.264 --> 00:06:56.223
Sites have their own SOPs.
00:06:56.884 --> 00:07:01.593
Sometimes they gather some information in addition to what might be required by protocol.
00:07:01.834 --> 00:07:11.163
And so the concept designed, eSource inherently has to have the flexibility to allow sites to comply with what's required.
00:07:11.434 --> 00:07:18.803
But also meet their own SOPs, which means they need to be able to enhance or modify that central eSource template to their needs.
00:07:19.303 --> 00:07:22.483
That's one of the two biggest differentiators.
00:07:22.783 --> 00:07:35.754
The other is even with the proliferation of eSource across our industry, one thing I was shocked to learn was that whether you're using a paper source document or an electronic source document.
00:07:36.098 --> 00:07:46.788
Most sites are still manually transcribing all of that data over into the EDC, and that's because any typical site is working with multiple sponsors using different EDC systems that are built differently.
00:07:47.059 --> 00:07:49.149
So there's never an easy way to automate that.
00:07:49.538 --> 00:07:55.598
When a sponsor gets involved and underwrites the cost and the rollout of an eSource solution.
00:07:56.319 --> 00:08:21.408
It gives us the ability to build that connection, that integration with the EDC that's being used for that study, and allows us to highly automate the process of moving that data from the eSource solution over to EDC eliminating most of the transcription work, which I'm guessing is not the activity that folks at your sites relish the most and they're happy to be able to highly automate that process instead of handling it entirely manually.
00:08:22.944 --> 00:08:24.074
That's excellent, Rick.
00:08:24.444 --> 00:08:40.283
There's two things I heard out of there that to me and I hope a lot of our listeners too, really hone in on the point that it sounds like you guys have really been listening to sites because I agree completely with the challenge we've had with eSource has been the rigidity of it with any central solution.
00:08:40.384 --> 00:08:57.604
The rigidity is what is the root of the challenge so by allowing the flexibility of your central eSource solution to better adhere with the site's, processes and SOPs and what's in the best interest of the patients, is a really critical success factor for how you guys are approaching this.
00:08:57.604 --> 00:08:58.714
So it's great to hear that.
00:08:58.894 --> 00:09:01.053
And then again, we've heard for years.
00:09:01.399 --> 00:09:10.308
That flow of data and the interoperability and the integration of one technology to the other where the data can seamlessly flow from one place to the next.
00:09:10.369 --> 00:09:15.769
In this case, from the eSource into the EDC has a lot of power and a lot of time savings.
00:09:15.818 --> 00:09:21.395
And from the sponsored CRO perspective, I imagine a lot of assurance around data integrity and consistency.
00:09:21.895 --> 00:09:25.150
That's supportive and positive for what we're trying to do
here.
00:09:25.448 --> 00:09:32.109
From a site perspective, Rick, you have alluded to some of the advantages here and if there's any more you wanna showcase, that's great.
00:09:32.109 --> 00:09:40.943
But, talk a little bit about from the site perspective, again, the biggest advantages, but also potential challenges that we might encounter when adopting some of these eSource models.
00:09:41.173 --> 00:09:41.864
Centralized.
00:09:42.979 --> 00:09:44.058
Yeah, absolutely.
00:09:44.558 --> 00:09:52.259
The site community, for the most part, has recognized the value of eSource and we're pretty far along the adoption curve there.
00:09:52.538 --> 00:09:54.918
What I would, point to as some challenges.
00:09:54.999 --> 00:09:58.568
Some of the things that I've mentioned already in terms of the flexibility and so forth.
00:09:58.568 --> 00:10:15.578
But something I would encourage sites to consider is that in the broader sense, we've seen this discussion, it's been at the SCRS summits around technology and the sort of two-sided coin of using technology driven by the sponsor, or technology driven by the site.
00:10:15.938 --> 00:10:25.958
And I think sponsors more than ever before are at a point where they're really seeing the value of adopting technology that is the technology of choice from the site.
00:10:26.019 --> 00:10:27.399
I think they're recognizing that.
00:10:27.399 --> 00:10:30.009
Obviously one of the challenges is that in many arenas.
00:10:30.323 --> 00:10:35.453
The site community has not sort of standardized on any one particular tool, and that's one of the challenges.
00:10:35.604 --> 00:10:44.423
I think the opportunity here is that we do have an eSource that has the majority of sort of the market of sites that are utilizing an eSource tool.
00:10:44.663 --> 00:10:56.063
So what I would encourage sites to think about in this process as a challenge is to recognize that we want to kind of meet the sponsors halfway, and that just means have an open mind around the central eSource concept.
00:10:56.224 --> 00:11:08.043
What the sites are gonna get is access to a tool that has been tried and true for sites, but there's gonna be a slightly different model in terms of the centrally designed eSource template and slightly different way of rolling it out.
00:11:08.344 --> 00:11:28.899
What I would encourage sites to consider and sponsors as well is when selecting this tool and'cause I imagine at some point other providers may start to explore the same concept we've developed is that the solution itself needs to not only be a very good eSource tool, it needs to not only have all the functionality that you are looking for at your site.
00:11:29.408 --> 00:11:34.043
But critically important is the support organization behind that solution.
00:11:34.043 --> 00:11:37.553
And that's really true for any software platform in the clinical trial space.
00:11:37.854 --> 00:11:48.094
But one thing that I've heard from sites that differentiates CRIO is
the degree to which we are able to support with 24 7 live chat and other levels of support.
00:11:48.094 --> 00:11:55.173
Our site training and enablement team, all the things that we invest into supporting our site community first and foremost.
00:11:55.384 --> 00:12:03.224
And secondly, to get sponsor programs up and running and successful because many of them involve introducing CRIO eSource to new sites.
00:12:03.403 --> 00:12:13.744
So the training and onboarding and support of those sites is critically important, and that's what I would encourage sites to do is to recognize that demand, require it, then I think they'll find success with this new model.
00:12:14.399 --> 00:12:15.149
It's great, Rick.
00:12:15.369 --> 00:12:33.619
I have been telling a lot of that story on stage and to sponsors and CROs for years now, trying to help them understand the best thing that you can do as a sponsor and CRO is adopt solutions that are driven by the sites and that have been able to showcase their ability to incorporate the feedback from the sites.
00:12:33.619 --> 00:12:38.129
And it sounds like that's exactly what CRIO has done with a lot of their solutions, if not all of them.
00:12:38.129 --> 00:12:44.609
In particular what we're talking about here, this Central eSource solution, and you've hit the nail on the head to try to emphasize that.
00:12:45.109 --> 00:12:53.708
This concept of adequate support, technical support, the flexibility of the platform itself, the data flow, integrations that you've been able to build in there.
00:12:53.708 --> 00:12:55.298
So that's really incredible to hear.
00:12:55.798 --> 00:13:00.928
And I hope that our sites and sponsors and CROs can listen to and perpetuate some of that.
00:13:01.791 --> 00:13:16.520
For sponsors then that are looking to consider approaches like this, what are some of the key factors that they should keep in mind to ensure that this adoption by the sites is long-term, but also then long-term successful?
00:13:16.520 --> 00:13:23.030
How do we make sure that this isn't something that we just is a one and done, or that we we pilot and then move on to something else?
00:13:24.035 --> 00:13:25.056
Yeah, that's another good point.
00:13:25.056 --> 00:13:34.936
So now we're looking at the sponsor perspective and what should their sort of punch list be of things to consider to make sure that moving in this direction is gonna be successful?
00:13:34.936 --> 00:13:36.615
And there's a few really important ones.
00:13:36.806 --> 00:13:40.525
But I'll start with kind of the same theme around site adoption.
00:13:41.025 --> 00:13:48.566
The model that has struggled has been the model when a purely sponsor chosen, sponsor selected solution.
00:13:49.245 --> 00:13:54.475
Which is also sometimes a technology that was developed purely with the sponsor's needs in mind.
00:13:55.076 --> 00:14:10.235
When that's the solution you try to roll out to sites, I think you can anticipate pushback and not just pushback for trivial reasons, but very real and significant and important reasons because the workflows that exist within a trial site are variable.
00:14:10.265 --> 00:14:15.035
And this is the challenge in conducting a clinical trial where you wanna have as little variability as possible.
00:14:15.306 --> 00:14:20.785
But the reality of it is, as you know, and as your listeners know, no two sites look exactly the same.
00:14:20.785 --> 00:14:26.826
There's larger sites, smaller sites, there's large site networks, there's independently owned sites there's academic medical centers.
00:14:26.826 --> 00:14:29.105
There's a lot of different types of sites out there.
00:14:29.405 --> 00:14:52.791
And if you're going to introduce an eSource solution to support a trial, you really need to make sure that that solution is flexible enough to support all those different types of sites, and that's where starting with a tool that is for the last almost 10 years, been designed and developed and enhanced based on feedback from sites.That I think puts you ahead of the game.
00:14:52.791 --> 00:14:57.110
So I'm obviously, I'm stumping for CRIO because I know that's the position we're in.
00:14:57.110 --> 00:15:17.499
But even more generically, I think if you're going to roll any central technology out that is core to site processes, it needs to be something that has been market proven, road proven at the sites and that the sites are embracing it because site adoption is the first barrier that if you can't get past that, you're really kind of dead in the water.
00:15:17.859 --> 00:15:19.509
There are a few other important considerations.
00:15:19.509 --> 00:15:22.149
I think one has to do with ability to scale.
00:15:22.158 --> 00:15:43.183
We've been fortunate enough to have a few partners in the pharma CRO world that have allowed us to support with the central eSource model, both small studies, studies as small as single site or a few sites with just a handful of patients all the way up to very large phase three global programs sponsored by top 10 pharma companies.
00:15:43.403 --> 00:15:47.043
These are the different types of scenarios that we are supporting.
00:15:47.254 --> 00:15:53.104
So the ability to scale across different study sizes and different therapeutic areas is also important.
00:15:53.604 --> 00:16:02.520
I mentioned the importance of support, so certainly sites are gonna be sensitive to the degree to which they get the technical support from a solution provider.
00:16:02.821 --> 00:16:19.660
I think it's fair for sponsors to take some responsibility there and say, we're not gonna roll a software application or a technology out to sites without assurances that the support organization is going to assist with onboarding, training, and ongoing support.
00:16:19.961 --> 00:16:32.250
And so if the sponsor's going to be driving a central eSource initiative, they then take on the responsibility to make sure that the technology partner they've selected
is providing that level of support to their sites.
00:16:32.250 --> 00:16:37.360
If that breaks down, the entire process is really less likely to be successful.
00:16:37.610 --> 00:16:58.461
The other advantage from a sponsor perspective that is new and coincides with the current movement towards more remote monitoring and the ability to reduce monitoring costs and source data verification by implementing a central eSource tool.
00:16:58.821 --> 00:17:03.801
Allowing sites to use the same technology that they've proven that they like to use for collecting data.
00:17:04.040 --> 00:17:10.461
But when it's rolled out in a central way, sponsors now have the ability to do remote monitoring.
00:17:10.641 --> 00:17:15.560
Not a week later when data is entered into the EDC.
00:17:15.980 --> 00:17:26.605
And believe me, I know many of your sites probably have a much better track record than a week, but in industry standards show that it could be seven to 10 days before data from a visit finds its way into EDC.
00:17:26.816 --> 00:17:32.536
That's a delay even if the EDC solution provides remote monitoring capabilities.
00:17:32.865 --> 00:17:45.355
When you have the ability to remotely monitor data, immediately after the patient visit, at the point of collection, you now have that central review capability that you may have never had before.
00:17:45.655 --> 00:18:11.096
And so in looking at a central eSource solution, you as a sponsor or a CRO would really wanna make sure that central review capability is there, otherwise, you're really missing out on what is potentially a big value proposition for sponsors in the difference between a central eSource rollout as opposed to what we often call local eSource the way eSource is typically used today.
00:18:11.893 --> 00:18:12.163
Wow.
00:18:12.163 --> 00:18:22.157
Rick, I mean, it's apparent to me that you guys have really embraced and perpetuated this message around solving some of the key challenges at a site level.
00:18:22.157 --> 00:18:28.518
And that concept of flexibility and an enhanced degree of support is really what we're trying to solve with technology.
00:18:28.518 --> 00:18:29.538
So it's great to hear that.
00:18:29.538 --> 00:18:42.758
I'm really excited especially after this conversation to hope and see the direction that this takes as another really positive solution for the industry and something that can help sites augment the work that they do with centralization.
00:18:42.758 --> 00:18:43.208
So, Rick.
00:18:43.387 --> 00:18:45.367
Thank you and thank you to the CRIO team.
00:18:45.367 --> 00:18:54.968
Thanks for being here with us today and having this conversation and helping our listeners deepen their insight into the evolution of source documentation and what the future of this means for the industry.
00:18:55.513 --> 00:18:57.523
Absolutely, Jimmy, I appreciate you having me.
00:18:57.554 --> 00:19:00.163
We value the partnership with SCRS.
00:19:00.433 --> 00:19:06.794
I'll be heading out to SCRS West in a few weeks and have an opportunity to present at that conference.
00:19:06.794 --> 00:19:09.614
And of course, I always look forward to the Global Summit.
00:19:09.614 --> 00:19:14.334
We have other folks from our company going down to the diversity event that's coming up even sooner.
00:19:14.624 --> 00:19:22.084
There's no better audience, no better venue for us to connect with our community and we use that term community in a very sincere way.
00:19:22.364 --> 00:19:54.798
As we build these new partnerships with sponsors and CROs we are adamantly dedicated to supporting our community, and it's important that our sites know that even though we are expanding sort of our client base from the site community into the sponsor and CRO world, we recognize that the foundation of our success are the sites that embrace our technology, provide us the kind of feedback we need to keep improving it and ultimately the success of CRIO long-term and the success of this central eSource concept is really gonna land on whether or not it's truly adding value to the site.
00:19:54.798 --> 00:20:02.118
So again, I appreciate the chance to speak to that community here today, and I look forward to seeing you and many of them at the next big SCRS summit.
00:20:02.634 --> 00:20:03.743
That sounds great, Rick.
00:20:03.743 --> 00:20:04.433
Yes, thank you.
00:20:04.433 --> 00:20:06.114
We're looking forward to it as well.
00:20:06.114 --> 00:20:16.913
And I'd also like to add that for everyone listening, make sure that you don't forget to explore other site focused resources made available to our entire community on our website, my scrs.org.
00:20:17.243 --> 00:20:25.284
It also showcases opportunities like our site Solutions summits, podcast publications, and webcasts made available throughout the year.
00:20:25.493 --> 00:20:28.493
Thanks again for listening, tuning in, and until next time.