WEBVTT
00:00:00.100 --> 00:00:04.820
Hello and welcome to SCRS Talks provided by the Society for Clinical Research Sites.
00:00:04.870 --> 00:00:16.189
I'm Jimmy Bechtel, the chief site success officer with the Society, and today I'm joined by Megan Richards, who's the director of sponsor operations with a long-standing partner with SCRS, Creo.
00:00:16.381 --> 00:00:22.400
megan is here to talk with us today a little bit about data and how sites might think of data differently.
00:00:22.411 --> 00:00:32.539
CRIO is in the business of information and data and has served as a, cruxical organization in the exchange of information between the sites and the sponsors and CROs, et cetera.
00:00:32.539 --> 00:00:35.109
So really excited, Megan, to have you here with us today.
00:00:35.298 --> 00:00:41.311
Before we get into the questions and start having our conversation, I'd love to learn maybe a little bit more about you or CRIO.
00:00:41.381 --> 00:00:41.671
Great.
00:00:41.692 --> 00:00:42.570
Thanks, Jimmy.
00:00:42.591 --> 00:00:44.171
So yes, my name is Megan Richards.
00:00:44.201 --> 00:00:47.911
I'm currently the director of sponsor operations here at CRIO.
00:00:47.951 --> 00:01:11.230
I've been here almost seven years now, and in my current role, I coordinate the rollout of central eSource to help sites increase data accuracy at the point of entry into the eSource tool itself through the use of real-time flags and alerts, and also to support sponsors in getting more real-time visibility into the data that's being captured in a standardized template.
00:01:11.231 --> 00:01:39.713
Prior to that, I worked on the site side, onboarding research sites to CRIO's eSource, CTMS, and eReg software, and I've also been heavily involved throughout my entire time at CRIO in rolling out our Looker reporting tool, and later, the BigQuery data warehouse, which we use to help support clients in identifying their key performance metrics and also in creating dashboards and visualizations to help track those metrics.
00:01:39.724 --> 00:01:41.293
So very excited to be here today.
00:01:41.394 --> 00:01:44.834
I am excited to talk with you about this as well, so really exciting.
00:01:44.843 --> 00:01:45.623
I love data.
00:01:45.784 --> 00:01:50.510
Anyone who's been around SCRS long enough knows that I'm definitely one of the data guys.
00:01:50.561 --> 00:01:57.626
And any time we can enhance the data that we get or drive us forward even faster with data, then I'm all for it.
00:01:57.647 --> 00:02:13.191
Megan, for sites that are just starting maybe on the opposite spectrum of you and I, to think about data more seriously, where do you even begin when it comes to thinking about or identifying KPIs that actually matter for their operations?
00:02:13.290 --> 00:02:14.661
Yeah, this is a great question.
00:02:14.661 --> 00:02:28.719
I think there are a lot of sites that are tracking things already, but there are plenty that just need to figure out where to start or perhaps some that might even be tracking too many things and just need to reset so that they can get things started in a more practical manner for their sites.
00:02:28.729 --> 00:02:33.620
So I think we can recognize that it can feel a bit overwhelming at first, perhaps.
00:02:33.659 --> 00:02:38.539
But definitely start small and slowly build things up.
00:02:38.610 --> 00:02:40.538
Add more metrics over time.
00:02:40.539 --> 00:02:49.985
As you and your team get more into the habit of it, it really becomes part of your company culture, and then it's going to be something that is just natural to be doing.
00:02:49.986 --> 00:02:59.713
Think about identifying areas where your team spends the most of their time or experiences the most friction in the day-to-day.
00:02:59.715 --> 00:03:11.822
Think of areas where you might be tracking things manually, or if there's anything that's being pulled from multiple places or multiple sources that needs to get joined together into spreadsheets or elsewhere.
00:03:11.921 --> 00:03:16.562
These can all be good areas to pinpoint to track for your KPIs.
00:03:16.580 --> 00:03:22.931
I think the most valuable ones will certainly be the ones that are going to help you solve certain problems.
00:03:22.931 --> 00:03:34.453
So it could be problems that the sponsor and CRO are going to be interested in, like enrollment rates or query resolution turnaround times, study startup turnaround times, protocol deviations.
00:03:34.473 --> 00:03:41.264
But don't forget about the internal metrics that help you keep track of your overall site health as well.
00:03:41.365 --> 00:04:04.316
So something as simple as tracking the number of studies by coordinator and coupling that with forecasting of future study awards so that you can better predict future staffing needs that your site might have And then ultimately, stay consistent, establish the standardized benchmarks or deviations and processes for capturing that data.
00:04:04.415 --> 00:04:17.838
And that way you know that you're making decisions based on reliable information and you're able to track the direction that your team might be going positively or negatively because you've got those benchmarks that are created as well
00:04:17.937 --> 00:04:18.367
Thanks, Megan.
00:04:18.367 --> 00:04:21.139
A lot of really great examples there for sites to think about.
00:04:21.139 --> 00:04:22.048
And I do, I agree with you.
00:04:22.048 --> 00:04:23.358
I think that's a really great way.
00:04:23.358 --> 00:04:28.117
It's, identify areas of friction or tension or unknown, and that's really where you start.
00:04:28.117 --> 00:04:32.288
And I think it's also really important, as you mentioned, you don't have to take on the world.
00:04:32.288 --> 00:04:35.519
Start slow, start small, integrate a couple of KPIs.
00:04:35.548 --> 00:04:39.348
And one of the other things I think that's really important is getting everyone aligned, right?
00:04:39.427 --> 00:04:41.096
And getting The buy-in with some of that.
00:04:41.096 --> 00:04:56.937
What kind of leads me to my next question around this, so which is once a site knows they've gone through what you just described, which metrics to track, what does building a dashboard or a database or a home for that information look like in practice?
00:04:56.937 --> 00:05:00.677
And what are some of the common pitfalls, sites fall into when they do this?
00:05:00.778 --> 00:05:01.228
Sure.
00:05:01.466 --> 00:05:21.860
So I would definitely say Utilize the tools that you have available to you If you're using an eSource or a CTMS system like CRIO or others, there are a lot of reports that might be pre-built, and there is scheduling functionality that's built into some of those reporting tools that allows you to send data to central dashboards.
00:05:21.956 --> 00:05:22.904
So start there.
00:05:22.985 --> 00:05:26.831
Usually that's a, a nice starting point for sites to then build from.
00:05:26.831 --> 00:05:40.529
But as you're thinking about what to put on these dashboards and how to build them, just remember that a, a successful and an effective dashboard is going to give you that real-time view into your site's operational health.
00:05:40.529 --> 00:05:48.572
It will help you highlight trends and flag issues that might require action before they become larger problems.
00:05:48.692 --> 00:05:57.372
And then for some pitfalls to avoid, I will try to summarize this into four key areas that I think are particularly important.
00:05:57.374 --> 00:06:03.223
One of those is to tailor your dashboards to the audience that is going to be using them.
00:06:03.242 --> 00:06:15.810
If you have data that's going to the site coordinators, they may need more of that day-to-day information that's going to help support their scheduling needs and room assignments and anything else that's gonna help in that...
00:06:15.850 --> 00:06:16.730
in the day-to-day.
00:06:16.740 --> 00:06:23.339
Whereas your site managers or executives at those sites are going to need high-level information about overall site health.
00:06:23.439 --> 00:06:28.720
And then again, even the sponsors and CROs that might be receiving some of this data are going to need something different.
00:06:28.720 --> 00:06:35.649
So that kind of one-size-fits-all concept of a dashboard is probably going to have too much information on it.
00:06:35.750 --> 00:06:43.942
And think about, again, who is the user really of this dashboard, and make sure to tailor different versions to those different groups of people.
00:06:43.942 --> 00:06:46.346
The second one I would say is define what you're tracking.
00:06:46.346 --> 00:06:59.112
If you don't know what it is exactly that you're tracking, or you don't really know if that metric is good or bad and what direction it's trending, you're not going to be able to tell other people at your site.
00:06:59.201 --> 00:07:03.591
And then if they're looking at the dashboard, it's going to be even more confusing to them.
00:07:03.670 --> 00:07:09.612
So add those definitions wherever is going to be needed on these visualized dashboards.
00:07:09.752 --> 00:07:26.456
Include ranges that can help to identify trends and outliers, and can actually allow you to then act upon those if you start to see patterns over time The third item I'd certainly recommend considering so that you can avoid is make sure you allocate enough time for this.
00:07:26.456 --> 00:07:33.088
It's an important part of the job, but it can take some time to start building out these dashboards and then maintain them.
00:07:33.088 --> 00:07:36.999
So again, remember that it's possible to be tracking too many things.
00:07:37.149 --> 00:07:44.533
Start small, add things as you go, but also ensure that time is allocated in whomever's role it's going to be.
00:07:44.552 --> 00:07:51.862
Add it to the job descriptions, make p- make people aware of this so that they know that it's part of what they will be doing in their day-to-day.
00:07:51.862 --> 00:07:55.134
And then finally, I would recommend automating what you can.
00:07:55.134 --> 00:08:03.754
So again, take advantage of those reports that might be built into systems that your site is already using that scheduling functionality, any additional support that they can provide.
00:08:03.754 --> 00:08:14.314
But if you can avoid having to track things manually, that can cause errors and take additional time certainly think about the automations and how that can help save your time overall
00:08:14.413 --> 00:08:15.144
Excellent, Megan.
00:08:15.144 --> 00:08:18.874
I couldn't agree more with really all those points, and I love how they were progressive too, right?
00:08:18.874 --> 00:08:22.372
It's almost like not only are these things you need to do, but they're also stepwise.
00:08:22.374 --> 00:08:24.432
There, there's an order in which you need to do this.
00:08:24.432 --> 00:08:32.337
And again, I think the really important part of the success here, as you allude to and mention, is really about involving multiple individuals, right?
00:08:32.337 --> 00:08:40.022
Getting the team on board with this and aligned around what needs to be done and how this is going to work so that it's useful.
00:08:40.022 --> 00:08:50.585
Because if you create this beautiful, complex, data abundant dashboard, but no one knows how to use it and no one knows what it means, and it doesn't make sense to the rest of the team it's worthless at that point.
00:08:50.909 --> 00:08:57.092
So getting Everyone aligned on that, is an excellent point, and you do that through exactly what you described in your process there.
00:08:57.092 --> 00:09:14.226
I think that's great So Megan then, as we can kinda continue to move through the the steps here and the, the timeline for successful data and implementation and usage, how can sites then, once they have this dashboard, use that data to benchmark their performance against maybe industry standards?
00:09:14.326 --> 00:09:17.836
And why does that comparison really matter?
00:09:17.937 --> 00:09:24.167
That's a great question, and I think the first point I would make there is figure out what those industry standards are.
00:09:24.225 --> 00:09:32.687
Ask your sponsors, ask the CROs if they can provide any metrics so that you actually have some, some metrics to benchmark against.
00:09:32.787 --> 00:09:40.710
If you don't have that information, I know SCRS puts a lot out there and I'm sure there's a lot more online that can help to identify some of the standards.
00:09:40.869 --> 00:09:47.687
But think about some of the external metrics that will help to showcase your site's success to sponsors.
00:09:47.697 --> 00:09:59.745
So again, things like your study startup turnaround times, query resolution rates, EDC data entry turnaround times, or participant retention, like really metrics that will help your site stand out.
00:09:59.765 --> 00:10:12.974
And then from there, in terms of the benchmarking piece of this, con- remember that benchmarking is really what is going to provide the context to your team and to anyone externally who's going to be receiving this data.
00:10:13.073 --> 00:10:33.621
So this is what allows you to compare your data against the industry averages and to show how successful your site is compared to other teams out there by, understanding how quick, again, those enrollment rates are, that query resolution time is compared to the averages to really showcase your successes.
00:10:33.623 --> 00:10:40.908
Compare the data to, again, just determine where you might be outperforming, and also to identify areas of improvement.
00:10:41.008 --> 00:11:04.813
That'll be helpful so that you can also monitor your progress over time, showcase the successes that you've made, and then highlight those to sponsors too, so that they can see how you are, putting effort as a team into improving upon some of your internal processes and helping to, ultimately turn everything over more quickly and efficiently and accurately.
00:11:05.193 --> 00:11:15.381
And then I would just say track your trends across studies as well, so that you can highlight areas of improvement over time, but also so that you can celebrate them internally.
00:11:15.381 --> 00:11:31.850
And as you have these successes, don't just forget to share them with the sponsor, but celebrate them with your site and with your team so that as you have these improvements, you're continuing to create this culture of Tracking metrics and making that really part of, an important day-to-day point on your team.
00:11:31.851 --> 00:11:45.244
But celebrating it so that people really want to continue to do this as a team to really create that team mentality that's going to set your site apart from others in terms of what the sponsor is seeing too
00:11:45.344 --> 00:11:47.788
Megan, another great set of sort of tips, right?
00:11:47.788 --> 00:11:50.865
Information, best practices really around how we do this.
00:11:50.865 --> 00:11:52.245
And you're exactly right.
00:11:52.245 --> 00:11:54.914
There's so many resources out there.
00:11:54.914 --> 00:11:58.557
It's just taking the time to distill and find the ones that work for you.
00:11:58.557 --> 00:12:01.428
And yeah, thanks for the the plug on SCRS, right?
00:12:01.428 --> 00:12:05.572
The landscape data really does help a lot of sites with their benchmarking.
00:12:05.572 --> 00:12:09.481
And I would also shamelessly plug SCRS, KPI resource as well.
00:12:09.481 --> 00:12:23.429
We have a really robust resource and document that helps sites maybe do some of the steps and think about some of the things that you mentioned previously in identifying which KPI they might need to track, what they mean, and then how to track them effectively.
00:12:23.758 --> 00:12:31.211
So if Anyone out there is looking to take some of the great information that Megan's sharing here and bring it into reality that might be a good resource to help supplement that.
00:12:31.490 --> 00:12:34.912
So Megan, As we begin to close the conversation here it's been great.
00:12:34.951 --> 00:12:38.865
The number of things for sites to think about that you've mentioned i- is really numerous.
00:12:38.945 --> 00:12:46.149
But as Sponsors are increasingly looking for proof of site performance before and during that trial, right?
00:12:46.149 --> 00:12:52.880
It's this constant interview that we're really going through as a site across a spectrum of any given study.
00:12:52.890 --> 00:12:58.985
So how can sites then use that data that we've, built here, and we're tracking, and it's working well for us?
00:12:59.024 --> 00:13:04.894
How can they use that operational data to then tell the compelling story and strengthen those relationships?
00:13:04.894 --> 00:13:07.394
Really because that's what we're, partially doing this for.
00:13:07.594 --> 00:13:16.346
As you've mentioned, it's not only internal and internal management here as a business, but it's also then putting their best foot forward with their sponsors and CROs they work with.
00:13:16.446 --> 00:13:16.785
Yeah.
00:13:17.066 --> 00:13:34.923
So- Definitely make sure you understand the data first, and then that goes back to the point I was making earlier with having those definitions and having the benchmarks available so that you can understand which direction you're trending and which items to highlight to the sponsor at any given time.
00:13:34.924 --> 00:13:37.489
So understand that data and then tell the story.
00:13:37.489 --> 00:13:56.625
Talk to the sponsors around where those successes are in participant enrollment and your, data quality and number of queries and query turnarounds, how you're meeting timelines and executing the protocol, consistently across all of your studies with minimal deviations.
00:13:56.647 --> 00:14:09.517
All of the data that's being shared, you wanna understand, and then you want to share those numbers so that you can provide that evidence that really helps to prove and showcase your site's success.
00:14:09.518 --> 00:14:30.868
And when thinking about telling the story with the numbers, don't just share the numbers, but talk about how some improvements that you've made to process at your site and staffing and investing in technology ultimately has led to better overall site performance, and most importantly, why we're all here, better participant outcomes.
00:14:30.868 --> 00:14:35.484
And that really helps to bring meaning to the numbers that you're sharing.
00:14:35.484 --> 00:15:02.708
And additionally, if you can tell a story on the tech side of how tech is saving your site's time and creating more quality data, that can also strengthen the case for your site to perhaps get that tech paid for by the sponsor Then think about, the big picture here, which is that partnership component, and that we want to develop that relationship with the sponsor, with the CRO so that we can continue to work with them on additional trials in the future.
00:15:02.729 --> 00:15:27.600
So if you are being very proactive about sharing these metrics and highlighting your successes, and you're seen as being a transparent site amongst the sponsor, landscape with all of the other sites out there, it helps to ultimately strengthen that partnership with the sponsor, help to win additional study awards, ideally really just opening the door for you for those future opportunities.
00:15:27.601 --> 00:15:40.864
And again, when you're considering all of this and which of these metrics is going to be most useful when you're talking to the sponsor, think about those external ones, those study turnaround times, time to visit, enroll, query resolution.
00:15:41.082 --> 00:16:02.929
Consider those, those metrics that the sponsors are going to want to see to say,"Yes, this is definitely a highly productive site that we wanna keep working with in the future." And really, Again, ultimately allows you to strengthen that relationship, keep winning study awards, and then keep improving your processes so that additional sponsors will want to work with your site as well.
00:16:03.029 --> 00:16:07.700
Winning all around is exactly what I received from that, Megan, and that's the goal here.
00:16:07.700 --> 00:16:19.085
We want the site to win, of course, but as long as we can demonstrate that the sponsors or CROs and sponsors through them are going to win as a result of, as well using data, then we're doing our jobs.
00:16:19.115 --> 00:16:25.874
And we're going to, as you state so eloquently really develop stronger relationships with those organizations.
00:16:25.874 --> 00:16:29.523
An excellent place, I think, for us to conclude our conversation here.
00:16:29.523 --> 00:16:40.490
And thank you so much for being with us today, for talking about this, sharing some insights again from a, an organization that really has always put data at the core of everything that they do a- and drive...
00:16:40.690 --> 00:16:43.448
help the industry drive decisions forward using that data.
00:16:43.448 --> 00:16:44.200
Again, thank you
00:16:44.299 --> 00:16:53.182
Thank you, Jimmy, and I'll definitely recommend for folks that may have heard about CRIO but are not current CRIO clients check out CRIO's website.
00:16:53.182 --> 00:16:54.991
It's clinicalresearch.io.
00:16:55.091 --> 00:17:00.631
Encourage you to learn more about how CRIO can set up your study operations for success.
00:17:00.760 --> 00:17:01.182
Excellent.
00:17:01.302 --> 00:17:02.916
And Thanks again, Megan.
00:17:02.916 --> 00:17:17.778
And for those listening, I'd like to also make sure that you check out other SCRS resources on our website, myscrs.org, like that KPI resource that I mentioned, other podcasts, webinars and a lot of other great content.
00:17:17.778 --> 00:17:21.198
But for now, thanks for tuning in, listening, and until next time.
00:00:00.100 --> 00:00:04.820
Hello and welcome to SCRS Talks provided by the Society for Clinical Research Sites.
00:00:04.870 --> 00:00:16.189
I'm Jimmy Bechtel, the chief site success officer with the Society, and today I'm joined by Megan Richards, who's the director of sponsor operations with a long-standing partner with SCRS, Creo.
00:00:16.381 --> 00:00:22.400
megan is here to talk with us today a little bit about data and how sites might think of data differently.
00:00:22.411 --> 00:00:32.539
CRIO is in the business of information and data and has served as a, cruxical organization in the exchange of information between the sites and the sponsors and CROs, et cetera.
00:00:32.539 --> 00:00:35.109
So really excited, Megan, to have you here with us today.
00:00:35.298 --> 00:00:41.311
Before we get into the questions and start having our conversation, I'd love to learn maybe a little bit more about you or CRIO.
00:00:41.381 --> 00:00:41.671
Great.
00:00:41.692 --> 00:00:42.570
Thanks, Jimmy.
00:00:42.591 --> 00:00:44.171
So yes, my name is Megan Richards.
00:00:44.201 --> 00:00:47.911
I'm currently the director of sponsor operations here at CRIO.
00:00:47.951 --> 00:01:11.230
I've been here almost seven years now, and in my current role, I coordinate the rollout of central eSource to help sites increase data accuracy at the point of entry into the eSource tool itself through the use of real-time flags and alerts, and also to support sponsors in getting more real-time visibility into the data that's being captured in a standardized template.
00:01:11.231 --> 00:01:39.713
Prior to that, I worked on the site side, onboarding research sites to CRIO's eSource, CTMS, and eReg software, and I've also been heavily involved throughout my entire time at CRIO in rolling out our Looker reporting tool, and later, the BigQuery data warehouse, which we use to help support clients in identifying their key performance metrics and also in creating dashboards and visualizations to help track those metrics.
00:01:39.724 --> 00:01:41.293
So very excited to be here today.
00:01:41.394 --> 00:01:44.834
I am excited to talk with you about this as well, so really exciting.
00:01:44.843 --> 00:01:45.623
I love data.
00:01:45.784 --> 00:01:50.510
Anyone who's been around SCRS long enough knows that I'm definitely one of the data guys.
00:01:50.561 --> 00:01:57.626
And any time we can enhance the data that we get or drive us forward even faster with data, then I'm all for it.
00:01:57.647 --> 00:02:13.191
Megan, for sites that are just starting maybe on the opposite spectrum of you and I, to think about data more seriously, where do you even begin when it comes to thinking about or identifying KPIs that actually matter for their operations?
00:02:13.290 --> 00:02:14.661
Yeah, this is a great question.
00:02:14.661 --> 00:02:28.719
I think there are a lot of sites that are tracking things already, but there are plenty that just need to figure out where to start or perhaps some that might even be tracking too many things and just need to reset so that they can get things started in a more practical manner for their sites.
00:02:28.729 --> 00:02:33.620
So I think we can recognize that it can feel a bit overwhelming at first, perhaps.
00:02:33.659 --> 00:02:38.539
But definitely start small and slowly build things up.
00:02:38.610 --> 00:02:40.538
Add more metrics over time.
00:02:40.539 --> 00:02:49.985
As you and your team get more into the habit of it, it really becomes part of your company culture, and then it's going to be something that is just natural to be doing.
00:02:49.986 --> 00:02:59.713
Think about identifying areas where your team spends the most of their time or experiences the most friction in the day-to-day.
00:02:59.715 --> 00:03:11.822
Think of areas where you might be tracking things manually, or if there's anything that's being pulled from multiple places or multiple sources that needs to get joined together into spreadsheets or elsewhere.
00:03:11.921 --> 00:03:16.562
These can all be good areas to pinpoint to track for your KPIs.
00:03:16.580 --> 00:03:22.931
I think the most valuable ones will certainly be the ones that are going to help you solve certain problems.
00:03:22.931 --> 00:03:34.453
So it could be problems that the sponsor and CRO are going to be interested in, like enrollment rates or query resolution turnaround times, study startup turnaround times, protocol deviations.
00:03:34.473 --> 00:03:41.264
But don't forget about the internal metrics that help you keep track of your overall site health as well.
00:03:41.365 --> 00:04:04.316
So something as simple as tracking the number of studies by coordinator and coupling that with forecasting of future study awards so that you can better predict future staffing needs that your site might have And then ultimately, stay consistent, establish the standardized benchmarks or deviations and processes for capturing that data.
00:04:04.415 --> 00:04:17.838
And that way you know that you're making decisions based on reliable information and you're able to track the direction that your team might be going positively or negatively because you've got those benchmarks that are created as well
00:04:17.937 --> 00:04:18.367
Thanks, Megan.
00:04:18.367 --> 00:04:21.139
A lot of really great examples there for sites to think about.
00:04:21.139 --> 00:04:22.048
And I do, I agree with you.
00:04:22.048 --> 00:04:23.358
I think that's a really great way.
00:04:23.358 --> 00:04:28.117
It's, identify areas of friction or tension or unknown, and that's really where you start.
00:04:28.117 --> 00:04:32.288
And I think it's also really important, as you mentioned, you don't have to take on the world.
00:04:32.288 --> 00:04:35.519
Start slow, start small, integrate a couple of KPIs.
00:04:35.548 --> 00:04:39.348
And one of the other things I think that's really important is getting everyone aligned, right?
00:04:39.427 --> 00:04:41.096
And getting The buy-in with some of that.
00:04:41.096 --> 00:04:56.937
What kind of leads me to my next question around this, so which is once a site knows they've gone through what you just described, which metrics to track, what does building a dashboard or a database or a home for that information look like in practice?
00:04:56.937 --> 00:05:00.677
And what are some of the common pitfalls, sites fall into when they do this?
00:05:00.778 --> 00:05:01.228
Sure.
00:05:01.466 --> 00:05:21.860
So I would definitely say Utilize the tools that you have available to you If you're using an eSource or a CTMS system like CRIO or others, there are a lot of reports that might be pre-built, and there is scheduling functionality that's built into some of those reporting tools that allows you to send data to central dashboards.
00:05:21.956 --> 00:05:22.904
So start there.
00:05:22.985 --> 00:05:26.831
Usually that's a, a nice starting point for sites to then build from.
00:05:26.831 --> 00:05:40.529
But as you're thinking about what to put on these dashboards and how to build them, just remember that a, a successful and an effective dashboard is going to give you that real-time view into your site's operational health.
00:05:40.529 --> 00:05:48.572
It will help you highlight trends and flag issues that might require action before they become larger problems.
00:05:48.692 --> 00:05:57.372
And then for some pitfalls to avoid, I will try to summarize this into four key areas that I think are particularly important.
00:05:57.374 --> 00:06:03.223
One of those is to tailor your dashboards to the audience that is going to be using them.
00:06:03.242 --> 00:06:15.810
If you have data that's going to the site coordinators, they may need more of that day-to-day information that's going to help support their scheduling needs and room assignments and anything else that's gonna help in that...
00:06:15.850 --> 00:06:16.730
in the day-to-day.
00:06:16.740 --> 00:06:23.339
Whereas your site managers or executives at those sites are going to need high-level information about overall site health.
00:06:23.439 --> 00:06:28.720
And then again, even the sponsors and CROs that might be receiving some of this data are going to need something different.
00:06:28.720 --> 00:06:35.649
So that kind of one-size-fits-all concept of a dashboard is probably going to have too much information on it.
00:06:35.750 --> 00:06:43.942
And think about, again, who is the user really of this dashboard, and make sure to tailor different versions to those different groups of people.
00:06:43.942 --> 00:06:46.346
The second one I would say is define what you're tracking.
00:06:46.346 --> 00:06:59.112
If you don't know what it is exactly that you're tracking, or you don't really know if that metric is good or bad and what direction it's trending, you're not going to be able to tell other people at your site.
00:06:59.201 --> 00:07:03.591
And then if they're looking at the dashboard, it's going to be even more confusing to them.
00:07:03.670 --> 00:07:09.612
So add those definitions wherever is going to be needed on these visualized dashboards.
00:07:09.752 --> 00:07:26.456
Include ranges that can help to identify trends and outliers, and can actually allow you to then act upon those if you start to see patterns over time The third item I'd certainly recommend considering so that you can avoid is make sure you allocate enough time for this.
00:07:26.456 --> 00:07:33.088
It's an important part of the job, but it can take some time to start building out these dashboards and then maintain them.
00:07:33.088 --> 00:07:36.999
So again, remember that it's possible to be tracking too many things.
00:07:37.149 --> 00:07:44.533
Start small, add things as you go, but also ensure that time is allocated in whomever's role it's going to be.
00:07:44.552 --> 00:07:51.862
Add it to the job descriptions, make p- make people aware of this so that they know that it's part of what they will be doing in their day-to-day.
00:07:51.862 --> 00:07:55.134
And then finally, I would recommend automating what you can.
00:07:55.134 --> 00:08:03.754
So again, take advantage of those reports that might be built into systems that your site is already using that scheduling functionality, any additional support that they can provide.
00:08:03.754 --> 00:08:14.314
But if you can avoid having to track things manually, that can cause errors and take additional time certainly think about the automations and how that can help save your time overall
00:08:14.413 --> 00:08:15.144
Excellent, Megan.
00:08:15.144 --> 00:08:18.874
I couldn't agree more with really all those points, and I love how they were progressive too, right?
00:08:18.874 --> 00:08:22.372
It's almost like not only are these things you need to do, but they're also stepwise.
00:08:22.374 --> 00:08:24.432
There, there's an order in which you need to do this.
00:08:24.432 --> 00:08:32.337
And again, I think the really important part of the success here, as you allude to and mention, is really about involving multiple individuals, right?
00:08:32.337 --> 00:08:40.022
Getting the team on board with this and aligned around what needs to be done and how this is going to work so that it's useful.
00:08:40.022 --> 00:08:50.585
Because if you create this beautiful, complex, data abundant dashboard, but no one knows how to use it and no one knows what it means, and it doesn't make sense to the rest of the team it's worthless at that point.
00:08:50.909 --> 00:08:57.092
So getting Everyone aligned on that, is an excellent point, and you do that through exactly what you described in your process there.
00:08:57.092 --> 00:09:14.226
I think that's great So Megan then, as we can kinda continue to move through the the steps here and the, the timeline for successful data and implementation and usage, how can sites then, once they have this dashboard, use that data to benchmark their performance against maybe industry standards?
00:09:14.326 --> 00:09:17.836
And why does that comparison really matter?
00:09:17.937 --> 00:09:24.167
That's a great question, and I think the first point I would make there is figure out what those industry standards are.
00:09:24.225 --> 00:09:32.687
Ask your sponsors, ask the CROs if they can provide any metrics so that you actually have some, some metrics to benchmark against.
00:09:32.787 --> 00:09:40.710
If you don't have that information, I know SCRS puts a lot out there and I'm sure there's a lot more online that can help to identify some of the standards.
00:09:40.869 --> 00:09:47.687
But think about some of the external metrics that will help to showcase your site's success to sponsors.
00:09:47.697 --> 00:09:59.745
So again, things like your study startup turnaround times, query resolution rates, EDC data entry turnaround times, or participant retention, like really metrics that will help your site stand out.
00:09:59.765 --> 00:10:12.974
And then from there, in terms of the benchmarking piece of this, con- remember that benchmarking is really what is going to provide the context to your team and to anyone externally who's going to be receiving this data.
00:10:13.073 --> 00:10:33.621
So this is what allows you to compare your data against the industry averages and to show how successful your site is compared to other teams out there by, understanding how quick, again, those enrollment rates are, that query resolution time is compared to the averages to really showcase your successes.
00:10:33.623 --> 00:10:40.908
Compare the data to, again, just determine where you might be outperforming, and also to identify areas of improvement.
00:10:41.008 --> 00:11:04.813
That'll be helpful so that you can also monitor your progress over time, showcase the successes that you've made, and then highlight those to sponsors too, so that they can see how you are, putting effort as a team into improving upon some of your internal processes and helping to, ultimately turn everything over more quickly and efficiently and accurately.
00:11:05.193 --> 00:11:15.381
And then I would just say track your trends across studies as well, so that you can highlight areas of improvement over time, but also so that you can celebrate them internally.
00:11:15.381 --> 00:11:31.850
And as you have these successes, don't just forget to share them with the sponsor, but celebrate them with your site and with your team so that as you have these improvements, you're continuing to create this culture of Tracking metrics and making that really part of, an important day-to-day point on your team.
00:11:31.851 --> 00:11:45.244
But celebrating it so that people really want to continue to do this as a team to really create that team mentality that's going to set your site apart from others in terms of what the sponsor is seeing too
00:11:45.344 --> 00:11:47.788
Megan, another great set of sort of tips, right?
00:11:47.788 --> 00:11:50.865
Information, best practices really around how we do this.
00:11:50.865 --> 00:11:52.245
And you're exactly right.
00:11:52.245 --> 00:11:54.914
There's so many resources out there.
00:11:54.914 --> 00:11:58.557
It's just taking the time to distill and find the ones that work for you.
00:11:58.557 --> 00:12:01.428
And yeah, thanks for the the plug on SCRS, right?
00:12:01.428 --> 00:12:05.572
The landscape data really does help a lot of sites with their benchmarking.
00:12:05.572 --> 00:12:09.481
And I would also shamelessly plug SCRS, KPI resource as well.
00:12:09.481 --> 00:12:23.429
We have a really robust resource and document that helps sites maybe do some of the steps and think about some of the things that you mentioned previously in identifying which KPI they might need to track, what they mean, and then how to track them effectively.
00:12:23.758 --> 00:12:31.211
So if Anyone out there is looking to take some of the great information that Megan's sharing here and bring it into reality that might be a good resource to help supplement that.
00:12:31.490 --> 00:12:34.912
So Megan, As we begin to close the conversation here it's been great.
00:12:34.951 --> 00:12:38.865
The number of things for sites to think about that you've mentioned i- is really numerous.
00:12:38.945 --> 00:12:46.149
But as Sponsors are increasingly looking for proof of site performance before and during that trial, right?
00:12:46.149 --> 00:12:52.880
It's this constant interview that we're really going through as a site across a spectrum of any given study.
00:12:52.890 --> 00:12:58.985
So how can sites then use that data that we've, built here, and we're tracking, and it's working well for us?
00:12:59.024 --> 00:13:04.894
How can they use that operational data to then tell the compelling story and strengthen those relationships?
00:13:04.894 --> 00:13:07.394
Really because that's what we're, partially doing this for.
00:13:07.594 --> 00:13:16.346
As you've mentioned, it's not only internal and internal management here as a business, but it's also then putting their best foot forward with their sponsors and CROs they work with.
00:13:16.446 --> 00:13:16.785
Yeah.
00:13:17.066 --> 00:13:34.923
So- Definitely make sure you understand the data first, and then that goes back to the point I was making earlier with having those definitions and having the benchmarks available so that you can understand which direction you're trending and which items to highlight to the sponsor at any given time.
00:13:34.924 --> 00:13:37.489
So understand that data and then tell the story.
00:13:37.489 --> 00:13:56.625
Talk to the sponsors around where those successes are in participant enrollment and your, data quality and number of queries and query turnarounds, how you're meeting timelines and executing the protocol, consistently across all of your studies with minimal deviations.
00:13:56.647 --> 00:14:09.517
All of the data that's being shared, you wanna understand, and then you want to share those numbers so that you can provide that evidence that really helps to prove and showcase your site's success.
00:14:09.518 --> 00:14:30.868
And when thinking about telling the story with the numbers, don't just share the numbers, but talk about how some improvements that you've made to process at your site and staffing and investing in technology ultimately has led to better overall site performance, and most importantly, why we're all here, better participant outcomes.
00:14:30.868 --> 00:14:35.484
And that really helps to bring meaning to the numbers that you're sharing.
00:14:35.484 --> 00:15:02.708
And additionally, if you can tell a story on the tech side of how tech is saving your site's time and creating more quality data, that can also strengthen the case for your site to perhaps get that tech paid for by the sponsor Then think about, the big picture here, which is that partnership component, and that we want to develop that relationship with the sponsor, with the CRO so that we can continue to work with them on additional trials in the future.
00:15:02.729 --> 00:15:27.600
So if you are being very proactive about sharing these metrics and highlighting your successes, and you're seen as being a transparent site amongst the sponsor, landscape with all of the other sites out there, it helps to ultimately strengthen that partnership with the sponsor, help to win additional study awards, ideally really just opening the door for you for those future opportunities.
00:15:27.601 --> 00:15:40.864
And again, when you're considering all of this and which of these metrics is going to be most useful when you're talking to the sponsor, think about those external ones, those study turnaround times, time to visit, enroll, query resolution.
00:15:41.082 --> 00:16:02.929
Consider those, those metrics that the sponsors are going to want to see to say,"Yes, this is definitely a highly productive site that we wanna keep working with in the future." And really, Again, ultimately allows you to strengthen that relationship, keep winning study awards, and then keep improving your processes so that additional sponsors will want to work with your site as well.
00:16:03.029 --> 00:16:07.700
Winning all around is exactly what I received from that, Megan, and that's the goal here.
00:16:07.700 --> 00:16:19.085
We want the site to win, of course, but as long as we can demonstrate that the sponsors or CROs and sponsors through them are going to win as a result of, as well using data, then we're doing our jobs.
00:16:19.115 --> 00:16:25.874
And we're going to, as you state so eloquently really develop stronger relationships with those organizations.
00:16:25.874 --> 00:16:29.523
An excellent place, I think, for us to conclude our conversation here.
00:16:29.523 --> 00:16:40.490
And thank you so much for being with us today, for talking about this, sharing some insights again from a, an organization that really has always put data at the core of everything that they do a- and drive...
00:16:40.690 --> 00:16:43.448
help the industry drive decisions forward using that data.
00:16:43.448 --> 00:16:44.200
Again, thank you
00:16:44.299 --> 00:16:53.182
Thank you, Jimmy, and I'll definitely recommend for folks that may have heard about CRIO but are not current CRIO clients check out CRIO's website.
00:16:53.182 --> 00:16:54.991
It's clinicalresearch.io.
00:16:55.091 --> 00:17:00.631
Encourage you to learn more about how CRIO can set up your study operations for success.
00:17:00.760 --> 00:17:01.182
Excellent.
00:17:01.302 --> 00:17:02.916
And Thanks again, Megan.
00:17:02.916 --> 00:17:17.778
And for those listening, I'd like to also make sure that you check out other SCRS resources on our website, myscrs.org, like that KPI resource that I mentioned, other podcasts, webinars and a lot of other great content.
00:17:17.778 --> 00:17:21.198
But for now, thanks for tuning in, listening, and until next time.
