1
00:00:10,200 --> 00:00:15,000
Hi, everyone, and Welcome to our
episode. 84 where we will talk 

2
00:00:15,000 --> 00:00:18,800
about how Rush monitors 
real-time shipment and 

3
00:00:18,800 --> 00:00:20,700
Temperature Control in clinical 
Supply. 

4
00:00:21,500 --> 00:00:24,900
To answer this question, I'm 
honored to have a special guest 

5
00:00:24,900 --> 00:00:28,700
on the show today. 
Let's work on guia De Boracay, 

6
00:00:28,700 --> 00:00:33,400
to product manager for Clinical 
and API supply chain from Rush 

7
00:00:33,900 --> 00:00:35,500
agita. 
How you doing today? 

8
00:00:36,000 --> 00:00:39,800
Hello, Marcus good to see you. 
I'm well and excited to take 

9
00:00:39,800 --> 00:00:42,500
part in this podcast. 
Thanks for being here and let's 

10
00:00:42,500 --> 00:00:45,700
start right into the subject 
agita. 

11
00:00:45,900 --> 00:00:48,800
What does monitoring real-time 
shipments and Temperature 

12
00:00:48,800 --> 00:00:53,000
Control in clinical Supply mean,
how can our audience Envision 

13
00:00:53,000 --> 00:00:55,700
the processes and what are the 
legal requirements? 

14
00:00:56,900 --> 00:00:59,500
Let me answer this question in 
two parts. 

15
00:00:59,500 --> 00:01:01,100
The why? 
And the what? 

16
00:01:01,500 --> 00:01:05,600
So first monitoring temperature?
During transportation in the 

17
00:01:05,600 --> 00:01:09,100
clinical Supply is the same 
process as in a lot of other 

18
00:01:09,100 --> 00:01:13,200
Industries in a nutshell. 
We must ensure that our products

19
00:01:13,200 --> 00:01:18,700
are exposed to the temperatures 
inside of the allowed range. 

20
00:01:18,700 --> 00:01:23,200
That is ambient product should 
not be frozen or heated and cool

21
00:01:23,200 --> 00:01:26,500
chain products must maintain 
their low temperatures. 

22
00:01:27,400 --> 00:01:30,800
However, there are several 
additional aspects that we must 

23
00:01:30,800 --> 00:01:36,600
consider in the clinical Supply.
First is Pharma, industry is 

24
00:01:36,600 --> 00:01:40,600
highly regulated. 
So we must ensure that our 

25
00:01:40,600 --> 00:01:44,600
clinical products reach the 
patients in the intended, State 

26
00:01:44,600 --> 00:01:51,100
and safety Second clinical 
product have relatively short 

27
00:01:51,100 --> 00:01:55,200
shelf life. 
As these are new medications and

28
00:01:55,200 --> 00:01:59,400
they are not yet approved and 
often the stability studies are 

29
00:01:59,400 --> 00:02:05,000
still ongoing Third, any 
potential deviation in terms, of

30
00:02:05,000 --> 00:02:08,100
temperature is a reason to 
discard the product. 

31
00:02:08,699 --> 00:02:11,900
This, of course, minimizes the 
risk for the patients. 

32
00:02:12,000 --> 00:02:15,000
And at the same time, is costly 
for the company. 

33
00:02:16,300 --> 00:02:19,900
Lastly, clinical shipments are 
usually going directly to the 

34
00:02:19,900 --> 00:02:24,300
hospitals. 
So let's say, the difference is 

35
00:02:24,300 --> 00:02:29,100
that in a regular supply chain a
wholesaler or other professional

36
00:02:29,100 --> 00:02:33,700
storage facility, is usually 
equipped, To keep the required 

37
00:02:33,700 --> 00:02:37,600
conditions and to end public 
institutions, like hospitals, 

38
00:02:37,600 --> 00:02:41,300
might have a variation in 
handling the products and 

39
00:02:41,300 --> 00:02:45,600
knowing these conditions that 
they are exposed to their is 

40
00:02:45,600 --> 00:02:49,300
especially important. 
So now the second part, what do 

41
00:02:49,300 --> 00:02:53,000
we do about it before the 
implementation of the smart 

42
00:02:53,000 --> 00:02:56,800
sensors in Rush clinical Supply,
we relied on the traditional 

43
00:02:56,800 --> 00:03:00,600
temperature monitoring either 
time-based where the product 

44
00:03:00,600 --> 00:03:04,500
should arrive within the Find 
number of hours or we had USB 

45
00:03:04,500 --> 00:03:09,800
loggers with the local storage. 
Given the reasons I mentioned in

46
00:03:09,800 --> 00:03:13,700
the first part. 
It was not enough, the old 

47
00:03:13,700 --> 00:03:17,200
methods. 
And last year we went live with 

48
00:03:17,200 --> 00:03:22,400
implementation of smart sensors.
So how does the process look 

49
00:03:22,400 --> 00:03:26,700
like in the first step? 
In the warehouse deliveries 

50
00:03:26,700 --> 00:03:29,200
being picked? 
Backed and paired with a small 

51
00:03:29,200 --> 00:03:34,000
physical device, which we call a
smart logger, and this device is

52
00:03:34,000 --> 00:03:39,200
put into a shipping box as a 
Step, they're also printing 

53
00:03:39,200 --> 00:03:42,300
special pairing. 
She to about the information. 

54
00:03:42,300 --> 00:03:44,700
What logger is inside of that 
box? 

55
00:03:44,700 --> 00:03:47,800
And also a QR code that I will 
come back to later. 

56
00:03:49,200 --> 00:03:52,900
Then our year p is triggering 
the interface to the cloud 

57
00:03:52,900 --> 00:03:58,900
application, where we send the 
very high delivery data source, 

58
00:03:58,900 --> 00:04:03,300
destination addresses, then we 
ship this box. 

59
00:04:03,800 --> 00:04:06,300
And then, as the last step, the 
delivery arrives at the 

60
00:04:06,300 --> 00:04:10,000
hospital, the medical Cool 
workers taking the pairing sheet

61
00:04:10,000 --> 00:04:15,100
scans, the QR barcode. 
And this link is then providing 

62
00:04:15,100 --> 00:04:20,600
the temperature report and the 
person in the hospital can 

63
00:04:20,600 --> 00:04:25,100
download it and file it, which 
is a regulatory requirement. 

64
00:04:25,400 --> 00:04:29,300
So, to wrap up the first 
question with this processor 

65
00:04:29,300 --> 00:04:31,500
ocean. 
Clinical investigation sites 

66
00:04:31,500 --> 00:04:34,600
have the temperature information
for the whole duration of the 

67
00:04:34,600 --> 00:04:37,400
shipment as compared to the 
previous methods. 

68
00:04:38,300 --> 00:04:40,900
And this ensures that our 
shipments are handled in 

69
00:04:40,900 --> 00:04:44,800
required conditions not only 
during Transportation but also 

70
00:04:44,800 --> 00:04:49,200
at the receiver side which 
consequently is also safe 

71
00:04:49,200 --> 00:04:52,900
medications to the patients. 
Maybe we go more into the 

72
00:04:52,900 --> 00:04:57,100
implementation and if I would be
another sap customer operating 

73
00:04:57,100 --> 00:05:00,700
in clinical Supply, and I would 
call you up and ask you. 

74
00:05:00,700 --> 00:05:03,400
So, tell me a little bit more 
about the software and Hardware,

75
00:05:03,400 --> 00:05:05,400
I would need to implement Your 
solution. 

76
00:05:05,400 --> 00:05:09,400
What would you tell me? 
So the basic kit for real-time 

77
00:05:09,400 --> 00:05:13,800
temperature monitoring during 
shipping consists of two parts. 

78
00:05:13,900 --> 00:05:16,800
First, you need the smart device
that collects the temperature 

79
00:05:16,800 --> 00:05:20,100
then data and sends the real 
time to the cloud application. 

80
00:05:20,600 --> 00:05:23,900
And second you need the 
cloud-based software to collect 

81
00:05:23,900 --> 00:05:27,000
this data with the front-end to 
report. 

82
00:05:28,000 --> 00:05:32,000
However, the real benefit comes 
if you integrate this process 

83
00:05:32,000 --> 00:05:36,200
into your supply chain and 
especially the quality decision 

84
00:05:36,200 --> 00:05:40,500
making software. 
For that, you would need three 

85
00:05:40,500 --> 00:05:44,100
additional elements. 
First Integrations between the 

86
00:05:44,100 --> 00:05:47,000
companies Erp and Cloud vendor 
systems. 

87
00:05:48,100 --> 00:05:53,200
Second logger report repository 
that is a database to store the 

88
00:05:53,200 --> 00:05:55,800
temperature reports about each 
shipment. 

89
00:05:56,400 --> 00:06:00,700
In our case, it can be accessed 
by Rush as well as by the 

90
00:06:00,700 --> 00:06:06,000
hospital's via QR code. 
And the last useful tool is a 

91
00:06:06,000 --> 00:06:09,400
power bi for reporting and data 
visualization. 

92
00:06:09,500 --> 00:06:12,200
You mentioned that you're using 
a cloud-based supply chain, 

93
00:06:12,200 --> 00:06:17,400
monitoring tool, or solution. 
Even a cold chain as a service 

94
00:06:17,400 --> 00:06:20,500
solution, Section of my hair 
that cloud is not suitable and 

95
00:06:20,500 --> 00:06:23,900
regulated environments where 
their concerns before the 

96
00:06:23,900 --> 00:06:26,400
project started. 
Maybe you can elaborate a little

97
00:06:26,400 --> 00:06:30,500
bit on that, you're absolutely 
right Marcus data. 

98
00:06:30,500 --> 00:06:35,500
Safety was a key Topic in our 
project so generally data is 

99
00:06:35,500 --> 00:06:39,300
especially sensitive and 
clinical studies, as some 

100
00:06:39,300 --> 00:06:44,300
Studies have blinded setup that 
is some drugs are pills with 

101
00:06:44,400 --> 00:06:46,900
active pharmaceutical 
ingredients and some are 

102
00:06:46,900 --> 00:06:50,300
placebos. 
It is called double blinded 

103
00:06:50,300 --> 00:06:54,500
because neither patient nor 
Hospital must know which is 

104
00:06:54,500 --> 00:07:01,100
which therefore any unblinded 
information related to materials

105
00:07:01,100 --> 00:07:03,800
batches. 
It's absolutely to be avoided to

106
00:07:03,800 --> 00:07:08,200
be leaked or sent to other 
systems especially Cloud 

107
00:07:08,200 --> 00:07:12,500
systems. 
In our case we built, we got 

108
00:07:12,500 --> 00:07:19,000
created for architecture and we 
used it to allow to send only 

109
00:07:19,000 --> 00:07:22,800
the basic data to the cloud 
about the delivery header. 

110
00:07:22,800 --> 00:07:26,400
So to say so that we have the 
relationship between the liver 

111
00:07:26,400 --> 00:07:30,700
and logger, but do not send the 
sensitive information on 

112
00:07:30,700 --> 00:07:34,400
materials and batches. 
In case of temperature 

113
00:07:34,400 --> 00:07:39,600
deviation, our middleware is 
receiving the data from the 

114
00:07:39,700 --> 00:07:44,900
cloud and then is proactively 
pulling the required detailed 

115
00:07:44,900 --> 00:07:51,200
information from the Erp. 
And then it collects this data 

116
00:07:51,200 --> 00:07:56,000
into one bag and this forwarding
to our quality decision-making 

117
00:07:56,000 --> 00:07:59,700
system. 
In this way, we're keeping the 

118
00:07:59,800 --> 00:08:03,100
confidential information within 
the rush Network. 

119
00:08:05,200 --> 00:08:09,600
Very good Ghidorah if you look 
back on the whole project but 

120
00:08:09,600 --> 00:08:11,500
we're the biggest Lessons 
Learned. 

121
00:08:11,600 --> 00:08:14,900
And what would you pay attention
to a while implementing today, 

122
00:08:14,900 --> 00:08:17,400
or if you would have to do it 
again I would like maybe to 

123
00:08:17,400 --> 00:08:22,700
mention three takeaways First is
the close collaboration with 

124
00:08:22,700 --> 00:08:29,100
your Cloud device supplier. 
Now a project, the devices got a

125
00:08:29,108 --> 00:08:34,700
new software upgrade while when 
the system was already live and 

126
00:08:34,700 --> 00:08:38,400
it took agile problem solving, 
and real-time communication 

127
00:08:38,400 --> 00:08:43,200
between Russia and device 
supplier to make it seamless for

128
00:08:43,200 --> 00:08:47,800
the supply chain. 
The second point is be creative 

129
00:08:47,800 --> 00:08:51,700
in your architecture. 
As I And before for data, 

130
00:08:51,700 --> 00:08:55,900
security reasons, we needed to 
find a solution to send only the

131
00:08:55,900 --> 00:08:59,500
generic data to the cloud, 
keeping the sensitive data 

132
00:08:59,500 --> 00:09:03,800
inside and we used the 
middleware for that. 

133
00:09:04,400 --> 00:09:08,200
The last point, it's important 
to have a team in place, that 

134
00:09:08,200 --> 00:09:11,900
customers can contact. 
The in case of any issues with 

135
00:09:11,900 --> 00:09:16,600
Device or report, it is 
especially important in the 

136
00:09:16,608 --> 00:09:19,900
beginning when the sides are 
learning. 

137
00:09:20,000 --> 00:09:25,100
How to use the loggers and need 
to fast and easily accessible 

138
00:09:25,100 --> 00:09:27,900
support. 
I would say not only reduces the

139
00:09:27,900 --> 00:09:32,600
errors but also has this effect 
of building trust with the 

140
00:09:32,600 --> 00:09:35,000
customers. 
I know you're very creative 

141
00:09:35,000 --> 00:09:38,700
person and cool to see that your
arms are creative at rush and 

142
00:09:38,800 --> 00:09:41,900
was a really surprised like a 
personal surprise for you as 

143
00:09:41,900 --> 00:09:43,700
well. 
Yeah. 

144
00:09:43,800 --> 00:09:48,100
What surprised me personally is 
that the Power of Habit should 

145
00:09:48,100 --> 00:09:52,100
not be underestimated. 
The process with the smart log 

146
00:09:52,100 --> 00:09:56,500
as was greatly simplified in 
comparison with the old process.

147
00:09:56,500 --> 00:10:00,400
So the receiving side has only 
to scan the QR code and gets 

148
00:10:00,400 --> 00:10:03,300
directly forwarded to 
temperature report that easy. 

149
00:10:03,700 --> 00:10:07,600
However, I was surprised that 
some customers have explicitly 

150
00:10:07,600 --> 00:10:13,200
preferred, the old and more 
time-consuming process where you

151
00:10:13,200 --> 00:10:17,700
would attach the device to the 
USB, download print and so on 

152
00:10:18,800 --> 00:10:23,100
Old Habits for never Estimated 
right, Deidre and private life. 

153
00:10:23,100 --> 00:10:25,600
And in business, I completely 
agree. 

154
00:10:26,500 --> 00:10:29,900
Can you or I allowed to talk 
about the return of investment 

155
00:10:29,900 --> 00:10:33,400
after implementing Your solution
or operational improvements? 

156
00:10:33,700 --> 00:10:37,700
I would say that the biggest 
improvements were in increased 

157
00:10:37,700 --> 00:10:41,800
supply chain transparency and 
quality assurance. 

158
00:10:42,500 --> 00:10:48,400
So for the absolute majority of 
shipments, luckily, we have no 

159
00:10:48,400 --> 00:10:52,700
temperature excursions. 
And with the data available now,

160
00:10:52,700 --> 00:10:56,600
from the smart sensors, we could
automate the quality release of 

161
00:10:56,600 --> 00:11:02,000
these transports, which highly 
reduced effort for the quality 

162
00:11:02,000 --> 00:11:06,500
department and for the 
deliveries, that did have an 

163
00:11:06,500 --> 00:11:09,600
Excursion. 
We were able to see not only 

164
00:11:10,400 --> 00:11:13,300
that temperature Excursion 
happened, but also where it 

165
00:11:13,300 --> 00:11:18,600
happened as the divides records 
also geolocation and this 

166
00:11:18,600 --> 00:11:22,000
allowed us to identify. 
Parts of the supply chain where 

167
00:11:22,000 --> 00:11:25,600
the temperature excursions 
happened and address them with 

168
00:11:25,600 --> 00:11:30,900
the transport providers, or even
sites in in hospitals, for 

169
00:11:30,900 --> 00:11:33,700
example, improper storage at the
receiving end. 

170
00:11:33,900 --> 00:11:36,800
So what's up with the future? 
Let's talk about the future. 

171
00:11:36,800 --> 00:11:40,700
Are there any plans or further 
plans to enhance your cold chain

172
00:11:40,700 --> 00:11:44,200
processes? 
Absolutely, we do have plans for

173
00:11:44,200 --> 00:11:47,400
the future. 
So the biggest plan is we're 

174
00:11:47,400 --> 00:11:49,800
moving the solution to as for 
Hannah. 

175
00:11:49,900 --> 00:11:54,900
Within next year, we also plan 
to expand the network where we 

176
00:11:54,900 --> 00:11:58,800
use the smart sensors in 
geographical terms to use it in 

177
00:11:58,800 --> 00:12:04,400
more countries, more Depots. 
And the last one is that we plan

178
00:12:04,400 --> 00:12:10,300
to connect more quality relevant
systems that store, for example 

179
00:12:10,300 --> 00:12:16,800
data, about product stability, 
and enhance the data quality for

180
00:12:16,800 --> 00:12:21,400
the monitoring reasons, The 
sounds great. 

181
00:12:21,400 --> 00:12:25,700
I see a great future for you and
for us and I'm happy you decided

182
00:12:25,700 --> 00:12:28,300
for sap as for Hannah. 
Yeah. 

183
00:12:28,300 --> 00:12:30,400
I think I'm giddy, we could talk
forever. 

184
00:12:31,700 --> 00:12:34,400
But I think, for time reasons, I
think this is a good point. 

185
00:12:34,400 --> 00:12:38,000
Maybe to stop this episode on. 
Hopefully, you will be a future 

186
00:12:38,000 --> 00:12:41,800
guest on the show as well. 
Talking about the sap as for 

187
00:12:41,800 --> 00:12:45,700
Hannah implementation, and thank
you so much for sharing your 

188
00:12:45,708 --> 00:12:49,900
knowledge today. 
Qiblah, Thank you, Marcus for 

189
00:12:49,900 --> 00:12:53,100
having me. 
It was a real pleasure listening

190
00:12:53,200 --> 00:12:56,700
to you. 
So I hope you like this episode.

191
00:12:56,700 --> 00:13:01,100
As much as I did, as always feel
free to drop us an email or via 

192
00:13:01,100 --> 00:13:06,300
inside as for at recipe.com and 
let us know which topics are of 

193
00:13:06,300 --> 00:13:10,500
your interest tune in next time 
and be inside as a p as for 

194
00:13:10,500 --> 00:13:11,000
Hannah.
