d38b9961-1a32-4b0a-a367-523501cb5ff5/6-0
00:00:03.359 --> 00:00:07.532
We are here today with Chuck Christian,
the VP of Technology and CTO at

d38b9961-1a32-4b0a-a367-523501cb5ff5/6-1
00:00:07.532 --> 00:00:10.140
Franciscan Health.
For those who don't know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/6-2
00:00:10.140 --> 00:00:15.009
Franciscan Health is a 13 hospital health
system with its headquarters in Mishawaka

d38b9961-1a32-4b0a-a367-523501cb5ff5/6-3
00:00:15.009 --> 00:00:18.719
IN near South Bend. Chuck,
thanks so much for joining us today.

d38b9961-1a32-4b0a-a367-523501cb5ff5/5-0
00:00:18.759 --> 00:00:20.799
Great. Thanks very much, Jordan.
Appreciate it.

d38b9961-1a32-4b0a-a367-523501cb5ff5/7-0
00:00:20.399 --> 00:00:25.629
So I'm excited to talk about today's
topic, which is cloud strategy.

d38b9961-1a32-4b0a-a367-523501cb5ff5/7-1
00:00:25.629 --> 00:00:31.618
Many large health systems across the
United States right now are either in the

d38b9961-1a32-4b0a-a367-523501cb5ff5/7-2
00:00:31.618 --> 00:00:37.379
midst of actively planning to or have
just recently completed some stage of

d38b9961-1a32-4b0a-a367-523501cb5ff5/7-3
00:00:37.379 --> 00:00:39.199
cloud strategy planning.

d38b9961-1a32-4b0a-a367-523501cb5ff5/8-0
00:00:39.559 --> 00:00:46.347
Whether that's moving your electronic
health record from an on Prem situation

d38b9961-1a32-4b0a-a367-523501cb5ff5/8-1
00:00:46.347 --> 00:00:53.483
to a cloud based arrangement or whether
you're going into the commercial cloud or

d38b9961-1a32-4b0a-a367-523501cb5ff5/8-2
00:00:53.483 --> 00:00:58.879
a private cloud system, there's many,
many different I guess.

d38b9961-1a32-4b0a-a367-523501cb5ff5/9-0
00:00:59.079 --> 00:00:59.199
Uh.

d38b9961-1a32-4b0a-a367-523501cb5ff5/11-0
00:01:00.999 --> 00:01:06.742
There's many things to consider when
evaluating your cloud strategy. So Chuck,

d38b9961-1a32-4b0a-a367-523501cb5ff5/11-1
00:01:06.742 --> 00:01:12.122
right now I understand Franciscan Health
has your Epic instance on Azure,

d38b9961-1a32-4b0a-a367-523501cb5ff5/11-2
00:01:12.122 --> 00:01:15.612
but apparently it took many years to get
there.

d38b9961-1a32-4b0a-a367-523501cb5ff5/10-0
00:01:12.559 --> 00:01:12.759
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/11-3
00:01:15.612 --> 00:01:20.919
So I'd love if you could walk our
listeners through your journey to get.

d38b9961-1a32-4b0a-a367-523501cb5ff5/12-0
00:01:21.119 --> 00:01:27.919
From an on on Prem to a Azure hosted Epic
instance in your cloud strategy.

d38b9961-1a32-4b0a-a367-523501cb5ff5/13-0
00:01:27.439 --> 00:01:31.415
Sure, I'd be happy to. Well,
and the thing about it is,

d38b9961-1a32-4b0a-a367-523501cb5ff5/13-1
00:01:31.415 --> 00:01:36.172
is that the our cloud strategy started
out a little bit different.

d38b9961-1a32-4b0a-a367-523501cb5ff5/13-2
00:01:36.172 --> 00:01:41.994
We actually were private hosted for five
years and then we're going to re-up that

d38b9961-1a32-4b0a-a367-523501cb5ff5/13-3
00:01:41.994 --> 00:01:44.479
private hosting in a private cloud.

d38b9961-1a32-4b0a-a367-523501cb5ff5/14-0
00:01:44.559 --> 00:01:47.743
And that that vendor,
which was a Dell Virtustream,

d38b9961-1a32-4b0a-a367-523501cb5ff5/14-1
00:01:47.743 --> 00:01:52.335
decided to get out of the hosting
business so that it kind of forced us to

d38b9961-1a32-4b0a-a367-523501cb5ff5/14-2
00:01:52.335 --> 00:01:56.989
move to the public cloud a little sooner
than we we had originally planned.

d38b9961-1a32-4b0a-a367-523501cb5ff5/14-3
00:01:56.989 --> 00:02:00.479
We knew we were going to get there one
way or the other.

d38b9961-1a32-4b0a-a367-523501cb5ff5/15-0
00:02:00.959 --> 00:02:06.223
But we had some other things going on,
but it just upped our timeline.

d38b9961-1a32-4b0a-a367-523501cb5ff5/15-1
00:02:06.223 --> 00:02:09.856
So and the Bill Laker,
who was the previous CIO,

d38b9961-1a32-4b0a-a367-523501cb5ff5/15-2
00:02:09.856 --> 00:02:15.639
Charles Wagner is the current CIO head.
That was one of the gifts he gave us.

d38b9961-1a32-4b0a-a367-523501cb5ff5/19-0
00:02:16.319 --> 00:02:20.454
Before he retired was he signed the the
hosting,

d38b9961-1a32-4b0a-a367-523501cb5ff5/19-1
00:02:20.454 --> 00:02:27.544
the first private cloud hosting agreement
and they took about 18 months to do that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/16-0
00:02:25.519 --> 00:02:25.639
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/19-2
00:02:27.544 --> 00:02:33.959
I joined the company in April of 2019 and
in May of what, 30 days later we.

d38b9961-1a32-4b0a-a367-523501cb5ff5/17-0
00:02:32.559 --> 00:02:33.039
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/20-0
00:02:34.359 --> 00:02:37.514
Turned it on in the Virtustream data
centers.

d38b9961-1a32-4b0a-a367-523501cb5ff5/18-0
00:02:34.639 --> 00:02:35.039
No.

d38b9961-1a32-4b0a-a367-523501cb5ff5/20-1
00:02:37.514 --> 00:02:43.207
And so we were there for five years and
then we spent another 18 months moving it,

d38b9961-1a32-4b0a-a367-523501cb5ff5/20-2
00:02:43.207 --> 00:02:48.901
building it inside of Azure and moving it.
But we had already moved some workloads

d38b9961-1a32-4b0a-a367-523501cb5ff5/20-3
00:02:48.901 --> 00:02:50.479
to Azure prior to that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/22-0
00:02:52.039 --> 00:02:57.734
So it's it's been an interesting journey
to say the least.

d38b9961-1a32-4b0a-a367-523501cb5ff5/22-1
00:02:57.734 --> 00:03:05.264
But the one thing that I did back in 23
was I created a position called Cloud

d38b9961-1a32-4b0a-a367-523501cb5ff5/22-2
00:03:05.264 --> 00:03:06.519
Cost Analyst.

d38b9961-1a32-4b0a-a367-523501cb5ff5/21-0
00:03:06.199 --> 00:03:06.479
Hmm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/23-0
00:03:06.839 --> 00:03:11.680
Is because I'd heard too many stories
about people who really were not watching

d38b9961-1a32-4b0a-a367-523501cb5ff5/23-1
00:03:11.680 --> 00:03:16.340
their spend in the cloud and just
thinking it was gonna take care of itself.

d38b9961-1a32-4b0a-a367-523501cb5ff5/23-2
00:03:16.340 --> 00:03:20.758
And they were getting hundreds of
thousands of dollars worth of surprise

d38b9961-1a32-4b0a-a367-523501cb5ff5/23-3
00:03:20.758 --> 00:03:23.119
billing. And so I decided that I would.

d38b9961-1a32-4b0a-a367-523501cb5ff5/25-0
00:03:23.559 --> 00:03:29.436
From the very beginning,
start watching that very carefully and we

d38b9961-1a32-4b0a-a367-523501cb5ff5/25-1
00:03:29.436 --> 00:03:36.102
had an analyst that was on my team that
reported up to one of my directors.

d38b9961-1a32-4b0a-a367-523501cb5ff5/24-0
00:03:30.799 --> 00:03:31.039
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/25-2
00:03:36.102 --> 00:03:38.559
He was very detail oriented.

d38b9961-1a32-4b0a-a367-523501cb5ff5/27-0
00:03:38.639 --> 00:03:45.582
I've been told not to use the word ****,
but I and Eric knows I talk about him a

d38b9961-1a32-4b0a-a367-523501cb5ff5/27-1
00:03:45.582 --> 00:03:51.924
lot like that. He is outstanding.
He's learned more about Fin OPS than he

d38b9961-1a32-4b0a-a367-523501cb5ff5/26-0
00:03:48.799 --> 00:03:49.439
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/27-2
00:03:51.924 --> 00:03:57.496
ever thought he would.
And every every Wednesday morning at 7:30

d38b9961-1a32-4b0a-a367-523501cb5ff5/27-3
00:03:57.496 --> 00:03:58.439
like clock.

d38b9961-1a32-4b0a-a367-523501cb5ff5/29-0
00:03:58.479 --> 00:04:01.414
Work.
I get a report in my e-mail of what our

d38b9961-1a32-4b0a-a367-523501cb5ff5/29-1
00:04:01.414 --> 00:04:05.561
spend is for the month,
how we compared to this same period last

d38b9961-1a32-4b0a-a367-523501cb5ff5/29-2
00:04:05.561 --> 00:04:09.390
year, what's trending,
if it's anything that's worrying him

d38b9961-1a32-4b0a-a367-523501cb5ff5/29-3
00:04:09.390 --> 00:04:14.749
about the spend that it's going up higher
than he thought because he's plugged into

d38b9961-1a32-4b0a-a367-523501cb5ff5/29-4
00:04:14.749 --> 00:04:16.919
as that infrastructure changes so.

d38b9961-1a32-4b0a-a367-523501cb5ff5/28-0
00:04:18.079 --> 00:04:18.559
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/30-0
00:04:18.159 --> 00:04:24.134
And we have a managed services company
that manages all of that for us in Azure,

d38b9961-1a32-4b0a-a367-523501cb5ff5/30-1
00:04:24.134 --> 00:04:29.519
but my team monitors all of that and we
manage from the application out,

d38b9961-1a32-4b0a-a367-523501cb5ff5/30-2
00:04:29.519 --> 00:04:32.839
they manage everything from the
application.

d38b9961-1a32-4b0a-a367-523501cb5ff5/31-0
00:04:33.279 --> 00:04:34.279
Below.

d38b9961-1a32-4b0a-a367-523501cb5ff5/32-0
00:04:34.919 --> 00:04:39.211
Well, Chuck,
I have so many questions based on what

d38b9961-1a32-4b0a-a367-523501cb5ff5/32-1
00:04:39.211 --> 00:04:43.587
you just said.
I think the most pertinent one to our

d38b9961-1a32-4b0a-a367-523501cb5ff5/32-2
00:04:43.587 --> 00:04:48.623
listeners would be,
has there been any point when your cloud

d38b9961-1a32-4b0a-a367-523501cb5ff5/32-3
00:04:48.623 --> 00:04:54.319
cost analyst since he's been hired has
actually alerted you to some?

d38b9961-1a32-4b0a-a367-523501cb5ff5/33-0
00:04:54.519 --> 00:04:57.832
Elevated spending that's been of concern
to him and if so,

d38b9961-1a32-4b0a-a367-523501cb5ff5/33-1
00:04:57.832 --> 00:05:02.324
what was your intervention at the time?
I think that would be of great interest

d38b9961-1a32-4b0a-a367-523501cb5ff5/33-2
00:05:02.324 --> 00:05:03.279
to our listeners.

d38b9961-1a32-4b0a-a367-523501cb5ff5/34-0
00:05:03.359 --> 00:05:07.670
Well, as you can well imagine,
there's a lot of things you can do inside

d38b9961-1a32-4b0a-a367-523501cb5ff5/34-1
00:05:07.670 --> 00:05:10.800
of Azure very quickly.
You can spin up environments,

d38b9961-1a32-4b0a-a367-523501cb5ff5/34-2
00:05:10.800 --> 00:05:14.697
you can increase storage.
And so our managed services partner was

d38b9961-1a32-4b0a-a367-523501cb5ff5/34-3
00:05:14.697 --> 00:05:18.359
doing some moves of storage from one
storage tier to another.

d38b9961-1a32-4b0a-a367-523501cb5ff5/37-0
00:05:19.279 --> 00:05:23.995
It took them longer than they had
anticipated and so we our storage costs

d38b9961-1a32-4b0a-a367-523501cb5ff5/37-1
00:05:23.995 --> 00:05:27.627
jumped up $20,
000 in one month and so that that's a red

d38b9961-1a32-4b0a-a367-523501cb5ff5/35-0
00:05:25.359 --> 00:05:25.519
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/37-2
00:05:27.627 --> 00:05:32.599
flag that's Erie's going to let us know.
So we immediately reached out to the

d38b9961-1a32-4b0a-a367-523501cb5ff5/37-3
00:05:32.599 --> 00:05:36.359
managed services partner and asked him
what are you doing?

d38b9961-1a32-4b0a-a367-523501cb5ff5/38-0
00:05:36.999 --> 00:05:40.111
And so then they mitigated it very
quickly.

d38b9961-1a32-4b0a-a367-523501cb5ff5/36-0
00:05:37.359 --> 00:05:37.679
Hello.

d38b9961-1a32-4b0a-a367-523501cb5ff5/38-1
00:05:40.111 --> 00:05:46.123
And so and then we've had some other ones,
Epic and requires a great deal of storage

d38b9961-1a32-4b0a-a367-523501cb5ff5/38-2
00:05:46.123 --> 00:05:49.659
and they use BLOB storage and that kind
of stuff.

d38b9961-1a32-4b0a-a367-523501cb5ff5/38-3
00:05:49.659 --> 00:05:53.479
And Microsoft didn't used to charge for
BLOB storage.

d38b9961-1a32-4b0a-a367-523501cb5ff5/39-0
00:05:53.959 --> 00:05:57.323
They had it in preview mode.
I don't know exactly what that means,

d38b9961-1a32-4b0a-a367-523501cb5ff5/39-1
00:05:57.323 --> 00:06:00.837
but it means you get to use it.
You don't have to get charged for it.

d38b9961-1a32-4b0a-a367-523501cb5ff5/39-2
00:06:00.837 --> 00:06:04.553
But then all of a sudden, you know,
we got noticed that next month you're

d38b9961-1a32-4b0a-a367-523501cb5ff5/39-3
00:06:04.553 --> 00:06:07.816
gonna get charged for it.
And what we saw was that BLOB storage,

d38b9961-1a32-4b0a-a367-523501cb5ff5/39-4
00:06:07.816 --> 00:06:11.029
the bill for that was over $200,
000 in one month. And we look,

d38b9961-1a32-4b0a-a367-523501cb5ff5/39-5
00:06:11.029 --> 00:06:13.239
we had a lot of conversations at
Microsoft.

d38b9961-1a32-4b0a-a367-523501cb5ff5/40-0
00:06:13.439 --> 00:06:17.658
And said that cannot possibly be correct.
And so sure enough,

d38b9961-1a32-4b0a-a367-523501cb5ff5/40-1
00:06:17.658 --> 00:06:20.721
they went back and said, yeah,
you're right,

d38b9961-1a32-4b0a-a367-523501cb5ff5/40-2
00:06:20.721 --> 00:06:25.485
we the billing is entirely wrong.
We've shut it off. We're, you know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/40-3
00:06:25.485 --> 00:06:28.887
we're going to give you a credit for all
of that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/40-4
00:06:28.887 --> 00:06:33.039
And you have our deepest apologies and we
won't do it again.

d38b9961-1a32-4b0a-a367-523501cb5ff5/41-0
00:06:33.039 --> 00:06:37.362
Well, it's Microsoft.
They're going to make mistakes just like

d38b9961-1a32-4b0a-a367-523501cb5ff5/41-1
00:06:37.362 --> 00:06:41.412
all of us. But as long as you watch it,
they've been very,

d38b9961-1a32-4b0a-a367-523501cb5ff5/41-2
00:06:41.412 --> 00:06:46.079
very good about if we can show them the
era that that we're seeing,

d38b9961-1a32-4b0a-a367-523501cb5ff5/41-3
00:06:46.079 --> 00:06:51.844
they're very good about applying a credit
back to us and removing that expense at a

d38b9961-1a32-4b0a-a367-523501cb5ff5/41-4
00:06:51.844 --> 00:06:52.599
later date.

d38b9961-1a32-4b0a-a367-523501cb5ff5/42-0
00:06:52.919 --> 00:06:59.539
Sounds like if a peer organization
without a cloud cost analyst proactively

d38b9961-1a32-4b0a-a367-523501cb5ff5/42-1
00:06:59.539 --> 00:07:03.982
monitoring your spend were to have
elevated costs,

d38b9961-1a32-4b0a-a367-523501cb5ff5/42-2
00:07:03.982 --> 00:07:10.602
it might be difficult to retroactively
identify where there were inaccurate

d38b9961-1a32-4b0a-a367-523501cb5ff5/42-3
00:07:10.602 --> 00:07:12.519
charges. So I suppose.

d38b9961-1a32-4b0a-a367-523501cb5ff5/43-0
00:07:12.639 --> 00:07:17.862
Having your analyst was able to
proactively avoid what could have

d38b9961-1a32-4b0a-a367-523501cb5ff5/43-1
00:07:17.862 --> 00:07:23.639
compounded into significant additional
erroneous charges. Is that right?

d38b9961-1a32-4b0a-a367-523501cb5ff5/47-0
00:07:21.919 --> 00:07:24.832
Right. Well,
it's kind of looking at your credit card

d38b9961-1a32-4b0a-a367-523501cb5ff5/47-1
00:07:24.832 --> 00:07:27.745
statement and going, damn,
I didn't buy that. And so,

d38b9961-1a32-4b0a-a367-523501cb5ff5/44-0
00:07:24.839 --> 00:07:25.679
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/47-2
00:07:27.745 --> 00:07:31.467
but then you have to, you know,
go through the trouble of getting it

d38b9961-1a32-4b0a-a367-523501cb5ff5/47-3
00:07:31.467 --> 00:07:34.219
taken off and disputing it and that kind
of stuff.

d38b9961-1a32-4b0a-a367-523501cb5ff5/47-4
00:07:34.219 --> 00:07:37.779
It's better to do it as you see it.
So you're absolutely correct.

d38b9961-1a32-4b0a-a367-523501cb5ff5/45-0
00:07:36.239 --> 00:07:36.719
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/47-5
00:07:37.779 --> 00:07:40.639
And so that those are the things that
Eric does and.

d38b9961-1a32-4b0a-a367-523501cb5ff5/49-0
00:07:40.639 --> 00:07:43.475
I will tell any of the viewers that are
out there,

d38b9961-1a32-4b0a-a367-523501cb5ff5/46-0
00:07:42.079 --> 00:07:42.159
I.

d38b9961-1a32-4b0a-a367-523501cb5ff5/49-1
00:07:43.475 --> 00:07:46.811
if they want the job description for my
cloud cost analyst,

d38b9961-1a32-4b0a-a367-523501cb5ff5/49-2
00:07:46.811 --> 00:07:50.370
I'll be happy to share it.
I have shared it out on probably two

d38b9961-1a32-4b0a-a367-523501cb5ff5/48-0
00:07:47.279 --> 00:07:48.719
Now um.

d38b9961-1a32-4b0a-a367-523501cb5ff5/52-0
00:07:49.879 --> 00:07:57.886
I do have a question that Eric probably
would not like me to ask, but nonetheless,

d38b9961-1a32-4b0a-a367-523501cb5ff5/49-3
00:07:50.370 --> 00:07:52.039
dozen times already. Go ahead.

d38b9961-1a32-4b0a-a367-523501cb5ff5/52-1
00:07:57.886 --> 00:08:02.323
Gen.
A I is rapidly making headway into every

d38b9961-1a32-4b0a-a367-523501cb5ff5/50-0
00:07:58.279 --> 00:07:58.559
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/52-2
00:08:02.323 --> 00:08:07.919
organization in America,
especially large health systems.

d38b9961-1a32-4b0a-a367-523501cb5ff5/51-0
00:08:03.879 --> 00:08:04.239
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/53-0
00:08:08.119 --> 00:08:12.926
Is there any planned use for Gen.
AI in your future road map to do some of

d38b9961-1a32-4b0a-a367-523501cb5ff5/53-1
00:08:12.926 --> 00:08:17.861
the to automate some of the work that
Eric is manually doing now and running

d38b9961-1a32-4b0a-a367-523501cb5ff5/53-2
00:08:17.861 --> 00:08:18.759
these reports?

d38b9961-1a32-4b0a-a367-523501cb5ff5/56-0
00:08:18.319 --> 00:08:21.585
Well, I mean,
we're we're already doing some of this

d38b9961-1a32-4b0a-a367-523501cb5ff5/56-1
00:08:21.585 --> 00:08:26.393
stuff. Microsoft has a lot of tools,
but we're not going to depend upon that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/54-0
00:08:25.079 --> 00:08:25.279
Review.

d38b9961-1a32-4b0a-a367-523501cb5ff5/56-2
00:08:26.393 --> 00:08:29.844
It's kind of like the Fox watching a hen
house. I mean,

d38b9961-1a32-4b0a-a367-523501cb5ff5/56-3
00:08:29.844 --> 00:08:34.344
we have a tendency to take Ronald
Reagan's approach of trust but verify.

d38b9961-1a32-4b0a-a367-523501cb5ff5/55-0
00:08:32.159 --> 00:08:32.639
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/56-4
00:08:34.344 --> 00:08:37.919
And I'm not sure that yet an A I could do
what Eric does.

d38b9961-1a32-4b0a-a367-523501cb5ff5/57-0
00:08:37.999 --> 00:08:42.391
If I had my guess,
if we have some new tools that come in,

d38b9961-1a32-4b0a-a367-523501cb5ff5/57-1
00:08:42.391 --> 00:08:48.048
it'll augment his ability to catch things
earlier on down the road. I mean,

d38b9961-1a32-4b0a-a367-523501cb5ff5/57-2
00:08:48.048 --> 00:08:53.929
I've had some conversation with some
folks that they have an AI tool that will

d38b9961-1a32-4b0a-a367-523501cb5ff5/57-3
00:08:53.929 --> 00:08:57.279
look around the utilization of the
hardware.

d38b9961-1a32-4b0a-a367-523501cb5ff5/59-0
00:08:57.639 --> 00:09:01.715
If they're seeing that it's being over
provisioned, I mean,

d38b9961-1a32-4b0a-a367-523501cb5ff5/59-1
00:09:01.715 --> 00:09:06.268
you've got more than you really need
based upon what's being used.

d38b9961-1a32-4b0a-a367-523501cb5ff5/58-0
00:09:04.999 --> 00:09:05.599
Mm-hmm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/59-2
00:09:06.268 --> 00:09:09.801
It'll resize it automatically.
And I'm going, well,

d38b9961-1a32-4b0a-a367-523501cb5ff5/59-3
00:09:09.801 --> 00:09:12.519
I'm not sure if I'm ready for the Tesla.

d38b9961-1a32-4b0a-a367-523501cb5ff5/61-0
00:09:12.799 --> 00:09:18.746
Opportunity inside my Epic environment to
tell you the truth because you could

d38b9961-1a32-4b0a-a367-523501cb5ff5/61-1
00:09:18.746 --> 00:09:24.468
resize it based upon you know a limited
data set and be and make a terrible

d38b9961-1a32-4b0a-a367-523501cb5ff5/60-0
00:09:21.399 --> 00:09:21.519
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/61-2
00:09:24.468 --> 00:09:30.491
mistake that you have to undo and that
would cause a performance issue for your

d38b9961-1a32-4b0a-a367-523501cb5ff5/61-3
00:09:30.491 --> 00:09:31.319
clinicians.

d38b9961-1a32-4b0a-a367-523501cb5ff5/65-0
00:09:31.479 --> 00:09:34.543
So I'd like to pivot for a moment, Chuck.
Actually,

d38b9961-1a32-4b0a-a367-523501cb5ff5/65-1
00:09:34.543 --> 00:09:39.081
there's a number of topics that we
haven't yet addressed that you alluded to

d38b9961-1a32-4b0a-a367-523501cb5ff5/62-0
00:09:34.799 --> 00:09:34.919
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/65-2
00:09:39.081 --> 00:09:43.678
earlier, and I'd like to dive into those.
So you did mention that Dell Virtue

d38b9961-1a32-4b0a-a367-523501cb5ff5/63-0
00:09:40.919 --> 00:09:41.039
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/65-3
00:09:43.678 --> 00:09:47.804
Stream didn't want to be in the data
center hosting business anymore,

d38b9961-1a32-4b0a-a367-523501cb5ff5/65-4
00:09:47.804 --> 00:09:51.399
and that originally is what prompted your
move to Microsoft.

d38b9961-1a32-4b0a-a367-523501cb5ff5/64-0
00:09:48.199 --> 00:09:48.439
Run.

d38b9961-1a32-4b0a-a367-523501cb5ff5/66-0
00:09:51.479 --> 00:09:55.797
Microsoft Azure and you said that you
initially Franciscan Health had some

d38b9961-1a32-4b0a-a367-523501cb5ff5/66-1
00:09:55.797 --> 00:10:00.289
hesitancy about going into the public
cloud as quickly as you ended up doing.

d38b9961-1a32-4b0a-a367-523501cb5ff5/66-2
00:10:00.289 --> 00:10:04.607
My question is how were you able to
overcome that hesitancy about going to

d38b9961-1a32-4b0a-a367-523501cb5ff5/66-3
00:10:04.607 --> 00:10:09.329
the public cloud from the private hosted
solution and why did you end up deciding

d38b9961-1a32-4b0a-a367-523501cb5ff5/66-4
00:10:09.329 --> 00:10:10.999
to go in that direction with?

d38b9961-1a32-4b0a-a367-523501cb5ff5/67-0
00:10:11.039 --> 00:10:14.922
In this case,
Microsoft Azure instead of seeking to

d38b9961-1a32-4b0a-a367-523501cb5ff5/67-1
00:10:14.922 --> 00:10:20.599
move from Dell versus Stream to another
competitor's fully hosted solution.

d38b9961-1a32-4b0a-a367-523501cb5ff5/68-0
00:10:20.799 --> 00:10:25.308
Well,
has a lot to unpack in that that question.

d38b9961-1a32-4b0a-a367-523501cb5ff5/68-1
00:10:25.308 --> 00:10:32.025
So I'll, I'll, I'll do my best.
And so Dale made some business decisions

d38b9961-1a32-4b0a-a367-523501cb5ff5/68-2
00:10:32.025 --> 00:10:39.202
about the time that we the the cost of
running Epic in a private cloud or the

d38b9961-1a32-4b0a-a367-523501cb5ff5/68-3
00:10:39.202 --> 00:10:40.399
public cloud.

d38b9961-1a32-4b0a-a367-523501cb5ff5/70-0
00:10:40.719 --> 00:10:45.046
Was not inexpensive.
And so our purchasing policies required

d38b9961-1a32-4b0a-a367-523501cb5ff5/70-1
00:10:45.046 --> 00:10:50.083
us to go out to RFP before we just
automatically renewed an agreement.

d38b9961-1a32-4b0a-a367-523501cb5ff5/70-2
00:10:50.083 --> 00:10:53.843
So we did that.
We sent it out to a lot of different

d38b9961-1a32-4b0a-a367-523501cb5ff5/70-3
00:10:53.843 --> 00:10:59.519
consulting firms, managed services firms.
We sent it out to AWS, Amazon, Azure.

d38b9961-1a32-4b0a-a367-523501cb5ff5/71-0
00:11:00.319 --> 00:11:06.603
We talked to Rackspace and of course Epic,
it's their self as well as Virtustream

d38b9961-1a32-4b0a-a367-523501cb5ff5/71-1
00:11:06.603 --> 00:11:12.734
because we didn't know at that point in
time that Dell was going to Virtustream

d38b9961-1a32-4b0a-a367-523501cb5ff5/71-2
00:11:12.734 --> 00:11:17.639
was a separate business unit inside of
Dell. It was autonomous.

d38b9961-1a32-4b0a-a367-523501cb5ff5/72-0
00:11:18.239 --> 00:11:23.079
But then they made the business decision
to move it into inside of Dell

d38b9961-1a32-4b0a-a367-523501cb5ff5/72-1
00:11:23.079 --> 00:11:28.593
Technologies and the leadership of Dell
Technologies decided they did not want to

d38b9961-1a32-4b0a-a367-523501cb5ff5/72-2
00:11:28.593 --> 00:11:34.106
be in the data center business anymore.
And so they they let their customers know

d38b9961-1a32-4b0a-a367-523501cb5ff5/72-3
00:11:34.106 --> 00:11:37.199
and we were given an off ramp to move and
so.

d38b9961-1a32-4b0a-a367-523501cb5ff5/73-0
00:11:37.519 --> 00:11:41.522
We knew that that gave us that limited
our choices.

d38b9961-1a32-4b0a-a367-523501cb5ff5/73-1
00:11:41.522 --> 00:11:46.141
We could either go to the public cloud,
we could, you know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/73-2
00:11:46.141 --> 00:11:50.760
turn to Epic for their their hosting or
we could, you know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/73-3
00:11:50.760 --> 00:11:52.839
go to Rackspace or AWS and.

d38b9961-1a32-4b0a-a367-523501cb5ff5/75-0
00:11:53.039 --> 00:11:56.796
Or Microsoft.
And so we did not have any workloads in

d38b9961-1a32-4b0a-a367-523501cb5ff5/75-1
00:11:56.796 --> 00:12:01.875
Amazon AWS at that point in time.
We'd already started and had built our

d38b9961-1a32-4b0a-a367-523501cb5ff5/75-2
00:12:01.875 --> 00:12:07.441
networking in two different data centers.
We were mostly everything that was in

d38b9961-1a32-4b0a-a367-523501cb5ff5/74-0
00:12:03.359 --> 00:12:03.479
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/75-3
00:12:07.441 --> 00:12:11.199
production was in North Central,
which is in Chicago.

d38b9961-1a32-4b0a-a367-523501cb5ff5/76-0
00:12:11.599 --> 00:12:18.556
And we had done some work out in Central,
which is in Iowa related to virtual

d38b9961-1a32-4b0a-a367-523501cb5ff5/76-1
00:12:18.556 --> 00:12:25.514
desktops and those type of things.
And so it wasn't an easy decision to make.

d38b9961-1a32-4b0a-a367-523501cb5ff5/76-2
00:12:25.514 --> 00:12:30.599
Microsoft came to the table with some
good partnerships.

d38b9961-1a32-4b0a-a367-523501cb5ff5/78-0
00:12:31.239 --> 00:12:34.963
Willing to make some investment in our
adventure.

d38b9961-1a32-4b0a-a367-523501cb5ff5/78-1
00:12:34.963 --> 00:12:40.921
There had not been a health system our
size that had actually moved to Azure at

d38b9961-1a32-4b0a-a367-523501cb5ff5/78-2
00:12:40.921 --> 00:12:45.539
that point in time.
And so we were kind of breaking ground on

d38b9961-1a32-4b0a-a367-523501cb5ff5/77-0
00:12:44.399 --> 00:12:44.519
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/78-3
00:12:45.539 --> 00:12:48.519
this and that was some of the hesitancy.

d38b9961-1a32-4b0a-a367-523501cb5ff5/80-0
00:12:48.919 --> 00:12:51.636
You know,
Franciscan is not considered a

d38b9961-1a32-4b0a-a367-523501cb5ff5/80-1
00:12:51.636 --> 00:12:56.871
organization that is pioneers and many
things. Sometimes we're fast followers.

d38b9961-1a32-4b0a-a367-523501cb5ff5/79-0
00:12:56.039 --> 00:12:56.599
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/80-2
00:12:56.871 --> 00:13:00.648
But you know what? You know,
you know what pioneers get.

d38b9961-1a32-4b0a-a367-523501cb5ff5/80-3
00:13:00.648 --> 00:13:03.762
They get the arrows from the from the
Indians.

d38b9961-1a32-4b0a-a367-523501cb5ff5/80-4
00:13:03.762 --> 00:13:08.799
And we don't really want to do that
because there's a risk associated with.

d38b9961-1a32-4b0a-a367-523501cb5ff5/81-0
00:13:08.959 --> 00:13:15.940
But we felt pretty confident with the
partners that we had and the managed

d38b9961-1a32-4b0a-a367-523501cb5ff5/81-1
00:13:15.940 --> 00:13:23.200
services group that had already moved
some workloads of size and had had that

d38b9961-1a32-4b0a-a367-523501cb5ff5/81-2
00:13:23.200 --> 00:13:27.947
experience.
And so we decided to not really take a

d38b9961-1a32-4b0a-a367-523501cb5ff5/81-3
00:13:27.947 --> 00:13:28.599
chance.

d38b9961-1a32-4b0a-a367-523501cb5ff5/84-0
00:13:28.799 --> 00:13:32.132
But it was a calculated risk of moving
out there.

d38b9961-1a32-4b0a-a367-523501cb5ff5/84-1
00:13:32.132 --> 00:13:37.332
We and that the full backing of Microsoft,
they weren't going to let us fail.

d38b9961-1a32-4b0a-a367-523501cb5ff5/84-2
00:13:37.332 --> 00:13:42.265
Epic was not going to let us fail.
Our managed services partner that were

d38b9961-1a32-4b0a-a367-523501cb5ff5/82-0
00:13:39.439 --> 00:13:39.959
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/83-0
00:13:40.959 --> 00:13:41.439
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/84-3
00:13:42.265 --> 00:13:45.999
doing the bill was not going to fail
because they were.

d38b9961-1a32-4b0a-a367-523501cb5ff5/85-0
00:13:45.999 --> 00:13:49.426
Reputationally,
it was there was too much at risk for

d38b9961-1a32-4b0a-a367-523501cb5ff5/85-1
00:13:49.426 --> 00:13:52.981
them. We had,
they had to have us succeed and we didn't

d38b9961-1a32-4b0a-a367-523501cb5ff5/85-2
00:13:52.981 --> 00:13:57.742
want to fail either. And so, you know,
and I will tell you that, you know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/85-3
00:13:57.742 --> 00:14:00.599
I had a meeting with Microsoft on
Wednesday.

d38b9961-1a32-4b0a-a367-523501cb5ff5/86-0
00:14:01.599 --> 00:14:07.248
With a lot of people that were involved
in this process and we are all in

d38b9961-1a32-4b0a-a367-523501cb5ff5/86-1
00:14:07.248 --> 00:14:13.203
agreement that it was a grand learning
opportunity for all everybody that was

d38b9961-1a32-4b0a-a367-523501cb5ff5/86-2
00:14:13.203 --> 00:14:16.639
involved.
So it's it turned out really well.

d38b9961-1a32-4b0a-a367-523501cb5ff5/88-0
00:14:15.039 --> 00:14:19.755
So you mentioned your implementation
partner a few times. You know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/88-1
00:14:19.755 --> 00:14:24.956
I know we've spoken about first.
I'd like to secondly address architecture

d38b9961-1a32-4b0a-a367-523501cb5ff5/88-2
00:14:24.956 --> 00:14:28.354
in light of,
but but first let's just talk about

d38b9961-1a32-4b0a-a367-523501cb5ff5/87-0
00:14:27.879 --> 00:14:28.039
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/88-3
00:14:28.354 --> 00:14:33.278
financial and general risk tolerance.
You said you need to pick a good

d38b9961-1a32-4b0a-a367-523501cb5ff5/88-4
00:14:33.278 --> 00:14:34.319
implementation.

d38b9961-1a32-4b0a-a367-523501cb5ff5/89-0
00:14:34.839 --> 00:14:38.424
Partner and a good integration engine
that can migrate data to the cloud

d38b9961-1a32-4b0a-a367-523501cb5ff5/91-0
00:14:38.279 --> 00:14:42.005
Not an integration engine,
an integration partner.

d38b9961-1a32-4b0a-a367-523501cb5ff5/89-1
00:14:38.424 --> 00:14:39.799
environment. How did you go?

d38b9961-1a32-4b0a-a367-523501cb5ff5/90-0
00:14:41.439 --> 00:14:43.479
In an integration part, so how?

d38b9961-1a32-4b0a-a367-523501cb5ff5/91-1
00:14:42.005 --> 00:14:45.439
It's a it's humans.
It's not done by machines.

d38b9961-1a32-4b0a-a367-523501cb5ff5/92-0
00:14:45.359 --> 00:14:48.845
So, well,
how do you pick the right implementation

d38b9961-1a32-4b0a-a367-523501cb5ff5/92-1
00:14:48.845 --> 00:14:52.194
partner?
And also how do you pick the right kind

d38b9961-1a32-4b0a-a367-523501cb5ff5/92-2
00:14:52.194 --> 00:14:55.475
of well,
also the integration platform in which

d38b9961-1a32-4b0a-a367-523501cb5ff5/92-3
00:14:55.475 --> 00:14:59.919
you're building those interfaces?
How do you pick both of those?

d38b9961-1a32-4b0a-a367-523501cb5ff5/95-0
00:14:59.119 --> 00:15:02.082
Well,
so here's The thing is Epic to Epic is

d38b9961-1a32-4b0a-a367-523501cb5ff5/95-1
00:15:02.082 --> 00:15:05.901
not that big a deal. Epic does a really,
really good job.

d38b9961-1a32-4b0a-a367-523501cb5ff5/93-0
00:15:04.799 --> 00:15:05.959
Mm-hmm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/95-2
00:15:05.901 --> 00:15:09.721
They have what they call their cloud
configuration guide.

d38b9961-1a32-4b0a-a367-523501cb5ff5/95-3
00:15:09.721 --> 00:15:14.199
They'll tell you exactly how that
environment needs to be stood up.

d38b9961-1a32-4b0a-a367-523501cb5ff5/94-0
00:15:11.279 --> 00:15:12.079
Mm-hmm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/97-0
00:15:14.719 --> 00:15:20.338
And built down to, you know,
they'll give you a, you know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/97-1
00:15:20.338 --> 00:15:25.004
Chinese menu of servers and things to put
it on.

d38b9961-1a32-4b0a-a367-523501cb5ff5/97-2
00:15:25.004 --> 00:15:30.719
So they have a good fundamental
underlying architecture of.

d38b9961-1a32-4b0a-a367-523501cb5ff5/96-0
00:15:27.039 --> 00:15:27.199
Hello.

d38b9961-1a32-4b0a-a367-523501cb5ff5/99-0
00:15:30.719 --> 00:15:35.153
You put it on this,
we know it's gonna run because they've

d38b9961-1a32-4b0a-a367-523501cb5ff5/98-0
00:15:32.879 --> 00:15:33.399
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/99-1
00:15:35.153 --> 00:15:39.812
got all the monitoring tools,
internal and external for that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/99-2
00:15:39.812 --> 00:15:45.599
So weren't worried about the architecture
because Epic had that nailed down.

d38b9961-1a32-4b0a-a367-523501cb5ff5/99-3
00:15:45.599 --> 00:15:50.559
Do they have everything perfect? No,
but it's a partnership that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/101-0
00:15:50.599 --> 00:15:56.009
But I think Epic got right from the very
beginning is that if you make your

d38b9961-1a32-4b0a-a367-523501cb5ff5/100-0
00:15:52.759 --> 00:15:53.239
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/101-1
00:15:56.009 --> 00:16:00.423
customers successful,
they're gonna stay with you to do that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/101-2
00:16:00.423 --> 00:16:06.190
And that's exactly what they do is they
work really hard to make sure that we're

d38b9961-1a32-4b0a-a367-523501cb5ff5/101-3
00:16:06.190 --> 00:16:10.319
successful and we're referenceable to
anybody that wants.

d38b9961-1a32-4b0a-a367-523501cb5ff5/104-0
00:16:10.399 --> 00:16:14.249
To talk to us.
And so the thing about it is that it's a

d38b9961-1a32-4b0a-a367-523501cb5ff5/104-1
00:16:14.249 --> 00:16:17.412
true migration.
We were running our system in

d38b9961-1a32-4b0a-a367-523501cb5ff5/102-0
00:16:14.319 --> 00:16:14.439
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/104-2
00:16:17.412 --> 00:16:23.118
Virtustream's data center in Sterling, VA.
That's where our production environment

d38b9961-1a32-4b0a-a367-523501cb5ff5/104-3
00:16:23.118 --> 00:16:27.725
was. And we migrated that data to Chicago.
But during the process,

d38b9961-1a32-4b0a-a367-523501cb5ff5/104-4
00:16:27.725 --> 00:16:29.719
Microsoft came back and said.

d38b9961-1a32-4b0a-a367-523501cb5ff5/103-0
00:16:29.039 --> 00:16:29.239
3.

d38b9961-1a32-4b0a-a367-523501cb5ff5/105-0
00:16:30.319 --> 00:16:33.320
You know,
we've learned something about our

d38b9961-1a32-4b0a-a367-523501cb5ff5/105-1
00:16:33.320 --> 00:16:36.731
environment. In Chicago,
we have one data center,

d38b9961-1a32-4b0a-a367-523501cb5ff5/105-2
00:16:36.731 --> 00:16:41.438
so we have availability zones.
That mean you can spread compute over

d38b9961-1a32-4b0a-a367-523501cb5ff5/105-3
00:16:41.438 --> 00:16:45.872
multiple racks of servers,
but you can't spread it over multiple

d38b9961-1a32-4b0a-a367-523501cb5ff5/105-4
00:16:45.872 --> 00:16:46.759
data centers.

d38b9961-1a32-4b0a-a367-523501cb5ff5/106-0
00:16:47.559 --> 00:16:51.750
And so they recommended that we we not go
live in Chicago,

d38b9961-1a32-4b0a-a367-523501cb5ff5/106-1
00:16:51.750 --> 00:16:55.514
but we moved to San Antonio,
which is South Central.

d38b9961-1a32-4b0a-a367-523501cb5ff5/106-2
00:16:55.514 --> 00:17:01.126
They have multiple data centers down
there and we have spread our compute over

d38b9961-1a32-4b0a-a367-523501cb5ff5/106-3
00:17:01.126 --> 00:17:03.399
two of their three data centers.

d38b9961-1a32-4b0a-a367-523501cb5ff5/107-0
00:17:03.799 --> 00:17:09.235
Mostly on the presentation layer because
we can't split our database,

d38b9961-1a32-4b0a-a367-523501cb5ff5/107-1
00:17:09.235 --> 00:17:13.973
it's not splittable.
So but everything's replicating back up

d38b9961-1a32-4b0a-a367-523501cb5ff5/107-2
00:17:13.973 --> 00:17:19.488
to Chicago where our Dr. is.
And so you need people that are certified

d38b9961-1a32-4b0a-a367-523501cb5ff5/107-3
00:17:19.488 --> 00:17:21.119
with Epic technology.

d38b9961-1a32-4b0a-a367-523501cb5ff5/110-0
00:17:21.199 --> 00:17:27.872
And know how to migrate that data.
I have a technical engineer on my team

d38b9961-1a32-4b0a-a367-523501cb5ff5/110-1
00:17:27.872 --> 00:17:34.005
who's absolutely outstanding.
She has been with Franciscan from the

d38b9961-1a32-4b0a-a367-523501cb5ff5/108-0
00:17:30.079 --> 00:17:30.679
Mm-hmm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/110-2
00:17:34.005 --> 00:17:40.679
first implementation of Epic in 2011.
She was a technical analyst before.

d38b9961-1a32-4b0a-a367-523501cb5ff5/111-0
00:17:40.719 --> 00:17:47.920
For that and she's extremely detail
oriented and she manages that environment

d38b9961-1a32-4b0a-a367-523501cb5ff5/109-0
00:17:41.639 --> 00:17:42.199
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/111-1
00:17:47.920 --> 00:17:55.491
from the application and the architecture
side and is the true interface with our

d38b9961-1a32-4b0a-a367-523501cb5ff5/111-2
00:17:55.491 --> 00:17:57.799
managed services partner.

d38b9961-1a32-4b0a-a367-523501cb5ff5/115-0
00:17:57.759 --> 00:18:02.346
Quick, quick question there.
When you're talking about Sterling,

d38b9961-1a32-4b0a-a367-523501cb5ff5/115-1
00:18:02.346 --> 00:18:05.734
VA and Texas and Chicago and you're in
Indiana,

d38b9961-1a32-4b0a-a367-523501cb5ff5/112-0
00:18:02.719 --> 00:18:03.399
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/113-0
00:18:05.039 --> 00:18:05.319
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/115-2
00:18:05.734 --> 00:18:10.039
are there any concerns about lag due to
geographic distance?

d38b9961-1a32-4b0a-a367-523501cb5ff5/114-0
00:18:08.839 --> 00:18:09.039
No.

d38b9961-1a32-4b0a-a367-523501cb5ff5/117-0
00:18:09.919 --> 00:18:16.943
Well, no. In my network architects,
we always have a conversation about the

d38b9961-1a32-4b0a-a367-523501cb5ff5/116-0
00:18:15.679 --> 00:18:16.159
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/117-1
00:18:16.943 --> 00:18:21.657
speed of light and how fast it takes to
propagate.

d38b9961-1a32-4b0a-a367-523501cb5ff5/117-2
00:18:21.657 --> 00:18:26.279
There's we're almost at the same network
latency.

d38b9961-1a32-4b0a-a367-523501cb5ff5/119-0
00:18:26.479 --> 00:18:31.886
Between our data centers and our
hospitals as we are from our colos

d38b9961-1a32-4b0a-a367-523501cb5ff5/119-1
00:18:31.886 --> 00:18:37.849
because we designed it that way.
We have 10 gig circuits that our topology

d38b9961-1a32-4b0a-a367-523501cb5ff5/119-2
00:18:37.849 --> 00:18:43.335
of our network is we have one of our
colos is in Equinix in Chicago.

d38b9961-1a32-4b0a-a367-523501cb5ff5/119-3
00:18:43.335 --> 00:18:46.039
The other colo is here in Indiana.

d38b9961-1a32-4b0a-a367-523501cb5ff5/118-0
00:18:44.039 --> 00:18:44.519
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/121-0
00:18:46.079 --> 00:18:49.979
Indianapolis at Henry St.
And so everything connects back to the

d38b9961-1a32-4b0a-a367-523501cb5ff5/121-1
00:18:49.979 --> 00:18:52.499
colos.
It doesn't connect through my data

d38b9961-1a32-4b0a-a367-523501cb5ff5/120-0
00:18:52.159 --> 00:18:52.679
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/121-2
00:18:52.499 --> 00:18:56.639
centers connect to the colos.
And so we're not everything's not home

d38b9961-1a32-4b0a-a367-523501cb5ff5/121-3
00:18:56.639 --> 00:18:59.399
running back through one of the data
centers.

d38b9961-1a32-4b0a-a367-523501cb5ff5/121-4
00:18:59.399 --> 00:19:03.959
So we have a data center in Indianapolis
and a data center in Lafayette IN.

d38b9961-1a32-4b0a-a367-523501cb5ff5/124-0
00:19:03.919 --> 00:19:08.104
I'd like to wrap up this podcast episode
in the next few minutes,

d38b9961-1a32-4b0a-a367-523501cb5ff5/124-1
00:19:08.104 --> 00:19:11.845
but I would be remiss to do so without
first asking about,

d38b9961-1a32-4b0a-a367-523501cb5ff5/124-2
00:19:11.845 --> 00:19:15.713
and you did allude to this,
your disaster recovery strategy.

d38b9961-1a32-4b0a-a367-523501cb5ff5/122-0
00:19:15.359 --> 00:19:16.279
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/124-3
00:19:15.713 --> 00:19:19.137
You mentioned it's the same size as
production. Also,

d38b9961-1a32-4b0a-a367-523501cb5ff5/124-4
00:19:19.137 --> 00:19:22.879
you mentioned an interesting story.
I think our listeners.

d38b9961-1a32-4b0a-a367-523501cb5ff5/123-0
00:19:19.319 --> 00:19:19.799
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/127-0
00:19:22.959 --> 00:19:25.947
Would be intrigued to hear about Black
Friday.

d38b9961-1a32-4b0a-a367-523501cb5ff5/127-1
00:19:25.947 --> 00:19:28.873
So can you give us some insight into your
Dr.

d38b9961-1a32-4b0a-a367-523501cb5ff5/125-0
00:19:27.319 --> 00:19:29.079
Yeah.

d38b9961-1a32-4b0a-a367-523501cb5ff5/127-2
00:19:28.873 --> 00:19:32.497
and HA disaster recovery and high
availability strategy,

d38b9961-1a32-4b0a-a367-523501cb5ff5/127-3
00:19:32.497 --> 00:19:37.394
how you chose to make sure that it was
the same size as prod instead of just

d38b9961-1a32-4b0a-a367-523501cb5ff5/126-0
00:19:32.719 --> 00:19:33.119
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/127-4
00:19:37.394 --> 00:19:41.590
making it smaller, cheaper,
but scaling to scale up later and how

d38b9961-1a32-4b0a-a367-523501cb5ff5/127-5
00:19:41.590 --> 00:19:42.799
that's relevant to?

d38b9961-1a32-4b0a-a367-523501cb5ff5/128-0
00:19:43.079 --> 00:19:43.479
Thanksgiving.

d38b9961-1a32-4b0a-a367-523501cb5ff5/129-0
00:19:43.439 --> 00:19:46.762
Well, everything is relevant. You know,
The thing about it is,

d38b9961-1a32-4b0a-a367-523501cb5ff5/129-1
00:19:46.762 --> 00:19:50.770
is that when you're using public cloud,
everybody's using the public cloud.

d38b9961-1a32-4b0a-a367-523501cb5ff5/129-2
00:19:50.770 --> 00:19:54.357
And what we found is it had nothing to do
with my epic environment,

d38b9961-1a32-4b0a-a367-523501cb5ff5/129-3
00:19:54.357 --> 00:19:58.735
but it had everything to do with the data
lake house that we were building at that

d38b9961-1a32-4b0a-a367-523501cb5ff5/129-4
00:19:58.735 --> 00:19:58.999
time.

d38b9961-1a32-4b0a-a367-523501cb5ff5/131-0
00:19:59.119 --> 00:20:05.052
We needed to add to that environment and
we this was the week the Monday before

d38b9961-1a32-4b0a-a367-523501cb5ff5/131-1
00:20:05.052 --> 00:20:10.911
Thanksgiving and so we my server team
went to provision additional hardware in

d38b9961-1a32-4b0a-a367-523501cb5ff5/131-2
00:20:10.911 --> 00:20:16.399
our environment in our subscription and
those servers were not available.

d38b9961-1a32-4b0a-a367-523501cb5ff5/130-0
00:20:14.999 --> 00:20:15.559
Mhm.

d38b9961-1a32-4b0a-a367-523501cb5ff5/132-0
00:20:37.639 --> 00:20:37.879
Google.

d38b9961-1a32-4b0a-a367-523501cb5ff5/133-0
00:20:37.919 --> 00:20:38.039
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/134-0
00:20:37.919 --> 00:20:41.707
We'll do the, you know,
kind of the pilot light where you'll

d38b9961-1a32-4b0a-a367-523501cb5ff5/134-1
00:20:41.707 --> 00:20:46.303
provision all that at one time.
But if you can't get the server you want,

d38b9961-1a32-4b0a-a367-523501cb5ff5/134-2
00:20:46.303 --> 00:20:50.589
you have to look for the next server and
the next one, the next one.

d38b9961-1a32-4b0a-a367-523501cb5ff5/134-3
00:20:50.589 --> 00:20:54.812
You can do it with, you know,
with orchestration and automation and

d38b9961-1a32-4b0a-a367-523501cb5ff5/134-4
00:20:54.812 --> 00:20:57.359
make it less painful. But what we did is.

d38b9961-1a32-4b0a-a367-523501cb5ff5/136-0
00:20:57.439 --> 00:21:03.148
We have the same number of Citrix servers
or VMS in both of our data centers.

d38b9961-1a32-4b0a-a367-523501cb5ff5/136-1
00:21:03.148 --> 00:21:08.711
And then in October of last year,
we did something we've never been able to

d38b9961-1a32-4b0a-a367-523501cb5ff5/136-2
00:21:08.711 --> 00:21:12.444
do before.
We actually flipped from South Central,

d38b9961-1a32-4b0a-a367-523501cb5ff5/136-3
00:21:12.444 --> 00:21:15.079
which is in San Antonio, to Chicago.

d38b9961-1a32-4b0a-a367-523501cb5ff5/137-0
00:21:15.519 --> 00:21:22.097
In 45 minutes we we were operational in
Chicago running and we ran there for 30

d38b9961-1a32-4b0a-a367-523501cb5ff5/137-1
00:21:22.097 --> 00:21:26.044
days.
And so in November we flipped back and we

d38b9961-1a32-4b0a-a367-523501cb5ff5/137-2
00:21:26.044 --> 00:21:32.212
got, we flipped back in 42 minutes.
So we now know that it's it's a viable

d38b9961-1a32-4b0a-a367-523501cb5ff5/137-3
00:21:32.212 --> 00:21:33.199
environment.

d38b9961-1a32-4b0a-a367-523501cb5ff5/138-0
00:21:33.279 --> 00:21:39.067
And it's all we have to do is change a
lot of DNS entries that we're working on

d38b9961-1a32-4b0a-a367-523501cb5ff5/138-1
00:21:39.067 --> 00:21:44.493
automating and then ensure all the
integrations to all the things that are

d38b9961-1a32-4b0a-a367-523501cb5ff5/138-2
00:21:44.493 --> 00:21:49.775
still running in our data center,
which is some third party applications

d38b9961-1a32-4b0a-a367-523501cb5ff5/138-3
00:21:49.775 --> 00:21:51.439
are connected properly.

d38b9961-1a32-4b0a-a367-523501cb5ff5/139-0
00:21:51.999 --> 00:21:57.820
The the the moral of this story is if you
if you want to make sure your doctor

d38b9961-1a32-4b0a-a367-523501cb5ff5/139-1
00:21:57.820 --> 00:22:01.430
works,
you really really have to test it and not

d38b9961-1a32-4b0a-a367-523501cb5ff5/139-2
00:22:01.430 --> 00:22:03.199
test it, but running it.

d38b9961-1a32-4b0a-a367-523501cb5ff5/142-0
00:22:03.319 --> 00:22:06.734
So Chuck,
we are are at the end of this podcast

d38b9961-1a32-4b0a-a367-523501cb5ff5/142-1
00:22:06.734 --> 00:22:10.292
episode.
We've really gotten in the weeds here of

d38b9961-1a32-4b0a-a367-523501cb5ff5/142-2
00:22:10.292 --> 00:22:14.562
Franciscan Health's cloud strategy over
the last few years.

d38b9961-1a32-4b0a-a367-523501cb5ff5/142-3
00:22:14.562 --> 00:22:19.615
And I'd like to ask one final question if
you were to speak to a peer,

d38b9961-1a32-4b0a-a367-523501cb5ff5/141-0
00:22:17.879 --> 00:22:18.759
Sure.

d38b9961-1a32-4b0a-a367-523501cb5ff5/142-4
00:22:19.615 --> 00:22:22.319
another VP of tech and CTO at another.

d38b9961-1a32-4b0a-a367-523501cb5ff5/143-0
00:22:22.879 --> 00:22:26.340
Health system in the United States
listening this episode right now.

d38b9961-1a32-4b0a-a367-523501cb5ff5/143-1
00:22:26.340 --> 00:22:29.199
And what would you,
what lessons learned would you share

d38b9961-1a32-4b0a-a367-523501cb5ff5/143-2
00:22:29.199 --> 00:22:31.807
about cloud strategy or what advice would
you give?

d38b9961-1a32-4b0a-a367-523501cb5ff5/143-3
00:22:31.807 --> 00:22:35.770
What would you want to tell that person
as they consider how to navigate these

d38b9961-1a32-4b0a-a367-523501cb5ff5/143-4
00:22:35.770 --> 00:22:38.479
obstacles as they determine their own
cloud strategy?

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-0
00:22:38.479 --> 00:22:41.920
Sure. When I joined Franciscan,
I was told that Franciscan had a cloud

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-1
00:22:41.920 --> 00:22:45.700
first strategy and that meant they were
going to put everything in the cloud.

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-2
00:22:45.700 --> 00:22:48.317
And so I looked at my team and I said,
so we do know,

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-3
00:22:48.317 --> 00:22:51.953
we know that everything can run in the
cloud. They said, well, no, I said.

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-4
00:22:51.953 --> 00:22:54.230
So then you don't have a cloud first
strategy,

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-5
00:22:54.230 --> 00:22:57.914
you have a workload placement strategy
because I've been in healthcare long

d38b9961-1a32-4b0a-a367-523501cb5ff5/144-6
00:22:57.914 --> 00:22:58.399
enough to.

d38b9961-1a32-4b0a-a367-523501cb5ff5/145-0
00:22:58.479 --> 00:23:03.215
There are certain applications that are
absolutely not tolerant at all for

d38b9961-1a32-4b0a-a367-523501cb5ff5/145-1
00:23:03.215 --> 00:23:06.814
network latency,
and there are things that need to be on

d38b9961-1a32-4b0a-a367-523501cb5ff5/145-2
00:23:06.814 --> 00:23:11.740
Prem that if everything else is gone,
it needs to work and that's like infant

d38b9961-1a32-4b0a-a367-523501cb5ff5/145-3
00:23:11.740 --> 00:23:13.319
safety for the nurseries.

d38b9961-1a32-4b0a-a367-523501cb5ff5/146-0
00:23:14.319 --> 00:23:17.088
You know and and you know cardiac
monitoring,

d38b9961-1a32-4b0a-a367-523501cb5ff5/146-1
00:23:17.088 --> 00:23:21.302
you need to have edge servers for packs
and all those type of things.

d38b9961-1a32-4b0a-a367-523501cb5ff5/146-2
00:23:21.302 --> 00:23:26.239
And so you need really have to understand
your environment and go through the app

d38b9961-1a32-4b0a-a367-523501cb5ff5/146-3
00:23:26.239 --> 00:23:31.055
rationalization about what can and cannot
live in the cloud and come up with an

d38b9961-1a32-4b0a-a367-523501cb5ff5/146-4
00:23:31.055 --> 00:23:32.079
appropriate plan.

d38b9961-1a32-4b0a-a367-523501cb5ff5/148-0
00:23:32.479 --> 00:23:38.528
That you can mitigate those those risk in
the event that you're gonna you're gonna

d38b9961-1a32-4b0a-a367-523501cb5ff5/148-1
00:23:38.528 --> 00:23:43.120
have a ADR event and you know it's in
like cyber cyber events.

d38b9961-1a32-4b0a-a367-523501cb5ff5/148-2
00:23:43.120 --> 00:23:48.878
It's not a matter of if it's a matter of
when and so you just you have to work

d38b9961-1a32-4b0a-a367-523501cb5ff5/148-3
00:23:48.878 --> 00:23:50.919
every day to make sure that.

d38b9961-1a32-4b0a-a367-523501cb5ff5/149-0
00:23:51.039 --> 00:23:54.745
You're going to have an environment
that's going to work.

d38b9961-1a32-4b0a-a367-523501cb5ff5/147-0
00:23:51.479 --> 00:23:51.599
OK.

d38b9961-1a32-4b0a-a367-523501cb5ff5/149-1
00:23:54.745 --> 00:23:58.899
We strive to have ours back in full
operation within 7072 hours.

d38b9961-1a32-4b0a-a367-523501cb5ff5/149-2
00:23:58.899 --> 00:24:02.926
Are we there yet? No.
But if our designs work the way we think

d38b9961-1a32-4b0a-a367-523501cb5ff5/149-3
00:24:02.926 --> 00:24:07.719
it will and we find the appropriate
partners to help us build it, it will.

d38b9961-1a32-4b0a-a367-523501cb5ff5/151-0
00:24:07.039 --> 00:24:10.159
I really appreciate our conversation
today, Chuck,

d38b9961-1a32-4b0a-a367-523501cb5ff5/151-1
00:24:10.159 --> 00:24:14.810
especially because I think when you are
in your position as CTO of a health

d38b9961-1a32-4b0a-a367-523501cb5ff5/151-2
00:24:14.810 --> 00:24:17.686
system,
you do have to think about things that

d38b9961-1a32-4b0a-a367-523501cb5ff5/151-3
00:24:17.686 --> 00:24:21.051
normally you wouldn't think are
particularly relevant,

d38b9961-1a32-4b0a-a367-523501cb5ff5/151-4
00:24:21.051 --> 00:24:26.130
like a Cyber Monday sale affecting retail.
How does that affect cardiac monitoring

d38b9961-1a32-4b0a-a367-523501cb5ff5/150-0
00:24:22.919 --> 00:24:23.239
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/151-5
00:24:26.130 --> 00:24:26.559
in the?

d38b9961-1a32-4b0a-a367-523501cb5ff5/153-0
00:24:26.559 --> 00:24:28.923
NICU,
but in fact there are potential

d38b9961-1a32-4b0a-a367-523501cb5ff5/153-1
00:24:28.923 --> 00:24:33.652
implications if you take processing from
servers on Prem and move them into

d38b9961-1a32-4b0a-a367-523501cb5ff5/153-2
00:24:33.652 --> 00:24:38.754
commercial cloud and there's no compute,
no servers available because they're all

d38b9961-1a32-4b0a-a367-523501cb5ff5/153-3
00:24:38.754 --> 00:24:42.425
being used for other applications in the
commercial cloud.

d38b9961-1a32-4b0a-a367-523501cb5ff5/152-0
00:24:42.319 --> 00:24:42.599
Yep.

d38b9961-1a32-4b0a-a367-523501cb5ff5/153-4
00:24:42.425 --> 00:24:46.159
So I think the cross area,
the many areas we covered today.

d38b9961-1a32-4b0a-a367-523501cb5ff5/154-0
00:24:46.239 --> 00:24:49.146
Think are are a lot of of great interest
to our listeners.

d38b9961-1a32-4b0a-a367-523501cb5ff5/154-1
00:24:49.146 --> 00:24:52.202
I appreciate you joining us.
For those who've been following,

d38b9961-1a32-4b0a-a367-523501cb5ff5/154-2
00:24:52.202 --> 00:24:55.306
this has been Chuck Christian,
the VP of Technology and CTO of

d38b9961-1a32-4b0a-a367-523501cb5ff5/154-3
00:24:55.306 --> 00:24:58.559
Franciscan Health. Chuck,
thank you so much for joining us today.