WEBVTT

1
00:00:18.735 --> 00:00:22.975
If you've just joined us, we're just gonna wait another minute to make sure that,

2
00:00:23.455 --> 00:00:25.075
everybody gets in.

3
00:00:39.075 --> 00:00:42.455
We're just waiting another minute for anybody who just came.

4
00:01:03.185 --> 00:01:07.445
If you just arrived, we're gonna wait another 30 seconds before we start.

5
00:01:18.720 --> 00:01:19.780
Alright. I think

6
00:01:20.160 --> 00:01:22.660
things have kinda CAEH down and people joining.

7
00:01:26.735 --> 00:01:28.595
So we'll go ahead and start.

8
00:01:29.110 --> 00:01:30.675
HIFIS, everybody, and welcome.

9
00:01:31.295 --> 00:01:38.595
If you haven't met me, my name is Chantal Perry, and I'm an improvement adviser with the Canadian Alliance to End Homelessness, the Built for 0 team.

10
00:01:38.810 --> 00:01:43.370
We also have a few of my colleagues with us today. We've got Kat Ryder and Melinda Bain.

11
00:01:43.370 --> 00:01:45.310
They're improvement advisers as well.

12
00:01:45.770 --> 00:01:51.150
So welcome to today's community of practice call about HIFIS and Binam list.

13
00:01:53.245 --> 00:01:57.505
I invite you to take this opportunity to put your own land acknowledgment in the chat.

14
00:01:57.645 --> 00:02:02.145
I'm located in Newtown Newfoundland, and I recognize that the island Newfoundland

15
00:02:02.845 --> 00:02:06.945
is the ancestral homeland of the Beothic and its traditional Mi'kmaq territory.

16
00:02:08.860 --> 00:02:10.800
Just some general housekeeping

17
00:02:11.100 --> 00:02:11.600
calls,

18
00:02:12.460 --> 00:02:13.680
housekeeping notes.

19
00:02:13.900 --> 00:02:21.120
The presentation and follow-up questions are being recorded, and they'll be posted on the Built for Xero website by Wednesday of next week,

20
00:02:21.615 --> 00:02:24.355
and conversation might be edited out where appropriate.

21
00:02:25.135 --> 00:02:30.595
If there are other questions or things that you'd like to talk about during the call, then just list them in the chat,

22
00:02:30.975 --> 00:02:36.675
and others can respond directly to you in the chat, or we'll get a chance to discuss them after today's presentation.

23
00:02:37.670 --> 00:02:41.530
Currently, everybody is muted, but use the chat, ask questions,

24
00:02:41.910 --> 00:02:45.770
make comments. You can also raise your hand and unmute yourself as well.

25
00:02:45.830 --> 00:02:47.610
We want this to be fairly conversational.

26
00:02:48.550 --> 00:02:56.662
Note that senior political and data staff from the ministry are on this call as observers to learn more about best practices in implementing binding HIFIS.

27
00:02:57.405 --> 00:03:02.065
They're not collecting questions or taking questions. They're just here to observe.

28
00:03:02.765 --> 00:03:08.545
And if you wanted to discuss any ideas further, please reach out to your friendly improvement adviser,

29
00:03:09.530 --> 00:03:12.510
or your Canadian Alliance to end homelessness coach.

30
00:03:13.290 --> 00:03:16.349
Also, have your smartphones handy for some Slido questions,

31
00:03:16.970 --> 00:03:18.510
and we'll get to that shortly.

32
00:03:20.170 --> 00:03:26.325
Just a reminder that the community of practice calls happen the 2nd Friday of every month from noon to 1 EST,

33
00:03:26.865 --> 00:03:28.965
and they will go until March 2023.

34
00:03:29.985 --> 00:03:30.805
There's reoccurring

35
00:03:31.185 --> 00:03:37.560
calendar teams invites that were sent out in May, and please continue to pass them along to anybody as needed.

36
00:03:38.040 --> 00:03:39.340
And if you have any,

37
00:03:40.120 --> 00:03:46.459
interesting topics you would like for us to cover, then just mention it to your, again, friendly community coach.

38
00:03:48.040 --> 00:03:48.860
All community

39
00:03:49.319 --> 00:03:52.380
of practice recordings can be found under resources,

40
00:03:53.525 --> 00:03:57.625
binding list, 10 steps to create and use a binding list.

41
00:03:59.845 --> 00:04:01.545
And at the bottom of the page,

42
00:04:02.245 --> 00:04:05.225
you will actually find links to the 2021

43
00:04:05.685 --> 00:04:07.305
community of practice series.

44
00:04:07.560 --> 00:04:12.860
And then directly under that, you will see new community of practice calls listed.

45
00:04:14.920 --> 00:04:20.460
This year as well, I'd like to remind everybody that we're adding 6 new prerecorded presentations,

46
00:04:20.839 --> 00:04:21.740
and we're updating

47
00:04:22.225 --> 00:04:23.765
10 of the previous presentations.

48
00:04:24.785 --> 00:04:26.645
So here's where we are today.

49
00:04:27.505 --> 00:04:28.485
We have 3

50
00:04:28.945 --> 00:04:32.085
new prerecorded webinars and 4 updated webinars.

51
00:04:32.305 --> 00:04:37.365
And more will be coming in Ali September, and all of them will be completed by the end of December.

52
00:04:37.660 --> 00:04:42.800
And, again, you can find those on our website under 10 steps to create and use a binding list.

53
00:04:44.380 --> 00:04:47.260
Here are our upcoming community of practice calls.

54
00:04:47.260 --> 00:04:51.840
In September, we are going to talk about improving data culture in your organization.

55
00:04:52.854 --> 00:04:55.275
October will be about indigenous participation

56
00:04:55.655 --> 00:04:58.875
and inclusion in binding lists. And then in November,

57
00:04:59.335 --> 00:05:07.275
we'll be talking about the data narrative, using data to inform resource and capacity responses, like winter warming centers and encampments.

58
00:05:09.320 --> 00:05:11.260
We really would like to celebrate,

59
00:05:12.520 --> 00:05:14.860
on today's call these communities

60
00:05:15.160 --> 00:05:15.660
that,

61
00:05:16.680 --> 00:05:18.940
the Canadian Alliance has confirmed

62
00:05:19.400 --> 00:05:22.460
for meeting their Ontario Binameless 2022

63
00:05:22.760 --> 00:05:23.260
requirements.

64
00:05:24.565 --> 00:05:26.665
So we're quite excited about that.

65
00:05:28.085 --> 00:05:31.544
Although service managers will confirm this with ministry

66
00:05:32.005 --> 00:05:35.865
separately through either the plan you submitted at the end of July

67
00:05:36.270 --> 00:05:38.770
or at the fiscal year end in April,

68
00:05:39.230 --> 00:05:43.889
we really welcome you to connect with your community coach to confirm that you've met these requirements

69
00:05:44.190 --> 00:05:44.930
as well.

70
00:05:45.230 --> 00:05:51.765
It's a really great opportunity to identify system strengths and improvement opportunities that your coach might be able to help you with.

71
00:05:53.285 --> 00:05:54.905
And more congratulations.

72
00:05:56.245 --> 00:06:01.945
We also wanna highlight those communities that we have confirmed a quality by name list with,

73
00:06:02.805 --> 00:06:06.640
using their by name list scorecard and tools, and they have submitted

74
00:06:07.020 --> 00:06:10.960
at least 3 months of reliable chronic BNL data.

75
00:06:11.260 --> 00:06:12.480
So a huge congratulations

76
00:06:12.860 --> 00:06:14.080
go out to these communities,

77
00:06:15.020 --> 00:06:17.120
including Lanark and York.

78
00:06:19.505 --> 00:06:20.245
And now,

79
00:06:20.625 --> 00:06:22.945
we'll get on to the business at hand today.

80
00:06:22.945 --> 00:06:30.805
So today's community of practice is gonna focus on what the homeless individuals and families information system, more affectionately

81
00:06:31.345 --> 00:06:32.640
known as HIFIS,

82
00:06:33.040 --> 00:06:38.100
is all about and how it can help communities with binding lists and coordinated access.

83
00:06:38.720 --> 00:06:42.500
So for communities on the call that are already working with HIFUS,

84
00:06:42.960 --> 00:06:51.725
this is probably not gonna be new information to you, but we really do encourage you to stay on the call and share your experience during the question answer time.

85
00:06:52.185 --> 00:06:55.385
We do have 2 HYFUS experts with us today.

86
00:06:55.385 --> 00:06:59.725
We have Britney Ali, senior program adviser with Infrastructure Canada,

87
00:07:00.190 --> 00:07:02.530
and Ali Ryder from ACRE Consulting.

88
00:07:03.470 --> 00:07:10.930
But, first, we wanna get some feedback to you before I hand it over to to them so we can tailor today's session towards

89
00:07:11.470 --> 00:07:13.250
who is on the call.

90
00:07:13.630 --> 00:07:14.130
So

91
00:07:14.505 --> 00:07:19.485
I really invite you to take out your mobile device and pull up Slido for some questions

92
00:07:20.025 --> 00:07:23.085
that can really help us narrow the focus today.

93
00:07:24.025 --> 00:07:26.365
So I'll give everybody a little bit of time,

94
00:07:26.825 --> 00:07:27.325
and

95
00:07:27.890 --> 00:07:29.190
you can access

96
00:07:30.130 --> 00:07:31.430
Slido by,

97
00:07:33.570 --> 00:07:36.230
by using the QR code or entering

98
00:07:36.610 --> 00:07:37.350
the hashtag.

99
00:07:39.490 --> 00:07:44.323
And the first question is, what is your current community involvement with HIFIS?

100
00:07:46.805 --> 00:07:51.305
So we're, like, 5050, not using HyFis, no plans, and then

101
00:07:52.965 --> 00:07:55.065
using HyFis in stage implementation.

102
00:08:06.449 --> 00:08:09.669
Alright. We've got some people fully using HIFUS.

103
00:08:14.855 --> 00:08:17.355
And then using HIFUS in staged implementation.

104
00:08:18.615 --> 00:08:19.115
Alright.

105
00:08:23.750 --> 00:08:26.890
That kinda gives us a good sense of who's in the audience.

106
00:08:33.510 --> 00:08:39.130
I'm gonna move on to the next question now about what is your personal knowledge level.

107
00:08:39.644 --> 00:08:41.985
So you don't even know what HIFUS means.

108
00:08:42.605 --> 00:08:47.985
No idea. You have a basic understanding, but you've never used it. You're a super user.

109
00:08:48.298 --> 00:08:49.824
ACRE would hire you.

110
00:08:55.010 --> 00:08:55.510
Alright.

111
00:08:57.170 --> 00:08:59.269
Wow. We have half of our users

112
00:09:00.130 --> 00:09:03.350
half of the people on the call using HIFIS on a regular basis.

113
00:09:05.649 --> 00:09:09.675
So we have a lot of people who are familiar with Hyphus on the call.

114
00:09:13.915 --> 00:09:15.055
We have 30%,

115
00:09:16.075 --> 00:09:16.575
27%

116
00:09:17.274 --> 00:09:17.774
that

117
00:09:18.154 --> 00:09:20.015
has no idea what HIFES means,

118
00:09:20.394 --> 00:09:20.894
and

119
00:09:21.274 --> 00:09:21.774
20%

120
00:09:22.075 --> 00:09:23.855
that has a basic understanding.

121
00:09:25.130 --> 00:09:26.510
And, Ali, with 6%

122
00:09:28.170 --> 00:09:31.710
of people you could HIFIS, so that might be good news for you.

123
00:09:34.170 --> 00:09:35.870
And just one last question,

124
00:09:36.250 --> 00:09:38.350
1 or 2 information tidbits

125
00:09:39.065 --> 00:09:42.365
about what you'd like to find out today. And, really,

126
00:09:42.745 --> 00:09:43.964
this is a free text,

127
00:09:44.904 --> 00:09:45.404
question.

128
00:09:45.625 --> 00:09:54.045
Really, we're just kind of looking for if we don't cover all points today, I can follow-up in an email and get the information out to you.

129
00:09:56.140 --> 00:09:56.640
So

130
00:09:57.980 --> 00:09:59.360
is Ali hiring?

131
00:10:00.700 --> 00:10:04.320
That's a great question. I'll leave that one to Ali's part of the conversation.

132
00:10:06.475 --> 00:10:11.215
And as those come up, I'll be able to monitor that. But in the interest of time,

133
00:10:12.075 --> 00:10:17.215
I am actually going to pass it over to Britney now to

134
00:10:17.595 --> 00:10:19.375
tell you a little bit about

135
00:10:19.735 --> 00:10:22.210
HIFIS from Where are you going, Ryder?

136
00:10:22.210 --> 00:10:23.590
Canada's point of view.

137
00:10:27.730 --> 00:10:33.190
Just a reminder that if if you're not on mute, please mute yourself unless you have a question.

138
00:10:34.529 --> 00:10:37.590
So alright. So I'll hand it over to you, Britney.

139
00:10:38.315 --> 00:10:40.015
Awesome. Thank you, Chantal.

140
00:10:40.875 --> 00:10:42.555
And good afternoon for everyone.

141
00:10:42.555 --> 00:10:48.095
I I might think I'm the only one well, actually, Melinda and I are the only ones in the morning still here, I believe.

142
00:10:49.435 --> 00:10:49.935
So

143
00:10:50.240 --> 00:10:54.339
I was asked today to speak about HIFIS and speak about,

144
00:10:54.800 --> 00:10:55.860
some of the overview

145
00:10:56.480 --> 00:10:58.420
of what it is, how it works,

146
00:10:58.959 --> 00:11:02.579
if there's interest to onboard, what does that process kind of start like?

147
00:11:03.199 --> 00:11:05.305
So if we can go to the first slide,

148
00:11:06.825 --> 00:11:07.565
it will

149
00:11:08.025 --> 00:11:10.365
walk us through a little bit of the agenda.

150
00:11:14.425 --> 00:11:15.725
Awesome. Thank you, Chantal.

151
00:11:16.345 --> 00:11:17.085
And so,

152
00:11:17.589 --> 00:11:21.290
again, as Chantelle said, this isn't intended to be a fully comprehensive conversation.

153
00:11:21.430 --> 00:11:23.690
It is supposed to be high level overview

154
00:11:24.470 --> 00:11:25.930
of what HIFIS is,

155
00:11:26.470 --> 00:11:28.649
a little bit about some of its functionality,

156
00:11:29.270 --> 00:11:38.334
and Ali will follow with a little bit more specifics around the, community experience of implementation and some, live examples of of how it gets used.

157
00:11:38.334 --> 00:11:40.915
So I'll start with some of the high level pieces

158
00:11:41.295 --> 00:11:46.035
around its evolution, some of its benefits, key features, data collection, etcetera,

159
00:11:46.680 --> 00:11:50.700
and then Ali will follow-up with some of the more specifics around community implementation.

160
00:11:52.760 --> 00:11:54.409
So what is HIFIS?

161
00:11:54.680 --> 00:11:56.380
It stands for homelessness

162
00:11:57.800 --> 00:12:03.055
sorry. It's a homelessness management information system. And so it really does help,

163
00:12:03.835 --> 00:12:04.815
its communities

164
00:12:05.115 --> 00:12:05.855
and individuals

165
00:12:06.395 --> 00:12:06.895
track

166
00:12:07.515 --> 00:12:17.240
information and collect information in a central space, not only to help coordinated access, but to help many other benefits, which we'll walk through in the next couple of slides.

167
00:12:18.180 --> 00:12:20.760
And why is it essential to coordinated access?

168
00:12:21.300 --> 00:12:23.320
It supports real time collection,

169
00:12:23.780 --> 00:12:24.920
meaning that individuals

170
00:12:25.220 --> 00:12:26.680
can log into a system

171
00:12:27.220 --> 00:12:31.800
and see in real time where or what services has been provided to an individual.

172
00:12:32.475 --> 00:12:35.375
It also supports triaging and prioritization

173
00:12:35.995 --> 00:12:36.815
of resources.

174
00:12:38.235 --> 00:12:41.055
It supports the reduction in administrative burden.

175
00:12:41.435 --> 00:12:47.690
So service providers can start update and share service plans when working with common individuals,

176
00:12:48.630 --> 00:12:51.690
and reports can be customized to meet various needs.

177
00:12:52.470 --> 00:12:58.570
It also helps generate data for core outcomes of reaching home, but also can support communities

178
00:12:59.030 --> 00:12:59.530
in

179
00:13:00.705 --> 00:13:05.605
creating reports to track for other funding requirements, let that be provincial, municipal,

180
00:13:06.225 --> 00:13:07.045
or even,

181
00:13:07.505 --> 00:13:08.805
fundraised dollars.

182
00:13:09.505 --> 00:13:12.485
There is that capacity within the system to customize

183
00:13:12.865 --> 00:13:13.845
what you're tracking

184
00:13:14.300 --> 00:13:16.879
so that you can then pull the reporting out for,

185
00:13:17.579 --> 00:13:18.800
those types of

186
00:13:19.500 --> 00:13:22.639
resources. Yeah. Next slide, please. Thank you.

187
00:13:23.819 --> 00:13:28.240
So just a little bit of the evolution of HIFIS. It's been around since 1999.

188
00:13:29.925 --> 00:13:32.425
And so for the until about 2006

189
00:13:32.805 --> 00:13:36.025
in HIFUS 3, it was based on a desktop

190
00:13:36.405 --> 00:13:41.065
application. So those old CD ROMs, loading it up into your computer,

191
00:13:42.085 --> 00:13:44.585
and there were a couple iterations of that.

192
00:13:45.240 --> 00:13:45.980
In 2015,

193
00:13:46.600 --> 00:13:48.460
it went to a web based application

194
00:13:49.080 --> 00:13:51.100
and came up to newer standards,

195
00:13:51.560 --> 00:13:55.420
and became a much more user friendly, much more configurable,

196
00:13:56.040 --> 00:13:59.175
and helped us shift towards coordinated access.

197
00:14:00.455 --> 00:14:01.355
In 2020

198
00:14:02.055 --> 00:14:06.875
oh, sorry. I was just going to speak a little bit about the more of the modules that were completed

199
00:14:07.255 --> 00:14:07.755
recently

200
00:14:08.295 --> 00:14:10.394
and offering a unique identifier

201
00:14:10.695 --> 00:14:13.800
list, or as we know it as a by name list.

202
00:14:14.500 --> 00:14:21.960
And we continue to create improvements within the system, not only in coordinated access module, but in other modules.

203
00:14:22.100 --> 00:14:22.600
And,

204
00:14:23.955 --> 00:14:28.535
upcoming in one of the new releases that are coming, so a little bit of a tidbit on what's to expect.

205
00:14:28.675 --> 00:14:31.895
There will be a lot more focus on outreach and diversion,

206
00:14:32.515 --> 00:14:35.255
and some new improvements in those modules as well.

207
00:14:37.235 --> 00:14:38.135
Thanks, Chantal.

208
00:14:39.160 --> 00:14:42.780
So I like to talk about HIFIS benefits in 3 different

209
00:14:43.160 --> 00:14:43.660
sections.

210
00:14:44.920 --> 00:14:45.420
Most

211
00:14:45.800 --> 00:14:46.300
importantly,

212
00:14:46.680 --> 00:14:49.580
it really does help with individuals' experiences.

213
00:14:50.600 --> 00:14:54.747
It helps eliminate the need to repeat their story during intake and assessment.

214
00:15:07.910 --> 00:15:10.170
To really help benefit those individuals,

215
00:15:10.710 --> 00:15:15.290
move through their experience of homelessness as quickly as possible and get the services that they need.

216
00:15:15.990 --> 00:15:19.050
Secondly, it does help with service providers and communities.

217
00:15:19.670 --> 00:15:21.290
And so as a service provider,

218
00:15:21.774 --> 00:15:23.795
you're able to log in and collaborate

219
00:15:24.255 --> 00:15:26.355
with all of your other community partners

220
00:15:27.055 --> 00:15:29.555
to support that individual through their journey.

221
00:15:30.175 --> 00:15:35.955
It helps collect the data, share it, and we can also report on those pieces to better understand

222
00:15:36.519 --> 00:15:39.500
the housing resources or the need for those resources,

223
00:15:40.360 --> 00:15:44.380
and the local state of, the homelessness in in your community.

224
00:15:45.240 --> 00:15:45.980
And finally,

225
00:15:46.920 --> 00:15:47.660
the broader

226
00:15:48.615 --> 00:15:50.075
homelessness serving sector,

227
00:15:51.175 --> 00:15:57.355
as stated, you are able to do your reporting for municipal, provincial, and federal requirements.

228
00:15:58.055 --> 00:15:59.915
And that information and collection

229
00:16:00.375 --> 00:16:04.380
really does help inform and advance research, supports policy development,

230
00:16:04.840 --> 00:16:07.500
and helps identify gaps within the sector.

231
00:16:12.280 --> 00:16:15.180
So there are many key features about HIFES,

232
00:16:16.064 --> 00:16:17.685
many of them listed here.

233
00:16:18.384 --> 00:16:24.084
What what I like to share when I think about HIFIS system is that it really does help

234
00:16:24.625 --> 00:16:31.529
understand an individual's journey from when they first start connecting with the homelessness sector to when they're stably housed.

235
00:16:31.910 --> 00:16:33.850
And there are different types of,

236
00:16:34.550 --> 00:16:35.050
modules

237
00:16:35.589 --> 00:16:36.649
that helps you

238
00:16:36.950 --> 00:16:40.089
support that process. So shelter admissions,

239
00:16:40.470 --> 00:16:41.610
goods and services

240
00:16:42.070 --> 00:16:42.570
tracking,

241
00:16:43.345 --> 00:16:44.725
any type of interaction,

242
00:16:45.505 --> 00:16:46.805
outreach, housing.

243
00:16:47.425 --> 00:16:48.245
There's several

244
00:16:48.625 --> 00:16:52.325
modules that help you with tracking that entire journey.

245
00:16:53.105 --> 00:16:56.805
And the fun part about the system is it is configurable

246
00:16:57.660 --> 00:17:00.720
As those types of services are not unique to a community,

247
00:17:01.180 --> 00:17:02.800
but the approach to those services,

248
00:17:03.260 --> 00:17:08.960
the partners that you might be partnering with, those things are very unique generally from community to community.

249
00:17:09.339 --> 00:17:11.839
And so you can configure each of those modules

250
00:17:12.355 --> 00:17:16.774
to have unique drop down menus or new service names or

251
00:17:17.154 --> 00:17:19.974
user rights that are different per community.

252
00:17:20.755 --> 00:17:22.694
This truly allows for your community

253
00:17:23.154 --> 00:17:25.494
to build a seamless service delivery model,

254
00:17:26.190 --> 00:17:30.450
and a unified service experience for those individuals who are experiencing homelessness.

255
00:17:35.789 --> 00:17:38.370
So what data gets collected in the system?

256
00:17:39.175 --> 00:17:41.515
That really depends on your community.

257
00:17:41.655 --> 00:17:48.555
So there's a lot of upfront work that goes into to understanding what data do you wanna collect and what data do you need to collect.

258
00:17:48.855 --> 00:17:54.075
And that has a different approach for communities. Many times, it's based on funding requirements.

259
00:17:54.960 --> 00:17:57.919
Also, there is just general service needs.

260
00:17:57.919 --> 00:18:00.980
What services are we providing and how do we collect that data?

261
00:18:01.520 --> 00:18:08.100
So as mentioned, HIFIS is extremely configurable, and it has 1,000 various data points that you can collect.

262
00:18:09.280 --> 00:18:18.634
When you would sign on to join HIFIS, there is a data provision agreement that gets signed between the HyFis lead, who would be the central lead for,

263
00:18:19.975 --> 00:18:20.794
for implementation,

264
00:18:21.654 --> 00:18:22.634
and INFC,

265
00:18:23.095 --> 00:18:24.235
Infrastructure Canada.

266
00:18:24.950 --> 00:18:27.130
And what that does is it allows us to,

267
00:18:27.910 --> 00:18:30.490
collect 38 non directly identifiable

268
00:18:30.790 --> 00:18:32.704
fields from HIFIS.

269
00:18:33.190 --> 00:18:36.170
And those get collected and submitted to automatically

270
00:18:36.790 --> 00:18:37.610
to INFC,

271
00:18:38.595 --> 00:18:42.054
and there's 38 of those fields that get anonymized and encrypted.

272
00:18:42.434 --> 00:18:47.495
And, there is a list there, and the link will work so you can look through them in more detail.

273
00:18:52.440 --> 00:18:57.420
So data sharing and data use. Each community has a HIFIS lead organization,

274
00:18:58.040 --> 00:19:00.060
and they are responsible for installing,

275
00:19:00.520 --> 00:19:03.900
configuring, and maintaining HIFUS for their local community.

276
00:19:04.360 --> 00:19:06.380
Or in some states in some

277
00:19:07.205 --> 00:19:09.065
areas, we have provincial installations,

278
00:19:10.325 --> 00:19:11.065
as well.

279
00:19:12.005 --> 00:19:18.665
And so each community does not see each other's information unless they would like that in one instance, like a provincial,

280
00:19:20.085 --> 00:19:20.585
install.

281
00:19:21.680 --> 00:19:22.340
And then,

282
00:19:22.800 --> 00:19:26.900
as mentioned, they get to choose how information gets shared

283
00:19:27.280 --> 00:19:31.460
within that community. There are different user rights, service provider rights,

284
00:19:32.080 --> 00:19:34.580
that you can set up in the back end configuration

285
00:19:35.040 --> 00:19:42.315
that you choose how data gets shared amongst community members and even amongst the user different user types that you can set up.

286
00:19:43.895 --> 00:19:47.115
Then, as mentioned again, 38 non directly identifiable

287
00:19:47.575 --> 00:19:49.275
fields get sent to INFC,

288
00:19:50.429 --> 00:19:54.210
and this supports research and analysis on homelessness in Canada

289
00:19:54.909 --> 00:19:58.929
and contributes to the evidence based policy and decision making and publications.

290
00:20:05.164 --> 00:20:10.205
So how is HIFIS implemented in the community? I think a lot of this I've kinda touched on.

291
00:20:10.445 --> 00:20:15.825
However, INFC develops HIFUS internally and provides a license to our community entities

292
00:20:16.445 --> 00:20:17.839
or those HIFIS

293
00:20:18.700 --> 00:20:22.480
leads to host and implement HIFUS locally within their community.

294
00:20:23.100 --> 00:20:28.159
And so we do have communities that are not funded by reaching home or by INFC

295
00:20:28.460 --> 00:20:30.159
that are utilizing HIFUS.

296
00:20:31.735 --> 00:20:35.595
We continue to maintain and update the system through series of releases.

297
00:20:35.975 --> 00:20:39.812
So there are 2 types of releases that we generally go through, minors and ACRE.

298
00:20:40.295 --> 00:20:44.059
And minor releases are bug fixes and and smaller feaks.

299
00:20:44.919 --> 00:20:46.940
And major releases are usually,

300
00:20:47.399 --> 00:20:49.980
big changes to modules or new implementations,

301
00:20:50.840 --> 00:20:51.980
that type of stuff.

302
00:20:53.399 --> 00:20:56.345
The community then is responsible for implementing and

303
00:20:56.945 --> 00:20:57.424
HIFIS

304
00:20:58.911 --> 00:20:59.231
HYPHIS based on the needs of their community and through community consultations.

305
00:20:59.231 --> 00:21:00.184
So the service provider CAEH,

306
00:21:01.284 --> 00:21:02.745
who needs access to what,

307
00:21:03.205 --> 00:21:04.825
including planning, needs assessments,

308
00:21:05.125 --> 00:21:05.865
designing how

309
00:21:06.325 --> 00:21:09.304
that will work within the confines of HYPHIS,

310
00:21:11.419 --> 00:21:12.240
how it works.

311
00:21:13.020 --> 00:21:19.440
And so we give the shell and those modules, and it really is based on the community's need for workflow development,

312
00:21:20.539 --> 00:21:23.360
to to build out what they would like from it.

313
00:21:28.685 --> 00:21:31.185
And then a little bit more detail just around,

314
00:21:32.045 --> 00:21:38.625
data protection and security, a very hot topic always around how do we ensure information is secure and safe

315
00:21:39.470 --> 00:21:41.010
for this vulnerable population.

316
00:21:42.110 --> 00:21:45.730
So on the left hand side, it talks about the roles of communities

317
00:21:46.030 --> 00:21:47.650
and really ensuring that

318
00:21:48.430 --> 00:21:52.130
information gets protected. And on the right hand side, it speaks to what HIFIS offers

319
00:21:52.455 --> 00:21:54.955
from a data protection and data security perspective.

320
00:21:55.975 --> 00:21:59.434
And so I'll start on the right hand side on what HIFUS provides,

321
00:21:59.975 --> 00:22:01.274
provides the configurable

322
00:22:01.575 --> 00:22:05.434
access and viewing rights. But it really is up to the community

323
00:22:05.735 --> 00:22:07.595
to define those roles and responsibilities,

324
00:22:08.480 --> 00:22:14.020
those user access rights, and those standards, policies, and procedures as each community

325
00:22:14.560 --> 00:22:19.220
is unique in its relationships with its community members, in its relationships

326
00:22:19.760 --> 00:22:21.780
even with the laws and practices,

327
00:22:22.400 --> 00:22:23.540
within their provinces.

328
00:22:25.093 --> 00:22:30.774
HIFIS offers the activity log and audit logs. There's a integrated help center

329
00:22:31.394 --> 00:22:32.534
that offers encrypted

330
00:22:32.995 --> 00:22:34.054
data exports.

331
00:22:34.995 --> 00:22:36.135
Again, those configurations,

332
00:22:37.870 --> 00:22:41.070
and user rights flexibilities and ability to be clustered.

333
00:22:41.070 --> 00:22:44.610
So ability to segregate data in different ways.

334
00:22:45.550 --> 00:22:53.585
And then on the left hand side, a couple additional components that are important that are needed from the community to ensure that data protection security is upheld,

335
00:22:54.765 --> 00:22:58.705
not only just on the governance aspect and the operations aspects,

336
00:22:59.085 --> 00:23:00.225
but in an IT,

337
00:23:00.765 --> 00:23:04.865
as this an IT platform, it really is to ensure that there's a secure server,

338
00:23:05.325 --> 00:23:06.304
local encryptions

339
00:23:06.605 --> 00:23:07.505
and firewalls,

340
00:23:09.010 --> 00:23:15.110
and that backups and safeguards are in place, and that there's expertise there for a community to be able to,

341
00:23:15.570 --> 00:23:19.510
troubleshoot or do audits to ensure that those pieces are upheld.

342
00:23:22.055 --> 00:23:22.555
So

343
00:23:23.175 --> 00:23:27.355
I will I think that was my last slide, Chantal, if I remember correctly.

344
00:23:31.015 --> 00:23:34.955
Yes. It was. So thank you very much for that,

345
00:23:37.820 --> 00:23:41.600
Britney. And, yeah, now I guess we'll hand it over

346
00:23:42.380 --> 00:23:44.065
to Ali with ACRE Consulting.

347
00:23:45.820 --> 00:23:54.025
Ali, again, is gonna review how HIFIS can help communities with priority, coordinated access, data completeness, completeness, and potential implementation

348
00:23:54.405 --> 00:23:54.905
planning,

349
00:23:55.365 --> 00:23:57.065
pretty much how it rolls out

350
00:23:57.365 --> 00:23:58.184
in communities.

351
00:23:58.485 --> 00:24:00.845
So I'm gonna hand it over to Ali.

352
00:24:01.365 --> 00:24:02.345
Thanks, Chantal.

353
00:24:03.045 --> 00:24:06.060
I can't remember what my first slide is, so you should probably just

354
00:24:06.620 --> 00:24:08.640
okay. That one's kinda boring.

355
00:24:09.420 --> 00:24:10.640
There we go. Cool.

356
00:24:11.020 --> 00:24:13.260
So thank you so much, Britney, for,

357
00:24:14.300 --> 00:24:16.240
giving us a big overview of the software.

358
00:24:17.260 --> 00:24:20.080
It was really great for those new communities.

359
00:24:20.865 --> 00:24:25.365
What I wanna talk about a little bit is how does this all relate to coordinated access?

360
00:24:25.745 --> 00:24:26.945
So a question that,

361
00:24:27.905 --> 00:24:33.425
I think a lot of communities maybe struggle with is, like, what's the difference between the binding list and the HIFIS?

362
00:24:33.425 --> 00:24:35.685
Like, how do those go together? How do they

363
00:24:36.460 --> 00:24:39.519
work together to make a coordinated access system?

364
00:24:39.659 --> 00:24:44.080
So first of all, HIFUS is just one ingredient in the coordinated access system.

365
00:24:44.460 --> 00:24:44.960
But

366
00:24:45.580 --> 00:24:51.039
if you think about it in the terms of the coordinated access sort of

367
00:24:52.165 --> 00:24:53.225
broadly speaking,

368
00:24:53.925 --> 00:24:58.439
then what you're going to see when your community is using HIFIS

369
00:24:58.725 --> 00:25:00.505
is that all of your

370
00:25:00.965 --> 00:25:01.465
community's

371
00:25:02.325 --> 00:25:07.169
access points, so drop in centers, emergency shelters, anywhere that a person might first

372
00:25:09.490 --> 00:25:12.390
person who is homeless might first encounter the system.

373
00:25:13.649 --> 00:25:16.649
So all access points are using HIFIS.

374
00:25:17.745 --> 00:25:24.225
And if you get to a point as a community that everyone who is or was homeless has a record in HIFUS.

375
00:25:24.225 --> 00:25:27.845
So, basically, if you're using the software across the system,

376
00:25:28.785 --> 00:25:33.830
then HIFUS makes a lot of your coordinated access system work,

377
00:25:34.610 --> 00:25:35.110
very

378
00:25:35.809 --> 00:25:40.710
much more streamlined and a lot easier to manage because all the data is in the same place.

379
00:25:41.010 --> 00:25:46.545
So one thing that HIFUS does is it'll calculate how long everyone has been homeless for.

380
00:25:46.845 --> 00:25:50.145
It calculates the first date that a client becomes homeless.

381
00:25:50.765 --> 00:25:55.345
And so it becomes a lot easier for you to look at your system level data,

382
00:25:56.900 --> 00:26:01.960
through BUILT for 0 and through a lot of other reporting requirements these days, including,

383
00:26:02.900 --> 00:26:04.200
the new Ontario,

384
00:26:06.179 --> 00:26:08.360
HPP program and the

385
00:26:10.375 --> 00:26:10.875
federal,

386
00:26:11.815 --> 00:26:13.275
community homeless response,

387
00:26:13.895 --> 00:26:15.195
yeah, CHR report.

388
00:26:16.294 --> 00:26:22.794
So there's a lot of reporting requirements out there now that require you to identify who is new to homelessness.

389
00:26:23.620 --> 00:26:27.399
And so if you're simply using HIFIS across the the community,

390
00:26:28.100 --> 00:26:32.279
then all you need to do is just look up to see which of the files were new.

391
00:26:32.500 --> 00:26:34.919
And so there's reports that can help you

392
00:26:35.220 --> 00:26:36.840
calculate that and

393
00:26:37.205 --> 00:26:38.265
avoid duplicating

394
00:26:38.565 --> 00:26:38.965
clients.

395
00:26:38.965 --> 00:26:45.925
Because if you just need to ask every service provider individually how many people were new, then you might be double counting people.

396
00:26:45.925 --> 00:26:53.519
But if you're putting all of your clients in a central database, then all you have to do is just run a report, and it'll tell you how many new clients

397
00:26:53.980 --> 00:26:56.399
were experiencing homelessness in a period,

398
00:26:56.779 --> 00:27:00.080
well, over over a month or over past year.

399
00:27:01.419 --> 00:27:03.425
You can also use it to,

400
00:27:04.084 --> 00:27:07.365
HIFIS can tell you who is close to becoming chronically homeless.

401
00:27:07.745 --> 00:27:20.970
So if that's part of your coordinated access process, you want to avoid people becoming chronically homeless, and you can get a list of who is going to become chronically homeless soon, and we'll see what we can do before they get to that point.

402
00:27:21.350 --> 00:27:22.250
You can also,

403
00:27:23.190 --> 00:27:26.090
identify who recently became chronically homeless.

404
00:27:26.390 --> 00:27:31.690
Perhaps that tips a point in your system where they become eligible for certain services.

405
00:27:33.425 --> 00:27:35.525
Alright. Next slide, please, Chantal.

406
00:27:36.225 --> 00:27:38.565
Now once you've identified who is,

407
00:27:39.665 --> 00:27:40.165
homeless,

408
00:27:41.905 --> 00:27:42.405
then

409
00:27:42.917 --> 00:27:43.777
HIFIS

410
00:27:43.905 --> 00:27:44.405
now

411
00:27:44.945 --> 00:27:50.770
knows a a master list of basically everyone who is experiencing homelessness now in your community.

412
00:27:51.950 --> 00:27:56.130
And there is this coordinated access module that Britney,

413
00:27:56.669 --> 00:27:57.890
was speaking about,

414
00:27:58.429 --> 00:27:59.570
and it generates

415
00:28:00.315 --> 00:28:05.934
a list of everyone who is homeless and everyone who is actively receiving services.

416
00:28:06.475 --> 00:28:07.934
And you can use this information

417
00:28:08.395 --> 00:28:09.215
to essentially

418
00:28:09.515 --> 00:28:13.695
prioritize and determine who your highest priority clients are.

419
00:28:14.260 --> 00:28:19.960
Now this is just a little animated screenshot that's showing the coordinated access module

420
00:28:20.420 --> 00:28:22.280
and some of the filtering options.

421
00:28:22.740 --> 00:28:24.840
But one of the things that a lot of communities

422
00:28:25.140 --> 00:28:25.640
do

423
00:28:26.020 --> 00:28:29.320
when they get to a little bit more of an advanced stage

424
00:28:29.775 --> 00:28:34.115
is they use this as a framework, but then might develop their own custom reports

425
00:28:34.495 --> 00:28:39.235
that further customizes the columns that they might want to use for prioritization

426
00:28:39.535 --> 00:28:40.035
purposes.

427
00:28:40.415 --> 00:28:42.180
Chantal, can you go to the next one, please?

428
00:28:43.940 --> 00:28:48.600
So one thing that I do want to be clear about, in terms of HIFIS' capabilities

429
00:28:49.380 --> 00:28:51.640
is HIFUS does not do resource

430
00:28:51.940 --> 00:28:52.440
matching.

431
00:28:52.900 --> 00:28:58.155
So it doesn't say, hey. There's a unit available here. This client should go in it.

432
00:28:58.315 --> 00:28:59.855
Click the button and it happens.

433
00:29:01.155 --> 00:29:07.055
Instead, you can just think about HIFIS as a database that contains all the information that you need

434
00:29:07.435 --> 00:29:08.495
to do your own,

435
00:29:09.195 --> 00:29:16.070
resource matching and decision making about which client you should prioritize for which housing unit or which

436
00:29:16.370 --> 00:29:16.870
caseworker.

437
00:29:17.889 --> 00:29:22.389
So what HIFIS would do in the real world, this is how communities are using it,

438
00:29:22.850 --> 00:29:26.309
you could use HIFUS to generate a list of available resources.

439
00:29:26.495 --> 00:29:31.315
For example, you could run a report that says, what are the caseloads of all my caseworkers?

440
00:29:31.695 --> 00:29:35.935
And, oh, I guess there's space on Chantelle's caseload. Picking on you, Chantelle.

441
00:29:35.935 --> 00:29:37.395
You've been slacking a bit.

442
00:29:39.720 --> 00:29:40.700
And then

443
00:29:41.080 --> 00:29:47.574
that you might notice that some housing units are are going to be vacant soon or have just become ACRE.

444
00:29:47.720 --> 00:29:50.220
So you can generate a list of available resources.

445
00:29:51.240 --> 00:29:53.980
And then you can generate a list of,

446
00:29:54.285 --> 00:29:57.265
I'm calling it likely clients, so potential

447
00:29:57.645 --> 00:30:01.665
high priority clients, maybe a list of people who are chronically homeless.

448
00:30:02.045 --> 00:30:10.170
And if perhaps this unit is only available for, say, veterans, then you can filter the list to just show chronically homeless veterans.

449
00:30:10.630 --> 00:30:12.650
And if your community has other prioritization

450
00:30:12.950 --> 00:30:14.730
criteria that you also use

451
00:30:15.030 --> 00:30:21.770
to determine which client should get that unit, then HIFIS can also provide you with that information.

452
00:30:21.830 --> 00:30:23.450
And you can narrow this down

453
00:30:23.815 --> 00:30:30.075
therefore, to a list of a couple likely clients who could be considered for the available resource.

454
00:30:30.535 --> 00:30:33.355
And then as a community, you'll sit down and say, hey.

455
00:30:33.895 --> 00:30:35.195
Should we give it to

456
00:30:36.470 --> 00:30:40.090
Britney, or should we give it to Kat? Like, they both are really

457
00:30:40.470 --> 00:30:41.290
high needs.

458
00:30:43.590 --> 00:30:48.090
Okay. So that's what kind of communities do using HYPHUS data.

459
00:30:48.870 --> 00:30:51.705
HYPHUS does not magically make your system,

460
00:30:52.085 --> 00:30:54.664
like, assign housing resources to people,

461
00:30:55.284 --> 00:30:56.965
but it provides you with the data.

462
00:30:56.965 --> 00:31:00.825
It's a central database that lets you keep track of all those things.

463
00:31:01.605 --> 00:31:02.105
So

464
00:31:02.640 --> 00:31:11.220
another data point that you're going to be required to report on for various provincial, federal, and bill for 0 things is how many,

465
00:31:12.000 --> 00:31:12.500
clients

466
00:31:12.960 --> 00:31:17.220
had a move in, how many homeless clients moved in to housing

467
00:31:17.665 --> 00:31:18.725
and ended their,

468
00:31:19.425 --> 00:31:20.485
episode of homelessness,

469
00:31:21.585 --> 00:31:22.965
in a period of time.

470
00:31:23.185 --> 00:31:28.125
So, again, if you get to the point where all of your housing programs are using HIFIS,

471
00:31:28.385 --> 00:31:32.725
then the move ins are captured simply by updating a client's housing status.

472
00:31:32.890 --> 00:31:34.990
And, again, you don't need to,

473
00:31:35.770 --> 00:31:38.190
do your work and then email somebody

474
00:31:38.490 --> 00:31:42.590
because they need to compile it on a spreadsheet to say that there was a move in this month.

475
00:31:42.890 --> 00:31:44.590
You would just use HIFUS

476
00:31:44.985 --> 00:31:46.365
not only for

477
00:31:46.825 --> 00:31:50.285
data entry, but also you can record your case notes and so on.

478
00:31:50.345 --> 00:31:52.765
And then it's just this one big store of information.

479
00:31:53.065 --> 00:31:57.005
So you can generate reports that'll tell you who moved into housing this month,

480
00:31:57.550 --> 00:32:01.090
who housed the client by caseworker or by organization,

481
00:32:01.950 --> 00:32:06.530
where did they move into, like, by address, by region, or by housing type,

482
00:32:06.910 --> 00:32:11.330
and you can measure how long they were homeless for before becoming housed.

483
00:32:14.845 --> 00:32:16.465
Go ahead to the next slide, please.

484
00:32:19.485 --> 00:32:24.065
So another feature of HIFIS that makes it a lot more smooth

485
00:32:24.409 --> 00:32:30.510
for your coordinated access is the inactivity piece. So, generally, you want to have,

486
00:32:31.450 --> 00:32:31.950
clients

487
00:32:32.250 --> 00:32:34.269
on your buy name list, on your prioritization

488
00:32:34.570 --> 00:32:37.470
list who are currently active. You've seen them recently.

489
00:32:37.529 --> 00:32:40.804
You know that they're around, and if you offer them a housing unit tomorrow,

490
00:32:41.184 --> 00:32:43.924
you'd be able to find them and offer them the housing unit.

491
00:32:44.784 --> 00:32:45.284
So

492
00:32:45.585 --> 00:32:46.405
most communities,

493
00:32:47.025 --> 00:32:49.365
are expected to have an inactivity policy.

494
00:32:50.304 --> 00:32:59.100
And if you're not using a central database like HIFIS, it's actually fairly difficult to implement that because you only have each person's narrow perspective.

495
00:32:59.560 --> 00:33:02.380
I haven't seen this client in a while. They must be inactive.

496
00:33:02.840 --> 00:33:04.220
But if we're not,

497
00:33:04.920 --> 00:33:10.125
sharing information, then I might not know that they went to some other service provider recently.

498
00:33:10.745 --> 00:33:15.565
So if your whole system is using Hyphasis, then Hyphasis tells system wide

499
00:33:16.025 --> 00:33:21.085
the last time that anyone has encountered a particular client, and then clients are automatically

500
00:33:21.465 --> 00:33:25.190
moved to inactive. You no longer have to do manual status updates.

501
00:33:25.490 --> 00:33:32.070
And, again, you can report off of things like who moved to inactive this month, which clients are about to come become inactive,

502
00:33:32.770 --> 00:33:36.390
and who is returning from a period of inactivity.

503
00:33:42.345 --> 00:33:42.425
Next please.

504
00:33:42.425 --> 00:33:51.965
And again, because HIFIS now has a lot of data in it, we can also detect patterns like who was homeless, then housed, then returned to homelessness.

505
00:33:52.370 --> 00:33:56.790
I'll skip the rest of the slide because it's kind of redundant. I already talked about it.

506
00:33:58.450 --> 00:33:58.950
Okay.

507
00:33:59.650 --> 00:34:04.950
So the next thing that I wanted to talk to you a little bit about is how to make all of this happen.

508
00:34:05.465 --> 00:34:08.045
So Chantelle has some resources

509
00:34:08.505 --> 00:34:15.545
on the slide at the end here, and one of the slides or one of the resources is a webinar that I delivered not too long ago.

510
00:34:15.545 --> 00:34:17.005
It's called the road to Hyphasis.

511
00:34:17.340 --> 00:34:20.719
So if your community is considering launching with Hyphasis,

512
00:34:21.020 --> 00:34:26.480
you can watch prerecorded webinar where I talk about all the different steps that you would need to go through.

513
00:34:28.060 --> 00:34:29.420
But I just wanted to talk,

514
00:34:30.315 --> 00:34:35.775
today a little bit about how to implement the the, like, last step. How would you do it?

515
00:34:36.315 --> 00:34:40.574
We we want it. We've tested it. We just don't quite know how to make it happen.

516
00:34:41.275 --> 00:34:44.014
So in terms of launch strategies,

517
00:34:45.179 --> 00:34:46.079
there's a couple

518
00:34:46.780 --> 00:34:47.679
key options.

519
00:34:48.139 --> 00:34:49.760
The first one is called the

520
00:34:50.060 --> 00:34:50.880
the plunge,

521
00:34:51.659 --> 00:34:56.219
or sometimes it's referred to as a big bang. You're just ripping off the band aid.

522
00:34:56.219 --> 00:35:02.225
And so you have your system set up, HIFUS is installed, and you just tell all of your service providers, okay.

523
00:35:02.605 --> 00:35:05.345
On Monday morning at 9 AM, we're all using HIFUS

524
00:35:06.205 --> 00:35:07.745
and not looking back ever.

525
00:35:08.445 --> 00:35:09.505
It's very exciting.

526
00:35:09.880 --> 00:35:16.760
It's the fastest way to implement, but, of course, the road is a bit rocky as you might understand with lots of change happening in one time.

527
00:35:16.760 --> 00:35:18.220
But you can do

528
00:35:23.160 --> 00:35:27.005
of, you know, people focusing on it right in a condensed period of time.

529
00:35:27.704 --> 00:35:30.285
So a really common way that communities do,

530
00:35:30.665 --> 00:35:33.005
their implementation is a phased implementation,

531
00:35:33.704 --> 00:35:37.565
which is to say something like, we're gonna launch our shelters in September,

532
00:35:38.060 --> 00:35:42.000
and then we're gonna launch the rest of our programs a couple months later in November.

533
00:35:42.300 --> 00:35:43.920
So you can do a bit staggered,

534
00:35:44.700 --> 00:35:48.080
and, this is a little bit easier on the logistics.

535
00:35:48.460 --> 00:35:49.840
For example, you could,

536
00:35:50.540 --> 00:35:53.200
you don't have to train as many people at the same time,

537
00:35:53.625 --> 00:35:59.165
and it's not quite as much turnover all at the same time or change at the same time.

538
00:35:59.465 --> 00:36:03.725
It's a little bit easier to manage that way, but it does draw out the implementation process.

539
00:36:04.825 --> 00:36:07.065
Another thing that you can do is do a pilot launch.

540
00:36:07.065 --> 00:36:11.869
So if you have one service provider or one program that's super keen, you can say like, hey.

541
00:36:11.869 --> 00:36:16.770
Why don't you guys try out using HIFIS for your real world day to day work,

542
00:36:17.630 --> 00:36:20.930
and we'll kind of figure it out as we go. You'll be our guinea pigs.

543
00:36:21.945 --> 00:36:26.365
And once we have the kinks figured out, then we'll start to onboard other providers.

544
00:36:27.145 --> 00:36:28.765
So that's a pilot implementation.

545
00:36:30.025 --> 00:36:35.645
And then the last option, which is you usually very unpopular is something called a parallel launch.

546
00:36:36.090 --> 00:36:39.790
So you launch HIFIS, and you also keep doing the old thing,

547
00:36:41.130 --> 00:36:42.510
for a period of time.

548
00:36:43.130 --> 00:36:46.670
So everyone's double entering things for a few months.

549
00:36:47.290 --> 00:36:51.710
And you do that until you get to the point where you're confident that the new system is working

550
00:36:52.224 --> 00:36:54.085
as expected and people are really,

551
00:36:55.185 --> 00:36:56.484
ready to fully commit.

552
00:36:56.785 --> 00:36:58.244
This one, nobody likes,

553
00:36:59.025 --> 00:37:00.885
but it is the most, like,

554
00:37:02.305 --> 00:37:04.865
safe, I guess, because you're not losing any data.

555
00:37:04.865 --> 00:37:11.030
And if something goes wrong, you have the backup plan, but it can really drag things on, and it's not a very popular option.

556
00:37:12.609 --> 00:37:16.790
If you can go ahead to the next I think you might need to skip 2 slides. Yep.

557
00:37:17.569 --> 00:37:21.109
Okay. So the last this is my last slide.

558
00:37:21.575 --> 00:37:25.035
It's alright. Cool. We're gonna do a plunge

559
00:37:25.735 --> 00:37:28.455
implementation. We're gonna do it tomorrow. It's gonna be great.

560
00:37:28.455 --> 00:37:32.115
And then next week, we're gonna have live data from HIFIS.

561
00:37:32.135 --> 00:37:35.310
Our buy name list is gonna be done, and we're all gonna be perfect. Right?

562
00:37:36.270 --> 00:37:37.970
Well, that might be an

563
00:37:38.270 --> 00:37:38.770
unrealistic,

564
00:37:39.950 --> 00:37:40.450
expectation.

565
00:37:41.230 --> 00:37:45.570
And so I just wanted to highlight to make sure that you were,

566
00:37:46.030 --> 00:37:46.530
aware

567
00:37:46.910 --> 00:37:50.450
that when you first launch with Hyphasis, you're not gonna have good data quality.

568
00:37:50.675 --> 00:37:55.015
So there's a couple of reasons for that. One is simply the number of hours in the day.

569
00:37:55.555 --> 00:37:57.575
So even if it takes, like, say,

570
00:37:58.035 --> 00:37:58.775
10 minutes

571
00:37:59.234 --> 00:38:00.055
per client

572
00:38:00.595 --> 00:38:07.100
to update their file, you know, if you have a 100 clients that you might want to put into HIFUS on day

573
00:38:07.400 --> 00:38:08.860
1, the it adds up.

574
00:38:09.080 --> 00:38:16.860
And that is time that's being taken away from whatever your the rest of your frontline staff actually need to do, like, actually help people.

575
00:38:17.560 --> 00:38:20.780
So generally speaking on at the beginning,

576
00:38:22.085 --> 00:38:36.964
there's gonna be not very much data that has been entered into Hyphasis yet, which means that all the cool features that I told you about, being able to run a report that tells you who's moving to inactive and who's about to become chronically homeless, you won't be able to be there because,

577
00:38:37.740 --> 00:38:40.480
there's just gonna be too many blanks in your database.

578
00:38:40.780 --> 00:38:43.600
So it takes time to get to data quality.

579
00:38:44.700 --> 00:38:45.200
So

580
00:38:46.220 --> 00:38:48.400
one thing that you may want to consider

581
00:38:48.860 --> 00:38:49.900
if you are,

582
00:38:50.220 --> 00:38:54.445
planning to launch with HIFIS and move your binding list

583
00:38:54.745 --> 00:38:55.485
to HIFUS

584
00:38:56.265 --> 00:38:59.165
is to maintain a separate binding list in an Excel document

585
00:38:59.625 --> 00:39:01.085
for a limited time.

586
00:39:01.385 --> 00:39:05.805
So that's the parallel launch that I was just talking about on a previous slide.

587
00:39:06.420 --> 00:39:08.920
I know it's not a popular option,

588
00:39:09.460 --> 00:39:13.560
but you can use it as kind of an incentive to say, hey.

589
00:39:13.940 --> 00:39:21.640
Once we get good data in HIFIS, then we can delete this Excel spreadsheet and not have to do manual updates anymore.

590
00:39:22.335 --> 00:39:24.515
So that could be a good strategy for you.

591
00:39:25.775 --> 00:39:28.755
And then the other thing that I just wanted to mention

592
00:39:29.055 --> 00:39:29.555
about

593
00:39:30.015 --> 00:39:35.315
reasons why you might not have good data quality to begin with, besides a lack of time,

594
00:39:35.700 --> 00:39:36.920
it does take some,

595
00:39:37.380 --> 00:39:39.780
yeah, the lack of time to actually do the data entry.

596
00:39:39.780 --> 00:39:43.800
It does take some time for staff to become familiar with the changing processes.

597
00:39:44.580 --> 00:39:45.080
So,

598
00:39:46.500 --> 00:39:47.480
I would say

599
00:39:47.859 --> 00:39:48.359
that

600
00:39:49.235 --> 00:39:49.735
probably

601
00:39:50.435 --> 00:39:52.135
3 months post implementation

602
00:39:52.595 --> 00:39:54.295
is about the fastest

603
00:39:54.675 --> 00:39:57.415
that you could probably get to a point where

604
00:39:57.715 --> 00:40:01.015
you think, hey. We have pretty good data quality now.

605
00:40:01.500 --> 00:40:08.560
Some communities, it might take 6 months or a year even depending on the size of their system and what's going on,

606
00:40:09.020 --> 00:40:13.520
and the resources that are available. Here's a hint. If you have the resources,

607
00:40:13.965 --> 00:40:19.025
you could hire a summer student to do a lot of data entry for you, and that can make things faster.

608
00:40:20.045 --> 00:40:24.385
I think that's the end of my slides, Chantal, so I'm gonna hand it right back to you.

609
00:40:25.005 --> 00:40:27.425
Awesome. Thanks, Ali. That was great.

610
00:40:28.450 --> 00:40:31.270
I'm just gonna put some resources here. Ali

611
00:40:31.570 --> 00:40:33.897
mentioned one of them, the road to HIFIS,

612
00:40:34.130 --> 00:40:37.510
which was a webinar that Ali did in November 2021.

613
00:40:38.610 --> 00:40:42.710
And that kind of covers the whole gamut from start to to finish.

614
00:40:43.155 --> 00:40:45.815
There's also some great resources here.

615
00:40:46.355 --> 00:40:49.495
There's the HIFIS Infrastructure Canada website,

616
00:40:50.595 --> 00:40:54.615
the HyFis demo site, how to sign up for the reaching home newsletter.

617
00:40:55.170 --> 00:41:03.190
Even if you're you're not a funded reaching home community, there's still lots of great information and tidbits in that newsletter.

618
00:41:04.530 --> 00:41:11.475
The homelessness learning hub has a whole HIFIS toolkit, and then there's a HYFUS readiness checklist as well.

619
00:41:11.535 --> 00:41:19.315
And that checklist is great for communities to kinda assess, you know, where what you need to do in order to prepare

620
00:41:19.695 --> 00:41:20.755
to get HYFUS.

621
00:41:21.330 --> 00:41:25.830
And then, of course, there's the HIFUS client support center and contact number

622
00:41:26.130 --> 00:41:26.630
and

623
00:41:27.105 --> 00:41:31.910
Ali website that is chock full of HIFUS support resources.

624
00:41:33.010 --> 00:41:33.510
So

625
00:41:34.494 --> 00:41:36.115
anybody have any questions

626
00:41:36.815 --> 00:41:37.315
for

627
00:41:37.615 --> 00:41:38.115
Britney

628
00:41:38.415 --> 00:41:39.575
or Ali?

629
00:41:40.335 --> 00:41:43.715
Now is your time to get all of those questions answered.

630
00:41:44.734 --> 00:41:49.650
We also have Dufferin, Brantford, and Waterloo, I believe, on the call.

631
00:41:49.710 --> 00:41:53.730
CK had to leave, Chad and Kent. But Dufferin, Brantford, and Waterloo,

632
00:41:55.150 --> 00:41:59.810
are pretty much experts in HIFIS. They've been using hyphist for some time.

633
00:42:05.895 --> 00:42:09.435
Any questions? Feel free to take yourself off chat or

634
00:42:09.735 --> 00:42:11.435
raise your hand or,

635
00:42:12.620 --> 00:42:13.440
type your question

636
00:42:14.220 --> 00:42:15.120
in the chat.

637
00:42:16.700 --> 00:42:21.040
One thing that wasn't covered, and I don't know who wants to kinda address this one,

638
00:42:21.740 --> 00:42:27.040
but the cost of HIFIS. And maybe if we could talk a little bit about that.

639
00:42:28.625 --> 00:42:34.165
I'm happy to start, and then, Ali, if you wanna jump in with some of the examples that you've seen.

640
00:42:35.744 --> 00:42:36.484
And so

641
00:42:37.505 --> 00:42:40.885
so the cost of the software itself is free. So,

642
00:42:41.744 --> 00:42:42.244
infrastructure

643
00:42:42.625 --> 00:42:43.125
provides

644
00:42:44.680 --> 00:42:47.020
the the software for free to communities.

645
00:42:47.880 --> 00:42:51.980
Now as as I kinda walked through, there are some operational

646
00:42:52.440 --> 00:42:53.260
and technical

647
00:42:53.560 --> 00:42:54.060
requirements

648
00:42:54.440 --> 00:42:54.940
that

649
00:42:55.320 --> 00:42:59.260
are asked by the communities to uphold to ensure Hyphasis is, successful.

650
00:42:59.945 --> 00:43:02.845
And so there are costs in regards to the server,

651
00:43:03.305 --> 00:43:04.605
in regards to,

652
00:43:05.065 --> 00:43:09.565
just maintaining the technical aspects of it, and then also the operations.

653
00:43:09.625 --> 00:43:14.045
So that would be, you know, a HIFUS lead, perhaps a reporting requirement,

654
00:43:14.425 --> 00:43:15.485
a data specialist,

655
00:43:16.240 --> 00:43:17.380
a support individual.

656
00:43:18.080 --> 00:43:25.540
Those are costs that ACRE are asked of the community to ensure ACRE in place to to ensure that the software is is

657
00:43:25.840 --> 00:43:27.780
maintained well within your community.

658
00:43:33.675 --> 00:43:35.855
Thanks, Britney. Ali, did you wanna

659
00:43:36.155 --> 00:43:43.695
discuss at all some of the training packages that you have or some of the supports that you offer and maybe what the range is in price there?

660
00:43:44.510 --> 00:43:48.369
I mean, if you're letting me advertise for myself,

661
00:43:48.670 --> 00:43:50.690
then I'm not gonna decline, but

662
00:43:51.150 --> 00:43:56.210
I feel a little awkward about that. Okay. So I am a consultant,

663
00:43:56.589 --> 00:43:59.325
and I will help you implement your HIFIS

664
00:44:00.285 --> 00:44:01.825
for some price tag.

665
00:44:02.125 --> 00:44:05.585
One of the things that I offer is the HIFUS for implementation

666
00:44:05.964 --> 00:44:06.785
master class,

667
00:44:07.325 --> 00:44:08.785
which is like a 6 month,

668
00:44:09.405 --> 00:44:10.224
kind of

669
00:44:10.925 --> 00:44:11.425
hybrid

670
00:44:12.030 --> 00:44:16.370
online course with some coaching that'll help you take all the steps that you need.

671
00:44:18.510 --> 00:44:20.130
The cost for that

672
00:44:20.510 --> 00:44:21.010
ranges

673
00:44:21.470 --> 00:44:22.770
between, I think, $610,000

674
00:44:23.790 --> 00:44:24.930
depending on how,

675
00:44:25.630 --> 00:44:30.724
much support that you want. But that being said, you don't have to go with me.

676
00:44:30.724 --> 00:44:32.505
You can do stuff on your own.

677
00:44:33.924 --> 00:44:35.625
And so some communities

678
00:44:36.005 --> 00:44:39.545
are very happy to do lots of things in house. There are resources

679
00:44:40.005 --> 00:44:41.305
available for that.

680
00:44:43.100 --> 00:44:48.880
Unfortunately, HIFIS can be a little daunting, a little overwhelming when you look at the whole thing, so I am available.

681
00:44:49.580 --> 00:44:51.600
Another thing to consider is the training.

682
00:44:52.780 --> 00:44:53.280
Typically,

683
00:44:54.585 --> 00:44:56.605
communities do a couple different things.

684
00:44:56.984 --> 00:45:03.065
One is they might set up in recent years, people have been setting up like a an elearning portal.

685
00:45:03.065 --> 00:45:05.724
Some some people have been talking about Moodle,

686
00:45:06.585 --> 00:45:08.365
in the in a recent

687
00:45:08.905 --> 00:45:09.405
meeting,

688
00:45:10.260 --> 00:45:13.080
which I believe is free. But you you may

689
00:45:13.380 --> 00:45:18.260
want to pay for a training portal to get set up. You may need to,

690
00:45:20.500 --> 00:45:23.880
spend some resources developing training materials,

691
00:45:24.865 --> 00:45:28.165
possibly renting a venue to do that, or

692
00:45:28.545 --> 00:45:32.645
you like, having appropriate software. You might need to, like, pay for,

693
00:45:33.425 --> 00:45:34.165
like, a

694
00:45:34.545 --> 00:45:39.045
screen recording software, anything. Just figuring out related to training,

695
00:45:39.990 --> 00:45:45.050
at least in terms of man hours or person hours, that's definitely going to be a

696
00:45:45.910 --> 00:45:51.770
a a resource that needs to get invested because every user is going to need some amount of training,

697
00:45:52.470 --> 00:45:54.490
depending on who they are. Perhaps

698
00:45:54.945 --> 00:45:55.445
2

699
00:45:56.465 --> 00:45:59.605
to 5 or 6 hours of training per user.

700
00:46:00.705 --> 00:46:02.165
So that's not an insignificant

701
00:46:02.625 --> 00:46:06.405
thing. I do offer elearning on my website for an affordable price.

702
00:46:08.545 --> 00:46:09.445
Thanks, Chantal.

703
00:46:11.529 --> 00:46:16.010
So I I'm sorry, Britney. Did you talk about the cost of hosting the server?

704
00:46:16.010 --> 00:46:18.109
I, I was distracted for a moment.

705
00:46:19.130 --> 00:46:23.789
No. I didn't go into specifics, but I did mention that there is the technical requirements

706
00:46:24.170 --> 00:46:25.470
of hosting a server.

707
00:46:26.405 --> 00:46:29.545
And there's multiple ways depending on your community's approach.

708
00:46:30.085 --> 00:46:40.345
So if it's on premise or in a server farm or those types of pieces, it really depends on what your community's comfort level is and what their technical expertise are,

709
00:46:41.120 --> 00:46:45.460
and then getting your own quotes in those types of pieces to support it.

710
00:46:46.400 --> 00:46:47.940
And I think this is, you know,

711
00:46:48.480 --> 00:46:52.580
outside of HIFIS. There's definitely these CAEH that would incrue with any centralized

712
00:46:52.960 --> 00:46:54.420
database. And so,

713
00:46:55.145 --> 00:46:57.005
many things we're talking about today,

714
00:46:57.625 --> 00:47:00.685
including like the training and the onboarding of your community,

715
00:47:01.464 --> 00:47:06.635
those are standard kind of practices when you're building in a centralized system such as HIFIS.

716
00:47:06.744 --> 00:47:07.484
And so,

717
00:47:08.390 --> 00:47:12.810
yeah, those would be expected of a community in in in in this process.

718
00:47:14.150 --> 00:47:16.490
Yes. I don't mean to say that they're exclusive

719
00:47:17.030 --> 00:47:20.150
to HIFUS, but there is the server element.

720
00:47:20.150 --> 00:47:26.684
So communities typically either purchase their own server and then have their own internal resources that will support it.

721
00:47:26.684 --> 00:47:29.585
So you are going to need some sort of like database administrator.

722
00:47:30.684 --> 00:47:33.025
Typically you can leverage your municipalities

723
00:47:33.645 --> 00:47:34.625
IT department.

724
00:47:35.724 --> 00:47:39.930
And then the cost to purchase a server, or to allocate some server space

725
00:47:40.310 --> 00:47:41.930
shouldn't be that high.

726
00:47:42.550 --> 00:47:44.730
The other option is that you

727
00:47:45.350 --> 00:47:45.850
purchase

728
00:47:46.230 --> 00:47:51.130
hosting space through commercial host, which would end up being like a like a monthly

729
00:47:51.775 --> 00:47:56.915
kind of subscription based model where you'd pay yearly or quarterly or monthly or something like that.

730
00:47:57.615 --> 00:48:01.395
So that's a CAEH that could come up also.

731
00:48:03.215 --> 00:48:07.530
Thank you, guys. That was that was great. Kinda gave the whole gamut there.

732
00:48:08.730 --> 00:48:10.190
Caitlin had a question.

733
00:48:10.250 --> 00:48:17.230
Any advice for getting buy in to use HIFIS from agencies that are already using other databases for case management?

734
00:48:19.610 --> 00:48:20.750
I'll take this one.

735
00:48:22.135 --> 00:48:22.635
So

736
00:48:23.654 --> 00:48:26.795
to be honest, I don't have a perfect solution for you.

737
00:48:28.214 --> 00:48:28.714
However,

738
00:48:29.095 --> 00:48:30.555
one thing that is helpful

739
00:48:31.095 --> 00:48:32.234
is to

740
00:48:32.535 --> 00:48:35.994
very clearly articulate what your minimum data entry expectations

741
00:48:36.295 --> 00:48:36.810
might be.

742
00:48:37.610 --> 00:48:42.750
So if they have another software that they're using for their case notes and they like using that,

743
00:48:43.050 --> 00:48:43.550
then,

744
00:48:44.490 --> 00:48:45.550
I wouldn't necessarily

745
00:48:46.090 --> 00:48:50.110
ask them to stop using it and enter all their case notes in HIFUS.

746
00:48:50.994 --> 00:48:57.015
What you might find is a necessary minimum would be something like indicating in HIFUS

747
00:48:57.395 --> 00:48:59.095
that they have a case file open

748
00:48:59.395 --> 00:49:05.645
so that other staff could say, oh, I know that this client is working with that agency, and this is the name of their CAEH

749
00:49:06.759 --> 00:49:07.420
worker. So

750
00:49:08.119 --> 00:49:10.380
there is an area where you can articulate

751
00:49:11.160 --> 00:49:13.900
what the, like, the minimum data expectations

752
00:49:14.279 --> 00:49:14.779
are

753
00:49:15.160 --> 00:49:27.145
and then if the if an individual provider wants to go above and beyond that such as using HIFIS for their own case notes, then they ACRE welcome to do so, but not required, and they could record their case notes elsewhere.

754
00:49:30.885 --> 00:49:31.625
The other

755
00:49:32.805 --> 00:49:34.825
thing that I would say is

756
00:49:35.940 --> 00:49:41.960
many of the things that I was talking about in my part of the presentation such as HIFIS being able to automatically

757
00:49:42.260 --> 00:49:42.760
calculate

758
00:49:43.300 --> 00:49:44.440
moves to inactivity

759
00:49:44.740 --> 00:49:45.800
and so on,

760
00:49:47.505 --> 00:49:52.085
Moves to inactivity, who became homeless, who became chronically homeless, who had to move in.

761
00:49:52.545 --> 00:49:53.285
So that's

762
00:49:53.585 --> 00:49:55.365
client information. So

763
00:49:56.065 --> 00:49:59.204
related to the minimum data entry, I would

764
00:49:59.540 --> 00:50:06.440
I would say that, you know, if a client has a change in housing status, that would be a minimum data entry point that you'd be required to enter.

765
00:50:06.900 --> 00:50:07.720
And so

766
00:50:08.420 --> 00:50:09.320
pointing out

767
00:50:09.780 --> 00:50:10.599
the benefits

768
00:50:11.380 --> 00:50:15.425
of being able to have that database of clients where we know

769
00:50:15.965 --> 00:50:20.545
everyone, their housing status, how long they've been homeless for, who had to move in this month,

770
00:50:20.925 --> 00:50:23.105
and whatever the community

771
00:50:23.485 --> 00:50:23.985
priorities

772
00:50:24.445 --> 00:50:24.945
are.

773
00:50:25.245 --> 00:50:28.945
What's their indigenous identity, whether they're chronically homeless,

774
00:50:29.780 --> 00:50:34.680
whether they're unsheltered or staying in shelter, whatever your community priorities might be.

775
00:50:35.060 --> 00:50:39.720
Just point to the advantages of having all of that information in a central database,

776
00:50:40.660 --> 00:50:42.599
so that you can see the big overview

777
00:50:42.900 --> 00:50:43.640
of homelessness.

778
00:50:44.755 --> 00:50:49.075
If you have most of that but you're missing one chunk, then that can be problematic as a community.

779
00:50:49.075 --> 00:50:57.335
So you can try to, like, point out how much more helpful the system would be if, you know, we had that kind of complete information about all the clients.

780
00:50:57.690 --> 00:51:00.109
But as I said earlier, I wouldn't necessarily

781
00:51:00.650 --> 00:51:03.710
require them to use HIFIS exclusively for all their

782
00:51:04.424 --> 00:51:05.630
Ali of their activities.

783
00:51:07.530 --> 00:51:09.230
One thing I remember too.

784
00:51:09.655 --> 00:51:10.395
Oh, sorry.

785
00:51:11.335 --> 00:51:14.395
One thing I remember too from implementing in communities

786
00:51:14.695 --> 00:51:16.155
was really being clear

787
00:51:16.615 --> 00:51:18.555
about how you want,

788
00:51:19.095 --> 00:51:21.355
your community partners to enter that information.

789
00:51:21.870 --> 00:51:26.370
And if you're funding community partners as part as your as part of your coordinated

790
00:51:26.670 --> 00:51:27.650
access system

791
00:51:28.030 --> 00:51:30.290
to write that into your service agreements,

792
00:51:30.990 --> 00:51:32.930
really clear roles, responsibilities,

793
00:51:33.470 --> 00:51:34.785
and how to do it.

794
00:51:35.025 --> 00:51:41.525
And I think staff training, having somebody appointed that will go out and train your community partners,

795
00:51:41.984 --> 00:51:45.285
is really, really helpful for getting buy in as well.

796
00:51:47.260 --> 00:51:51.040
Yeah. It's a great one, Chantal. And the only thing I was gonna say is that

797
00:51:51.580 --> 00:51:54.080
in many communities, we're taking a very

798
00:51:54.620 --> 00:51:55.120
isolated,

799
00:51:55.660 --> 00:51:56.160
segregated

800
00:51:56.700 --> 00:51:57.680
service provision

801
00:51:58.380 --> 00:52:03.055
process and trying to create this coordinated effort, and that takes a lot of trust and relationships

802
00:52:03.515 --> 00:52:04.575
amongst agencies

803
00:52:04.955 --> 00:52:06.095
and service providers.

804
00:52:06.475 --> 00:52:08.494
And so that takes a lot of time.

805
00:52:09.035 --> 00:52:13.215
And so sometimes it's just about that continuing to build relationships,

806
00:52:13.915 --> 00:52:14.415
trust,

807
00:52:16.349 --> 00:52:19.170
and and sharing as as Chantal, you're saying, the vision

808
00:52:19.470 --> 00:52:22.049
as well as you, Ali, the intention, the benefits,

809
00:52:22.750 --> 00:52:23.569
and continuing

810
00:52:23.869 --> 00:52:25.170
to show that,

811
00:52:26.109 --> 00:52:27.010
with examples

812
00:52:27.455 --> 00:52:31.935
is is really always a helpful component, but to also continue to build trust in,

813
00:52:32.335 --> 00:52:35.955
in relationship with with those individuals, I think, is really important.

814
00:52:38.575 --> 00:52:47.020
One of the other questions that we had that came in on the Slido for other tidbits was about integration with health CAEH partners.

815
00:52:47.480 --> 00:52:48.300
I was wondering,

816
00:52:48.600 --> 00:52:53.740
you know, if you guys had any advice on that or if you know communities that are doing that well.

817
00:52:59.035 --> 00:53:00.734
I think, again, this is very,

818
00:53:01.595 --> 00:53:02.734
based on relationships

819
00:53:03.035 --> 00:53:04.174
with municipal

820
00:53:04.795 --> 00:53:06.974
and provincial partners. And so,

821
00:53:07.515 --> 00:53:08.575
there are certainly

822
00:53:09.440 --> 00:53:12.660
some examples that that come to mind around where

823
00:53:12.960 --> 00:53:16.900
health partners have come to the forefront to help support.

824
00:53:18.320 --> 00:53:19.040
And some,

825
00:53:19.360 --> 00:53:24.100
don't maybe have direct access to the database, but maybe helping support

826
00:53:25.265 --> 00:53:27.365
providing data towards it.

827
00:53:28.785 --> 00:53:30.405
There's there there's definitely,

828
00:53:32.065 --> 00:53:32.565
multiple

829
00:53:33.345 --> 00:53:33.845
approaches,

830
00:53:34.785 --> 00:53:36.245
in regards to it,

831
00:53:36.545 --> 00:53:41.260
and it really does come back come back to, like, data provision agreements and client consent practices,

832
00:53:43.000 --> 00:53:44.060
and legislation

833
00:53:44.360 --> 00:53:48.520
a little bit around making sure that those pieces are CAEH as well. Yeah.

834
00:53:48.520 --> 00:53:51.100
Ellie, I see you're off, so I'll let you jump in as well.

835
00:53:51.494 --> 00:53:57.914
I just wanted to say that this is one of the things that is really variable from community to community.

836
00:53:58.375 --> 00:54:03.595
Some places I've worked with have the the health partners are really, really quite integrated

837
00:54:04.089 --> 00:54:08.990
and some places that it's like there's a wall and we're not allowed to talk to each other at all.

838
00:54:09.290 --> 00:54:11.309
So this is highly variable.

839
00:54:12.089 --> 00:54:14.190
I do wanna point out York Region.

840
00:54:15.050 --> 00:54:18.465
One of the innovative things that they did related to HIFIS is,

841
00:54:19.025 --> 00:54:19.925
they decided

842
00:54:20.225 --> 00:54:23.605
when they were first implementing on their client consent forms

843
00:54:23.985 --> 00:54:25.685
that they were collecting data

844
00:54:26.145 --> 00:54:27.685
both under MFIPA,

845
00:54:27.985 --> 00:54:33.720
that's the municipal freedom of information and then protection and privacy act, and PHIPA, which is the health one.

846
00:54:33.940 --> 00:54:39.480
So the consent form says we're collecting information under both, and that kind of allowed them to,

847
00:54:40.019 --> 00:54:44.599
sort of share and, like, share information with other health partners a little bit more freely.

848
00:54:45.045 --> 00:54:46.744
And so that's kind of an interesting,

849
00:54:47.365 --> 00:54:48.265
case there,

850
00:54:48.964 --> 00:54:51.785
but I've definitely seen quite a range. So

851
00:54:52.085 --> 00:54:55.305
I think what I'm just trying to say is there are solutions.

852
00:54:55.444 --> 00:54:59.704
You just need to figure out what they are in in your community. And also,

853
00:55:00.500 --> 00:55:05.780
I'm sure Chantal would be happy to give you some more examples of communities that are,

854
00:55:06.819 --> 00:55:09.160
that are doing health integration a little bit better.

855
00:55:11.140 --> 00:55:12.760
Yeah. I can certainly

856
00:55:13.285 --> 00:55:17.225
kinda do a landscape survey of that and get that out to the group.

857
00:55:19.445 --> 00:55:28.510
You brought up, Britney, about data sharing agreements, and I just really wanted to highlight for everybody on the call that if you are thinking about implementing HIFIS

858
00:55:28.930 --> 00:55:33.670
or your community is is starting to do that, you're not alone. There's tons of

859
00:55:33.970 --> 00:55:36.869
resources out there. Communities have already,

860
00:55:37.890 --> 00:55:41.029
done a lot of this work. And most of the communities

861
00:55:41.410 --> 00:55:47.405
that I know that are using HIFIS are quite generous in sharing the work that they have done. So,

862
00:55:48.665 --> 00:55:55.485
I don't know, Ali, Britney, if you wanted to to chime in there about the the wealth of resources that communities,

863
00:55:56.265 --> 00:55:57.405
are open to sharing.

864
00:55:59.860 --> 00:56:03.960
I definitely think the homelessness hub has a plethora of details.

865
00:56:04.100 --> 00:56:10.920
It's it's a little bit overwhelming to get in there and sift through what you need, but there is a lot of resources there,

866
00:56:11.380 --> 00:56:12.280
to start with.

867
00:56:13.495 --> 00:56:17.995
And and, again, it's very local. We're we're sitting here with 1 province, but sometimes,

868
00:56:18.535 --> 00:56:19.755
some of them are provincially

869
00:56:20.615 --> 00:56:22.715
provided, and the laws can be different

870
00:56:23.095 --> 00:56:28.730
between provinces. So just always being cautious around it. Can't always be a copy and paste unless,

871
00:56:29.590 --> 00:56:31.770
you're very familiar with those legislations.

872
00:56:33.030 --> 00:56:36.730
So, yeah, just very, very aware that there's a lot of already,

873
00:56:37.590 --> 00:56:39.610
community data sharing agreements

874
00:56:39.954 --> 00:56:41.335
as well as consent,

875
00:56:42.915 --> 00:56:45.015
for the participant or your client,

876
00:56:45.875 --> 00:56:52.135
available online to to review and see if you can use them as a starting place anyways for sure.

877
00:56:52.710 --> 00:56:57.290
I wanna open the floor to Miles if he's around for a little shout out.

878
00:56:59.109 --> 00:57:01.050
I am here. Yes. Yeah.

879
00:57:02.869 --> 00:57:05.990
Did you have something specific you wanted me to comment on? Just the help one.

880
00:57:05.990 --> 00:57:09.125
Or Do Do communities collaborate with each other?

881
00:57:12.545 --> 00:57:14.005
Yes, we do. There's

882
00:57:14.465 --> 00:57:15.525
an off brand

883
00:57:16.545 --> 00:57:21.045
working group that we've kind of put together just talking about like some specific provincial,

884
00:57:22.340 --> 00:57:23.800
Ontario provincial reporting

885
00:57:24.100 --> 00:57:25.880
and just trying to work through that

886
00:57:26.980 --> 00:57:31.000
in Ontario. So, if you're interested in that group, shoot anybody

887
00:57:31.700 --> 00:57:32.360
an email.

888
00:57:33.060 --> 00:57:35.800
I think Britney has my info. Ali, Chantal

889
00:57:36.100 --> 00:57:37.427
will get you connected in there. So, there's lots of opportunity to collaborate. In there.

890
00:57:37.427 --> 00:57:40.709
So, there's lots of opportunity to collaborate as well, like through unofficial means as well with other communities.

891
00:57:40.709 --> 00:57:44.615
We bounce HIFUS ideas off of each other and kind of work through that.

892
00:57:49.590 --> 00:57:53.290
And then the Slack page is a really great, opportunity as well.

893
00:57:55.590 --> 00:57:57.430
So thanks, Miles, for that. Yeah.

894
00:57:57.430 --> 00:58:03.690
And if anybody would like to connect with that group, just ask your improvement adviser, and we can get you Miles' contact information.

895
00:58:04.195 --> 00:58:05.755
Ali, you were about to say something.

896
00:58:06.135 --> 00:58:08.635
Oh, yeah. And there's a Slack group too.

897
00:58:10.295 --> 00:58:12.235
Thanks, Miles, for reminding me.

898
00:58:15.975 --> 00:58:19.020
One last question that I had that hadn't come up,

899
00:58:19.500 --> 00:58:29.420
and that I get asked a lot about is what level of tech support do communities need to to maintain the server and and to maintain HIFIS?

900
00:58:29.420 --> 00:58:29.920
Like,

901
00:58:30.940 --> 00:58:35.775
is it a half time role? Is it a third of a role? Is it a full time role?

902
00:58:35.775 --> 00:58:39.715
Or does does that kinda all depends? Any comments on that?

903
00:58:40.415 --> 00:58:43.795
Maybe I'll start, and then we can get some real examples from community.

904
00:58:45.295 --> 00:58:49.940
There's there's definitely 2 types of, like, tech roles and support roles.

905
00:58:50.640 --> 00:58:52.160
So I just wanna separate those out.

906
00:58:52.160 --> 00:58:56.500
Like, one is really the back end technical aspects of HIFIS and doing,

907
00:58:57.120 --> 00:59:04.954
the upgrades and doing the system upgrades and, when releases come out, just making sure you're in the test environment and testing it and it gets rolled out.

908
00:59:05.575 --> 00:59:06.234
So definitely

909
00:59:06.535 --> 00:59:07.174
need more,

910
00:59:07.974 --> 00:59:11.914
you know, IT specialty to ensure that that that operates

911
00:59:12.295 --> 00:59:16.555
smoothly. And and, you know, as we said, there is a server involved.

912
00:59:17.255 --> 00:59:21.170
There is those components, and we wanna make sure that those are firewalled accurately,

913
00:59:21.470 --> 00:59:23.710
secure, and safe based on those pieces.

914
00:59:23.710 --> 00:59:27.490
So there is definitely some more higher tech requirements on that.

915
00:59:27.950 --> 00:59:28.610
And then,

916
00:59:29.230 --> 00:59:33.410
the second component would definitely be more of, like, your support to community,

917
00:59:34.415 --> 00:59:35.875
and definitely understanding

918
00:59:36.255 --> 00:59:40.595
how the application works and how to enter data appropriately.

919
00:59:42.015 --> 00:59:46.494
So that doesn't involve, like, the back end technical aspects. It's more of that front end,

920
00:59:46.815 --> 00:59:47.315
database

921
00:59:48.110 --> 00:59:49.730
review and support for community.

922
00:59:49.790 --> 00:59:53.970
So there was just I just wanted to separate those 2 types of supports that,

923
00:59:54.590 --> 00:59:55.490
would be needed.

924
00:59:55.790 --> 00:59:56.290
Yeah.

925
00:59:56.830 --> 01:00:00.290
And, Ali, I see you're writing database administrator. Yeah. There's there's.

926
01:00:00.895 --> 01:00:03.315
Yeah. No. Thanks. That's the that's the perfect,

927
01:00:04.015 --> 01:00:04.975
division of roles.

928
01:00:04.975 --> 01:00:11.155
So the first one that she described, the back end IT stuff, that would be someone with a job title of database administrator.

929
01:00:11.615 --> 01:00:13.395
Typically, they work for your municipality's,

930
01:00:14.415 --> 01:00:15.395
IT department.

931
01:00:16.490 --> 01:00:17.390
I don't know

932
01:00:17.770 --> 01:00:20.030
what percentage of an FTE

933
01:00:20.490 --> 01:00:24.589
it would be necessary here, but it's a fraction. It's not a full time job.

934
01:00:25.290 --> 01:00:28.845
One thing that I want to point out in terms of maintaining HIFIS

935
01:00:29.085 --> 01:00:32.465
is that it does vary in terms of your,

936
01:00:32.925 --> 01:00:34.865
the demands on your IT

937
01:00:35.165 --> 01:00:36.065
people's times,

938
01:00:36.605 --> 01:00:39.825
depending on where you're at. So when you have your implementation

939
01:00:40.205 --> 01:00:40.705
day,

940
01:00:41.740 --> 01:00:45.820
then obviously your IT people are gonna be very busy. They have to set up the server.

941
01:00:45.820 --> 01:00:50.000
They have to make sure that the the the sudden spike in users doesn't,

942
01:00:50.940 --> 01:00:52.240
doesn't cause any trouble.

943
01:00:52.620 --> 01:00:58.924
So there will be, like, a week or a couple of weeks where your IT people might be working on HIFIS full time,

944
01:00:59.464 --> 01:00:59.964
but,

945
01:01:00.904 --> 01:01:05.164
but for the rest of the time, there would be very little maintenance required.

946
01:01:05.305 --> 01:01:07.085
The key piece though is that,

947
01:01:07.865 --> 01:01:12.204
generally, you'd want to have IT people who are available on call should

948
01:01:12.560 --> 01:01:14.020
should some problem happen.

949
01:01:14.640 --> 01:01:20.500
And then you might want to have a discussion about whether it truly needs to be 247

950
01:01:21.680 --> 01:01:26.420
or if the IT people only need to be available, say, 9 to 5. So for example,

951
01:01:26.755 --> 01:01:29.734
your HIFIS server goes down at 9 o'clock at night.

952
01:01:30.275 --> 01:01:37.494
You you would probably want to decide as a community, is it a super high priority that we need it to be running before 8 AM the next day,

953
01:01:38.195 --> 01:01:40.055
in which case you're paying for 247

954
01:01:40.355 --> 01:01:41.415
support, which is

955
01:01:41.990 --> 01:01:42.710
much more expensive,

956
01:01:45.270 --> 01:01:47.849
or if they can fix it when they come in in the morning.

957
01:01:48.150 --> 01:01:53.625
So that could be, an area where you as a community can decide what is more important there.

958
01:01:53.705 --> 01:01:57.405
But generally speaking for your, your database administrator,

959
01:01:58.905 --> 01:02:02.845
the I'm gonna say it's, like, less than a quarter FTE. Typically,

960
01:02:03.305 --> 01:02:07.805
you would borrow some of the time of one of your DBAs at your municipality,

961
01:02:09.010 --> 01:02:11.350
and they're also maintaining other servers

962
01:02:12.050 --> 01:02:14.710
too. So but then for the front end,

963
01:02:15.330 --> 01:02:19.750
so the second piece, you generally want to designate someone in your community,

964
01:02:20.050 --> 01:02:31.494
like, probably one of you on this CAEH, to be your subject matter expert to really understand how things work in HIFIS, how the rights get set up, and what programs do, and all of the,

965
01:02:32.115 --> 01:02:32.615
configuration

966
01:02:33.075 --> 01:02:38.530
pieces. You'd want to become an expert in that. And then that person's job would be

967
01:02:38.990 --> 01:02:40.610
to make sure that people's,

968
01:02:41.470 --> 01:02:44.050
user rights are acting as intended

969
01:02:44.670 --> 01:02:48.850
and that people are collecting the right data and have access to the right pieces of the software.

970
01:02:48.910 --> 01:02:49.970
And once again,

971
01:02:50.385 --> 01:02:53.445
it depends on where you're at in your implementation journey.

972
01:02:53.745 --> 01:02:57.605
So that person is gonna have a lot of work to do leading up to implementation.

973
01:02:58.785 --> 01:03:02.645
But then once you get to a stable point where you've implemented,

974
01:03:03.265 --> 01:03:04.405
then that person's

975
01:03:05.460 --> 01:03:10.359
requirements will switch to a little bit more maintenance, probably some data analysis,

976
01:03:11.300 --> 01:03:14.200
running reports, looking at the system stuff. So,

977
01:03:15.140 --> 01:03:19.080
so you could hire someone temporarily for the project of implementation,

978
01:03:20.395 --> 01:03:22.815
and then switch their role after implementation.

979
01:03:23.595 --> 01:03:25.135
But post implementation,

980
01:03:25.515 --> 01:03:26.575
you don't need

981
01:03:27.755 --> 01:03:28.975
a full time

982
01:03:29.835 --> 01:03:30.335
person

983
01:03:31.035 --> 01:03:31.535
to

984
01:03:32.330 --> 01:03:33.150
keep maintaining,

985
01:03:33.770 --> 01:03:34.750
like, the configuration

986
01:03:35.210 --> 01:03:37.790
piece. You would need to move into

987
01:03:38.170 --> 01:03:44.650
ensuring data quality and making sure that the needs of your service providers are being met through new reports and stuff.

988
01:03:44.650 --> 01:03:49.145
So the job changes a little bit depending on the the phase of your journey.

989
01:03:49.924 --> 01:03:51.865
Thank you, Ali. Not too rambling.

990
01:03:52.484 --> 01:03:53.765
No. That was great.

991
01:03:53.765 --> 01:03:59.785
And, we do have Build for 0 does have some job descriptions for, like, the database administrator

992
01:04:00.164 --> 01:04:01.230
and HIFIS

993
01:04:01.390 --> 01:04:04.770
kind of coordinated access manager on our website as well.

994
01:04:04.910 --> 01:04:10.450
So if you're having trouble locating those, then just ask your improvement adviser, and we can flip those to you.

995
01:04:10.750 --> 01:04:12.369
So I see that we're out of time.

996
01:04:12.670 --> 01:04:13.390
Thank you.

997
01:04:13.390 --> 01:04:23.675
I'd really like to say thank you to Britney, to Ali, and to Miles for once again jumping in and being put on the spot at one of our community of practice calls.

998
01:04:23.675 --> 01:04:28.415
So thank you everybody for attending, and we will see you in September.

999
01:04:30.720 --> 01:04:32.100
Have a great day. Thank

1000
01:04:32.880 --> 01:04:33.380
you.