WEBVTT

1
00:00:00.120 --> 00:00:03.480
<v Speaker 1>So we've heard throughout the conference how important it is

2
00:00:04.480 --> 00:00:07.799
<v Speaker 1>that we impact patients. How we get patients medicines they need,

3
00:00:08.199 --> 00:00:11.160
<v Speaker 1>how we bring them access to clinical trials. If you

4
00:00:11.240 --> 00:00:13.560
<v Speaker 1>take that stake out, hold a group out of the equation,

5
00:00:13.880 --> 00:00:17.480
<v Speaker 1>I think the next most impactful relationship you could possibly

6
00:00:17.559 --> 00:00:20.839
<v Speaker 1>have to influence that goal of bringing medicines to patients

7
00:00:20.839 --> 00:00:24.640
<v Speaker 1>and bringing trials to patients is the site sponsor relationship.

8
00:00:25.160 --> 00:00:27.519
<v Speaker 1>So we're going to focus our panel on solutions to

9
00:00:27.559 --> 00:00:29.440
<v Speaker 1>address some of the challenges that get in the way

10
00:00:29.879 --> 00:00:32.039
<v Speaker 1>day to day when we're trying to work together as

11
00:00:32.039 --> 00:00:36.560
<v Speaker 1>sponsors and sites. Now we've had some very lively panel

12
00:00:36.560 --> 00:00:39.640
<v Speaker 1>prep calls, and one of the things I was thinking

13
00:00:39.640 --> 00:00:43.479
<v Speaker 1>about as I'm watching the Olympics and Paralympics the last

14
00:00:43.479 --> 00:00:46.240
<v Speaker 1>couple of months was how to referee and how to

15
00:00:46.320 --> 00:00:47.920
<v Speaker 1>rain this in a little bit. And one of the

16
00:00:47.920 --> 00:00:49.759
<v Speaker 1>things that struck me as a data of a couple

17
00:00:49.799 --> 00:00:52.159
<v Speaker 1>of field hockey players and just watching those sports was

18
00:00:52.200 --> 00:00:55.159
<v Speaker 1>how in the Olympics and the Paralympics they use cards

19
00:00:55.200 --> 00:00:57.719
<v Speaker 1>to communicate, right, whether it's a challenge card or a

20
00:00:57.719 --> 00:01:02.280
<v Speaker 1>penalty card or whatnot. So today, and I apologize for

21
00:01:02.359 --> 00:01:04.640
<v Speaker 1>all of the innovative technology suppliers are going to get

22
00:01:04.640 --> 00:01:05.959
<v Speaker 1>a cringe when we talk about doing this.

23
00:01:06.480 --> 00:01:08.120
<v Speaker 2>We're going to use physical cards.

24
00:01:08.120 --> 00:01:09.879
<v Speaker 1>We've got a stack of green and a stack of

25
00:01:09.920 --> 00:01:12.319
<v Speaker 1>red cards, and we're going to challenge our panel today

26
00:01:12.359 --> 00:01:16.159
<v Speaker 1>that as we raise a challenge, they take a red card,

27
00:01:16.879 --> 00:01:20.079
<v Speaker 1>but that when a challenge is presented, we then have

28
00:01:20.159 --> 00:01:23.120
<v Speaker 1>to present solutions to that challenge and we get awarded

29
00:01:23.159 --> 00:01:24.920
<v Speaker 1>some green cards. And the goal by the end of

30
00:01:24.959 --> 00:01:27.959
<v Speaker 1>this panel will be that we have an overwhelming amount

31
00:01:27.959 --> 00:01:31.079
<v Speaker 1>of green cards to show rather than red and pull

32
00:01:31.159 --> 00:01:33.159
<v Speaker 1>them up maybe in the final few minutes in a

33
00:01:33.480 --> 00:01:38.040
<v Speaker 1>very analog dashboard of red and green. So with that,

34
00:01:38.760 --> 00:01:40.719
<v Speaker 1>and coming off of some of the panels that we

35
00:01:40.760 --> 00:01:43.680
<v Speaker 1>heard earlier this morning, we spoke a lot about people

36
00:01:43.799 --> 00:01:45.879
<v Speaker 1>and a lot about the next generation. I think it

37
00:01:45.920 --> 00:01:49.079
<v Speaker 1>was in Deirdre Bivard's closing comments. I think she spoke

38
00:01:49.120 --> 00:01:51.359
<v Speaker 1>a little bit about how we bring in the next

39
00:01:51.400 --> 00:01:52.760
<v Speaker 1>generation of professionals.

40
00:01:52.760 --> 00:01:55.159
<v Speaker 2>So I wanted to start with people for our panel.

41
00:01:55.560 --> 00:01:59.959
<v Speaker 1>And maybe we could start with Lisa, maybe you could

42
00:02:00.079 --> 00:02:02.239
<v Speaker 1>jump in on this one first, and then we'll probably

43
00:02:02.319 --> 00:02:04.439
<v Speaker 1>have everyone way on and this one as such a

44
00:02:04.480 --> 00:02:08.560
<v Speaker 1>hot topic. But when we think about the challenge that

45
00:02:08.599 --> 00:02:12.159
<v Speaker 1>we're presented with at sites as it pertains to people

46
00:02:12.240 --> 00:02:15.280
<v Speaker 1>to acquiring and retaining people. How do you see that

47
00:02:15.400 --> 00:02:17.199
<v Speaker 1>challenge and what are some of the solutions that you

48
00:02:17.240 --> 00:02:19.680
<v Speaker 1>think are out there that we could put into practice.

49
00:02:19.439 --> 00:02:20.199
<v Speaker 2>To address it.

50
00:02:20.400 --> 00:02:23.599
<v Speaker 3>Thank you, Dennis so Lisa KINI great to meet everybody.

51
00:02:23.639 --> 00:02:26.639
<v Speaker 4>I work for the START Center for Cancer Research, and

52
00:02:26.680 --> 00:02:29.240
<v Speaker 4>that is a network of sites, so heavily steeped in

53
00:02:29.280 --> 00:02:32.639
<v Speaker 4>the challenge of keeping good people at sites. I've also

54
00:02:32.759 --> 00:02:35.840
<v Speaker 4>worked in organizations that are academic health centers that are

55
00:02:35.840 --> 00:02:37.439
<v Speaker 4>also doing clinical.

56
00:02:37.000 --> 00:02:39.520
<v Speaker 3>Care combined with the work of research.

57
00:02:40.159 --> 00:02:44.719
<v Speaker 4>And I don't think that any of you are unfamiliar

58
00:02:44.840 --> 00:02:47.319
<v Speaker 4>with the fact that research is perpetually unique, right, and

59
00:02:47.360 --> 00:02:49.759
<v Speaker 4>we're research and we do it differently, and it requires

60
00:02:49.800 --> 00:02:52.280
<v Speaker 4>a different level of leadership and leaders who really understand

61
00:02:52.360 --> 00:02:55.159
<v Speaker 4>the challenges of the people who are working at the sites.

62
00:02:55.840 --> 00:02:57.919
<v Speaker 3>And I don't have any quick solutions.

63
00:02:58.039 --> 00:03:01.639
<v Speaker 4>I've got a lot of long, longer term, longer horizon solutions.

64
00:03:01.680 --> 00:03:04.400
<v Speaker 4>It really is just give the people a place where

65
00:03:04.400 --> 00:03:07.120
<v Speaker 4>they can do research and they're supported in the specific

66
00:03:07.159 --> 00:03:09.439
<v Speaker 4>activities that they need to do to do research. So

67
00:03:09.520 --> 00:03:11.960
<v Speaker 4>really focus on retention and I think you get a

68
00:03:11.960 --> 00:03:16.240
<v Speaker 4>group of people in research that are really passionate about

69
00:03:16.240 --> 00:03:19.000
<v Speaker 4>the science and also the care delivery. That's the people

70
00:03:19.000 --> 00:03:20.680
<v Speaker 4>that you have at the sites, and they want to

71
00:03:20.719 --> 00:03:23.039
<v Speaker 4>be there, right And I know there's a lot of

72
00:03:23.039 --> 00:03:26.039
<v Speaker 4>great jobs in industry and people who are great at

73
00:03:26.039 --> 00:03:27.919
<v Speaker 4>that and want to do that will find their way there.

74
00:03:28.639 --> 00:03:30.319
<v Speaker 3>A lot of people who work at the sites.

75
00:03:30.159 --> 00:03:32.479
<v Speaker 4>Want to be there and just want an infrastructure and

76
00:03:32.520 --> 00:03:35.599
<v Speaker 4>a leadership team that supports them. And so it requires

77
00:03:35.680 --> 00:03:39.360
<v Speaker 4>having the middle management team that really understand what the

78
00:03:39.360 --> 00:03:41.719
<v Speaker 4>work of the CRC is and how that's different from

79
00:03:41.719 --> 00:03:44.479
<v Speaker 4>the data manager and how that's different from the pharmacy

80
00:03:44.560 --> 00:03:47.960
<v Speaker 4>tech and they're getting really specific about what the job

81
00:03:48.520 --> 00:03:50.759
<v Speaker 4>needs to be. We're not good at measuring what their

82
00:03:50.879 --> 00:03:54.719
<v Speaker 4>units of service are right and knowing what each job

83
00:03:54.800 --> 00:03:57.719
<v Speaker 4>needs to be and reassessing that as the protocol has changed.

84
00:03:57.759 --> 00:04:00.439
<v Speaker 3>The protocols are changing, and so it's just keeping finger

85
00:04:00.520 --> 00:04:01.199
<v Speaker 3>on that pulse.

86
00:04:01.639 --> 00:04:06.319
<v Speaker 4>So I'd say great managers role delineation a lot of ways,

87
00:04:07.000 --> 00:04:10.919
<v Speaker 4>a focus on retention more so than recruitment, and thinking

88
00:04:11.039 --> 00:04:14.520
<v Speaker 4>through career levels and how we can move pharmacy techs

89
00:04:14.560 --> 00:04:17.800
<v Speaker 4>up a ladder and how we can move research coordinators

90
00:04:17.879 --> 00:04:21.319
<v Speaker 4>up a ladder and also not let the jobs get

91
00:04:21.439 --> 00:04:26.120
<v Speaker 4>so big for those patient care facing people that we

92
00:04:26.360 --> 00:04:29.480
<v Speaker 4>forget that they have an impossible job. So like this

93
00:04:29.639 --> 00:04:32.720
<v Speaker 4>constant assessment of what's the highest and best use of

94
00:04:32.800 --> 00:04:35.680
<v Speaker 4>our licensed team, what's the highest and best use of

95
00:04:35.720 --> 00:04:39.879
<v Speaker 4>our research experience team, and calling away all the junk

96
00:04:40.360 --> 00:04:42.319
<v Speaker 4>that they don't need to be doing and finding the

97
00:04:43.439 --> 00:04:46.279
<v Speaker 4>right role to do that. So splitting the roles very finely,

98
00:04:46.360 --> 00:04:49.800
<v Speaker 4>focusing on retention, focusing on career ladders, making sure you

99
00:04:49.839 --> 00:04:53.240
<v Speaker 4>have managers who get research and who want to support

100
00:04:53.360 --> 00:04:55.959
<v Speaker 4>a team of people that want to do research.

101
00:04:57.319 --> 00:05:00.279
<v Speaker 1>So a very deliberate focus on career path thing and

102
00:05:00.399 --> 00:05:03.079
<v Speaker 1>career development, really elevating the role of folks at the site.

103
00:05:03.079 --> 00:05:05.959
<v Speaker 1>I think that earns a green card to give out

104
00:05:05.959 --> 00:05:07.240
<v Speaker 1>that oh wow stage if I try.

105
00:05:08.600 --> 00:05:08.680
<v Speaker 5>So.

106
00:05:09.199 --> 00:05:13.519
<v Speaker 1>What struck me is that there's also a parallel opportunity

107
00:05:13.560 --> 00:05:16.000
<v Speaker 1>for potentially and Eileen, I think if you could explain

108
00:05:16.000 --> 00:05:18.759
<v Speaker 1>a little bit perhaps in your role insite partnerships, how

109
00:05:18.800 --> 00:05:21.160
<v Speaker 1>as a sponsor we may parallel some of the same

110
00:05:21.920 --> 00:05:24.399
<v Speaker 1>solutions that Lisa was kind enough to share.

111
00:05:25.600 --> 00:05:30.240
<v Speaker 6>Sure, so as a as a sponsor, you know, obviously

112
00:05:30.319 --> 00:05:33.920
<v Speaker 6>working with the sites, you want to have a nice

113
00:05:34.240 --> 00:05:37.360
<v Speaker 6>relationship and you want to really listen to your sites

114
00:05:37.639 --> 00:05:40.920
<v Speaker 6>and try to make adjustments where you can to make

115
00:05:40.959 --> 00:05:44.800
<v Speaker 6>the burden on the sites less and whatever, you know,

116
00:05:45.120 --> 00:05:47.240
<v Speaker 6>way you can do that in terms of having a

117
00:05:47.279 --> 00:05:50.560
<v Speaker 6>system with a single sign on if that's something you

118
00:05:50.600 --> 00:05:52.839
<v Speaker 6>know that that is something that we hear a lot

119
00:05:52.879 --> 00:05:55.600
<v Speaker 6>from sites that there's just so many systems and so

120
00:05:55.639 --> 00:05:58.639
<v Speaker 6>many processes and how can we you know, how you know,

121
00:05:58.879 --> 00:06:01.879
<v Speaker 6>can't you make this easy for us? So I think

122
00:06:02.839 --> 00:06:05.000
<v Speaker 6>not only CSL Barn, but I think a lot of

123
00:06:05.040 --> 00:06:09.639
<v Speaker 6>the pharmaceutical companies are looking to try to take that

124
00:06:09.680 --> 00:06:11.600
<v Speaker 6>burden and lessen it for the sites.

125
00:06:13.759 --> 00:06:17.480
<v Speaker 1>Tracy, if I could ask you, yeah, Bearinger, are you

126
00:06:17.560 --> 00:06:18.240
<v Speaker 1>creating roles?

127
00:06:18.240 --> 00:06:20.399
<v Speaker 2>Are you taking similar approaches? How are you upscaling your

128
00:06:20.439 --> 00:06:22.639
<v Speaker 2>workforce to support sites?

129
00:06:22.959 --> 00:06:26.439
<v Speaker 5>It's actually not necessarily upskilling, but it's reflecting on the

130
00:06:26.480 --> 00:06:28.800
<v Speaker 5>points that have been made both from a site perspective

131
00:06:28.879 --> 00:06:35.240
<v Speaker 5>and from a sponsor perspective. It's really listening and working together.

132
00:06:35.279 --> 00:06:39.439
<v Speaker 5>We've spoken a lot about co creation with patients, but

133
00:06:39.600 --> 00:06:43.800
<v Speaker 5>we're actually also focusing on co creation with sites. So

134
00:06:44.279 --> 00:06:46.959
<v Speaker 5>taking the time to get the feedback, really understanding what's

135
00:06:47.000 --> 00:06:51.519
<v Speaker 5>important to them and seeing whether or not by implementing

136
00:06:51.560 --> 00:06:56.759
<v Speaker 5>certain solutions, we're actually addressing the core like the personal

137
00:06:56.959 --> 00:06:59.600
<v Speaker 5>problem that people have with the personal challenge that they

138
00:06:59.639 --> 00:07:03.279
<v Speaker 5>have could be as simple as identifying a single point

139
00:07:03.319 --> 00:07:08.199
<v Speaker 5>of contact for support questions. But it's also recognizing that

140
00:07:08.279 --> 00:07:11.800
<v Speaker 5>there isn't a one size fits all because the sites

141
00:07:11.879 --> 00:07:15.079
<v Speaker 5>are all very unique, their focus is slightly different, their

142
00:07:15.079 --> 00:07:17.680
<v Speaker 5>management is slightly different, and so we actually have to

143
00:07:17.680 --> 00:07:20.920
<v Speaker 5>look at what's the as far as we can can

144
00:07:20.959 --> 00:07:23.240
<v Speaker 5>we actually take it to that level where it is

145
00:07:23.720 --> 00:07:27.839
<v Speaker 5>a site specific solution within you know, the broad range

146
00:07:27.879 --> 00:07:28.759
<v Speaker 5>of what we can do.

147
00:07:29.920 --> 00:07:32.600
<v Speaker 1>Excellent, So please take a couple of cards and share

148
00:07:32.639 --> 00:07:37.160
<v Speaker 1>them with Eileen as well. Chris sites site specific solutions.

149
00:07:37.160 --> 00:07:40.720
<v Speaker 1>I see nodding quite a bit as Tracy was describing that,

150
00:07:41.519 --> 00:07:43.759
<v Speaker 1>what's your your reaction to that, as as someone who

151
00:07:43.839 --> 00:07:46.319
<v Speaker 1>works at a site, someone who has oversight over the

152
00:07:46.360 --> 00:07:49.240
<v Speaker 1>research at Sydney Kimmel, how does that resonate with you?

153
00:07:49.839 --> 00:07:50.079
<v Speaker 3>Sure?

154
00:07:50.160 --> 00:07:53.079
<v Speaker 7>Thank you so, Kristin Hermann, Executive director of the Clinical

155
00:07:53.120 --> 00:07:57.040
<v Speaker 7>Trials Office at Sydney Kimmel Comprehensive Cancer Center, And I

156
00:07:57.040 --> 00:08:01.560
<v Speaker 7>would say you know, I've been to the cancer center

157
00:08:02.000 --> 00:08:04.759
<v Speaker 7>at Sidney Kimmel for the last two years, and when

158
00:08:04.800 --> 00:08:09.040
<v Speaker 7>I started in the position, we had forty percent turnover annually,

159
00:08:09.639 --> 00:08:12.399
<v Speaker 7>and that will crush us, and it will crush your trials.

160
00:08:13.319 --> 00:08:15.800
<v Speaker 7>They're not going to get done. And so you know,

161
00:08:15.879 --> 00:08:18.720
<v Speaker 7>that was the immediate concern and the fire that we

162
00:08:18.800 --> 00:08:22.000
<v Speaker 7>needed to fight. And within eighteen months we had that

163
00:08:22.079 --> 00:08:27.199
<v Speaker 7>turnover down to thirteen percent, and so that's a big difference.

164
00:08:27.199 --> 00:08:31.600
<v Speaker 7>But retention is the key indicator right over time, and

165
00:08:31.639 --> 00:08:33.200
<v Speaker 7>so we're still looking at that retention.

166
00:08:34.200 --> 00:08:34.799
<v Speaker 3>But some of the.

167
00:08:34.759 --> 00:08:37.000
<v Speaker 7>Things I think that we're really helpful. You had touched

168
00:08:37.039 --> 00:08:41.320
<v Speaker 7>on previously about these generational differences, the differences in the

169
00:08:41.360 --> 00:08:44.559
<v Speaker 7>folks that we are hiring and recognizing who they are

170
00:08:44.600 --> 00:08:47.000
<v Speaker 7>and what their background is and what they care about,

171
00:08:47.080 --> 00:08:50.679
<v Speaker 7>and so you know, this youngest generation perhaps doesn't maybe

172
00:08:50.720 --> 00:08:53.720
<v Speaker 7>even think that retirement's going to be a reasonable option

173
00:08:53.799 --> 00:08:56.240
<v Speaker 7>for them, and so thinking that they're going to want

174
00:08:56.240 --> 00:08:59.960
<v Speaker 7>to work overtime for you is maybe, you know, not.

175
00:09:02.279 --> 00:09:02.960
<v Speaker 3>A reality.

176
00:09:04.399 --> 00:09:06.440
<v Speaker 7>While we have some of our staff who've been with

177
00:09:06.559 --> 00:09:11.399
<v Speaker 7>us longer and very much you know, maybe that's like

178
00:09:11.600 --> 00:09:15.759
<v Speaker 7>our clinicians that are kind of mid career, our managers

179
00:09:15.759 --> 00:09:18.600
<v Speaker 7>that are mid career, who really are going to want

180
00:09:18.639 --> 00:09:20.720
<v Speaker 7>to be moving up. And so I think taking the

181
00:09:20.759 --> 00:09:24.480
<v Speaker 7>consideration who you're hiring and what their interests are, and

182
00:09:24.519 --> 00:09:29.200
<v Speaker 7>then customizing the job to a degree and the opportunities

183
00:09:29.200 --> 00:09:31.840
<v Speaker 7>to their needs. So whether they're desiring to go back

184
00:09:31.879 --> 00:09:34.720
<v Speaker 7>to school and you can kind of highlight those opportunities,

185
00:09:34.759 --> 00:09:38.559
<v Speaker 7>whether they're looking for specific experiences. There will be people

186
00:09:38.639 --> 00:09:40.799
<v Speaker 7>who want to go back to school and get an MBA,

187
00:09:41.200 --> 00:09:43.840
<v Speaker 7>and then I want to put them on connecting them

188
00:09:43.840 --> 00:09:47.559
<v Speaker 7>with our finance folks and our contracts folks. They still

189
00:09:47.600 --> 00:09:49.679
<v Speaker 7>may be a data manager, but they can learn a

190
00:09:49.679 --> 00:09:53.639
<v Speaker 7>whole lot more about the business internally and then help

191
00:09:53.679 --> 00:09:56.120
<v Speaker 7>them to sit in on sponsor meetings, help them sit

192
00:09:56.159 --> 00:09:59.639
<v Speaker 7>down on budget negotiation. And so I think developing people

193
00:09:59.759 --> 00:10:03.080
<v Speaker 7>that way and customizing the opportunities to their interests isn't

194
00:10:03.120 --> 00:10:06.360
<v Speaker 7>a real opportunity. And so I kind of say, you know,

195
00:10:06.440 --> 00:10:11.440
<v Speaker 7>I think that there are additionally opportunities, you know, sponsor

196
00:10:11.840 --> 00:10:15.559
<v Speaker 7>and site, especially academic site opportunities that I think we

197
00:10:15.639 --> 00:10:20.159
<v Speaker 7>have yet to explore. This kind of like symbiotic desire

198
00:10:20.320 --> 00:10:25.480
<v Speaker 7>to keep our trials staffed and recognizing that there will

199
00:10:25.559 --> 00:10:28.639
<v Speaker 7>be people looking to build their careers both in academia

200
00:10:28.679 --> 00:10:32.000
<v Speaker 7>but also an industry, and so how can we share better?

201
00:10:32.840 --> 00:10:35.240
<v Speaker 7>How can we know that as an academic center, we

202
00:10:35.279 --> 00:10:39.720
<v Speaker 7>are primed to educate and train people, but we all

203
00:10:39.759 --> 00:10:42.480
<v Speaker 7>do better when we know a little bit more about

204
00:10:42.519 --> 00:10:45.519
<v Speaker 7>each other. And so, you know, we did have somebody

205
00:10:45.519 --> 00:10:48.360
<v Speaker 7>on our team who started as a coordinator. She ended

206
00:10:48.440 --> 00:10:52.000
<v Speaker 7>up going to industry. She worked as a monitor and

207
00:10:52.039 --> 00:10:55.240
<v Speaker 7>she decided that you know, she had experience there that

208
00:10:55.279 --> 00:10:58.120
<v Speaker 7>she liked, but she really missed the patient interaction. And

209
00:10:58.159 --> 00:11:01.279
<v Speaker 7>she came back and it has been so valuable to

210
00:11:01.360 --> 00:11:05.759
<v Speaker 7>us to have her insider industry experience on our team.

211
00:11:06.039 --> 00:11:10.639
<v Speaker 7>That's improved the quality of our monitoring visits, our documentation,

212
00:11:10.960 --> 00:11:13.399
<v Speaker 7>and so I think that there's also an opportunity for

213
00:11:13.480 --> 00:11:15.840
<v Speaker 7>us to explore that further.

214
00:11:17.159 --> 00:11:19.120
<v Speaker 1>So the common theme I think we hear please take

215
00:11:19.159 --> 00:11:21.679
<v Speaker 1>a card. I think that's an excellent solution is really

216
00:11:21.720 --> 00:11:26.759
<v Speaker 1>creating persons specific approaches right tailoring some of the experience. Chris,

217
00:11:26.840 --> 00:11:28.320
<v Speaker 1>I want to bring you into this because I think

218
00:11:28.440 --> 00:11:31.759
<v Speaker 1>the thread that I heard through that was the experience

219
00:11:32.080 --> 00:11:35.840
<v Speaker 1>at the site, whether that's a sponsor creating that experience,

220
00:11:35.919 --> 00:11:40.639
<v Speaker 1>by being more site centric, whether that's the leadership at

221
00:11:40.639 --> 00:11:44.200
<v Speaker 1>the site or the site network, providing professional development and

222
00:11:44.279 --> 00:11:47.000
<v Speaker 1>things that create a better employment experience. What are some

223
00:11:47.039 --> 00:11:49.080
<v Speaker 1>things from your perspective if you could share a little

224
00:11:49.120 --> 00:11:51.279
<v Speaker 1>bit about your role then that you see that might

225
00:11:51.320 --> 00:11:54.360
<v Speaker 1>create a more positive work experience at the sites.

226
00:11:54.840 --> 00:11:55.600
<v Speaker 2>Yeah. Sure, So.

227
00:11:55.799 --> 00:11:58.679
<v Speaker 8>I am Chris mcnairm, the director of Data Science also

228
00:11:58.679 --> 00:12:01.759
<v Speaker 8>at the Singe Chemical Comprehensive Center, and so in the

229
00:12:01.759 --> 00:12:06.240
<v Speaker 8>clinical trial space, my team leads the clinical trial analytics

230
00:12:06.240 --> 00:12:09.000
<v Speaker 8>and the reporting groups. But I think one of the things,

231
00:12:09.159 --> 00:12:11.799
<v Speaker 8>you know, I think kudos to Christen when when she

232
00:12:12.000 --> 00:12:15.720
<v Speaker 8>came in, was how can we take all of these

233
00:12:15.840 --> 00:12:19.519
<v Speaker 8>pain points from the staff, right, and you know, automate

234
00:12:19.559 --> 00:12:21.919
<v Speaker 8>some of them, right. Nobody wants to spend their days

235
00:12:22.320 --> 00:12:25.960
<v Speaker 8>chasing people down through emails and manually filling out, you know,

236
00:12:26.039 --> 00:12:28.360
<v Speaker 8>word documents that they have to chief back through. So

237
00:12:28.399 --> 00:12:33.039
<v Speaker 8>it was basically tell us what you are doing repetitively

238
00:12:33.080 --> 00:12:35.840
<v Speaker 8>on a day today. And this is kind of between people,

239
00:12:35.919 --> 00:12:38.240
<v Speaker 8>but also between our different disease groups. Why are we

240
00:12:38.279 --> 00:12:41.279
<v Speaker 8>reinventing the wheel between all of our different disease groups

241
00:12:41.320 --> 00:12:44.879
<v Speaker 8>from study feasibility to startup to all of these different pieces,

242
00:12:45.159 --> 00:12:47.720
<v Speaker 8>and so it was really going back to see, you know,

243
00:12:47.879 --> 00:12:50.159
<v Speaker 8>what can we create so that people don't have to

244
00:12:50.200 --> 00:12:53.600
<v Speaker 8>spend their day doing these manual, repetitive tasks and can

245
00:12:53.639 --> 00:12:56.360
<v Speaker 8>actually spend it doing things that they enjoy. And I

246
00:12:56.399 --> 00:12:58.960
<v Speaker 8>think one of the things for us that you know,

247
00:12:59.120 --> 00:13:01.919
<v Speaker 8>I don't think this solution has to be the sexiest

248
00:13:01.919 --> 00:13:03.679
<v Speaker 8>thing is in the world, as long as it gets

249
00:13:03.679 --> 00:13:06.039
<v Speaker 8>the job done. And so we've been able to automate

250
00:13:06.120 --> 00:13:08.639
<v Speaker 8>a ton of just the you know, normal day to

251
00:13:08.679 --> 00:13:11.279
<v Speaker 8>day operations just using you know, data capture and you

252
00:13:11.320 --> 00:13:15.039
<v Speaker 8>know reporting software, and I think that's been kind of

253
00:13:15.360 --> 00:13:17.879
<v Speaker 8>a huge relief to the folks that have been involved.

254
00:13:17.919 --> 00:13:20.320
<v Speaker 8>And then I think it starts to create this feed

255
00:13:20.360 --> 00:13:23.120
<v Speaker 8>forward loop. I think initially, you know, change is kind

256
00:13:23.159 --> 00:13:25.480
<v Speaker 8>of hard for everybody. So even if it's like we're

257
00:13:25.480 --> 00:13:27.720
<v Speaker 8>trying to make your life easier by getting you know,

258
00:13:27.759 --> 00:13:29.759
<v Speaker 8>these papers out of your hand, it's a little bit

259
00:13:29.799 --> 00:13:31.960
<v Speaker 8>of book. Have always used this paper? Why why you're

260
00:13:31.960 --> 00:13:34.679
<v Speaker 8>taking this paper away from me? But I think once

261
00:13:34.720 --> 00:13:37.799
<v Speaker 8>you kind of change that mindset, then people will come

262
00:13:37.799 --> 00:13:41.840
<v Speaker 8>to us more to kind of proactively say, hey, I'm

263
00:13:41.879 --> 00:13:43.960
<v Speaker 8>doing this thing. It's kind of a pain point for me.

264
00:13:44.000 --> 00:13:47.919
<v Speaker 8>It seems similar to other processes that we've automated. Can

265
00:13:47.960 --> 00:13:50.559
<v Speaker 8>you help us fix this? So I think that's been

266
00:13:50.679 --> 00:13:53.360
<v Speaker 8>very helpful and I think also rewarding for the team

267
00:13:53.480 --> 00:13:56.080
<v Speaker 8>to kind of see what they've built be used on

268
00:13:56.120 --> 00:13:56.720
<v Speaker 8>the day to day.

269
00:13:58.320 --> 00:14:00.519
<v Speaker 1>Well, I have a question for the panel, but I

270
00:14:00.559 --> 00:14:03.440
<v Speaker 1>think this is for everyone on the panel. How are

271
00:14:03.480 --> 00:14:06.360
<v Speaker 1>those sorts of situations being surfaced back to sponsors? I

272
00:14:06.399 --> 00:14:08.600
<v Speaker 1>bet Tracy or Eileen, you'd love to hear where a

273
00:14:08.639 --> 00:14:10.519
<v Speaker 1>site has figured out how to do that and share

274
00:14:10.519 --> 00:14:12.759
<v Speaker 1>it with every site you work with. But has anyone

275
00:14:12.799 --> 00:14:15.759
<v Speaker 1>had that experience? Is anyone having that dialogue within their

276
00:14:15.799 --> 00:14:18.639
<v Speaker 1>relationships to share those sorts of things.

277
00:14:20.360 --> 00:14:24.440
<v Speaker 5>I'm going to say for our part, we sometimes hear

278
00:14:24.480 --> 00:14:31.440
<v Speaker 5>it a little more randomly. Ad hoc. We systematically get

279
00:14:31.480 --> 00:14:37.639
<v Speaker 5>feedback on the challenges, but we are yet to see if,

280
00:14:37.679 --> 00:14:40.879
<v Speaker 5>for example, we start to see in the uptick in

281
00:14:41.480 --> 00:14:44.720
<v Speaker 5>let's say there is a challenge associated with the use

282
00:14:44.759 --> 00:14:48.320
<v Speaker 5>of technology, and we maybe see this consistently coming back

283
00:14:48.320 --> 00:14:52.279
<v Speaker 5>from our sites. If we see next time round that

284
00:14:52.399 --> 00:14:55.440
<v Speaker 5>this is scoring higher in the trial experience, survice that

285
00:14:55.519 --> 00:15:00.240
<v Speaker 5>we will regularly be sending out we already know. Yes,

286
00:15:00.240 --> 00:15:03.159
<v Speaker 5>there's certain things that we would expect maybe to see

287
00:15:03.559 --> 00:15:07.039
<v Speaker 5>based on what we're doing. But I think it's going

288
00:15:07.080 --> 00:15:10.080
<v Speaker 5>to be an interesting thing if we not necessarily made

289
00:15:10.360 --> 00:15:14.159
<v Speaker 5>any changes, do we then have the mechanism or it's

290
00:15:14.240 --> 00:15:16.600
<v Speaker 5>worth us taking it back to say, Okay, we need

291
00:15:16.639 --> 00:15:19.960
<v Speaker 5>to put in place the mechanism for following up if

292
00:15:20.000 --> 00:15:26.879
<v Speaker 5>we've got this let's say, unprecedented change coming back in

293
00:15:26.879 --> 00:15:29.080
<v Speaker 5>the feedback, because it may not be anything that we've done,

294
00:15:29.120 --> 00:15:32.200
<v Speaker 5>it may be something that they've done on the site themselves.

295
00:15:32.519 --> 00:15:34.720
<v Speaker 5>So I think it's a feedback loope that we need

296
00:15:34.759 --> 00:15:37.519
<v Speaker 5>to systematically put in place to make sure that we're

297
00:15:37.519 --> 00:15:40.279
<v Speaker 5>actually recognizing the actions that not just that we're taking,

298
00:15:40.320 --> 00:15:42.519
<v Speaker 5>but also that the sites are taking.

299
00:15:43.639 --> 00:15:47.519
<v Speaker 3>I think from my standpoint, it's really tempting to.

300
00:15:49.120 --> 00:15:52.840
<v Speaker 4>Find an automated solution that's going to fix your problem,

301
00:15:52.919 --> 00:15:54.879
<v Speaker 4>right because we've got a ton of problems, and it

302
00:15:54.879 --> 00:15:57.039
<v Speaker 4>would be so easy to say, if we just had

303
00:15:57.039 --> 00:16:00.399
<v Speaker 4>this system, this problem will go away, and times out

304
00:16:00.440 --> 00:16:02.919
<v Speaker 4>of ten, in my experience, there's an issue with the

305
00:16:03.159 --> 00:16:06.519
<v Speaker 4>with the functional process right where just something that is

306
00:16:06.559 --> 00:16:09.720
<v Speaker 4>not sexy at all is broken and you've just got

307
00:16:09.759 --> 00:16:12.720
<v Speaker 4>to like roll your sleeves up and resist the urge

308
00:16:12.759 --> 00:16:15.120
<v Speaker 4>to find a thingy that'll fix it, and just say,

309
00:16:15.360 --> 00:16:17.120
<v Speaker 4>how are we going to fix the process and kind

310
00:16:17.159 --> 00:16:20.320
<v Speaker 4>of do the hard work of getting the functional process

311
00:16:20.399 --> 00:16:20.879
<v Speaker 4>ready to go.

312
00:16:21.240 --> 00:16:22.679
<v Speaker 3>Once you really know that.

313
00:16:22.679 --> 00:16:26.799
<v Speaker 4>Your functional process is working, then yes, absolutely automate. But

314
00:16:26.840 --> 00:16:29.399
<v Speaker 4>I think you really need from the site standpoint at

315
00:16:29.480 --> 00:16:32.399
<v Speaker 4>least to kick tires on is tech really going to

316
00:16:32.480 --> 00:16:32.840
<v Speaker 4>fix this?

317
00:16:33.080 --> 00:16:35.120
<v Speaker 3>Or do we have some hard work to do that's.

318
00:16:34.960 --> 00:16:38.720
<v Speaker 4>Going to require change and multiple departments at the table

319
00:16:38.759 --> 00:16:40.559
<v Speaker 4>and a little bit of arm wrestling for us to

320
00:16:40.600 --> 00:16:42.840
<v Speaker 4>decide here's how we're going to do it. And in

321
00:16:42.879 --> 00:16:46.759
<v Speaker 4>those cases like our drug accountability platform, I think is

322
00:16:46.759 --> 00:16:49.480
<v Speaker 4>probably the best one where we were sure, sure sure

323
00:16:49.639 --> 00:16:52.840
<v Speaker 4>that we had a solution that would really help us

324
00:16:52.960 --> 00:16:56.720
<v Speaker 4>as the site and then we've you know, deployed that

325
00:16:56.840 --> 00:16:59.080
<v Speaker 4>at all of our sites and we love it in

326
00:16:59.159 --> 00:17:01.759
<v Speaker 4>our pharmacists are all always perfect when it comes to

327
00:17:01.840 --> 00:17:04.559
<v Speaker 4>audits and monitors, you know, because we've got a very

328
00:17:04.599 --> 00:17:08.920
<v Speaker 4>fit for purpose solution. But it took us several years

329
00:17:08.920 --> 00:17:11.839
<v Speaker 4>of ground lane to go, Okay, now we're ready to

330
00:17:11.880 --> 00:17:13.000
<v Speaker 4>put this on a flywheel.

331
00:17:13.920 --> 00:17:16.480
<v Speaker 8>Yeah, I just want to echo those sentiments to about

332
00:17:16.519 --> 00:17:21.240
<v Speaker 8>needing to have a standard process across all of your

333
00:17:21.720 --> 00:17:24.359
<v Speaker 8>different pieces, right, because I think you made a great

334
00:17:24.400 --> 00:17:27.119
<v Speaker 8>point about no amount of technology in the world is

335
00:17:27.119 --> 00:17:30.119
<v Speaker 8>going to fix a process that is not standard and

336
00:17:30.240 --> 00:17:31.880
<v Speaker 8>is not working already.

337
00:17:31.960 --> 00:17:32.079
<v Speaker 5>Right.

338
00:17:32.119 --> 00:17:34.720
<v Speaker 8>You need a place where you say, here's our process,

339
00:17:34.720 --> 00:17:37.480
<v Speaker 8>and here is the exact area where this technology is

340
00:17:37.480 --> 00:17:40.039
<v Speaker 8>actually going to help us. Otherwise you're just going to

341
00:17:40.079 --> 00:17:43.160
<v Speaker 8>have a different technology for every single different problem that

342
00:17:43.200 --> 00:17:46.279
<v Speaker 8>comes up, which is just not going to work for

343
00:17:46.640 --> 00:17:47.799
<v Speaker 8>the entirety to site.

344
00:17:48.200 --> 00:17:48.440
<v Speaker 3>Yeah.

345
00:17:48.480 --> 00:17:51.160
<v Speaker 7>So, and I can add to that because Chris and

346
00:17:51.160 --> 00:17:54.319
<v Speaker 7>I have worked on specific projects and I'm imagining he's

347
00:17:54.359 --> 00:17:59.079
<v Speaker 7>thinking about specifically clinical trial matching platforms, which we've explored

348
00:17:59.480 --> 00:18:04.880
<v Speaker 7>and are about. But we recognized after meeting with several

349
00:18:04.960 --> 00:18:07.720
<v Speaker 7>vendors that we actually had our own work to do

350
00:18:08.599 --> 00:18:11.480
<v Speaker 7>before we were primed to really take advantage of the

351
00:18:11.480 --> 00:18:15.640
<v Speaker 7>technology that exists there just in our own process, and

352
00:18:15.720 --> 00:18:20.680
<v Speaker 7>that taking on the technology, you know, really that wasn't

353
00:18:20.680 --> 00:18:22.400
<v Speaker 7>going to solve our process issue.

354
00:18:22.400 --> 00:18:25.039
<v Speaker 3>We need to solve our process issue first.

355
00:18:24.720 --> 00:18:28.359
<v Speaker 7>And kind of figure out those customized roles and how

356
00:18:28.400 --> 00:18:30.839
<v Speaker 7>they're doing the work today and then be able to

357
00:18:30.920 --> 00:18:36.160
<v Speaker 7>kind of exploit that knowledge base and primate for the technology.

358
00:18:37.000 --> 00:18:40.160
<v Speaker 1>That's fascinating. I think it makes me wonder and cringe

359
00:18:40.160 --> 00:18:42.279
<v Speaker 1>a little bit as a sponsor just when we impose

360
00:18:42.359 --> 00:18:46.960
<v Speaker 1>technology on a site hearing that feedback, you know, how

361
00:18:47.000 --> 00:18:49.119
<v Speaker 1>well do we know and are we listening to hear

362
00:18:49.160 --> 00:18:49.839
<v Speaker 1>what that might.

363
00:18:49.720 --> 00:18:52.880
<v Speaker 2>Do to their processes of their day to day.

364
00:18:53.279 --> 00:18:55.960
<v Speaker 1>Aileen, I don't know if through your work in site partnerships,

365
00:18:55.960 --> 00:18:58.559
<v Speaker 1>if you've had those dialogue you mentioned single sign on earlier,

366
00:18:58.599 --> 00:19:03.519
<v Speaker 1>are there any solutions maybe to how you've seen this approach,

367
00:19:03.880 --> 00:19:05.640
<v Speaker 1>you know, in terms of technology of sites.

368
00:19:08.519 --> 00:19:11.519
<v Speaker 6>In terms of technology, I have had feedback from sites

369
00:19:11.519 --> 00:19:16.119
<v Speaker 6>obviously about all of the technology that sponsor imposes upon sites.

370
00:19:17.640 --> 00:19:20.799
<v Speaker 6>And the thing is to continue to listen to the

371
00:19:20.839 --> 00:19:24.920
<v Speaker 6>sites and obviously there are certain things that we have

372
00:19:25.039 --> 00:19:27.759
<v Speaker 6>to have in place, but there are definitely ways that

373
00:19:27.799 --> 00:19:32.640
<v Speaker 6>we can improve how we're deploying them to the sites

374
00:19:32.680 --> 00:19:37.880
<v Speaker 6>and what we're requiring of the sites, and sponsors should

375
00:19:37.920 --> 00:19:43.480
<v Speaker 6>continue to look for solutions with vendors to make these

376
00:19:43.519 --> 00:19:47.960
<v Speaker 6>processes and technologies easier on the sites whenever possible.

377
00:19:48.599 --> 00:19:50.039
<v Speaker 7>Yay, love that comment.

378
00:19:51.480 --> 00:19:54.440
<v Speaker 1>So any tech solutions providers face you know in the

379
00:19:54.480 --> 00:19:57.480
<v Speaker 1>audience please take heed to that. One of the things

380
00:19:57.519 --> 00:20:02.119
<v Speaker 1>that struck me, h listening to presentation yesterday about a

381
00:20:02.160 --> 00:20:04.079
<v Speaker 1>topic that's near and dear to me is it was

382
00:20:04.119 --> 00:20:07.079
<v Speaker 1>around vendor qualification and around thinking differently about how we

383
00:20:07.119 --> 00:20:09.880
<v Speaker 1>do that and centralizing that I was it struck me

384
00:20:09.920 --> 00:20:13.279
<v Speaker 1>as very analogous to when we go out we qualify sites,

385
00:20:13.279 --> 00:20:16.319
<v Speaker 1>and we do pssbs and you know, pre study visits.

386
00:20:16.000 --> 00:20:19.119
<v Speaker 2>And all of these things are there areas there If.

387
00:20:18.960 --> 00:20:21.359
<v Speaker 1>I could challenge the panel to think about where there

388
00:20:21.480 --> 00:20:26.039
<v Speaker 1>might be opportunities to streamline, whether it includes technology or

389
00:20:26.319 --> 00:20:27.880
<v Speaker 1>process changes.

390
00:20:28.839 --> 00:20:33.640
<v Speaker 6>I think definitely. I've had I've heard multiple complaints from sites.

391
00:20:34.680 --> 00:20:37.319
<v Speaker 6>You know, we were just working on the study with you,

392
00:20:37.720 --> 00:20:40.640
<v Speaker 6>Why do you need to do another qualification visit? I know,

393
00:20:41.319 --> 00:20:44.400
<v Speaker 6>you know, one thing is an soop where if we're

394
00:20:44.799 --> 00:20:46.720
<v Speaker 6>you know, if we recently worked with the site, then

395
00:20:46.759 --> 00:20:52.519
<v Speaker 6>the PSB visit on site can be waived. So that's

396
00:20:52.559 --> 00:20:54.759
<v Speaker 6>one of the ways. But I think there are ways

397
00:20:54.759 --> 00:20:59.640
<v Speaker 6>for technology to help with ps PSBs and site qualification visits,

398
00:21:01.359 --> 00:21:04.079
<v Speaker 6>and I think sponsors should explore them a little more.

399
00:21:06.880 --> 00:21:10.559
<v Speaker 4>We put a lot of thought at start into the

400
00:21:10.720 --> 00:21:13.880
<v Speaker 4>study what we would say the study activation process, but

401
00:21:14.000 --> 00:21:17.000
<v Speaker 4>I think we think of that as a lot at

402
00:21:17.039 --> 00:21:21.240
<v Speaker 4>an earlier point, right, is not just like SIV is

403
00:21:22.319 --> 00:21:24.559
<v Speaker 4>the few things leading up to SIV is the study

404
00:21:24.599 --> 00:21:28.279
<v Speaker 4>activation process. But as soon as we have interest from

405
00:21:28.319 --> 00:21:32.519
<v Speaker 4>a sponsor and a potential protocol, having a fullsome conversation

406
00:21:32.680 --> 00:21:36.480
<v Speaker 4>about what systems do you intend to use from your

407
00:21:36.559 --> 00:21:40.799
<v Speaker 4>lab vendor, from EDC, any other e things that might

408
00:21:40.839 --> 00:21:43.440
<v Speaker 4>be in the cards, let's talk about that early on. Right,

409
00:21:43.480 --> 00:21:46.079
<v Speaker 4>we have to be flexible and as a site, we

410
00:21:46.160 --> 00:21:48.519
<v Speaker 4>work with hundreds of sponsors and we need to be

411
00:21:48.599 --> 00:21:49.839
<v Speaker 4>able to use.

412
00:21:49.720 --> 00:21:51.640
<v Speaker 3>Their systems and technologies. We get that.

413
00:21:52.200 --> 00:21:56.400
<v Speaker 4>And also if we are clear at the jump about

414
00:21:56.480 --> 00:21:58.559
<v Speaker 4>what it's going to take, what those systems are, and

415
00:21:58.599 --> 00:22:02.359
<v Speaker 4>we have some back and worth conversation at an earlier

416
00:22:02.359 --> 00:22:05.000
<v Speaker 4>stage than I think most of us are used to that,

417
00:22:05.160 --> 00:22:09.119
<v Speaker 4>it can really grease the skids for a successful study activation.

418
00:22:09.200 --> 00:22:10.559
<v Speaker 3>And you're not sitting there in the.

419
00:22:10.599 --> 00:22:13.519
<v Speaker 4>SIV with all of these surprises and like bombs going

420
00:22:13.559 --> 00:22:16.039
<v Speaker 4>off and gashing them the teeth, you know what's happened

421
00:22:17.119 --> 00:22:20.079
<v Speaker 4>where it can just make for like a much more

422
00:22:20.119 --> 00:22:24.079
<v Speaker 4>seamless process. So again I don't have any fancy solution

423
00:22:24.200 --> 00:22:26.519
<v Speaker 4>but it's really about thinking about all of these things

424
00:22:26.559 --> 00:22:29.279
<v Speaker 4>earlier on. I think the presence of all of the

425
00:22:29.319 --> 00:22:32.880
<v Speaker 4>new technologies requires us to have a deeper conversation.

426
00:22:32.839 --> 00:22:33.799
<v Speaker 3>At the PSSB.

427
00:22:34.000 --> 00:22:36.680
<v Speaker 4>We call it the discovery call, which is even preempting

428
00:22:36.720 --> 00:22:39.279
<v Speaker 4>the pss B to say, what are we really talking

429
00:22:39.319 --> 00:22:42.160
<v Speaker 4>about here? In terms of operations, we get the science

430
00:22:42.160 --> 00:22:44.759
<v Speaker 4>and our people are connected on the science, but operationally

431
00:22:45.480 --> 00:22:48.359
<v Speaker 4>our PK team wants to know what vendor you're going

432
00:22:48.440 --> 00:22:50.279
<v Speaker 4>to use to pick up the kits. Do you have

433
00:22:50.359 --> 00:22:52.480
<v Speaker 4>that information for us or not? And if not, can

434
00:22:52.519 --> 00:22:54.880
<v Speaker 4>you please chase that down so we could clear all

435
00:22:54.920 --> 00:22:58.400
<v Speaker 4>of this now. And that's been really key for us

436
00:22:58.440 --> 00:23:02.599
<v Speaker 4>in terms of making it, you know, a seamless integration,

437
00:23:02.880 --> 00:23:06.799
<v Speaker 4>in terms of getting that site study activated.

438
00:23:07.880 --> 00:23:11.799
<v Speaker 1>Earlier decision making and earlier communication around those key vendor

439
00:23:11.920 --> 00:23:14.079
<v Speaker 1>decisions sounds like a potential solution.

440
00:23:15.119 --> 00:23:18.079
<v Speaker 7>Yeah, And I would say, you know, echoing what Eileen said,

441
00:23:18.440 --> 00:23:20.599
<v Speaker 7>if you don't have to send someone to come do

442
00:23:20.720 --> 00:23:23.480
<v Speaker 7>the tour of the facility again for the you know,

443
00:23:23.599 --> 00:23:26.640
<v Speaker 7>second third or fourth time in the last two years.

444
00:23:26.680 --> 00:23:29.319
<v Speaker 7>I mean, you know, the question is like what's the value?

445
00:23:29.640 --> 00:23:31.640
<v Speaker 7>So many of the things have not changed, the rooms

446
00:23:31.640 --> 00:23:34.400
<v Speaker 7>haven't changed, the equipment hasn't changed, and are you sending

447
00:23:34.440 --> 00:23:36.480
<v Speaker 7>someone who's even qualified.

448
00:23:35.920 --> 00:23:37.599
<v Speaker 3>To evaluate what's there.

449
00:23:38.440 --> 00:23:42.160
<v Speaker 7>We're taking detailed, high resolution photographs and providing them, and

450
00:23:42.200 --> 00:23:44.559
<v Speaker 7>so just thinking about like that takes time away from

451
00:23:44.559 --> 00:23:48.319
<v Speaker 7>a coordinator who could be enrolling a patient. And so

452
00:23:48.799 --> 00:23:52.000
<v Speaker 7>you know that time is preparation time, and I just

453
00:23:52.000 --> 00:23:54.000
<v Speaker 7>think that there are opportunities to kind of cut the

454
00:23:54.039 --> 00:23:58.359
<v Speaker 7>fat on things that aren't essential and to gather the

455
00:23:58.480 --> 00:24:02.359
<v Speaker 7>information which is so common across so many of our

456
00:24:02.400 --> 00:24:06.680
<v Speaker 7>different sponsors and CROs that we work with. And so

457
00:24:07.039 --> 00:24:09.319
<v Speaker 7>you know, I think you had touched on before, Dennis.

458
00:24:09.759 --> 00:24:13.119
<v Speaker 7>You know this potential opportunity to kind of partner with

459
00:24:13.200 --> 00:24:16.160
<v Speaker 7>someone who can collect that information and then disperse it

460
00:24:16.240 --> 00:24:19.559
<v Speaker 7>and then we're only really answering questions that are really

461
00:24:19.680 --> 00:24:22.799
<v Speaker 7>pertinent to a specific trial at hand, and kind of

462
00:24:22.839 --> 00:24:27.039
<v Speaker 7>that big picture qualification of our site can really already

463
00:24:27.079 --> 00:24:30.960
<v Speaker 7>have been accomplished and not be this kind of repetitive burden.

464
00:24:31.279 --> 00:24:34.119
<v Speaker 7>Our staff turns over, right, we know that, and so

465
00:24:34.480 --> 00:24:36.599
<v Speaker 7>when they turn over and this is a new person

466
00:24:36.640 --> 00:24:40.599
<v Speaker 7>trying to address the PSSV, it's going to take longer.

467
00:24:40.640 --> 00:24:42.400
<v Speaker 7>And so I just think we can make the most

468
00:24:42.480 --> 00:24:46.640
<v Speaker 7>of the information that we already have and make it available.

469
00:24:47.240 --> 00:24:49.319
<v Speaker 1>So I think that's a call to action for any

470
00:24:49.559 --> 00:24:52.759
<v Speaker 1>tech or other innovators in the crowd. It sounds like

471
00:24:52.799 --> 00:24:55.680
<v Speaker 1>there's a solution opportunity there out in the market that

472
00:24:55.720 --> 00:24:57.200
<v Speaker 1>would satisfy both sponsors and.

473
00:24:57.480 --> 00:24:57.839
<v Speaker 7>Talk to me.

474
00:24:58.279 --> 00:24:59.240
<v Speaker 2>Yeah, there you go.

475
00:25:00.279 --> 00:25:03.160
<v Speaker 5>Yeah, I was going to say, just to add to that,

476
00:25:03.319 --> 00:25:06.640
<v Speaker 5>I think it's a very clear example of where I mean,

477
00:25:06.720 --> 00:25:10.000
<v Speaker 5>if I think of it from a sponsor's perspective, sponsors

478
00:25:10.319 --> 00:25:13.119
<v Speaker 5>all would like to be the sponsor of choice, right,

479
00:25:13.599 --> 00:25:17.400
<v Speaker 5>It's a common it's a common theme, but then we

480
00:25:17.480 --> 00:25:22.559
<v Speaker 5>still go out with an approach that reflects us selecting sites.

481
00:25:23.359 --> 00:25:27.240
<v Speaker 5>And so how do you switch that mindset around. It's

482
00:25:27.279 --> 00:25:29.599
<v Speaker 5>like you tackle that as a common problem, but you

483
00:25:29.640 --> 00:25:31.319
<v Speaker 5>know it's a shared probably.

484
00:25:31.799 --> 00:25:37.319
<v Speaker 7>And I've utilized all of Chris's skill set to kind

485
00:25:37.359 --> 00:25:40.160
<v Speaker 7>of help us approach that, right. And so when we

486
00:25:40.240 --> 00:25:44.160
<v Speaker 7>start looking at activation, we have dashboards and metrics, and

487
00:25:44.200 --> 00:25:47.839
<v Speaker 7>we're kind of looking at those and evaluating not just

488
00:25:47.920 --> 00:25:50.519
<v Speaker 7>our own performance, but also the sponsors that we work

489
00:25:50.559 --> 00:25:53.319
<v Speaker 7>with to say, hey, we want to prioritize this trial

490
00:25:53.359 --> 00:25:55.720
<v Speaker 7>because we know we can get this contract and budget

491
00:25:55.759 --> 00:25:58.000
<v Speaker 7>done with them and we can start in rolling patients.

492
00:25:58.720 --> 00:26:02.240
<v Speaker 7>And so we really are keeping that in mind as

493
00:26:02.279 --> 00:26:05.200
<v Speaker 7>we prioritize the work that we're doing. Who do we know,

494
00:26:05.519 --> 00:26:07.880
<v Speaker 7>as you know, when we work with your legal it's

495
00:26:07.920 --> 00:26:10.519
<v Speaker 7>going to take a lot longer than most other folks,

496
00:26:11.440 --> 00:26:14.480
<v Speaker 7>and so you know, that's really a way for us

497
00:26:14.559 --> 00:26:17.960
<v Speaker 7>to kind of streamline things and also put a little

498
00:26:17.960 --> 00:26:20.759
<v Speaker 7>pressure on to say, hey, this is kind of taking

499
00:26:20.920 --> 00:26:24.400
<v Speaker 7>longer than some other sponsors that we work with, and

500
00:26:24.440 --> 00:26:26.599
<v Speaker 7>so what might we be able to do to kind of,

501
00:26:27.440 --> 00:26:29.319
<v Speaker 7>you know, break down some of those roadblocks.

502
00:26:31.000 --> 00:26:35.079
<v Speaker 4>Yeah, I think the idea of preferred sponsor, preferred site,

503
00:26:35.319 --> 00:26:37.319
<v Speaker 4>I mean, it's it's a great idea and at the

504
00:26:37.359 --> 00:26:41.480
<v Speaker 4>end of the day, to me, it just means templatizing

505
00:26:42.240 --> 00:26:44.359
<v Speaker 4>a lot of the steps in the process right so

506
00:26:44.480 --> 00:26:46.559
<v Speaker 4>that you can manage, my exception, don't have to do

507
00:26:46.599 --> 00:26:49.400
<v Speaker 4>the same thing over and over again. And it can

508
00:26:49.440 --> 00:26:51.960
<v Speaker 4>take some time to get that set up at the

509
00:26:51.960 --> 00:26:54.160
<v Speaker 4>front end, to make sure that you've got to mutually

510
00:26:54.200 --> 00:26:57.559
<v Speaker 4>agreed upon template for name the document that you need

511
00:26:57.640 --> 00:27:00.000
<v Speaker 4>to get going right, whether that's the CTA or your

512
00:27:00.039 --> 00:27:02.880
<v Speaker 4>budget or your treatsfer agreements or whatever it might be.

513
00:27:03.319 --> 00:27:06.000
<v Speaker 4>But once you've got that setup and you've got that

514
00:27:06.079 --> 00:27:09.079
<v Speaker 4>kind of common understanding checked off of like we know

515
00:27:09.160 --> 00:27:11.240
<v Speaker 4>how you work, you know how we work, we've got

516
00:27:11.279 --> 00:27:14.359
<v Speaker 4>the points of contact, it really can make things.

517
00:27:14.640 --> 00:27:16.519
<v Speaker 3>It just avoids so many headaches.

518
00:27:17.880 --> 00:27:21.279
<v Speaker 8>I think the idea of like the templatizing things to

519
00:27:21.519 --> 00:27:24.000
<v Speaker 8>steal your word, I think makes a ton of sense.

520
00:27:24.039 --> 00:27:27.839
<v Speaker 8>But I think there's also an opportunity to even standardize

521
00:27:27.839 --> 00:27:31.640
<v Speaker 8>and templatize across sponsors, right because you know you mentioned

522
00:27:31.680 --> 00:27:34.119
<v Speaker 8>before its sites are working with so many different sponsors.

523
00:27:34.119 --> 00:27:36.359
<v Speaker 8>Like it's great to have you know, some some priority

524
00:27:36.359 --> 00:27:38.519
<v Speaker 8>sponsors that you know you work with and work with well,

525
00:27:38.920 --> 00:27:41.160
<v Speaker 8>but that only goes so far if you're going to

526
00:27:41.240 --> 00:27:44.119
<v Speaker 8>reinvent the wheel over and over again for other sponsors

527
00:27:44.119 --> 00:27:46.920
<v Speaker 8>for the same things, for study feasibility, for all of

528
00:27:46.960 --> 00:27:50.039
<v Speaker 8>these other downstream pieces. And so I think there's still

529
00:27:50.039 --> 00:27:54.079
<v Speaker 8>an opportunity to kind of close the gap between the

530
00:27:54.119 --> 00:27:58.519
<v Speaker 8>different sponsors so that you're decreasing the amount of variability

531
00:27:58.680 --> 00:28:02.279
<v Speaker 8>and customization that exist it's across each of those different sponsors.

532
00:28:02.319 --> 00:28:04.839
<v Speaker 8>I think one of the issues from a site perspective

533
00:28:05.680 --> 00:28:09.599
<v Speaker 8>is that it's really really hard to be proactive and

534
00:28:09.720 --> 00:28:11.319
<v Speaker 8>kind of find you know. I know this is a

535
00:28:11.359 --> 00:28:13.759
<v Speaker 8>solutions based off, but it's hard to do that a

536
00:28:13.759 --> 00:28:16.920
<v Speaker 8>lot of time when you're constantly being reactive to all

537
00:28:16.960 --> 00:28:19.119
<v Speaker 8>of these different things that are being thrown at you

538
00:28:19.160 --> 00:28:21.599
<v Speaker 8>all the time. So I think the more you can

539
00:28:21.759 --> 00:28:24.720
<v Speaker 8>kind of take away those pieces up front, the more

540
00:28:24.720 --> 00:28:28.240
<v Speaker 8>we can focus on, you know, getting a standard process

541
00:28:28.240 --> 00:28:30.480
<v Speaker 8>in place so we can find solutions for all these

542
00:28:30.519 --> 00:28:31.559
<v Speaker 8>other other issues.

543
00:28:32.519 --> 00:28:34.960
<v Speaker 1>So I can't play guitar for those who are in

544
00:28:35.000 --> 00:28:37.920
<v Speaker 1>the keynote, I can't play guitar or do anything like that.

545
00:28:37.960 --> 00:28:41.200
<v Speaker 1>But what if, right, what if as sponsors we came

546
00:28:41.279 --> 00:28:44.359
<v Speaker 1>together and agreed upon a set of standards and templates

547
00:28:44.359 --> 00:28:46.920
<v Speaker 1>for some of these very common things. I think if

548
00:28:46.960 --> 00:28:49.480
<v Speaker 1>we could do that as sponsors, I'm sure there's innovative

549
00:28:49.640 --> 00:28:52.079
<v Speaker 1>solutions providers out there that would figure out a way

550
00:28:52.119 --> 00:28:54.559
<v Speaker 1>to surface that in a really clever way.

551
00:28:54.920 --> 00:28:57.200
<v Speaker 2>So excellent, excellent.

552
00:28:58.400 --> 00:29:01.000
<v Speaker 1>I want to we haven't talked about DCTs, and I

553
00:29:01.000 --> 00:29:02.960
<v Speaker 1>feel like you should just talk about DCTs at every

554
00:29:02.960 --> 00:29:06.359
<v Speaker 1>one of these conferences. So I wanted to ask, as

555
00:29:06.359 --> 00:29:08.920
<v Speaker 1>we have sponsors and sites here, because as a guy

556
00:29:08.920 --> 00:29:12.680
<v Speaker 1>who heads clinical outsourcing for a sponsor. I'm constantly in

557
00:29:12.720 --> 00:29:15.319
<v Speaker 1>the tug of war of do you do it, which

558
00:29:15.359 --> 00:29:17.599
<v Speaker 1>provider do you work with? How do you apply it?

559
00:29:17.640 --> 00:29:19.759
<v Speaker 1>And I'm interested as we have a site, so we

560
00:29:19.759 --> 00:29:24.200
<v Speaker 1>have sites perspective, site networks perspective, and sponsor perspective. Is

561
00:29:24.240 --> 00:29:27.279
<v Speaker 1>that something that when we look at those enabling capabilities,

562
00:29:27.319 --> 00:29:29.200
<v Speaker 1>how do we do that in a way that's patient

563
00:29:29.319 --> 00:29:32.200
<v Speaker 1>centric that kind of satisfies all the things we talk about.

564
00:29:32.200 --> 00:29:34.799
<v Speaker 1>We're trying to reduce burden, increase access and diversity to

565
00:29:34.839 --> 00:29:37.480
<v Speaker 1>a trial, but not due harm to some of our

566
00:29:37.519 --> 00:29:41.440
<v Speaker 1>stakeholders at sites, or increase burden or increase the burden

567
00:29:41.480 --> 00:29:43.559
<v Speaker 1>of technology and some of the challenges we've spoken about

568
00:29:43.640 --> 00:29:47.160
<v Speaker 1>during this panel. I'm just curious, Tracy, perhaps you'd like

569
00:29:47.200 --> 00:29:48.839
<v Speaker 1>to jump in on that one.

570
00:29:49.480 --> 00:29:56.759
<v Speaker 5>So we've obviously had several different variations of decentralized approaches

571
00:29:56.839 --> 00:30:00.640
<v Speaker 5>embedded into our carials, and I think so it goes

572
00:30:00.680 --> 00:30:04.799
<v Speaker 5>back to what I said initially, we have to we

573
00:30:04.920 --> 00:30:08.559
<v Speaker 5>have to actually understand what the impact is on the trail.

574
00:30:08.559 --> 00:30:10.440
<v Speaker 5>We don't just do it for the sake of doing it.

575
00:30:10.920 --> 00:30:15.559
<v Speaker 5>In some cases there are contractual limitations or oversighte limitations

576
00:30:15.599 --> 00:30:21.039
<v Speaker 5>that a site may not want to use the mobile

577
00:30:21.119 --> 00:30:24.839
<v Speaker 5>nurses that we've contracted. You know, it may not make

578
00:30:24.920 --> 00:30:30.680
<v Speaker 5>sense and therefore you're limited in the uptake of the

579
00:30:30.720 --> 00:30:33.720
<v Speaker 5>remote visits in a particular trial. I think we have

580
00:30:33.799 --> 00:30:36.920
<v Speaker 5>to look at it very much again, case by case.

581
00:30:37.680 --> 00:30:40.880
<v Speaker 5>Now the approach for us would be certainly, don't make

582
00:30:40.920 --> 00:30:44.720
<v Speaker 5>the assumption that don't make the assumption either way the

583
00:30:44.759 --> 00:30:47.000
<v Speaker 5>site that the sites don't want to do it or

584
00:30:47.359 --> 00:30:49.920
<v Speaker 5>do want to do it can do it. Are unable

585
00:30:49.960 --> 00:30:55.000
<v Speaker 5>to actually talk about what is possible see the extent

586
00:30:55.079 --> 00:30:58.920
<v Speaker 5>to which the technology that we use to support it

587
00:30:58.960 --> 00:31:02.119
<v Speaker 5>can be embedded with in the technology that's already used

588
00:31:02.160 --> 00:31:04.200
<v Speaker 5>on site. The scheduling is an obvious one for me,

589
00:31:05.079 --> 00:31:08.200
<v Speaker 5>because if you're scheduling within an app at the same

590
00:31:08.240 --> 00:31:12.119
<v Speaker 5>time as scheduling within your regular scheduling system, it's pain.

591
00:31:13.839 --> 00:31:17.440
<v Speaker 5>But also look at is ultimately, if the goal of

592
00:31:17.519 --> 00:31:22.920
<v Speaker 5>a decentralized approach is to reach a different patient population,

593
00:31:23.920 --> 00:31:26.039
<v Speaker 5>is that even the way that we should be doing it.

594
00:31:26.480 --> 00:31:29.119
<v Speaker 5>And yes, in some cases it may extend the reach

595
00:31:29.160 --> 00:31:31.279
<v Speaker 5>of the existing sites and it may be something that

596
00:31:31.279 --> 00:31:34.880
<v Speaker 5>they want to do. But in other cases, let's accept

597
00:31:35.200 --> 00:31:38.599
<v Speaker 5>the population that we've got and then look for other

598
00:31:38.680 --> 00:31:43.839
<v Speaker 5>ways to embed DCT approaches to reach that missing part

599
00:31:43.920 --> 00:31:46.960
<v Speaker 5>of the patient population. So I think it's be very

600
00:31:47.000 --> 00:31:51.359
<v Speaker 5>flexible and actually understand what the limitations are and you know,

601
00:31:51.599 --> 00:31:52.000
<v Speaker 5>what are.

602
00:31:51.920 --> 00:31:54.880
<v Speaker 2>The goals of the site, and have that dialogue. I

603
00:31:54.960 --> 00:31:57.839
<v Speaker 2>think I'm interested in that dialogue.

604
00:31:57.839 --> 00:31:59.480
<v Speaker 1>And I think Lisa goes back to what you said

605
00:31:59.480 --> 00:32:02.240
<v Speaker 1>about early engagement, about hey, we're thinking about this approach.

606
00:32:02.279 --> 00:32:05.440
<v Speaker 1>Does that idea of asking and kind of inquiring what

607
00:32:05.559 --> 00:32:08.119
<v Speaker 1>is the existing infrastructure, you know, and how can we

608
00:32:08.240 --> 00:32:10.799
<v Speaker 1>leverage it versus impose a new solution?

609
00:32:10.960 --> 00:32:11.799
<v Speaker 3>Thens That's right.

610
00:32:11.880 --> 00:32:15.440
<v Speaker 4>So I think we're in a situation where the technology

611
00:32:15.920 --> 00:32:21.680
<v Speaker 4>outpaces the readiness of the site to fully apply that

612
00:32:21.759 --> 00:32:23.960
<v Speaker 4>technology and not just apply it, but integrate it. And

613
00:32:24.000 --> 00:32:26.079
<v Speaker 4>so I think the question it's not like how good

614
00:32:26.160 --> 00:32:28.400
<v Speaker 4>is the tech? The text very very good, the idea

615
00:32:28.480 --> 00:32:31.160
<v Speaker 4>behind the tech is very good. The sites would love

616
00:32:31.279 --> 00:32:34.720
<v Speaker 4>to see this work, and all they can see.

617
00:32:34.759 --> 00:32:37.400
<v Speaker 3>Are the red cards. Right, are all the reasons right?

618
00:32:37.480 --> 00:32:41.359
<v Speaker 4>You're immediately going to get like fifteen reasons why this

619
00:32:41.400 --> 00:32:44.039
<v Speaker 4>is going to be really really hard. And I think

620
00:32:44.160 --> 00:32:47.839
<v Speaker 4>that's the interesting conversation is to say, what is it

621
00:32:47.880 --> 00:32:50.319
<v Speaker 4>going to take to make this clinic ready and what

622
00:32:50.480 --> 00:32:52.079
<v Speaker 4>people would you need to add to.

623
00:32:52.039 --> 00:32:52.680
<v Speaker 3>Your team rate.

624
00:32:52.759 --> 00:32:55.400
<v Speaker 4>So it's like, here's this great tex site, figure it out,

625
00:32:55.880 --> 00:32:58.480
<v Speaker 4>and then the sites are trying to figure it out

626
00:32:58.599 --> 00:33:01.400
<v Speaker 4>in their spare time on top of the job that

627
00:33:01.400 --> 00:33:06.079
<v Speaker 4>they're already doing. So I think having like a real

628
00:33:06.200 --> 00:33:10.480
<v Speaker 4>assessment of these are the five to six things that

629
00:33:10.519 --> 00:33:13.160
<v Speaker 4>would need to be present at your site, whether that

630
00:33:13.319 --> 00:33:16.319
<v Speaker 4>is people, whether that is an org structure setup, whether

631
00:33:16.400 --> 00:33:18.640
<v Speaker 4>that's a plug in to somebody who's going to help

632
00:33:18.680 --> 00:33:20.279
<v Speaker 4>people troubleshoot.

633
00:33:19.680 --> 00:33:20.319
<v Speaker 3>Whatever it is.

634
00:33:21.079 --> 00:33:23.519
<v Speaker 4>To what degree are these five to six things that

635
00:33:23.559 --> 00:33:26.279
<v Speaker 4>we think must be present at your site for this

636
00:33:26.359 --> 00:33:26.839
<v Speaker 4>to work?

637
00:33:26.920 --> 00:33:28.279
<v Speaker 3>To what degree can you do that?

638
00:33:28.319 --> 00:33:31.359
<v Speaker 4>And what is a true readiness assessment and how far

639
00:33:31.400 --> 00:33:32.599
<v Speaker 4>away are you from readiness?

640
00:33:32.640 --> 00:33:34.240
<v Speaker 3>And what can we help you do to make.

641
00:33:34.119 --> 00:33:37.799
<v Speaker 4>Ready for this Because there's some scaffolding that you've got

642
00:33:37.799 --> 00:33:39.880
<v Speaker 4>to build if you're really going to deploy it and

643
00:33:39.920 --> 00:33:40.559
<v Speaker 4>have it work.

644
00:33:41.160 --> 00:33:42.279
<v Speaker 3>And right now, the.

645
00:33:42.240 --> 00:33:45.240
<v Speaker 4>Feeling, at least at the sites is like, here you go,

646
00:33:45.319 --> 00:33:49.200
<v Speaker 4>we built it, tell us how goes you know exactly?

647
00:33:51.480 --> 00:33:54.559
<v Speaker 8>I think there's also potentially, as I'm kind of hearing

648
00:33:54.559 --> 00:33:57.440
<v Speaker 8>you guys, talk through this. There is also kind of

649
00:33:57.519 --> 00:34:01.079
<v Speaker 8>a potential opportunity analogous to you know, right now, there's

650
00:34:01.079 --> 00:34:04.279
<v Speaker 8>a lot of focus on like for patient treatment, show

651
00:34:04.359 --> 00:34:07.480
<v Speaker 8>me other patients like me that have been treated just

652
00:34:07.799 --> 00:34:11.159
<v Speaker 8>like with a certain you know, treatment and responded well

653
00:34:11.280 --> 00:34:14.119
<v Speaker 8>due to like having a specific criteria, right, is there

654
00:34:14.119 --> 00:34:16.559
<v Speaker 8>an opportunit tunity for the same thing you're talking about

655
00:34:16.599 --> 00:34:20.519
<v Speaker 8>meeting kind of both an organizational and kind of technology

656
00:34:20.760 --> 00:34:24.119
<v Speaker 8>stack already at the ready to use some of these

657
00:34:24.159 --> 00:34:27.199
<v Speaker 8>different approaches. So is there an ability to kind of,

658
00:34:28.159 --> 00:34:30.719
<v Speaker 8>you know, for lack of a better term, been institutions

659
00:34:30.760 --> 00:34:34.679
<v Speaker 8>together to say, okay, these are similar functioning institutions with

660
00:34:35.079 --> 00:34:38.760
<v Speaker 8>you know, similar technologies and organization structures. It's worked very

661
00:34:38.760 --> 00:34:41.880
<v Speaker 8>well for organization X. You guys are very similar, so

662
00:34:41.920 --> 00:34:44.079
<v Speaker 8>we think that it's also going to work well for you.

663
00:34:44.440 --> 00:34:47.519
<v Speaker 8>So that again you're not siloing these discussions for each

664
00:34:47.639 --> 00:34:53.199
<v Speaker 8>individual site and you're kind of learning as you're going.

665
00:34:53.440 --> 00:34:55.719
<v Speaker 5>In some ways, I actually think that's probably the only

666
00:34:55.840 --> 00:34:58.920
<v Speaker 5>pragmatic way. You know, I like to see you can

667
00:34:58.920 --> 00:35:02.079
<v Speaker 5>figure it out site by site, but you can't. It's

668
00:35:02.440 --> 00:35:08.119
<v Speaker 5>not pragmatic. But rather than just saying okay, here's an approach,

669
00:35:08.280 --> 00:35:10.360
<v Speaker 5>see what you can do with it if you can

670
00:35:10.440 --> 00:35:13.559
<v Speaker 5>at least start to figure out how it might look

671
00:35:14.119 --> 00:35:17.239
<v Speaker 5>in a couple of the setups that you're working with,

672
00:35:17.920 --> 00:35:20.760
<v Speaker 5>and then offer that as a It's almost like an

673
00:35:20.760 --> 00:35:24.360
<v Speaker 5>add on to here's the protocol that tells you what

674
00:35:24.400 --> 00:35:29.320
<v Speaker 5>you can do remotely on what you can't. At least

675
00:35:29.360 --> 00:35:33.039
<v Speaker 5>if you've had that dialogue and you've got some co

676
00:35:33.199 --> 00:35:38.159
<v Speaker 5>created approaches that might work, then I think that's a

677
00:35:38.199 --> 00:35:41.400
<v Speaker 5>step ahead of where we are today.

678
00:35:41.559 --> 00:35:44.519
<v Speaker 3>Yeah, I think the rapid cycle feedback loop. You know

679
00:35:44.719 --> 00:35:45.719
<v Speaker 3>that we had a.

680
00:35:45.679 --> 00:35:48.400
<v Speaker 4>Great experience and at start this was at another organization

681
00:35:48.440 --> 00:35:52.159
<v Speaker 4>with a vendor that was doing how managoring, you know,

682
00:35:52.320 --> 00:35:54.519
<v Speaker 4>using all kinds of slick stuff and all of these

683
00:35:54.559 --> 00:35:59.440
<v Speaker 4>like plug ins and a tablet, and they provided full

684
00:35:59.559 --> 00:36:03.880
<v Speaker 4>infrast structure to troubleshooting, you know, is this working or not?

685
00:36:04.000 --> 00:36:06.519
<v Speaker 4>And we had the mutual goal of let's fail fast.

686
00:36:06.559 --> 00:36:08.719
<v Speaker 4>If it's not going to work, let's try something different.

687
00:36:09.039 --> 00:36:11.519
<v Speaker 4>And we had the right level of project support to

688
00:36:11.639 --> 00:36:15.039
<v Speaker 4>really be successful at implementing it, which we ultimately were,

689
00:36:15.840 --> 00:36:20.000
<v Speaker 4>despite the skepticism of most of the clinicians involved, because

690
00:36:20.039 --> 00:36:23.760
<v Speaker 4>they put the people they really partnered in terms of

691
00:36:23.920 --> 00:36:26.000
<v Speaker 4>people and support with us to do it.

692
00:36:27.079 --> 00:36:29.440
<v Speaker 5>That actually just makes me think of we did have

693
00:36:29.480 --> 00:36:31.920
<v Speaker 5>an example of where we were looking at a particular

694
00:36:32.000 --> 00:36:34.800
<v Speaker 5>monitoring and the question was, you know, if the alarm

695
00:36:34.880 --> 00:36:39.239
<v Speaker 5>goes not quite physically, who's answering it? Yes, And they said, well,

696
00:36:39.280 --> 00:36:41.920
<v Speaker 5>we don't actually know what we have to do. And

697
00:36:41.960 --> 00:36:44.159
<v Speaker 5>I said, okay, you need to talk to the sites

698
00:36:44.199 --> 00:36:47.239
<v Speaker 5>about that because and they did. And actually it was

699
00:36:47.280 --> 00:36:50.239
<v Speaker 5>a very positive outcome because as long as they knew,

700
00:36:51.000 --> 00:36:54.400
<v Speaker 5>you know, they were quite they were excited about the science,

701
00:36:55.639 --> 00:36:58.360
<v Speaker 5>excited about where it would go, and as long as

702
00:36:58.360 --> 00:37:01.880
<v Speaker 5>they understood that there wasn't expectation that they had to

703
00:37:01.920 --> 00:37:02.719
<v Speaker 5>handle this.

704
00:37:03.239 --> 00:37:05.360
<v Speaker 3>You know, they knew how to respond to the patients, etc.

705
00:37:06.559 --> 00:37:09.840
<v Speaker 5>But it's exactly that it's making sure that that conversation

706
00:37:09.960 --> 00:37:10.880
<v Speaker 5>is happening.

707
00:37:11.880 --> 00:37:14.880
<v Speaker 1>So much around communication and around having that dialogue. I

708
00:37:14.920 --> 00:37:17.159
<v Speaker 1>think if there's one takeaway, I think that's you know,

709
00:37:17.199 --> 00:37:19.800
<v Speaker 1>that's what I'm getting from this panel discussion. We've had

710
00:37:19.840 --> 00:37:22.159
<v Speaker 1>a great discussion within the panel around the challenges and

711
00:37:22.159 --> 00:37:24.280
<v Speaker 1>some of the solutions. I did want to make the

712
00:37:24.280 --> 00:37:26.440
<v Speaker 1>audience aware if there's any questions anyone has, we do

713
00:37:26.480 --> 00:37:28.559
<v Speaker 1>have mic set up, so please, you know, feel free

714
00:37:28.559 --> 00:37:31.519
<v Speaker 1>to engage, wave your hand or you know, shout at me.

715
00:37:31.519 --> 00:37:32.800
<v Speaker 1>There's a bright light in my eyes.

716
00:37:32.840 --> 00:37:34.280
<v Speaker 2>But but but.

717
00:37:34.320 --> 00:37:36.800
<v Speaker 1>Do please, you know, engage with our panel, race questions,

718
00:37:36.920 --> 00:37:40.280
<v Speaker 1>race challenges. We won't autograph them. Well, we might autograph them,

719
00:37:40.320 --> 00:37:44.679
<v Speaker 1>but you'll get a card if you do. So if

720
00:37:44.719 --> 00:37:47.079
<v Speaker 1>any of those pop up, we'll grab them.

721
00:37:48.360 --> 00:37:49.320
<v Speaker 2>We already have a.

722
00:37:49.239 --> 00:37:53.880
<v Speaker 9>Brave volunteer, Marcy Kravit is it on and the can

723
00:37:53.920 --> 00:37:56.760
<v Speaker 9>you hear me all right, Rusty Kravit from Anado.

724
00:37:56.880 --> 00:37:58.639
<v Speaker 3>So it's an interesting topic.

725
00:37:58.760 --> 00:38:01.039
<v Speaker 9>And I'm going to SCRs next week as well too,

726
00:38:01.119 --> 00:38:04.480
<v Speaker 9>so interesting to hear the site's perspective. But in terms

727
00:38:04.519 --> 00:38:07.119
<v Speaker 9>of tracy, you said, you know to talk to every

728
00:38:07.199 --> 00:38:09.760
<v Speaker 9>site like you just can't do it right, So who

729
00:38:09.840 --> 00:38:15.119
<v Speaker 9>in the sponsor company is doing some of this intelligence gathering?

730
00:38:15.159 --> 00:38:16.519
<v Speaker 9>Like what are the challenges going to be?

731
00:38:16.559 --> 00:38:17.559
<v Speaker 3>Okay, now I know it.

732
00:38:17.480 --> 00:38:20.960
<v Speaker 9>So before the study starts, we're already building in sort

733
00:38:21.000 --> 00:38:25.599
<v Speaker 9>of mitigation strategies. So the cras right, they don't have

734
00:38:25.639 --> 00:38:29.480
<v Speaker 9>the capacity. I'm understanding sponsors now have like site engagement

735
00:38:29.519 --> 00:38:33.719
<v Speaker 9>type of teams, But how are the sponsors thinking about

736
00:38:34.199 --> 00:38:38.000
<v Speaker 9>this sponsor site engagement at scale to get that rapid

737
00:38:38.039 --> 00:38:40.280
<v Speaker 9>feedback about Okay, this is what we're going to have

738
00:38:40.320 --> 00:38:43.360
<v Speaker 9>to wrap around the technology to make it successful.

739
00:38:44.119 --> 00:38:47.719
<v Speaker 5>I'll just give you a quick review of what we've done.

740
00:38:48.519 --> 00:38:52.079
<v Speaker 5>So actually, when I say we can't get all of

741
00:38:52.079 --> 00:38:55.039
<v Speaker 5>that feedback, I don't think that's actually a fair statement.

742
00:38:56.079 --> 00:38:57.760
<v Speaker 5>We can probably gather it.

743
00:38:57.800 --> 00:38:59.360
<v Speaker 3>We do have site facing roles.

744
00:38:59.519 --> 00:39:02.679
<v Speaker 5>Those sites facing roles, so we've actually established a site

745
00:39:02.679 --> 00:39:08.760
<v Speaker 5>engagement academy specifically focusing on it's more on the soft

746
00:39:08.760 --> 00:39:12.280
<v Speaker 5>skills for site facing roles within the organization to really

747
00:39:13.239 --> 00:39:15.960
<v Speaker 5>get to know the sites they're working with to understand

748
00:39:16.039 --> 00:39:20.440
<v Speaker 5>their challenges. So the conversation you hope happens, it will

749
00:39:20.639 --> 00:39:23.000
<v Speaker 5>you know, we'll start to see the update, we'll see

750
00:39:23.000 --> 00:39:25.360
<v Speaker 5>what comes out of that. But then at the same

751
00:39:25.440 --> 00:39:30.679
<v Speaker 5>times we have to have we have implemented Global Insights

752
00:39:31.719 --> 00:39:36.400
<v Speaker 5>system solution, just a mechanism for sharing insights and so

753
00:39:36.519 --> 00:39:40.280
<v Speaker 5>obviously then you hope that the conversations that are happening

754
00:39:40.280 --> 00:39:42.199
<v Speaker 5>with the sites make it into their way into the

755
00:39:42.239 --> 00:39:44.440
<v Speaker 5>insights system. We have to think about how we communicate

756
00:39:44.480 --> 00:39:48.320
<v Speaker 5>it internally so that it gets back to the individuals

757
00:39:48.320 --> 00:39:51.599
<v Speaker 5>that can actually take action on it. And so it's

758
00:39:51.639 --> 00:39:57.159
<v Speaker 5>slowly building up that understanding skill set in terms of

759
00:39:57.280 --> 00:40:01.800
<v Speaker 5>the empathy building and the mechanisms by which they can

760
00:40:01.880 --> 00:40:06.039
<v Speaker 5>share and action the insights that they gather. And then

761
00:40:06.079 --> 00:40:11.320
<v Speaker 5>we want to obviously see those actions within any clinical,

762
00:40:11.559 --> 00:40:14.679
<v Speaker 5>any protocol and the in the way that we actually

763
00:40:14.679 --> 00:40:18.400
<v Speaker 5>approach implementing that at a site. But it's going to

764
00:40:18.440 --> 00:40:20.920
<v Speaker 5>be taking some time. But that's why I say you

765
00:40:20.960 --> 00:40:23.800
<v Speaker 5>have to start somewhere in terms of getting some learnings

766
00:40:23.840 --> 00:40:24.760
<v Speaker 5>and implementing them.

767
00:40:25.239 --> 00:40:26.800
<v Speaker 3>But a couple of things that we're.

768
00:40:26.679 --> 00:40:31.880
<v Speaker 6>Doing, Yeah, I definitely feel like, you know, sponsors have

769
00:40:31.920 --> 00:40:36.800
<v Speaker 6>gotten very good at getting patient advocacy boards in touch

770
00:40:37.079 --> 00:40:41.000
<v Speaker 6>with protocol development, and I think we should move along.

771
00:40:41.159 --> 00:40:43.199
<v Speaker 6>And I think an idea would be to have like

772
00:40:43.360 --> 00:40:47.760
<v Speaker 6>a group of sites who can give feedback as well,

773
00:40:48.280 --> 00:40:50.280
<v Speaker 6>you know, is this going to work, what way, what

774
00:40:50.480 --> 00:40:53.440
<v Speaker 6>parts of this protocol can be decentralized? Things like that,

775
00:40:54.280 --> 00:40:59.440
<v Speaker 6>And I think having site partnerships or site engagement can

776
00:40:59.519 --> 00:41:02.599
<v Speaker 6>relate also help bring the feedback from the site to

777
00:41:02.679 --> 00:41:06.159
<v Speaker 6>the sponsor so that they know, you know, what ways

778
00:41:06.159 --> 00:41:07.960
<v Speaker 6>we can really help these issues.

779
00:41:09.440 --> 00:41:12.360
<v Speaker 1>I can speak for Jazz and that we have dedicated resources.

780
00:41:12.360 --> 00:41:16.800
<v Speaker 1>We've created fairly recently a global Patient Site Engagement.

781
00:41:16.280 --> 00:41:19.360
<v Speaker 2>Group, although they are overwhelmed with the task. I think

782
00:41:19.360 --> 00:41:21.559
<v Speaker 2>for a lot of the reasons we've described.

783
00:41:21.559 --> 00:41:23.599
<v Speaker 1>I will say, if there was someone out there developing

784
00:41:23.599 --> 00:41:26.800
<v Speaker 1>a solution that could help with integrating those insights from

785
00:41:26.880 --> 00:41:29.559
<v Speaker 1>the site perspective, similar to what we do sometimes with

786
00:41:29.559 --> 00:41:31.280
<v Speaker 1>some of the solutions I saw the exhibit Hall four

787
00:41:31.400 --> 00:41:34.599
<v Speaker 1>with patient input of patient insights, that would be a

788
00:41:34.719 --> 00:41:35.920
<v Speaker 1>valued add to the market.

789
00:41:36.199 --> 00:41:37.239
<v Speaker 3>I'd also add, just.

790
00:41:38.840 --> 00:41:42.360
<v Speaker 7>For sites for cancer sites, in particular, the Association of

791
00:41:42.400 --> 00:41:46.400
<v Speaker 7>American Cancer Institute's the AACI, we have a list ser we

792
00:41:46.519 --> 00:41:50.079
<v Speaker 7>have a conference, the Clinical Research Innovation Conference, once annually,

793
00:41:51.039 --> 00:41:54.039
<v Speaker 7>and these types of issues surface there and so we

794
00:41:54.079 --> 00:41:59.440
<v Speaker 7>are discussing kind of commonality shared commonalities with troubleshooting, whether

795
00:41:59.480 --> 00:42:02.800
<v Speaker 7>it's a vender issue or a sponsor issue, or just

796
00:42:02.880 --> 00:42:05.800
<v Speaker 7>your site's issue. But we are having those conversations there,

797
00:42:05.840 --> 00:42:08.639
<v Speaker 7>and so if there's interest in kind of gathering a forum,

798
00:42:08.639 --> 00:42:10.199
<v Speaker 7>that may be an opportunity.

799
00:42:11.880 --> 00:42:13.880
<v Speaker 2>I see a gentleman by the microphone and the work.

800
00:42:15.440 --> 00:42:17.440
<v Speaker 2>Do you have any preferences or bust case scenarios?

801
00:42:17.440 --> 00:42:20.199
<v Speaker 3>A house sponsors can reimburse you besides paying a lot

802
00:42:20.239 --> 00:42:23.519
<v Speaker 3>and immediately, wait, what was the last part of that

803
00:42:23.599 --> 00:42:31.199
<v Speaker 3>is besides obviously paying fast and well, I'm not.

804
00:42:31.119 --> 00:42:34.320
<v Speaker 7>Sure if this is specifically reimbursement. I think it ties

805
00:42:34.360 --> 00:42:40.440
<v Speaker 7>to reimbursement, but amendments. For example, when we receive an amendment,

806
00:42:40.639 --> 00:42:44.199
<v Speaker 7>it can be weeks even months a year. I've seen

807
00:42:44.440 --> 00:42:47.559
<v Speaker 7>in cases where we don't have a budget for that amendment.

808
00:42:47.599 --> 00:42:51.679
<v Speaker 7>That adds a new cohort and all different visits, and

809
00:42:52.039 --> 00:42:53.719
<v Speaker 7>so there's a lot of risk that we face in

810
00:42:53.800 --> 00:42:57.280
<v Speaker 7>doing that. And so we have this challenge of deciding

811
00:42:57.320 --> 00:42:59.400
<v Speaker 7>do we take on the risk of maybe we don't

812
00:42:59.480 --> 00:43:01.599
<v Speaker 7>even know what the expenses are, but also a billing

813
00:43:01.599 --> 00:43:05.199
<v Speaker 7>compliance risk and not knowing what we should be billing

814
00:43:05.199 --> 00:43:08.639
<v Speaker 7>a patient versus what will be reimbursed. And so, you know,

815
00:43:09.039 --> 00:43:11.280
<v Speaker 7>my one solution there is that if you're going to

816
00:43:11.320 --> 00:43:14.199
<v Speaker 7>send an amendment, we very much want to open that cohort.

817
00:43:14.400 --> 00:43:16.880
<v Speaker 3>We really do. We want to.

818
00:43:16.840 --> 00:43:19.079
<v Speaker 7>Enroll patients, and in fact, we have patients primed in

819
00:43:19.159 --> 00:43:22.679
<v Speaker 7>many cases to enroll, but we do need to understand

820
00:43:22.840 --> 00:43:27.159
<v Speaker 7>how we're going to get paid, and that has been

821
00:43:27.199 --> 00:43:29.440
<v Speaker 7>a significant challenge for us.

822
00:43:30.800 --> 00:43:31.880
<v Speaker 3>I would also add.

823
00:43:32.800 --> 00:43:36.039
<v Speaker 7>You know, in some ways acknowledging what you're paying us

824
00:43:36.079 --> 00:43:37.159
<v Speaker 7>for it really helps a lot.

825
00:43:38.760 --> 00:43:44.159
<v Speaker 10>From Dennis, So, going back rewriting a bit, I'm the

826
00:43:44.199 --> 00:43:47.480
<v Speaker 10>executive director of the Site Council. We've over three thousand

827
00:43:47.639 --> 00:43:50.079
<v Speaker 10>side members, including Jefferson help. By the way, you may

828
00:43:50.119 --> 00:43:54.719
<v Speaker 10>not be aware and be happy to help find sites

829
00:43:54.960 --> 00:43:57.920
<v Speaker 10>personnel to support your engagement operations and.

830
00:43:57.920 --> 00:43:58.840
<v Speaker 2>We won't charge for it.

831
00:44:00.079 --> 00:44:03.519
<v Speaker 10>And if you don't work with I cruinly recommends you

832
00:44:03.519 --> 00:44:07.280
<v Speaker 10>don't need the ko well input anymore. You need the workhorse,

833
00:44:08.159 --> 00:44:10.480
<v Speaker 10>and you need especially need the coordinators. The coordinators know

834
00:44:10.480 --> 00:44:13.079
<v Speaker 10>what's going on totally. They'll tell you the truth, so

835
00:44:13.840 --> 00:44:17.599
<v Speaker 10>focus on them, and if anybody wants to pursue anything that.

836
00:44:17.840 --> 00:44:20.159
<v Speaker 5>I'm around, I was actually just going to make a

837
00:44:20.159 --> 00:44:22.880
<v Speaker 5>comment to that, because we're we're doing a very large

838
00:44:24.039 --> 00:44:27.760
<v Speaker 5>internal systems rollout which we know will impact our sites,

839
00:44:29.239 --> 00:44:32.199
<v Speaker 5>and so there is the document exchange element of it.

840
00:44:33.079 --> 00:44:36.280
<v Speaker 3>We love it and when that's good to know. Actually,

841
00:44:37.039 --> 00:44:38.280
<v Speaker 3>but when we.

842
00:44:38.199 --> 00:44:40.559
<v Speaker 5>Originally started to look at it from a patient and

843
00:44:41.119 --> 00:44:43.840
<v Speaker 5>site engagement perspective, which is the team that I am

844
00:44:44.039 --> 00:44:48.719
<v Speaker 5>responsible for, I said that we have to get the coordinators,

845
00:44:48.920 --> 00:44:51.880
<v Speaker 5>specifically the coordinators and we now have a panel of

846
00:44:52.039 --> 00:44:56.000
<v Speaker 5>coordinators that they basically, I mean, we can't do much

847
00:44:56.000 --> 00:44:59.000
<v Speaker 5>about the system, but it is good to get the

848
00:44:59.079 --> 00:45:02.960
<v Speaker 5>direct feedback the system to the from the site advisory

849
00:45:03.039 --> 00:45:07.199
<v Speaker 5>panel to the vendor. But what it does do is

850
00:45:07.239 --> 00:45:10.199
<v Speaker 5>it makes us more aware of what we should be

851
00:45:10.239 --> 00:45:12.840
<v Speaker 5>thinking about when we communicate and roll it out.

852
00:45:13.880 --> 00:45:15.440
<v Speaker 3>Yeah, I think it starts.

853
00:45:16.000 --> 00:45:18.880
<v Speaker 4>We have kind of set up our org chart to

854
00:45:18.920 --> 00:45:22.679
<v Speaker 4>be responsive to the way the sponsors org charts are designed, right,

855
00:45:22.719 --> 00:45:24.760
<v Speaker 4>and so you've got your site engagement people and we

856
00:45:24.840 --> 00:45:28.079
<v Speaker 4>have our sponsor engagement people, and these exact conversations are

857
00:45:28.079 --> 00:45:30.119
<v Speaker 4>the ones that are going there to have where we

858
00:45:30.239 --> 00:45:33.960
<v Speaker 4>had one sponsor who we were running their entire portfolio

859
00:45:34.000 --> 00:45:37.119
<v Speaker 4>of a specific mechanism of action and we simply could

860
00:45:37.199 --> 00:45:40.400
<v Speaker 4>not work with the lab interface that they had in place.

861
00:45:40.480 --> 00:45:42.920
<v Speaker 4>And so that's where the intent is that this is

862
00:45:42.920 --> 00:45:46.159
<v Speaker 4>a forum where those types of you know, just operational

863
00:45:46.239 --> 00:45:49.320
<v Speaker 4>roadblocks are surfacing so that we can be connected into

864
00:45:49.360 --> 00:45:52.280
<v Speaker 4>the right person on the sponsor side and say what

865
00:45:52.320 --> 00:45:55.880
<v Speaker 4>can we do about this? And again respecting that you've

866
00:45:55.880 --> 00:45:57.280
<v Speaker 4>got a lot of sites to work with, we have

867
00:45:57.320 --> 00:45:59.119
<v Speaker 4>a lot of sponsors to work with, and so at the.

868
00:45:59.159 --> 00:46:00.719
<v Speaker 3>End of the day, we have to be flexible.

869
00:46:00.760 --> 00:46:02.960
<v Speaker 4>Whatever we're designing on our side has to be able

870
00:46:02.960 --> 00:46:06.880
<v Speaker 4>to plug into one hundred different flavors of doing it.

871
00:46:07.320 --> 00:46:10.239
<v Speaker 4>But having the forum in place and having the right

872
00:46:10.280 --> 00:46:12.199
<v Speaker 4>people on each side of the table to say a right,

873
00:46:12.199 --> 00:46:15.000
<v Speaker 4>how are we going to tackle this one has been

874
00:46:15.159 --> 00:46:17.119
<v Speaker 4>a strategy that's worked well for us.

875
00:46:17.320 --> 00:46:18.679
<v Speaker 3>Yeah, I see that.

876
00:46:18.679 --> 00:46:20.920
<v Speaker 1>We have one more question, but we're also winding down

877
00:46:20.960 --> 00:46:23.079
<v Speaker 1>to the last two minutes of the shop clock, so

878
00:46:23.800 --> 00:46:25.920
<v Speaker 1>we'll take that question. We'll try to keep it brief,

879
00:46:25.960 --> 00:46:27.599
<v Speaker 1>and then if I could ask each of the panel

880
00:46:27.599 --> 00:46:30.960
<v Speaker 1>members following that question to think about one call to

881
00:46:31.000 --> 00:46:33.519
<v Speaker 1>action maybe to put out there so it's something we

882
00:46:33.599 --> 00:46:36.360
<v Speaker 1>can start doing or stop doing to solution some of

883
00:46:36.400 --> 00:46:37.079
<v Speaker 1>the challenges.

884
00:46:37.599 --> 00:46:38.719
<v Speaker 3>Very likely, Please thank you.

885
00:46:38.760 --> 00:46:41.639
<v Speaker 11>I'll be quick. So, first of all, great panel, very

886
00:46:41.679 --> 00:46:47.800
<v Speaker 11>interesting discussion. I'm Karina adit sanchio and feasibility something you mentioned, Kristin.

887
00:46:48.159 --> 00:46:52.280
<v Speaker 11>I actually started my career as a research coordinator, eventually

888
00:46:52.280 --> 00:46:55.320
<v Speaker 11>moved to the sponsor side because of lack of career

889
00:46:55.320 --> 00:46:58.559
<v Speaker 11>growth opportunities on the site. How could the sponsor help

890
00:46:58.719 --> 00:47:03.760
<v Speaker 11>sites essentially ensure attention with staff by supporting these career

891
00:47:03.880 --> 00:47:06.400
<v Speaker 11>growth opportunities that you're mentioning. Is there anything that the

892
00:47:06.440 --> 00:47:09.400
<v Speaker 11>sponsor can do the support?

893
00:47:10.280 --> 00:47:13.360
<v Speaker 8>I think ultimately a lot of that, unfortunately, is kind

894
00:47:13.360 --> 00:47:16.519
<v Speaker 8>of internally, right. I think if you don't have a

895
00:47:16.599 --> 00:47:20.239
<v Speaker 8>really good leader, obviously it's going to be kind of

896
00:47:20.639 --> 00:47:23.840
<v Speaker 8>hard for people to see their value right and you know,

897
00:47:23.880 --> 00:47:26.880
<v Speaker 8>see their value at the institution. But also you need

898
00:47:26.880 --> 00:47:29.159
<v Speaker 8>a leader that is going to work hard internally to

899
00:47:29.280 --> 00:47:33.280
<v Speaker 8>create those steps, which you know personally from an academic

900
00:47:33.280 --> 00:47:36.639
<v Speaker 8>institution perspective can be very difficult. So I think just

901
00:47:36.760 --> 00:47:40.000
<v Speaker 8>keeping that communication open. It could be different at different institutions,

902
00:47:40.039 --> 00:47:41.719
<v Speaker 8>but I think a lot of that has to be

903
00:47:41.800 --> 00:47:46.119
<v Speaker 8>kind of introspectively pushed at an institutional level.

904
00:47:46.760 --> 00:47:48.960
<v Speaker 7>I would also say, maybe we look, we've seen things

905
00:47:49.000 --> 00:47:52.440
<v Speaker 7>like clinical fellowships, and is there an opportunity for research

906
00:47:52.480 --> 00:47:56.480
<v Speaker 7>support staff type of fellowship with you know, working with

907
00:47:56.519 --> 00:48:01.159
<v Speaker 7>a sponsor to kind of gather some information expertise and

908
00:48:01.199 --> 00:48:05.480
<v Speaker 7>then coming back. I think that there's an opportunity for that. Likewise,

909
00:48:05.519 --> 00:48:07.519
<v Speaker 7>for people who are enrolled in say like our Masters

910
00:48:07.559 --> 00:48:12.039
<v Speaker 7>of Clinical Research programs at Jefferson and some fellowships there,

911
00:48:12.199 --> 00:48:14.360
<v Speaker 7>and so you know, some collaboration in that way.

912
00:48:16.039 --> 00:48:18.239
<v Speaker 1>I think we had a wonderful conversation. We're down to

913
00:48:18.280 --> 00:48:20.800
<v Speaker 1>our last few seconds. I want to thank our panel

914
00:48:20.880 --> 00:48:22.920
<v Speaker 1>and please thank you for sharing some solutions from the

915
00:48:22.960 --> 00:48:23.760
<v Speaker 1>audience as well.

916
00:48:24.079 --> 00:48:28.280
<v Speaker 3>Thank you everyone, and thank you, thank you, thank you, Dennis,

917
00:48:29.119 --> 00:48:29.400
<v Speaker 3>thank you.
