WEBVTT

1
00:08:50.880 --> 00:08:52.110
Hi there is fabulous.

2
00:11:53.040 --> 00:12:01.860
The day everyone. This is Rose. We're going to wait a couple more minutes. Before getting started, but glad to see so many people here are looking forward to this presentation.

3
00:12:09.720 --> 00:12:12.180
I wrote just making sure you can hear me and john

4
00:12:14.370 --> 00:12:18.180
Hi john coming through loud and clear, looking forward to hearing more today from you.

5
00:12:18.300 --> 00:12:20.100
Okay, great.

6
00:12:20.340 --> 00:12:20.880
Okay, great.

7
00:12:30.510 --> 00:12:36.030
So we'll wait until about two or three past the hour just to let some last people on then.

8
00:12:38.460 --> 00:12:39.690
antitrust statement.

9
00:12:39.690 --> 00:12:45.300
That's required, and then we can get going so appreciate everybody's patience for everyone who is here on time.

10
00:12:45.600 --> 00:12:46.110
Wow.

11
00:12:48.480 --> 00:12:50.310
Was up at the time.

12
00:13:11.460 --> 00:13:11.940
Hello, Matt.

13
00:14:07.980 --> 00:14:09.390
Alright, let's get started.

14
00:14:11.370 --> 00:14:14.490
With the team from Uzbekistan, are you here.

15
00:14:15.900 --> 00:14:17.190
Can produce Becca, Stan.

16
00:14:20.760 --> 00:14:21.630
Money you NDP

17
00:14:24.030 --> 00:14:25.620
Hello, thank you for inviting me.

18
00:14:26.490 --> 00:14:29.130
very welcome. Thank you for joining will go around, I think.

19
00:14:29.130 --> 00:14:33.480
You're doing production if 17 participants today, which is very exciting.

20
00:14:34.500 --> 00:14:41.820
Those of you who are on if you could mute your microphones. It's in at least for me at the bottom left hand.

21
00:14:42.090 --> 00:14:47.160
Except for when you're talking, then that would be terrific. And we'll get going.

22
00:14:49.200 --> 00:14:51.300
Roads, you have the power to mute as well.

23
00:14:52.920 --> 00:14:55.440
I'm not sure I can do I

24
00:14:57.060 --> 00:15:00.690
Know you can easily go on the participants and right click and say news.

25
00:15:01.980 --> 00:15:05.310
I'm here the meeting organizer. You know, I think.

26
00:15:05.400 --> 00:15:11.850
I unfortunately or fortunately, we're in an extremely gala cheering situation. And I don't think I've the ability to meet me, buddy.

27
00:15:14.460 --> 00:15:15.120
But that's okay.

28
00:15:16.950 --> 00:15:20.790
All right, I think we will get started.

29
00:15:20.880 --> 00:15:21.270
Yeah.

30
00:15:22.530 --> 00:15:23.460
Our actual

31
00:15:25.590 --> 00:15:26.160
Military and

32
00:15:31.470 --> 00:15:31.890
So,

33
00:15:31.920 --> 00:15:33.240
I'm going to get us started with

34
00:15:33.240 --> 00:15:35.190
The traditional opening

35
00:15:36.870 --> 00:15:44.850
Every one of our meetings so hello everybody can't wait to see who's here there's 18 participants, which is great, but first we have to read some formalities.

36
00:15:47.580 --> 00:16:00.930
Anti trust policy. Notice the Linux Foundation meetings involved participation by industry competitors and it is the intention of the Linux Foundation to conduct all of its activities in accordance with a clickable anti trust and competition laws.

37
00:16:01.350 --> 00:16:10.200
Is there for extremely important that attendees adhere to meeting agendas and be aware of and not participate in any activities that are prohibited under a clickable US state, federal

38
00:16:10.500 --> 00:16:13.050
Or foreign anti trust and competition laws.

39
00:16:13.410 --> 00:16:22.770
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation anti trust policy available.

40
00:16:23.070 --> 00:16:25.920
At Linux Foundation org anti trust stash policy.

41
00:16:26.430 --> 00:16:33.390
If you have questions about these matters, please contact your company council or if you're a member of the Linux Foundation, feel free to contact into

42
00:16:33.630 --> 00:16:43.590
The groove of the firm guys were up to group LLP which provides a legal counsel to the Linux Foundation, he ended up okay so good day to everybody.

43
00:16:43.920 --> 00:16:49.980
Thank you so much for joining. What I think is going to be a really exciting meeting thanks to our friends from Canada.

44
00:16:50.910 --> 00:16:54.060
To the public sector working group of hyper ledger.

45
00:16:54.630 --> 00:17:07.080
I think it would be great for people to could just go around and introduce themselves. I think we have some new faces here and those who are here as well be great to reintroduce yourself. I'm Rose Sherman and I am the chair and traffic director of this meeting.

46
00:17:08.130 --> 00:17:09.690
And on to the next.

47
00:17:13.530 --> 00:17:31.020
My name is scholarly coming from government Ontario Ministry our government and the consumer service and my senior solution design of it. I'm looking forward to hear more from the group up all the technology and the possible use cases that we may use. Well, thank you.

48
00:17:32.310 --> 00:17:48.210
Hi I'm Bobby mascara. I'm from Princeton. I'm the Director of Education at ledger Academy and I am here just to learn and contribute from also being a member of the training and education and work group. So I'm trying to contribute from that group as well.

49
00:17:52.410 --> 00:18:05.940
I am aka Sam from five software, they'll open and consultancy company with a couple of public sector customers and I'm looking to share and learning from experience.

50
00:18:09.270 --> 00:18:21.330
Hi I'm letter that when an independent consultant, but also with the hyper ledger identity and architectural work in groups and currently on this global forum.

51
00:18:22.350 --> 00:18:30.930
And I've also done quite a lot of consulting work for the Ministry of Natural Resources and empty Cs and Ontario, Canada.

52
00:18:32.700 --> 00:18:42.240
Yeah, so I'm looking justice lie said for the use case says that will be applicable to public sector, you might say implementations of blockchain.

53
00:18:57.330 --> 00:18:59.820
Anybody else would like to introduce themselves.

54
00:18:59.940 --> 00:19:00.630
It does. I

55
00:19:01.830 --> 00:19:05.880
Hi, my name is Mariana, I'm from Moldova Social Innovation Lab, you

56
00:19:05.880 --> 00:19:12.510
NTP Moldova and I'm currently coordinating block chain based projects fleet management system for you and Moldova.

57
00:19:18.510 --> 00:19:34.080
Hi there, only in me Tosca government of Ontario. I mean his garments and humor services and I'm here to talk about on terrorists experience participation in a blockchain pilots, the government of and the Federal procurement. Thank you.

58
00:19:36.450 --> 00:19:41.430
Hi this is Paul brechner director of technology policy with the chamber of digital commerce.

59
00:19:43.590 --> 00:19:50.040
I this is Pete Teigen with IBM global government team focused on what Cain in the public sector.

60
00:19:54.120 --> 00:19:54.630
Hello.

61
00:19:56.040 --> 00:20:00.990
Judy time and the money analyst with the Office of the resident coordinator United Nations in Moldova.

62
00:20:07.260 --> 00:20:12.210
All right, Mama. So Bonnie global global program advisor you in the private sector.

63
00:20:16.680 --> 00:20:26.490
Hello, I'm sorry, from university office was biggest on I joined recently the UFC office in Pakistan, and I look forward to learning new stuff here. Thanks.

64
00:20:32.700 --> 00:20:44.640
Hello to everyone. This is Mike Luba from our office on his biggest done. And that's offices in Vegas done is coordinating the joint project on blockchain in public.

65
00:20:45.630 --> 00:20:55.500
Services. So we've been implemented by three agencies with you, NTP in lead and you know the sea and Unicef and then apologizing for the noise that we're

66
00:20:56.550 --> 00:20:59.550
Here on the background. Thank you for understanding

67
00:21:04.740 --> 00:21:11.250
Glad you could join us. And thanks to all our friends from various UN agencies who are here. We're excited to have you on board.

68
00:21:13.530 --> 00:21:25.440
Hello, let me also introduce myself. My name is New York. I'm from Uzbekistan us in the project on digital transformation. And we're also eager to learn

69
00:21:27.780 --> 00:21:33.420
Interesting information on Hyper ledger block chain proposals and solutions.

70
00:21:45.060 --> 00:21:48.000
See someone here named, would you like to introduce yourself.

71
00:21:55.980 --> 00:22:00.840
Okay, that's fine. Would anyone else like to make an introduction. So we know who's in the meeting.

72
00:22:02.430 --> 00:22:11.160
Oh hi this is after she have from Paramount software solutions I presently take care of the emerging technologies as a director of operations. Thank you.

73
00:22:20.610 --> 00:22:24.720
Terrific. Anyone else john, perhaps, have you introduced yourself.

74
00:22:26.310 --> 00:22:27.120
Not yet really

75
00:22:28.920 --> 00:22:31.350
Jordan from the province of BC.

76
00:22:32.700 --> 00:22:43.890
In Canada, and I guess leading this object in collaboration with Ontario and the chairman agency from the Government of Canada. Oh, sure.

77
00:22:45.810 --> 00:22:47.760
chat a little bit more about this a few minutes.

78
00:22:50.520 --> 00:22:50.940
Great.

79
00:22:52.050 --> 00:22:56.070
Anyone else who hasn't introduce themselves who would like to

80
00:23:06.600 --> 00:23:14.400
All right, well, then we'll just presume that everyone who has wanted to introduce themselves has introduced themselves, of course, if you change your mind you're free to

81
00:23:15.210 --> 00:23:27.210
Jump in later but thank you everyone for joining this Webinar and call of the hyper ledger public sector working group again I'm Rose I direct traffic.

82
00:23:29.160 --> 00:23:33.090
We're having a very interesting meeting today with a cool agenda.

83
00:23:34.110 --> 00:23:44.910
Two presenters one Bobby, who's going to talk a bit about educational resources and then john and perhaps members of his team, which is going to go in depth to a case study.

84
00:23:45.360 --> 00:23:56.160
Just so that we have good timing sense Bobby and john can you teach indicate about how long you ideally would have for your presentations, just to make sure that we can fit everything in right or discuss

85
00:23:56.670 --> 00:24:02.100
My presentation runs probably about eight minutes. Okay. That should fit.

86
00:24:02.490 --> 00:24:03.630
John. How about yourself.

87
00:24:04.110 --> 00:24:23.610
Right, I can well we can do whatever whatever you want. I mean, I think the fastest meaningful one is probably 20 or 25 but there's more time than we can get into more detail. Turns out we can talk about this stuff for a long, long time. And I can shorten mine.

88
00:24:24.150 --> 00:24:24.600
To the

89
00:24:25.140 --> 00:24:26.190
tone of the meeting.

90
00:24:26.520 --> 00:24:30.390
Well, I think even it's should be fine. Let's anybody Jack's

91
00:24:31.050 --> 00:24:32.010
Asking the group.

92
00:24:32.760 --> 00:24:36.420
Is there anybody else who would like to add anything to the agenda.

93
00:24:42.150 --> 00:24:52.440
Okay, so we'll provisionally say no. So that means we'll just need a little bit of time at the end to see who would like to present at the next meeting in two weeks.

94
00:24:52.740 --> 00:25:01.440
So you all have about, you know, 3040 minutes to get yourself up to volunteer. If there's anything else you'd like to present as well as a discussion about

95
00:25:01.740 --> 00:25:09.000
Any other materials or group work, we'd like to do. So let's aim to land at about

96
00:25:09.270 --> 00:25:23.670
1045 1050 or sorry, I'm talking Easter time 45 or 50 past the hour with all the presentations and Q AMP. A and then just do some discussion around next steps if that's quick that we can go back into Q AMP. A is that sound good with everyone.

97
00:25:26.100 --> 00:25:26.340
All right.

98
00:25:26.400 --> 00:25:28.170
I'll accept that. Good. Yep.

99
00:25:28.260 --> 00:25:34.710
Body, would you like to jump in first with some broad setting the stage about

100
00:25:35.160 --> 00:25:39.570
Absolutely. I'm not sure. Let me see if I can show my screen. Does that work.

101
00:25:40.740 --> 00:25:41.400
Hold on.

102
00:25:45.720 --> 00:25:46.830
Everybody see my screen.

103
00:25:49.860 --> 00:25:50.760
Yeah. Yes. No.

104
00:25:53.940 --> 00:25:54.270
Yes.

105
00:25:55.320 --> 00:25:55.650
It is

106
00:25:56.310 --> 00:25:57.600
Okay, can you hear me.

107
00:25:58.440 --> 00:25:58.890
Yes.

108
00:25:59.190 --> 00:25:59.940
Okay, here we go.

109
00:26:00.990 --> 00:26:14.430
I'm gonna go through, I made a little slide presentation just to show you the resources I found for the group. So, two weeks ago, it was my charge to find very basic training materials for this group when they are

110
00:26:14.850 --> 00:26:32.550
Out and about and need to explain block chain on a non technical level. So what I did was I found actually three resources that we can access as a group, constantly online. And then the last one is just a little fun Friday video. So let me see if I can get this going.

111
00:26:33.660 --> 00:26:35.670
Okay, so our first resource is the

112
00:26:35.670 --> 00:26:49.080
Hyper ledger video resource page and there is a link to the right, where you can access this video page. And at the end of this presentation. There is a resource page for all the links which I will post on the chat.

113
00:26:49.980 --> 00:26:59.160
So the hyper ledger video resource page opens up to one presentation on top which is called a greenhouse incubator for block chain projects.

114
00:26:59.610 --> 00:27:05.190
It is a great overview. It is a three minute video. It goes into

115
00:27:05.850 --> 00:27:14.130
What's going on, talks about your business talks about how your business needs to transact with other businesses, very, very superficial high level.

116
00:27:14.550 --> 00:27:31.710
And that it talks about how everyone requires an agreed upon ledger. Then it goes into our hyper ledger software helps keep these Ledger's it talks about different forms of ledger systems and how they need to be an operable it also goes into a little bit about

117
00:27:33.420 --> 00:27:43.290
global collaboration and crossing industry lines and then it ends with a little bit about the open source software and how that works. Again, it's a three minute video

118
00:27:44.550 --> 00:27:55.950
Very good. Very overview moves quick also on that page, our resources for introductory videos for all of the tools in the umbrella.

119
00:27:56.490 --> 00:28:04.890
Not all of the tools, but the tools that have good videos I've seen them and they're they're worthwhile to watch if someone wants to get a little bit into each one of the product lines.

120
00:28:05.580 --> 00:28:17.760
The next resources, the hyper ledger Google Doc links. And what that's going to give you is a very introductory Powerpoint, you would have to give the powerpoint. If you use this resource.

121
00:28:18.120 --> 00:28:27.780
It's broken out into five parts. The first part just explains a high level block chain technology goes a little into the smart contract.

122
00:28:28.170 --> 00:28:36.510
Talks about trucks trust mechanisms goes into what hyper ledger is and does. And my favorite are the use cases.

123
00:28:36.930 --> 00:28:46.710
They really go into specific and I'll show you a little bit more. So the outline here. It's one slide for each one of these topics. So if you don't want to get into

124
00:28:47.070 --> 00:28:55.740
blockchain smart contracts, you can skip that slide again and it's one definition it's not high level, but it does talk a little bit more

125
00:28:55.740 --> 00:28:57.510
About the structure of block chains.

126
00:28:57.510 --> 00:28:59.100
Then that first fun video

127
00:29:00.690 --> 00:29:07.440
Again, it introduces hyper ledger. It talks about the modular approach the architecture and the goals of the hyper ledger.

128
00:29:07.950 --> 00:29:08.520
Found the

129
00:29:08.550 --> 00:29:09.720
Hyper ledger project.

130
00:29:10.140 --> 00:29:11.280
And the Linux Foundation.

131
00:29:12.660 --> 00:29:13.620
The use cases.

132
00:29:13.680 --> 00:29:24.180
I just listed them here for everyone to see it goes into a use case on cross borders healthcare digital identity. So if you're interested in your target audience, you can go

133
00:29:24.180 --> 00:29:26.580
Right to the slide that has that use

134
00:29:26.580 --> 00:29:28.410
Case and discuss that.

135
00:29:29.820 --> 00:29:30.990
The next is the movie.

136
00:29:31.140 --> 00:29:32.430
That just came out August

137
00:29:33.000 --> 00:29:33.420
2

138
00:29:33.450 --> 00:29:35.010
That's something that the training.

139
00:29:35.190 --> 00:29:35.430
And an

140
00:29:35.550 --> 00:29:36.750
Educational work.

141
00:29:36.750 --> 00:29:37.560
Group has been

142
00:29:39.360 --> 00:29:40.710
EDX company.

143
00:29:41.310 --> 00:29:42.420
It is a free course.

144
00:29:42.510 --> 00:29:44.880
It is very, very interesting.

145
00:29:44.910 --> 00:29:50.550
I suggest everyone take it on. It is newly released them again. It is open source.

146
00:29:51.090 --> 00:29:53.160
So dive right in and you can

147
00:29:53.460 --> 00:29:58.020
Direct your clients to this again free open source.

148
00:29:59.730 --> 00:30:00.150
And the federal

149
00:30:00.240 --> 00:30:00.810
MOOC is a

150
00:30:01.830 --> 00:30:03.750
Massive Online Open Source.

151
00:30:03.750 --> 00:30:04.800
Course, if that

152
00:30:05.190 --> 00:30:06.030
clarifies things

153
00:30:06.390 --> 00:30:11.220
So it's a huge course out there for people to take and it is again a free enrollment.

154
00:30:12.510 --> 00:30:16.530
And here's the core syllable. It goes into the block chain. It goes a little bit into

155
00:30:16.560 --> 00:30:19.140
Governance and consensus solving problems.

156
00:30:19.170 --> 00:30:22.200
And then again, use cases. And there's a final exam at the end.

157
00:30:23.790 --> 00:30:36.270
Okay. To sum it all up on a really high level I showed this video and some of my classes because it lightens the mood, a little and it explains thing it is from the BBC. It is not a hyper ledger.

158
00:30:36.630 --> 00:30:49.260
Resource I but it is open for anyone to copy for their slides because they do give themselves credit for the whole thing and if nobody minds will just watch that and that's how well and my presentation. So here we go.

159
00:30:54.060 --> 00:30:54.480
Sure.

160
00:30:55.980 --> 00:30:57.240
It went to the money.

161
00:30:59.850 --> 00:31:00.570
To see if I got

162
00:31:02.790 --> 00:31:07.050
If I do, let's shop. No, it updates. It's records.

163
00:31:10.020 --> 00:31:12.720
To show the movement of money to the shops.

164
00:31:17.280 --> 00:31:21.330
Now if you wanted to remove the bank system.

165
00:31:26.190 --> 00:31:28.470
Also the morn cheats one

166
00:31:33.510 --> 00:31:36.180
I wouldn't trust single person.

167
00:31:44.730 --> 00:31:58.170
You don't have a central recorded transactions instead you distributed many, many copies of this lecture around the world. Each owner of each company records every transaction.

168
00:31:58.800 --> 00:32:10.260
So why something using crypto currency, I get the shot my details the shop asks all the bookkeepers aren't good for the money the gatekeepers all check their records.

169
00:32:11.310 --> 00:32:12.450
To see if I have enough

170
00:32:14.670 --> 00:32:16.740
If I do they tell the shot.

171
00:32:19.650 --> 00:32:21.210
And then all of a direct goes

172
00:32:27.330 --> 00:32:35.550
So there's no way that a transaction can make it in if I try to alter a ledger one match all topics.

173
00:32:45.300 --> 00:32:48.360
One of them at random will be given a reward. So

174
00:32:51.780 --> 00:32:52.470
This is

175
00:32:54.060 --> 00:32:59.010
Where and remember all of these bookkeepers for these niches. They're not actually people

176
00:33:11.550 --> 00:33:25.740
Okay, so that was the little cute video, I will post this resource page which just has the links for those three training basic videos. So that's all for my presentation. Thank you for listening and enjoy.

177
00:33:28.470 --> 00:33:40.380
Thanks so much, Bobby. This was engaging and really succinct and I'm sure valuable for everyone. So you said you're going to post this on rocket chat or to the mailing list or perhaps you could send to both

178
00:33:40.590 --> 00:33:42.000
That Bob. Okay, I can do both.

179
00:33:42.360 --> 00:33:43.050
That would be great.

180
00:33:44.160 --> 00:33:55.500
If everyone looks at their chat screen. I've posted how to enroll in the the public sector group mailing list so we can get Bobby's presentation.

181
00:33:56.280 --> 00:34:06.960
That's the last link at the bottom, there's also a chat called rocket chat and there's instructions in this message to everyone about how you can sign up really encourage you, so you can, if you're new.

182
00:34:07.980 --> 00:34:13.800
To this group to be able to keep getting updates about our next meetings, please go to list hyper ledger.

183
00:34:14.430 --> 00:34:24.150
Public Sector working group in sign yourself up for the mailing list so that you always be on top. But wait, does anyone have any questions for Bobby or want to discuss anything about this great presentation.

184
00:34:35.670 --> 00:34:47.820
Alright, well, I thought this was very educational and a nice and clear way to find resources to help explain the concept of blockchain and crypto currency to

185
00:34:48.330 --> 00:34:53.280
non technical audiences. So thank you so much for sharing these really carefully cultivated resources.

186
00:34:53.880 --> 00:35:01.650
To other people find it useful. I mean, mood can talk about this at the end, but be great if you think about for next call what kinds of

187
00:35:02.460 --> 00:35:05.880
Resources would we'd like to get a little taste of next time.

188
00:35:06.390 --> 00:35:13.410
Either as a suggestion for someone to look up and share with us or volunteer to go find some resources yourself because I think it's always helpful.

189
00:35:13.740 --> 00:35:20.100
To be able to talk with non technical audiences. So if you don't know quite yet. Think about it for the end of the call, or it can jump in. Now,

190
00:35:24.780 --> 00:35:28.200
Okay, well, without further ado,

191
00:35:29.700 --> 00:35:39.330
And thanks john for chatting about India. That sounds like a great idea. JOHN, you ready to take it away and present about the work that you're involved in in Canada.

192
00:35:40.710 --> 00:35:41.220
Yes, sir.

193
00:35:42.900 --> 00:35:43.320
Great.

194
00:35:44.640 --> 00:35:45.150
So,

195
00:35:46.380 --> 00:35:52.920
So we're gonna do little joint presentation. My colleague, Elena is on the phone or zoom

196
00:35:54.840 --> 00:35:58.410
So thanks, thanks for those links Bobby that's helpful.

197
00:36:01.200 --> 00:36:05.970
We're going to do a short presentation, we kind of have different lengths. But given the time we're going to give you the

198
00:36:07.110 --> 00:36:17.850
Short version, some slides to provide the sort of context of what the work we're doing is what the motivation is problem we're trying to tackle a little bit about the model that we

199
00:36:18.930 --> 00:36:24.510
Were working with and then we're going to do a live demonstration of the work that we've been co

200
00:36:25.950 --> 00:36:29.970
Co designing and CO developing with our colleagues. So that's all right. I'll just

201
00:36:31.110 --> 00:36:39.840
jump right into this. I can remember it use Powerpoint. Great. So we're talking a bit about. I mean, ultimately what we're talking about here is how the government

202
00:36:40.560 --> 00:36:51.630
Can sort of step up to its role as providing trust to the economy. So in the in the sort of normal economy, you know, government tend to be

203
00:36:52.410 --> 00:37:04.380
A source of trust, we, we, you know, money exists because we say it exists identities are issued and so forth. And so what's missing in a lot of places is this ability to do trust.

204
00:37:05.190 --> 00:37:11.460
Me in the internet. We don't have any trust there and, you know, we talked about the idea that there's really only two

205
00:37:11.850 --> 00:37:21.360
Types of business transaction that occurs on the internet. One is advertising, which is basically exploiting your data without your consent and two is you know you buy shoes.

206
00:37:22.410 --> 00:37:33.840
So you need a credit card and just want to give a bit of a shout out to my colleague, Carol. She's not here, she's on holidays, but she's the registrar and BC. So she's responsible for the organization that

207
00:37:35.070 --> 00:37:45.900
enrolls all legal entities and so she and I have been collaborating closely on this. This is, you know, I work for the office because CIO and Carol works for service PC.

208
00:37:47.460 --> 00:37:54.510
And and so we're going to talk about the problem that we're tackling i mean that's problem that we're tackling as a not a new problem.

209
00:37:55.590 --> 00:37:59.490
We're trying to we're focusing in on business people here for a start.

210
00:38:02.160 --> 00:38:12.660
The goal here is to help business people make it easier to do things with government and to give them the tools that they can go out and interact digitally and the and the world with a

211
00:38:13.800 --> 00:38:14.730
Trustworthy basis.

212
00:38:15.840 --> 00:38:27.390
The typical situation as a business person, you know, lots of start a business or so forth. We're sort of picking a, you know, regulated area like food services here, Mary wants to open her bakery.

213
00:38:28.740 --> 00:38:36.840
Mary is a great Baker, but she's not so familiar with the fact that she had to get a series of permits and licenses in order to open her bakery and this sort of begins.

214
00:38:37.560 --> 00:38:42.510
Kind of a frustrating journey for her, which we have done a bunch of user research.

215
00:38:43.200 --> 00:38:48.960
Here, I'm in Ontario, they've done this. I know in Nova Scotia, you know, we've actually documented their journeys.

216
00:38:49.470 --> 00:38:58.470
And Austin, they're faced with, you know, 468 months delays before they can open because of permitting and licensing requirements that they didn't understand they needed

217
00:38:58.980 --> 00:39:05.370
Once they understand they needed than their experiences still fairly frustrating because they're going to different levels of government.

218
00:39:05.730 --> 00:39:14.760
They're using different modes of delivery could be online where they're managing a series of username passwords could be paper. They're emailing pdfs

219
00:39:15.330 --> 00:39:23.400
And when they add in the fact that they might have other people representing their business on their behalf that even gets more complicated.

220
00:39:23.820 --> 00:39:30.090
And so we're, we're trying to find a way to do this in a digital manner. And so all of this is very difficult.

221
00:39:30.990 --> 00:39:39.660
Presents a barrier to doing business here and it also presents a burden to the government because we're provided with all these sort of disparate sets of evidence.

222
00:39:40.350 --> 00:39:50.550
And we have to spend time and energy, which of course is taxpayer money on verifying stuff that we typically already know, but is in some other part of government.

223
00:39:51.660 --> 00:39:53.850
So what are we doing to to deal with this.

224
00:39:55.110 --> 00:40:11.970
NBC and in some other governments Canada we are you know we're learning how to deliver new services and a more agile ways. So here in BC. Anyways, we have a lab where we have a soul platform as a service infrastructure using Red Hat open shift.

225
00:40:13.140 --> 00:40:15.690
You know, put the techies out there. This is a cooper Nettie

226
00:40:16.890 --> 00:40:35.910
Container orchestration platform. So we're able to deploy applications on this platform and we're able to continuously improve them. We have an almost I think about 20 production application not huge ones, but things like medical plan enrollment groundwater wells carbon trading.

227
00:40:38.010 --> 00:40:53.550
School Bus licensing and so forth. And our all of our work is on this platform and it allows us to Kenny continuously deploy new versions of the software in incremental pieces and we've done hundreds and hundreds of deployments and the last year and a half or so.

228
00:40:54.660 --> 00:41:01.230
And more importantly for this audience and with our colleagues here from Ontario, which I'm very grateful joining in.

229
00:41:01.830 --> 00:41:10.590
we're collaborating across three governments in Canada. So two provinces and the federal government. We have, we have a small team, we are

230
00:41:11.220 --> 00:41:16.770
Contributing a couple of technical resources couple developers and a couple of business folks.

231
00:41:17.220 --> 00:41:27.390
And we are sprinting together in an agile fashion every two weeks, we have a sprint review every Monday, Wednesday and Friday, we have a stand up and we are writing code together and building this

232
00:41:28.770 --> 00:41:32.310
Capability together that we call the verifiable organizations network.

233
00:41:34.350 --> 00:41:41.730
We're also, of course, doing this with blockchain technology. And in this particular case, we're using Hyper ledger indie as our starting point.

234
00:41:42.180 --> 00:41:47.760
But we hope that standards emerged in that area around verifiable credentials and so forth.

235
00:41:48.660 --> 00:42:02.970
So that we can interoperate with other implementations across, you know, the country and across the world, of course, our businesses and our people are not just staying here in DC or Ontario or whatever they're traveling there transacting globally.

236
00:42:04.920 --> 00:42:06.930
We are not talking about

237
00:42:08.040 --> 00:42:17.820
That sort of more wild west aspects of blockchain. So we're not into crypto currencies, or, you know, sort of permission list network here we're looking at networks that are governed

238
00:42:18.285 --> 00:42:28.080
By an understood structure and they're using a combination of human governance and technical governance in order to establish this layer of technical track.

239
00:42:29.820 --> 00:42:42.330
I mentioned that our overall goal of course is to, you know, enable Mary with the digital versions of her credentials, which would include eventually her digital identity which we are on the cusp of here in DC, we have

240
00:42:42.960 --> 00:42:52.200
Services card that we have an identity program where we have enrolled all of our citizens over the last five years into a high assurance.

241
00:42:53.130 --> 00:42:59.970
System and we are in the position to be able to begin shooting digital identity. And that's partly why we're very interested in this sort of

242
00:43:00.390 --> 00:43:08.790
Decentralized identity because we think this can kind of unlock some of the challenges we've had in the past with traditional identity system, but

243
00:43:09.240 --> 00:43:16.200
We're experimenting with the business world first. So this is just an idea that, you know, Mary is going to receive these credentials from various

244
00:43:17.190 --> 00:43:21.990
Organization. In this case, the BC registry and she's going to be able to use those credentials.

245
00:43:22.620 --> 00:43:37.080
At her time her way to to provide them to service providers like banks and other government services, insurance companies other company to have them understand that she is holding a particular permission. So that brings us to the

246
00:43:38.130 --> 00:43:44.100
General model which which we discovered after a project that we did with fabric. We kind of

247
00:43:44.850 --> 00:44:00.360
stumbled into Indy and we discovered this kind of verifiable credentials model, which has the blockchain implementation, as I mentioned, we're using indie right now there are others like various one you poured and a few others.

248
00:44:01.410 --> 00:44:07.650
That are essentially using this decentralized Ledger as a distributed key management system.

249
00:44:08.310 --> 00:44:15.960
So it's very important to understand that in our case, in the case of envy that the ledger is all about helping manage public keys and

250
00:44:16.530 --> 00:44:28.680
Enabling the exchange of verifiable credentials between peers and that no data about the transaction and no men of the personal data or business data is put on the block chain itself.

251
00:44:29.280 --> 00:44:33.300
So kind of a different architecture than and what you know most people are familiar with.

252
00:44:34.230 --> 00:44:42.030
And this pattern of issuers and holders and verifiers turned out to be, I think, a very general pattern. We all have things

253
00:44:42.630 --> 00:45:02.760
That have been issued to us, usually in the form of, you know, documents like a driver's license or some other identity document banking credentials, you know, credit cards marriage licenses, whatever we get these things from trusted issuers and they come in the form of some sort of physical

254
00:45:03.960 --> 00:45:15.570
Manifestation, you know, a card or a piece of paper and we use those things to gain access to services until this pattern repeats itself over and over again. And when we sort of

255
00:45:16.080 --> 00:45:25.320
Realized this sometime about last September, we thought, oh, this, this is something we're very familiar with and government. We have a lot of issuers, we do a lot of verifying

256
00:45:25.890 --> 00:45:43.290
And I think this pattern could be, you know, very helpful, but we realized we had a sort of a problem here. We didn't have any services that we could issue from and we didn't have anywhere to issue, too. So we sort of had a traditional network.

257
00:45:44.910 --> 00:45:45.900
bootstrapping problem.

258
00:45:47.190 --> 00:45:51.090
So that was one we had a little bit of a brainstorm and we had an idea that if

259
00:45:51.540 --> 00:45:59.190
If we do have all these issuers, we could probably give them something to issue to if we sort of looked at this world in terms of business.

260
00:45:59.730 --> 00:46:05.790
Data and public business data in particular we issue all these things to businesses and quite often it's open.

261
00:46:06.510 --> 00:46:13.140
You see them on the walls of restaurants you see them in construction site you can ask the government for them. Sometimes they're posted is open data.

262
00:46:13.830 --> 00:46:19.620
And if we empowered are issuers with a piece of software that allows them to create these verified credentials.

263
00:46:20.040 --> 00:46:33.270
And we gave them a target tissue them to them that might help us bootstrap the supply side of the market. And that's where we came up with this idea of the org book, which is a simple directory of verifiable credentials about businesses.

264
00:46:34.560 --> 00:46:47.550
And it has a sort of a transparency value. And we think it has a sort of a service delivery value, which we're going to demonstrate. So this is just a slide to suggest that you know that we're going to empower these

265
00:46:49.980 --> 00:46:57.210
These issuers with with some software based on Hyper ledger indie to issue credentials to be orange book, and that this is going to create

266
00:46:57.960 --> 00:47:07.650
A new experience for Mary, she's gonna have a somewhat better experience. And this is an intermediate experience where data is getting issue to the org books as a public record.

267
00:47:08.340 --> 00:47:16.620
But eventually, we would like to have Mary have our own wallet, and this is where we're hoping and believing that the private sector.

268
00:47:16.980 --> 00:47:32.850
Is going to provide a variety of products that are citizens and business people can use to receive credentials and to offer credential to verifying organization so that they can conduct their business and a trustworthy way and that's kind of the

269
00:47:34.200 --> 00:47:39.750
Hope that this is going to be helpful to marry and ultimately our citizens. So that's kind of

270
00:47:40.800 --> 00:47:48.060
The motivation. We do have another version of the deck where we actually get into some explanation around

271
00:47:48.450 --> 00:48:03.720
The improvements we think this offers over certain centralized capabilities and the past like one stop and single windows and so forth that in our experience having been very successful and so forth. But we can share that at another time. So, so now I think

272
00:48:04.740 --> 00:48:09.030
It's possible. Maybe Alaina you would step in and

273
00:48:09.870 --> 00:48:10.620
Talk a bit about

274
00:48:10.980 --> 00:48:13.110
Your experience in Ontario and show us the org

275
00:48:14.250 --> 00:48:16.590
Chart. Thank you for the excellent presentation john

276
00:48:17.820 --> 00:48:23.130
I think it clearly states are problem statements and obviously not Tara, we have the same problem too.

277
00:48:24.330 --> 00:48:28.620
Clunky business processes that can be see and other provinces.

278
00:48:32.580 --> 00:48:33.150
Another

279
00:48:36.465 --> 00:48:37.200
Benefit that

280
00:48:38.280 --> 00:48:42.510
We saw in this project was to explore different

281
00:48:43.740 --> 00:48:54.540
Approach to collaboration between different governments, we are very excited to participate in their Agile project management with screens. We do stand up and

282
00:48:57.540 --> 00:49:03.360
And now that new for the government experiences as we do everything in the open, so we have

283
00:49:04.650 --> 00:49:13.920
code base and Github and all our documentation on Google Drive still you know we calibrate and the open will be consulted the

284
00:49:15.360 --> 00:49:17.610
Community international community.

285
00:49:18.540 --> 00:49:19.350
And I think

286
00:49:19.800 --> 00:49:20.610
It's going great.

287
00:49:22.020 --> 00:49:28.800
Another comment, they can make is like one of the reasons why this project looks very appealing to us. It's

288
00:49:30.030 --> 00:49:43.650
It's run. And one of the pilots and they're Ontario's digital identity program that we are working on right now. And while we still kinda working on figuring out the individual against you, the personal I think to

289
00:49:44.730 --> 00:49:51.420
Business identity. Seems like an easy task like that low hanging fruit that there we went after and

290
00:49:53.010 --> 00:49:55.170
kinda helps us gain knowledge.

291
00:49:56.850 --> 00:50:01.980
Of the of using distributed lotion base layer just for identity information.

292
00:50:03.570 --> 00:50:04.950
For businesses and

293
00:50:06.015 --> 00:50:10.020
Without having to tackle this complex problem of verifying

294
00:50:11.490 --> 00:50:25.290
Because, you know, when you talk about people, then you have to go out the biometrics sources of data, which can be you know different governments different databases with the business it's, it seems easy because single

295
00:50:26.310 --> 00:50:34.620
Business registered system in Ontario and that's what we will be using as an issue and service for the Orange Book for Ontario claims.

296
00:50:38.190 --> 00:50:44.760
So maybe without so that you I can show our version of your book. I just want to draw your attention to the fact that

297
00:50:46.050 --> 00:50:51.450
The scene Ontario strive to keep a single code base for the web application.

298
00:50:52.920 --> 00:50:54.810
So that we can continue

299
00:50:55.830 --> 00:50:59.610
Collaboration on the code development. So, you know, any set on carrier put

300
00:51:00.900 --> 00:51:04.110
immediately become available to BC and vice versa.

301
00:51:05.220 --> 00:51:05.490
And

302
00:51:06.630 --> 00:51:11.490
Each of the problems is built a sync customization layer on top of their shared code base.

303
00:51:13.350 --> 00:51:15.480
Different design elements graphics

304
00:51:17.280 --> 00:51:20.640
To give it look and feel of their corresponding province.

305
00:51:22.290 --> 00:51:25.380
And other differences. Is there a difference.

306
00:51:26.640 --> 00:51:44.790
These rules at a decrease in each province of BC I able to post. More information online through there or books or period in Ontario, some of the details are only available on a daily basis. He has to pay to get reports so

307
00:51:46.050 --> 00:51:48.180
We, we obviously couldn't

308
00:51:49.530 --> 00:51:56.850
Compromise. They existence methods. So we only display the publicly available information. So what you see in them to book.

309
00:51:57.150 --> 00:51:58.230
In terms of the data is

310
00:51:59.400 --> 00:52:01.200
Less probably what you see

311
00:52:02.250 --> 00:52:03.420
In basis on book.

312
00:52:05.220 --> 00:52:09.870
But as I said, you know, the main goal was to get an experience.

313
00:52:11.040 --> 00:52:17.640
With the block chain based against the system. We also based in and your business model because we use

314
00:52:18.750 --> 00:52:20.130
public infrastructure.

315
00:52:21.480 --> 00:52:32.700
Hyper ledger in debates block chain network that the sun globally. So it's not the traditional approach when I go and build that only you know see them behind the network.

316
00:52:33.180 --> 00:52:35.370
And then only certain pockets connects us it

317
00:52:35.550 --> 00:52:45.210
So that's the opposite of that we use an existing public infrastructure to support our business process. So that's another new experience for us.

318
00:52:46.530 --> 00:52:48.840
So I'm trying to share my screen with you.

319
00:52:53.460 --> 00:52:55.500
And I will show you

320
00:52:59.400 --> 00:53:00.900
How imperial or books.

321
00:53:02.550 --> 00:53:04.950
Will look wanted goes life.

322
00:53:05.985 --> 00:53:18.780
They'll probably some changes in there you i and maybe the language will change, but essentially it's a searchable database or business registration information.

323
00:53:20.460 --> 00:53:27.150
In the phase one. The only issue verifiable claims for incorporation and

324
00:53:28.470 --> 00:53:32.130
Doing business as claims that comes from Ontario register system.

325
00:53:34.080 --> 00:53:38.940
And what's new is the ability to verify this information online by

326
00:53:40.620 --> 00:53:41.100
Chicken.

327
00:53:42.810 --> 00:53:44.910
The digital signatures against the block chain.

328
00:53:46.170 --> 00:53:48.150
So right now, let's find a record.

329
00:53:50.610 --> 00:53:52.650
So I'm searching for a king.

330
00:53:55.620 --> 00:54:00.990
And I apologize that is still some work in progress on the side.

331
00:54:04.890 --> 00:54:09.900
This is a verifiable claim that contains details of their

332
00:54:11.040 --> 00:54:12.060
Incorporation

333
00:54:13.710 --> 00:54:17.340
For the king continue. So I can look into the details of it.

334
00:54:18.390 --> 00:54:20.040
I see the information about the issue.

335
00:54:23.400 --> 00:54:31.890
And when I click diversify record that their requests will descend to the distributed ledger to modify the cryptographic mosquito associated with the SEC

336
00:54:33.060 --> 00:54:43.140
So keep in mind that the or book is essentially a community wallet. While we are waiting for the technology to catch up to provide the to the mobile based individuals wallet.

337
00:54:43.620 --> 00:54:54.360
So what you see now on the screen will be pushed into a business owner or an authorized representative, the business digital wallet on their mobile phone.

338
00:54:55.980 --> 00:55:06.570
But for now we just build this you know community water that's available online for everybody to access. It's no security, and this is why the information that they put into this community wallet is publicly available.

339
00:55:08.370 --> 00:55:10.980
So if I click the verify record button.

340
00:55:11.985 --> 00:55:18.540
This is when the authenticity and integrity of the record is verified against the block chain.

341
00:55:19.860 --> 00:55:25.530
So when the guests status success. It means the blockchain confirm that

342
00:55:27.930 --> 00:55:33.750
This verifiable claims have been issued by a legitimate issue there Ontario corporate that I just read

343
00:55:35.250 --> 00:55:37.410
The digital signature matches and

344
00:55:39.030 --> 00:55:40.140
The community of wanted to

345
00:55:40.140 --> 00:55:41.910
Told in this information is

346
00:55:43.110 --> 00:55:49.710
has indeed received this claim, and it hasn't been stolen and presented by some other holder.

347
00:55:50.760 --> 00:55:58.140
And then they integrity records the integrity of the record has been compromised. So they're like multi step verification that takes place.

348
00:55:59.250 --> 00:56:03.000
So in the future, when this record resides on a business owners.

349
00:56:04.290 --> 00:56:10.950
Mobile phone and then they share it save it an inspector that comes to check the construction side effect.

350
00:56:12.000 --> 00:56:26.640
Will be able to verify that you know this information is is accurate is legitimate and the businesses good standing. And in the future, we will add other types of claims is a test right now for theatre. We only issue two types of claims.

351
00:56:27.960 --> 00:56:30.000
Legal and corporation and

352
00:56:31.440 --> 00:56:34.710
Or businesses that are not incorporated the issue.

353
00:56:36.090 --> 00:56:41.970
Business name registration claims, but in the future can be various permits and licenses.

354
00:56:42.990 --> 00:56:50.820
Industrial finance can issue a report that the businesses in good standing. And it to all be available in digital form.

355
00:56:52.530 --> 00:57:03.450
And will be under the control of the business owners, so they can share this information with partners customers with government authorities and this information can be verified.

356
00:57:04.830 --> 00:57:06.720
In a secure privacy enhancing wait

357
00:57:09.090 --> 00:57:10.320
Thanks, everyone. Any questions.

358
00:57:13.740 --> 00:57:17.070
But I have a another couple minutes, I can demonstrate

359
00:57:18.300 --> 00:57:21.630
How this can help a business enroll in a government program.

360
00:57:23.160 --> 00:57:30.240
Maybe Elena, you can relinquished screen and I'll show that piece and hopefully we have back to you.

361
00:57:34.020 --> 00:57:35.070
Great. Thanks, Atlanta.

362
00:57:37.020 --> 00:57:43.470
This is Lana dad Winchester Lena. In the meantime, great presentation Alina. I'm very happy to see that both governments work and moving in this

363
00:57:43.470 --> 00:57:44.100
Direction.

364
00:57:45.240 --> 00:57:53.130
Is this part of the open for business initiative and Ontario because I worked in that several years.

365
00:57:53.130 --> 00:57:54.915
Ago, to allow businesses.

366
00:57:55.230 --> 00:58:03.270
Are corporations worldwide globally to be able to do business in Ontario and it could be as simple as perspective for gold.

367
00:58:05.850 --> 00:58:06.900
In the Yukon

368
00:58:07.170 --> 00:58:15.510
Or just opening a new cafe, you know in in in Ontario, or even bc is a fault of that big initiatives.

369
00:58:17.010 --> 00:58:24.570
While we haven't been officially aligned to them yet is a said we run it in the pilot under there on theaters each though I didn't see program.

370
00:58:26.760 --> 00:58:33.090
I think at some point, we may be moving under their umbrella. That's good to know. Thank you. Yeah, yeah.

371
00:58:34.890 --> 00:58:35.400
So,

372
00:58:35.670 --> 00:58:46.200
That's great. We also like to mention, so I can show you know we also can search bc businesses and see various aspects here.

373
00:58:48.090 --> 00:59:03.990
We can see they have different credentials and so forth. But the value here. I mean, there's a bit of public value to that. But the real value is. There's an API to this or book and we have also produced the same call the bond X adapter which allows it's an open source.

374
00:59:05.640 --> 00:59:07.080
Tool that can be

375
00:59:08.100 --> 00:59:26.490
installed and configured to interact with or books and wallets and the sovereign indie ledger. So in this case, the supplier registration service for the Government of Canada is using the adapter and is connected to the Orange Book and business person can add a new

376
00:59:27.510 --> 00:59:38.610
Vendor to their record. So when they do that using this new application, they're presented with a search field. So we can do that same search and it's looking it up live on the

377
00:59:39.030 --> 00:59:47.070
DC org book and they can identify which business. They are adding to their record and when they do this and I pushed this continue

378
00:59:47.760 --> 00:59:57.390
That von X agent does interacting with the Orange Book using the indie protocol asking for a proof. The proof is offered that formation occurs with the crypto

379
00:59:58.050 --> 01:00:04.830
Check using the ledger material and the proof and the forum is populated with the verified data from the Orange Book

380
01:00:05.370 --> 01:00:09.600
So here the really important thing is that the legal name is be authentic legal name.

381
01:00:10.110 --> 01:00:17.910
And this is an area where business people have a lot of challenges and we know that data in basically every database that has a business name cut inaccuracy

382
01:00:18.660 --> 01:00:31.410
So we think that this does two things. One is Mary has little less work to do. And we know that this supplier database now contains highly accurate data, which is really great.

383
01:00:32.850 --> 01:00:47.040
They continue their process enroll. It's supplier and it turns out that you know supplier is a kind of an important aspect in the procurement world and there are other forms of credentials that are

384
01:00:49.200 --> 01:00:50.760
Added to be

385
01:00:51.990 --> 01:00:59.520
Added around a supplier. So I think in this case, we looked at CGS. So if we take a look. Public Works has

386
01:01:02.370 --> 01:01:11.970
Has traded their own Orange Book around suppliers, so we can see that the supplier has been enrolled as a vendor. There are other credentials that they care about in the

387
01:01:12.750 --> 01:01:20.190
In the vendor vendor world around maybe perhaps being an Aboriginal business. It's just special procurement program or being able to bid on

388
01:01:21.060 --> 01:01:31.860
Secure document or a secure procurement, so that's a little bit of a demo, we have a really cool thing that I can't have time to show, but if you look at the video that we

389
01:01:32.400 --> 01:01:40.980
Posted there's a, you know, towards the end, we show about like a multi issue or a situation where we can guide us through an entire permitting experience.

390
01:01:42.150 --> 01:01:45.840
In this kind of decentralized workflow away so we'll leave it there.

391
01:01:47.160 --> 01:01:56.340
appreciate everybody's time and attention and then really appreciate Elena and government material, folks, you know, joining in. So a lot of fun doing this together.

392
01:01:57.780 --> 01:01:57.930
Thank

393
01:01:58.200 --> 01:01:59.670
JOHN. JOHN in Atlanta.

394
01:01:59.700 --> 01:02:01.530
This is such great work. It's an

395
01:02:01.530 --> 01:02:15.510
eye opener for all of us looking to see how far ahead all the two governments are collaborating and it's a very high level of collaboration. I'm very happy to see this demo. And I think it's a value to everyone. But thank you very much.

396
01:02:17.070 --> 01:02:17.580
Thank you to

397
01:02:18.300 --> 01:02:19.350
Read first here.

398
01:02:19.680 --> 01:02:20.700
Just to direct some

399
01:02:20.760 --> 01:02:33.390
Some trafficking and this was absolutely inspiring quickly just looking at our timing here. I know there's many people, including Pete who's already posted something in the chat. Who would be very

400
01:02:33.450 --> 01:02:35.160
Eager to talk more about

401
01:02:35.190 --> 01:02:38.820
This very briefly. So we know exactly how much time we have

402
01:02:39.900 --> 01:02:47.730
Going to jump ahead, and then we'll jump back into Q AMP. A with everyone's permission. Just so we have something lined up for the next call in two weeks.

403
01:02:48.540 --> 01:02:59.610
Is there anybody who so sorry everyone, we're going to have to switch modes, mentally, but will switch right back. Otherwise we won't have an agenda for our next call and this is obviously been incredibly valuable.

404
01:03:00.030 --> 01:03:01.320
Is there anybody here.

405
01:03:01.350 --> 01:03:08.490
Who would be interested in excited or at least open to presenting some work they have in progress.

406
01:03:09.330 --> 01:03:22.860
It doesn't have to be as complete and polish though. It's welcome as this candidate example. But the point here is we all share and learn. Is there anybody who would be willing to share anything that they're working on next time.

407
01:03:29.370 --> 01:03:43.770
It doesn't have to be an actual technical thing. So here's another way of putting it. Would anybody be willing to share their problem that they're trying to think through, and perhaps next time we could have a group of everyone's expertise share and help you think through your problem.

408
01:03:44.910 --> 01:03:56.910
Including just thinking through the uses of hyper ledger block chain for your use case. So. Would anybody like to have the benefit of some expertise on the issues they're thinking about next time.

409
01:04:00.810 --> 01:04:13.470
Rose. This is Pete Teigen, I'd be happy to share a little bit of the journey that we've undertaken with the state of Delaware here in the US, we have a couple of use cases that we're implementing

410
01:04:14.940 --> 01:04:18.450
In it won't get down into the tactical but just really kind of

411
01:04:20.430 --> 01:04:34.320
Introduction for what the use cases that they're looking at. And interestingly enough, it ties directly into john and holiness demonstration that they just did with your Bible organizations. So it would be kind of a

412
01:04:35.370 --> 01:04:38.910
Complimentary demonstrator discussion for the next session.

413
01:04:41.370 --> 01:04:41.910
Yes. Can you

414
01:04:45.480 --> 01:04:53.910
Know, okay well quickly to respond to Pete and then whomever next Pete. That sounds absolutely fantastic. It would be wonderful to have that demonstration.

415
01:04:54.330 --> 01:05:03.330
If you could be so kind as to send a paragraph describing exactly what you just said to the lift server directly to me. Then we'll make sure that that's

416
01:05:03.750 --> 01:05:07.320
high on the agenda for for the next time as this is a very valuable forum.

417
01:05:08.040 --> 01:05:23.220
Anybody else want to jump in about our next call, then we can get into the Q AMP. A, which I'm sure we're all extremely eager to do but anybody who would like to get some advice about something they're thinking about doing or like to share something they're already doing next time.

418
01:05:31.200 --> 01:05:39.360
Can you hear me. Hello. I Camila from Pakistan, and basically, we're here with the team.

419
01:05:41.520 --> 01:05:43.020
You and is doing a

420
01:05:43.170 --> 01:05:45.030
Big project not big project.

421
01:05:45.510 --> 01:06:01.050
But a very interesting project on blockchain introduction of blockchain in land registry and our services, having that I think will discuss with colleagues and maybe next time we'll have definitely we have some

422
01:06:01.140 --> 01:06:02.760
Problems maybe to share

423
01:06:03.210 --> 01:06:07.800
We had just at the beginning of the initial stages of the process between and we may have some

424
01:06:07.830 --> 01:06:09.000
issues to discuss

425
01:06:09.210 --> 01:06:10.920
And maybe we even present

426
01:06:13.020 --> 01:06:15.870
We don't have something to show yet but maybe we will

427
01:06:15.960 --> 01:06:17.160
Present some kind of

428
01:06:17.190 --> 01:06:19.380
Challenges we're encountering go

429
01:06:20.010 --> 01:06:21.960
At least raise some problems if

430
01:06:21.960 --> 01:06:22.680
Possible.

431
01:06:23.790 --> 01:06:27.420
Let us discuss with the RC office and the colleagues afterwards but

432
01:06:27.480 --> 01:06:29.760
Most probably will come up with something next time.

433
01:06:31.080 --> 01:06:35.670
That would be terrific. I'm sure everyone here would love to hear what you're thinking about in Uzbekistan.

434
01:06:35.700 --> 01:06:36.060
And

435
01:06:36.045 --> 01:06:37.080
Be willing to share their

436
01:06:37.080 --> 01:06:41.160
Experience. Yeah, that'd be great. Okay.

437
01:06:45.330 --> 01:06:47.310
Anyone else alright well

438
01:06:48.510 --> 01:06:52.380
Just really encouraging everyone if you're not already on the mailing list.

439
01:06:52.470 --> 01:07:01.020
Please, please sign yourself up. It's in the chat to the right, at least on my screen, but that will ensure that you continue to get updates.

440
01:07:02.340 --> 01:07:07.770
So we can all share all this valuable information and chameleon. There was back team if you could please email me.

441
01:07:08.100 --> 01:07:16.500
About whether you'll be able to participate in two weeks, then that would be fabulous. I'm sure many people here have a lot to share. All right, I will step away.

442
01:07:17.040 --> 01:07:30.870
And now that we have our agenda for next two weeks and go into Q AMP. A I moving to keep this running until people have to go. I don't know. JOHN AND A Lena how long you can stay but I'm sure people have a lot of questions.

443
01:07:33.990 --> 01:07:35.760
Sure, that's fine. Yep.

444
01:07:36.330 --> 01:07:38.190
Peter Pete had one here.

445
01:07:39.330 --> 01:07:57.300
That we answered in the in the chat around, you know, different kinds of statements like in good standing. So that's totally possible. The other thing I didn't mention is, and we think is going to be a really great feature of your book, even when businesses hold their own credentials that

446
01:07:58.530 --> 01:08:08.700
You know issuers can keep issuing to the org book changes and in state of a parameter license or, for example, we're going to be constantly monitoring the registry.

447
01:08:09.840 --> 01:08:15.540
With the business registry, so that if a name change that occurs or if a business status changes to inactive.

448
01:08:16.110 --> 01:08:31.260
Credential be reissued to the order book. And that means that all these other services can monitor it plan to implement something like a Github web hook so that signals can be made about changes and stay really hard problem right now that we don't

449
01:08:33.030 --> 01:08:38.970
We can't solve very well. And therefore, you know, data and things go off the rail often

450
01:08:47.070 --> 01:09:00.480
That's a tremendous solution to an age old problem everywhere about how to propagate changes and status, that's very exciting. Who else has any questions that they'd like to ask or chat.

451
01:09:13.080 --> 01:09:19.530
Any program questions or technical questions or even clarifications, no question too small.

452
01:09:26.010 --> 01:09:38.670
Oh lows. Hi, this is Leonard, I guess, today was it's all related to the demos of just add, but I guess. Today is the final day for completing to infuse for the full them.

453
01:09:40.110 --> 01:09:41.280
Presentations and

454
01:09:42.870 --> 01:09:50.610
In Switzerland. I don't remember the date for it but i i did as many as I could because I'm also trial and and

455
01:09:51.630 --> 01:10:00.060
And work with a few new client. So I've done as much as I can. But if today's the cut of day, then I think I didn't do 300

456
01:10:01.230 --> 01:10:04.860
But I got just over 200 will doubt suffice.

457
01:10:04.920 --> 01:10:05.250
Now,

458
01:10:08.670 --> 01:10:13.950
That sounds very impressive. And unfortunately, I very low context about the review process.

459
01:10:15.510 --> 01:10:16.740
So I

460
01:10:16.800 --> 01:10:22.560
Okay, well, that's okay, because I think we'll hear back from wherever you might say,

461
01:10:23.640 --> 01:10:25.860
Determine which ones get into

462
01:10:27.060 --> 01:10:29.190
The three day presentation.

463
01:10:31.320 --> 01:10:36.660
For our for them. So that should be OK. I just thought, if you could give us an update, but that's all right. Thanks.

464
01:10:37.800 --> 01:10:41.100
Thank you. Leonard sounds like you've been very productive and unfortunately I'm

465
01:10:41.130 --> 01:10:49.230
I have, I have done my best. And I think all of all of us have done what we could self. Thanks for giving us the opportunity to a few

466
01:10:50.790 --> 01:10:58.650
Very impressive. Leonard it. Anybody else like to add any last questions or comments about this presentation or anything else.

467
01:11:04.290 --> 01:11:10.920
Well, I'll just like to say john and Elena, the standard and quality of work that you presented is

468
01:11:12.210 --> 01:11:20.910
impeccable. I couldn't have done better. So I would I really on behalf of everyone. I really do. Thank you for that level of foster laughs and fallen.

469
01:11:21.840 --> 01:11:26.760
And the level of interoperability, it will provide for Ontario and BC.

470
01:11:27.000 --> 01:11:32.070
And all the other governments provincial governments, I think in the near future. So thanks, everyone, very much.

471
01:11:33.570 --> 01:11:33.810
Thank you.

472
01:11:35.640 --> 01:11:36.120
Thank you guys.

473
01:11:39.960 --> 01:11:53.010
Any last comments I think also that, you know, for those who might have questions afterwards, presumably john in Atlanta, you would be happy to receive questions from people through the

474
01:11:53.880 --> 01:12:04.560
Mailing list or through the chat. Perhaps if they have more specific questions, once they've collected their thoughts on how you implemented this as it seems to be in a very coherent, they thought through.

475
01:12:05.820 --> 01:12:10.350
And and actually very impressive model partnership between multiple

476
01:12:10.350 --> 01:12:11.280
Parts of government.

477
01:12:13.260 --> 01:12:22.710
Yeah, for sure. And you know I posted a few links in there with some more details and all of everything we showed you today is available through

478
01:12:23.520 --> 01:12:33.960
On the internet through a web site that we have, you know, sort of, it's a bit of a modest lives, but in all our curriculum mentioned all the code is open and it's all

479
01:12:35.100 --> 01:12:41.370
deployable into Docker containers and open shift containers and Ontario's working on an IBM Cloud and

480
01:12:43.260 --> 01:12:50.190
So, you know, we're encouraging anyone one to take a look and you know join the verifiable organizations network.

481
01:12:51.330 --> 01:13:01.680
Yes, thanks. JOHN and if I could just add to that will all looking at how well these platforms will scale and perform, you might say.

482
01:13:03.120 --> 01:13:11.250
Safe all the governments of Ontario did not have their own copy of the blockchain. But it was one distributors.

483
01:13:11.880 --> 01:13:25.620
blockchain setup, which is what block chains all about the scalability and the performance because that is always the but bear in any large and so will be very happy to follow talks to see how you guys able to scale and ensure performance.

484
01:13:26.880 --> 01:13:29.160
Over time, I don't think it's gonna be an issue because

485
01:13:29.670 --> 01:13:36.870
In the end, model. The only pieces of data that go on the ledger and we're planning to use the sovereign provisional venture, which has already got

486
01:13:37.410 --> 01:13:46.380
3040 operators is the key materials and schema definitions and so forth all of the interactions actually occur peer to peer

487
01:13:46.920 --> 01:13:57.000
So we're going to issue somewhere on the order of a million plus credentials from the registry to the Orange Book. But that happens directly between those two systems.

488
01:13:58.440 --> 01:14:06.270
And so that's just normal computing scaling, so there won't be any issue there it'll take some time, but it's a one time cost.

489
01:14:08.250 --> 01:14:09.030
So I don't. I don't.

490
01:14:10.170 --> 01:14:10.830
I'm not trying to

491
01:14:11.430 --> 01:14:13.080
And it sounds good that you

492
01:14:13.110 --> 01:14:28.350
Move your container lies and let the same via doc and Cuban as kids and movement into the IBM Cloud. So that was certainly and show a much higher level of performance and scalability over time and happy to hear that architectures being adopted.

493
01:14:31.080 --> 01:14:46.320
Yeah. JOHN. This is my i joined in just a few minutes back in the gym or you're discussing. You were mentioning about the public website where we can access that information architecture of your solution. Could you just being that

494
01:14:48.000 --> 01:14:49.110
What is the URL.

495
01:14:49.410 --> 01:14:49.890
For the

496
01:14:53.340 --> 01:14:57.360
main one is Vo n dot Pathfinder

497
01:14:59.070 --> 01:15:06.660
BC dot ca I posted it in the chat for zoom and also in Hyper ledger rocket chat.

498
01:15:07.380 --> 01:15:10.020
Yeah, I'm just, I'm not in the chat so it's

499
01:15:11.160 --> 01:15:11.520
Okay.

500
01:15:11.610 --> 01:15:12.750
Yeah, we will end.

501
01:15:14.640 --> 01:15:15.420
Pathfinder

502
01:15:16.470 --> 01:15:17.790
Doc Pathfinder or

503
01:15:18.930 --> 01:15:19.125
Yeah.

504
01:15:21.060 --> 01:15:24.120
PC God see a lot bc dot

505
01:15:25.770 --> 01:15:26.220
CA.

506
01:15:27.930 --> 01:15:28.890
For Canada. Yeah.

507
01:15:30.270 --> 01:15:30.930
Thank you very much.

508
01:15:32.220 --> 01:15:32.640
No problem.

509
01:15:35.985 --> 01:15:49.200
Last but not least, a john in Atlanta or the presentations that you shared things that can be put on public repository for the public sector working group or these internal and just for the

510
01:15:49.200 --> 01:15:51.630
Weapon. Yeah, no, no.

511
01:15:52.560 --> 01:15:55.650
Okay, no, it seems like it would be quite great if we

512
01:15:55.650 --> 01:16:06.900
Could start building out on the wiki all of these presentations so that people who miss them could come back to them. So we'll circle back about that. But thank you for being willing to share these

513
01:16:06.900 --> 01:16:08.430
Materials. Yeah.

514
01:16:08.550 --> 01:16:09.390
That would be awesome.

515
01:16:09.900 --> 01:16:10.080
And

516
01:16:11.310 --> 01:16:12.000
By the people

517
01:16:13.080 --> 01:16:13.830
Yeah, is the

518
01:16:13.860 --> 01:16:16.110
Video of the demonstration recorded

519
01:16:18.420 --> 01:16:18.990
Recording

520
01:16:20.550 --> 01:16:22.770
Okay, so they can record it and I've also

521
01:16:26.130 --> 01:16:38.640
I also included a link on the rocket chat, where we did a seminar. I mean, I did a seminar. A little while ago for sovereign players like a 40 minute and it goes into more detail and add some more demonstrations in there as well.

522
01:16:41.340 --> 01:16:43.080
It's one right we all in

523
01:16:44.460 --> 01:16:46.410
The LM yeah yeah

524
01:16:49.980 --> 01:16:51.420
Enrolled in the rocket chat.

525
01:16:52.950 --> 01:16:57.360
No, not yet started logging into these calls, we need to create a rocket

526
01:16:58.170 --> 01:17:00.030
Or you enrolled on the mailing list.

527
01:17:03.870 --> 01:17:05.970
I'm not sure, you know,

528
01:17:07.845 --> 01:17:09.360
This is the first column logging in, so

529
01:17:09.630 --> 01:17:10.560
Thank you for joining.

530
01:17:11.520 --> 01:17:13.590
Are you able to find the links.

531
01:17:13.590 --> 01:17:20.460
To get into the mailing list because that that will be an announcement for every single one of these calls, which is every two weeks.

532
01:17:21.090 --> 01:17:23.310
Every two weeks. Okay. Yeah, I'll sign up into that.

533
01:17:24.690 --> 01:17:24.870
Yeah.

534
01:17:25.470 --> 01:17:27.480
And you'll be on top of everything that would be great.

535
01:17:28.410 --> 01:17:30.060
Thanks for us, please. Thanks.

536
01:17:30.870 --> 01:17:35.520
Um, and rose the surveys still live with new members want to take it.

537
01:17:36.630 --> 01:17:37.620
That's a great idea.

538
01:17:37.650 --> 01:17:38.430
Yeah, sure.

539
01:17:39.120 --> 01:17:50.640
Um, perhaps, Bobby, would you be willing to remind the group, maybe in a day or two. One some new members have signed up a link to the survey, would you mind sharing it with everyone in

540
01:17:51.360 --> 01:17:52.050
The group email.

541
01:17:52.320 --> 01:17:57.780
That would be great. Like you there maybe beginning of next week. Once everyone signed up. That would be really useful. Thank you.

542
01:17:57.810 --> 01:17:58.380
No problem.

543
01:18:04.650 --> 01:18:12.330
Great. Anyone else want to chime in with any questions ideas contributions before we wind down today.

544
01:18:19.500 --> 01:18:32.010
Okay, we're looking good. Again, many, many, many thanks to our presenters today. Bobby miscarried, as well as john in Atlanta from respective governments in Canada in

545
01:18:33.000 --> 01:18:43.740
BC and Ontario for sharing. But some broad educational materials that will really help articulate the value proposition of blockchain and

546
01:18:44.610 --> 01:18:55.110
A very advanced and just about to come live, real world use case on a large scale that shows how this can work in action. So this has been extremely valuable for everyone here.

547
01:18:55.500 --> 01:19:04.560
I'm really looking forward to us all as our community develops being able to use one another as resources as we think through our respective projects.

548
01:19:05.100 --> 01:19:18.240
At any stage of development from conceptual too deep in the weeds for technology and programmatic. So thank you. This has been great and extremely excited about next call from

549
01:19:18.900 --> 01:19:33.090
The Uzbekistan group as well as from IBM to both learn about some new use cases as well as work as a group to help our new friends understand how block chain could work.

550
01:19:33.180 --> 01:19:35.070
In their land registry program.

551
01:19:35.520 --> 01:19:45.090
So with that, I'm going to say thank you to everyone. And if anyone wants to say goodbye or anything else. Please go ahead. But otherwise, thank you so much, really very appreciative.

552
01:19:45.870 --> 01:19:50.430
I would say lows and the rest of the team mean and all of us.

553
01:19:51.960 --> 01:19:57.960
An excellent body to be to get to work with and I wish you all a wonderful day, and a great weekend. Thanks.

554
01:20:01.920 --> 01:20:02.640
Hi everybody.

555
01:20:07.980 --> 01:20:09.450
Bye bye. Thank you very much.

556
01:20:10.620 --> 01:20:11.730
Thank you. Bye.

557
01:20:12.210 --> 01:20:13.140
everybody. Bye bye.

558
02:08:37.890 --> 02:08:38.610
Another option.

559
02:11:25.980 --> 02:11:27.060
Here.

560
02:11:28.440 --> 02:11:29.460
In the chat.

561
02:12:05.850 --> 02:12:06.690
Okay.

562
02:12:08.220 --> 02:12:25.890
Wanting folks feel free to use what I encourage video chat if anybody is willing to do that with me, just to kind of build community and be able to see who we're talking to you. I'm going to share my screen to show the antitrust policy will read through that and

563
02:12:28.770 --> 02:12:31.710
We will get get going. So once again.

564
02:12:57.630 --> 02:12:58.020
Okay.

565
02:13:01.890 --> 02:13:12.450
So Linux Foundation meetings involved participation by industry competitors and it is the intention of the Linux Foundation to conduct all its activities in accordance with applicable and a trusting competition law.

566
02:13:14.430 --> 02:13:19.500
It is there for extremely important but attendees adhere to meeting agendas and be aware of and not

567
02:13:19.920 --> 02:13:26.430
Participate in any activities that are prohibited under applicable USD federal or foreign entity trust in competition loss.

568
02:13:27.150 --> 02:13:33.540
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities.

569
02:13:33.900 --> 02:13:42.630
are described in the Linux Foundation, and I trust policy available at w w w dot Linux Foundation org forward slash antitrust

570
02:13:43.140 --> 02:13:59.520
Policy, you have any questions about these matters, please contact your company council or if you are a member of the Linux Foundation, feel free to contact Andrew up to grow of the firm and gizmo or have to grow up LP, which provides legal counsel to the Linux Foundation.

571
02:14:02.310 --> 02:14:03.630
Get that part out of the way.

572
02:14:06.630 --> 02:14:12.480
It looks like a small group so far today I'm anticipating some others will will join us, but

573
02:14:14.250 --> 02:14:20.160
For the agenda today. My thoughts were to just kind of go over the healthcare working group meeting that was last Friday.

574
02:14:20.700 --> 02:14:32.970
We had some interesting conversations there and I sent out a summary via email but wanted to check if anyone has any questions or and I have a small update just regarding our labs application for the donor milk.

575
02:14:34.200 --> 02:14:41.760
Use case that I can go over and then I was hoping that we could review so Anton sent

576
02:14:42.960 --> 02:14:46.230
A slide deck with a workflow.

577
02:14:48.000 --> 02:15:01.500
And that is in the US or in the business case that I put in the chat window. So I wanted to start collecting questions and discussing that a little bit and then ultimately a talk about

578
02:15:02.610 --> 02:15:17.490
The timeline and still trying to work towards having a proof of concept for the global forum in in December. And was there anything else that folks wanted to chat about today.

579
02:15:21.720 --> 02:15:22.590
Sounds good.

580
02:15:22.650 --> 02:15:24.030
Sounds like a full plate, actually.

581
02:15:25.380 --> 02:15:25.920
Yeah, right.

582
02:15:26.970 --> 02:15:31.500
The agenda is very tight so if it's a small group, maybe it's more feasible. So

583
02:15:33.180 --> 02:15:36.270
John you're in a very sunny place and I don't know if I

584
02:15:38.130 --> 02:15:41.220
Well that's why they want to go on video chat, because they might, you know, upset some

585
02:15:41.280 --> 02:15:43.020
People saw but I live in West Palm Beach, Florida.

586
02:15:43.830 --> 02:15:44.850
Now it looks amazing.

587
02:15:51.840 --> 02:16:00.630
Okay, so in the healthcare working group meeting on Friday, we had representatives, both from medical Greenwich Brian had

588
02:16:01.710 --> 02:16:09.780
Brought to the group around an EMR block chain based EMR system that seemed very relevant for the

589
02:16:10.800 --> 02:16:18.270
Kind of connecting patient data across silos use case that we were looking at. And so we had Dave

590
02:16:19.470 --> 02:16:28.710
He gets a bit from from medical chain come and talk to us about what they're doing and answer some questions and you know we left that conversation really with

591
02:16:29.910 --> 02:16:39.240
Dave having some additional questions about how we might be able to collaborate. It sounds like they were rolling out a pilot in the UK last meets this week.

592
02:16:39.990 --> 02:16:51.240
And so there it did seem like there would be potential for the the subgroup to engage in different components, but we've really kind of ask Dave to get back to us with

593
02:16:51.990 --> 02:17:00.150
Areas were eating sweet we be able to contribute. I've connected him with neat and just ask them to send any questions along

594
02:17:01.380 --> 02:17:16.320
So my thinking for that use cases that we kind of put it on the back burner until we hear from Dave or get a little bit more direction, about how we want to engage their. That being said, and enough people saw what Johnson out about

595
02:17:17.460 --> 02:17:27.360
Kind of businesses companies in the the healthcare block chain space. There are a lot of folks working in the space. So if people are passionate about.

596
02:17:28.500 --> 02:17:33.810
Driving that conversation, for there is an EMR subgroup, and there's

597
02:17:33.990 --> 02:17:34.200
There's

598
02:17:34.290 --> 02:17:36.810
opportunity there. So, you know, don't

599
02:17:38.280 --> 02:17:41.400
Don't be shy about wanting to kind of follow that path.

600
02:17:41.970 --> 02:17:42.210
Folks

601
02:17:44.820 --> 02:17:45.900
And then we had

602
02:17:46.020 --> 02:17:48.030
Anton and Ron from

603
02:17:48.090 --> 02:17:49.620
Rabbit healthcare, who have

604
02:17:49.620 --> 02:17:52.560
The donor milk and mother's milk.

605
02:17:52.740 --> 02:18:08.550
Mobile applications in Southern California, and who were working with on this donor milk proof of concept work and the recording is now up on on the website. But that's kind of just a high level summary of that.

606
02:18:08.760 --> 02:18:09.420
Conversation.

607
02:18:10.500 --> 02:18:20.160
We also went through a lads application with hyper ledger to get a github repo. So a code repository for the proof of concept.

608
02:18:21.030 --> 02:18:38.610
I worked on that this week, my Github skills are rather poor and that became rather evident. This week, but I think we're at a point where we should be getting on repost that up in the next couple days. So that will be a place for the code that Angela has put together so far.

609
02:18:38.880 --> 02:18:40.950
And then where we can start building

610
02:18:41.940 --> 02:18:43.200
Any questions there.

611
02:18:47.880 --> 02:18:52.770
Courtney. Hi, everyone. I'm happy to hear that. That's, that's getting closer.

612
02:18:54.330 --> 02:18:54.810
Yeah.

613
02:18:56.160 --> 02:18:56.910
It's interesting.

614
02:18:57.330 --> 02:19:09.150
I mean, you basically have to fork. The, the application repo and and add a file to and then do a pull request. And so I learned a lot in the process, but

615
02:19:09.840 --> 02:19:20.430
Tracy and and the folks have been really helpful. But so we're getting closer. But I do not have Tracy so that she was in for today to get that setup for us. So I will keep you guys posted

616
02:19:21.930 --> 02:19:22.080
Are

617
02:19:24.690 --> 02:19:32.790
Great. So moving on to, well, actually I should check. Anyone else have questions around that summary from

618
02:19:33.840 --> 02:19:35.100
Healthcare working group meeting.

619
02:19:37.440 --> 02:19:40.500
I do have a quick question from the the

620
02:19:41.730 --> 02:19:42.690
Large meeting.

621
02:19:43.740 --> 02:19:53.880
I was kind of surprised when I asked you know where their code resides. And their answer was, well, we're not really sure if we're going to make our code available.

622
02:19:55.710 --> 02:19:57.720
I didn't even know that was an option.

623
02:19:59.130 --> 02:20:02.760
If you're part of, you know, the hyper ledger and Linux.

624
02:20:03.900 --> 02:20:11.550
combo that everything had to be open source that they basically are taking a private company kind of model.

625
02:20:13.170 --> 02:20:19.350
So that was that was surprising because I know we have that conversation as to whether or not we were you know

626
02:20:21.390 --> 02:20:23.610
How, how, what we were building was going to

627
02:20:23.640 --> 02:20:24.510
Look in the end.

628
02:20:27.480 --> 02:20:30.540
And an open source was like the only way

629
02:20:32.520 --> 02:20:34.050
That was surprising.

630
02:20:34.890 --> 02:20:37.140
Yeah, and that's a really good point and

631
02:20:37.950 --> 02:20:46.380
So the only distinction that and I have no expertise in this at all, but the distinction that I saw was then taking the open source.

632
02:20:47.370 --> 02:21:06.960
Software from the Linux. Actually, I don't know, taking, you know, the hyper ledger platform and then building their product outside of the hyper ledger umbrella, not as a project, not as a lab, whereas what we're trying to do is actually work within that framework to

633
02:21:06.960 --> 02:21:07.380
Leverage

634
02:21:08.490 --> 02:21:12.450
The infrastructure and should create that. But I don't know if anyone else.

635
02:21:12.660 --> 02:21:14.580
Has any feedback on that.

636
02:21:22.200 --> 02:21:32.130
So I guess, in the end, and we may never see their code. I get to go to the take that I got from that you may never people for code on

637
02:21:34.380 --> 02:21:41.250
I would agree with with that. And that's something that's a really good point that I can make sure to follow up with

638
02:21:41.880 --> 02:21:48.480
With Nate on is, you know, and I think we're still trying to get quick answers to Anton's questions around

639
02:21:48.900 --> 02:21:56.220
You know, what does the, you know, if we do this proof concept for the donor milk. What is the the privatization look like

640
02:21:56.880 --> 02:22:10.860
They are there opportunities for funding who determines who is that entity that manages the move from the proof of concept out into the market and so I think there's a lot of questions in that space, but

641
02:22:12.030 --> 02:22:19.950
It would be good to understand the mechanism for which you know medical chain is leveraging not hyper ledger technology and

642
02:22:21.060 --> 02:22:24.930
Infrastructure, but not allowing access to the code base.

643
02:22:26.850 --> 02:22:27.210
Yeah.

644
02:22:30.615 --> 02:22:30.840
Well,

645
02:22:30.930 --> 02:22:32.220
So, so just to chime in.

646
02:22:33.210 --> 02:22:38.940
I'm pretty, pretty sure we're looking at Apache two licenses for hyper ledger.

647
02:22:39.300 --> 02:22:50.760
Frameworks. And so that's pretty permissive which basically means you can use the software off the shelf and unless you're making anything specific. Any changes specifically to the the

648
02:22:51.930 --> 02:22:55.290
The code base. Specifically, not, not anything on top of that.

649
02:22:56.370 --> 02:23:08.580
You don't necessarily have to make that open source. So it's possible that you know we may not see code base coming back from hyper electric projects, if they decided to keep it private.

650
02:23:11.070 --> 02:23:19.620
So sorry. What was the distinction you you mean they're like the change to the code base itself versus building something on top of that.

651
02:23:20.100 --> 02:23:22.440
Right, so, so if I wanted to make a change.

652
02:23:22.560 --> 02:23:36.000
To the actual code in Hyper ledger. So, so say add a feature or at functionally to hyper ledger. The framework proper so you know we could talk about fabric. For example, I, I'm pretty sure that has to come back.

653
02:23:36.870 --> 02:23:39.180
To the hyper ledger maintainer.

654
02:23:39.840 --> 02:23:51.450
But if I'm making if I'm building with that product I don't necessarily have to make that openly available. And that's just the definition of how a permissive

655
02:23:52.110 --> 02:24:04.260
License works patchy to, if I recall is probably the second most permissive behind MIT license or recall. So, you know, MIT, just to put in some contexts.

656
02:24:04.890 --> 02:24:13.590
Basically says you can do whatever you want to it and short of, you know, stepping on on any existing licenses in the in the product.

657
02:24:14.190 --> 02:24:26.250
I don't really care what you do code base, which means that you can go close source if you want, and with MIT license. It really doesn't matter now Apache to, like I said, I'm pretty sure

658
02:24:27.360 --> 02:24:36.570
Has a minor distinction there that says that if you're making changes specifically to the code base in this case will say fabric. It does have to come back.

659
02:24:38.160 --> 02:24:55.230
But anyway, so. So the takeaway is that in the context of what we're talking about, given that we're looking at open source that doesn't necessarily mean that we have or will have accessed deep access to code base for a company

660
02:25:03.270 --> 02:25:11.130
Great, thank you so rich and made a good point. I think we do have some new folks on the call today least names that don't look familiar to me.

661
02:25:11.760 --> 02:25:21.240
So for new folks that are on, welcome. Thank you for, for joining the the patient numbers of group meeting I just to give you guys a very short.

662
02:25:21.840 --> 02:25:38.970
Kind of context setting piece we are subgroup of the healthcare working group within the hyper ledger umbrella, which is part of the Linux Foundation. And while the the working group at large is more of

663
02:25:40.830 --> 02:25:45.750
What I've seen so far as kind of a place for thought leadership and discussion and bringing in

664
02:25:47.970 --> 02:26:06.450
Speakers and having dialogue, the sub groups were actually released this subgroup. I would say specifically is looking at trying to actually operationalize. Some of the use cases that have been created by the the healthcare working group and so

665
02:26:07.980 --> 02:26:16.950
I will actually put the the wiki in the chat box for the working group itself and that links to

666
02:26:18.330 --> 02:26:29.730
All of the use cases and specifically the donor milk and the connecting data across silo use case that we have mentioned here so far.

667
02:26:30.870 --> 02:26:31.110
And

668
02:26:32.250 --> 02:26:39.900
I would also like to plug. We have a wiki page for folks that want to be identified via the wiki as members of the

669
02:26:40.500 --> 02:26:52.980
Of this subgroup specifically. So if folks want to put or just like let me know either via chat or edit the wiki themselves and put your linkedin profile or however you want to be reached out to you, please feel free to do that.

670
02:26:55.680 --> 02:27:03.180
I guess all I'll stop there. Are there any new folks on the line that have questions or would like a little bit more information before he will flourish.

671
02:27:08.130 --> 02:27:09.960
So I'll just jump in. So I'll just

672
02:27:10.080 --> 02:27:24.720
I'll just also plug our rocket chat. So we've got a slack light channel for for this working group to healthcare working group and and it would be great to keep people sort of looked into that as well. Yes, great point.

673
02:27:24.750 --> 02:27:28.920
Let me put that in the chat box as well.

674
02:27:30.570 --> 02:27:31.110
There's very

675
02:27:36.105 --> 02:27:36.840
This is ready.

676
02:27:37.740 --> 02:27:41.820
Have a good question. New for the first time. This is my first column taking on the working group.

677
02:27:43.650 --> 02:27:51.000
Thank you. And I'm new to block chain space in a hyper ledger been following it on reading stuff, but then when I found out this working group so

678
02:27:51.450 --> 02:28:05.250
I thought I could learn more from here. So it's going to be a mutual interest from going to learn from you guys talking and any way I can jump in. I'll surely jump in and help out the working group impossible. No.

679
02:28:06.870 --> 02:28:12.090
That's about me. And one thing I had his back the rocket chat. Is there an app to use it from the phone or is it

680
02:28:13.620 --> 02:28:27.720
was great. It was just gonna ask that I have not successfully been able to get rocket chat on my phone and I don't know if anyone else has had success with that I've only been able to use it via the browser.

681
02:28:28.350 --> 02:28:31.200
So, at least on Android, there is a rocket chat app.

682
02:28:32.250 --> 02:28:42.990
You can I, I, personally, generally don't use Slack or record chat on my iphone. It's just too hard to maneuver around. And of course, you know, there's the web app.

683
02:28:44.700 --> 02:28:47.730
For I think slack. I don't know, for I could chat has standalone web app.

684
02:28:48.810 --> 02:28:50.580
And of course, there's the website. It's so

685
02:28:50.940 --> 02:29:01.860
Yeah, I guess I did. Download the the the rocket chat app. I have an iphone but my credentials, my Linux Foundation credentials didn't seem to to work so

686
02:29:03.270 --> 02:29:13.230
If anyone has access to that I will try it again because I did also have a bit of a password kerfuffle on try but ready as as a right now. I don't. I haven't seen that.

687
02:29:13.620 --> 02:29:13.920
Working

688
02:29:16.200 --> 02:29:22.890
Hi this is Jeff just getting back to something rich mentioned about the licensing would seem to me that

689
02:29:23.100 --> 02:29:23.490
If

690
02:29:24.510 --> 02:29:30.960
We're not going to have be working with open source code, trying to operationalize something as a group will be impossible.

691
02:29:33.120 --> 02:29:38.160
To be a characteristic a criterion for selection of whatever we decide to work on.

692
02:29:38.670 --> 02:29:50.280
Yeah, no. That makes sense. I mean, I think we have talked about whatever we make as far as the proof of concept being being in an open source product.

693
02:29:51.480 --> 02:30:02.160
What that means for moving something like our proof of concept into market. I don't know what that looks like. But I think for these conversations and working within

694
02:30:04.080 --> 02:30:06.840
It would definitely be an open source effort.

695
02:30:09.360 --> 02:30:14.700
Yeah, I think you're right. Marissa, that the way that I would approach it. Jeff, and I've done this in another working group.

696
02:30:15.720 --> 02:30:33.270
Situations basically anything that we do. It's sort of in this public space generally is a proof of concept and. And the idea is to collaborate on this product and then from that point usually companies, you know, can take it and work with it, to the extent that they want to

697
02:30:34.410 --> 02:30:35.580
And it may be that they they

698
02:30:35.760 --> 02:30:40.740
You know, they take an extra 90% to the product eyes it under their label.

699
02:30:41.760 --> 02:30:50.700
It gets to be a little sticky going forward. Since we're sort of operating under the auspices of a nonprofit organization and actually to that point.

700
02:30:51.540 --> 02:31:04.020
morose and I are working to bring in an attorney who was it who actually specializes in technology and we're hoping to get them on either sub forum or the the the proper

701
02:31:05.370 --> 02:31:12.150
Health care. Working Group forum for hyper ledger in the next couple of weeks, so that we can sort some of this stuff out. But that said,

702
02:31:13.140 --> 02:31:26.670
In the past we've never had an issue where this has been a hang up. What it really means is we just have to be sensitive to the notion that we're we're working on something that's collaborative and really can never be a an entity own product.

703
02:31:28.590 --> 02:31:32.100
You can only go so far before someone decides to take it and use it for

704
02:31:32.100 --> 02:31:39.120
The for their own purposes. So we're really when we talk about what we're product sizing. It is really going to be a proof of concept.

705
02:31:40.230 --> 02:31:42.720
And and i don't know if we want to push it much for the

706
02:31:48.300 --> 02:31:52.380
Great. Any other comments or questions before we move on to the

707
02:31:58.620 --> 02:31:59.520
Rapid healthcare.

708
02:32:00.870 --> 02:32:04.260
Just wanted to make sure everyone had a chance to review the

709
02:32:06.060 --> 02:32:07.800
The architecture diagram.

710
02:32:09.000 --> 02:32:16.020
Anyone had any feedback in relation to that, whether it was clear whether we didn't make any further.

711
02:32:17.400 --> 02:32:18.810
I'd love some feedback on that.

712
02:32:20.250 --> 02:32:21.510
And here, let me

713
02:32:21.510 --> 02:32:30.300
And I'll share my screen as well, but also in the chat box. There's a link in the business case that goes straight to

714
02:32:30.870 --> 02:32:37.710
She the the workflow and Anton did provide both the powerpoint and add the

715
02:32:37.800 --> 02:32:39.960
The workflow. So

716
02:32:40.530 --> 02:32:47.370
I don't know if folks have had a chance to to look at it or not. Are there any

717
02:32:47.970 --> 02:32:50.100
questions or feedback, right off the

718
02:32:50.160 --> 02:32:51.090
Right off the bat.

719
02:32:56.070 --> 02:32:57.240
Everybody see that okay

720
02:32:58.950 --> 02:32:59.520
Yes.

721
02:33:08.010 --> 02:33:20.250
So I did have a question regarding the the milk collection. Just wondering when its stated that the collection and milk will be at the Nick, you

722
02:33:21.810 --> 02:33:31.890
Can you explain the logic behind that piece. And I think I saw in the deck as well that it seemed like the lab testing wouldn't be

723
02:33:33.420 --> 02:33:37.320
It for mothers that are currently in the hospital. Is that correct,

724
02:33:40.740 --> 02:33:45.210
So this is for the government side of the hospital.

725
02:33:47.580 --> 02:33:59.550
Yeah yeah what we've heard is that, you know, there is a combination of tournaments and collected outside and then that comes in from external

726
02:34:00.960 --> 02:34:05.280
Areas and then there are some hospitals that have a milk bank internally.

727
02:34:06.630 --> 02:34:07.980
But they're not

728
02:34:09.450 --> 02:34:13.890
as big or as large as the ones from external

729
02:34:15.630 --> 02:34:16.440
sharing my screen.

730
02:34:18.990 --> 02:34:22.290
Okay, so this would be the internal note.

731
02:34:24.240 --> 02:34:25.500
Workflow basically

732
02:34:27.000 --> 02:34:30.240
This would be for milk bank like

733
02:34:31.290 --> 02:34:34.140
Nonprofit ones as well as the for profit one

734
02:34:35.820 --> 02:34:39.360
So we hope that they can utilize the technology to try and

735
02:34:40.530 --> 02:34:51.690
Track and be able to record the quantities. The lab testing components, the labeling and all that can be done and recorded on the block chain.

736
02:34:58.080 --> 02:35:06.120
Now our application inside the hospital takes care of everything else for the hospital to track internally.

737
02:35:08.370 --> 02:35:18.000
We have to figure out if they're willing to share any of that data into the block chain but maybe through anonymized

738
02:35:19.350 --> 02:35:24.990
Or just related to the consumption and the quantities that they requiring

739
02:35:27.630 --> 02:35:30.990
Area that we may focus on the last mile

740
02:35:34.980 --> 02:35:40.800
Hey, I tend this rich. So I have just a real practical question and it's sort of non technical i mean

741
02:35:42.090 --> 02:35:47.070
When we talk about so so imagine that we've we've just source milk.

742
02:35:48.150 --> 02:35:55.170
And it's in a some sort of container. How do you, how do you guarantee that that that milk isn't tampered with.

743
02:35:56.820 --> 02:36:04.650
Or, you know, I think one of the articles that that circulated was that some percentage of milk ends up with cold milk in it.

744
02:36:05.700 --> 02:36:15.480
How are you, guaranteeing that that doesn't happen. I mean is are you putting some sort of cap on the container or is there a lock on this or how

745
02:36:15.600 --> 02:36:17.400
How is that manage that just a real practical

746
02:36:17.400 --> 02:36:17.790
Level.

747
02:36:19.320 --> 02:36:33.030
Yeah, I think the some of the banks that we've worked with the have procedures in place to be able to have a untampered and it comes in specialized boxes.

748
02:36:36.075 --> 02:36:43.950
There is also like additional layers of security behind there so that you can verify that it hasn't been opened.

749
02:36:44.970 --> 02:36:57.810
From the source. And again, you know, we have to help define some things for the nonprofit ones. I'm not sure how the nonprofit groups are doing it, whether they have the technology in place for the

750
02:36:58.890 --> 02:37:01.110
Possibility of that or whether it's

751
02:37:02.760 --> 02:37:03.060
So,

752
02:37:04.380 --> 02:37:06.900
We'll have to do some research on finding that out.

753
02:37:11.280 --> 02:37:12.300
That's how I believe in it.

754
02:37:16.890 --> 02:37:22.530
Seems like if there's a physical physical security solution. We don't need a logical security solution.

755
02:37:25.380 --> 02:37:33.690
Well, yeah, it's interesting because in my mind it you know if if I were to want to corrupt the system, I'd look at the weakest link right and so

756
02:37:35.460 --> 02:37:41.130
The system that we have in place for sort of managing the asset sort of through this workflow.

757
02:37:41.850 --> 02:37:56.970
Is great, except you know, as it turns out, and this is this is not just for this particular use case, it tends to work across a lot of these sort of workflows, where if there's no way to secure the actual asset.

758
02:37:57.990 --> 02:38:01.800
Then the management of the assets sort of the handoff between

759
02:38:02.970 --> 02:38:17.610
Actors sort of becomes irrelevant, you know, and so that my concern would be so you know, thinking critically and I liked the thread that we had in an email and Thanks Jeff for your critical nature because that's I

760
02:38:17.610 --> 02:38:18.270
Tend to work this

761
02:38:18.360 --> 02:38:21.360
Way. Some people say cynical. I like to say critical

762
02:38:23.100 --> 02:38:23.400
I mean,

763
02:38:23.520 --> 02:38:34.950
Realistically, it's, it's just a question of, you know, how do you, how do you make this work in a ways that you really do look for security and and not for, you know, you just basically

764
02:38:35.490 --> 02:38:43.740
For someone to to move further upstream or downstream in the workflow to to find a way to get around a system.

765
02:38:45.990 --> 02:38:53.370
Yeah, and then just to recreate you know one of the key things that we're trying to do is to really be able to track.

766
02:38:54.780 --> 02:38:57.960
The supply and demand for the product.

767
02:38:59.490 --> 02:39:04.290
And be able to have some traceability as to the origins of where it came from.

768
02:39:05.430 --> 02:39:05.790
So,

769
02:39:07.320 --> 02:39:08.850
from a security perspective.

770
02:39:09.870 --> 02:39:12.120
You know, I do think it's very important.

771
02:39:13.560 --> 02:39:20.370
But the lab testing when it goes to these labs, who are actually testing it on verifying and

772
02:39:21.570 --> 02:39:26.040
The product is real or not. So a lot of it can be caught at that level.

773
02:39:27.270 --> 02:39:36.270
But from the lab to the hospital system. I'm pretty sure that the secure process. That's the delivery and happens

774
02:39:42.330 --> 02:39:50.550
Okay, so, so it sounds like the assumption here is that the product, the physical product is secure through the workflow that

775
02:39:55.200 --> 02:40:09.870
At least from one point to the other. I think the filtration happens at the lab well level to be able to make sure that it tested and verified and then it can only go further down the supply chain so

776
02:40:09.990 --> 02:40:17.190
At that point, we're able to create labels we can track the product and have the global identification number

777
02:40:18.840 --> 02:40:19.920
Expiration date.

778
02:40:21.090 --> 02:40:22.620
And it's treated like any other

779
02:40:23.760 --> 02:40:26.370
Regulated product in the supply chain process.

780
02:40:31.980 --> 02:40:36.120
Is, do you think it's overkill that even after at least lab testing and it gets to the milk banks.

781
02:40:36.570 --> 02:40:37.650
That they retested

782
02:40:37.650 --> 02:40:39.930
Before they even distributed to the mothers.

783
02:40:41.460 --> 02:40:42.780
I was thinking the same thing. JOHN

784
02:40:44.520 --> 02:40:48.510
I'm just saying if it sealed in. Okay, there may be some happening shipment, whatever.

785
02:40:48.990 --> 02:40:50.130
Double check, kind of like

786
02:40:50.400 --> 02:40:53.370
If I were yeah i would i would want that.

787
02:40:57.750 --> 02:41:01.770
What happens in the for profit ones. And, you know, companies like

788
02:41:03.150 --> 02:41:11.490
If you go to their website, you'll see the process that they and it's very rigorous and they, I think they're FDA regulated.

789
02:41:13.890 --> 02:41:16.680
A lot of this stuff that they ship out

790
02:41:17.940 --> 02:41:21.420
Products bottled on the field.

791
02:41:22.080 --> 02:41:28.470
And they have identification numbers on them. They know exactly where it came from. And so

792
02:41:29.910 --> 02:41:37.500
They do it correctly. I'm just not sure about the nonprofit one, and some of them are being sent up independently.

793
02:41:40.680 --> 02:41:41.190
The laugh.

794
02:41:43.290 --> 02:41:45.240
And verify that they're able to do this.

795
02:41:48.150 --> 02:41:55.410
What's the problem we're trying to solve if your product is C is tested and secured.

796
02:41:57.330 --> 02:42:01.200
I don't understand what the problem is that we're solving with a blockchain.

797
02:42:05.790 --> 02:42:08.820
Is a more than the traceability accountability of work came from.

798
02:42:09.450 --> 02:42:11.040
Or having kind of an audit trail.

799
02:42:11.850 --> 02:42:13.650
From the labs or from any distribution.

800
02:42:13.650 --> 02:42:16.410
Center of where everything. So if there is an outbreak.

801
02:42:17.100 --> 02:42:18.870
Know exactly where it came from that kind of

802
02:42:19.440 --> 02:42:20.340
Sets on the label.

803
02:42:20.520 --> 02:42:22.020
That should already be on the label.

804
02:42:22.980 --> 02:42:23.640
To come to. Yeah.

805
02:42:25.290 --> 02:42:27.960
Yeah, we're trying to solve two problems. One is

806
02:42:29.940 --> 02:42:33.780
Traceability for the nonprofit donor milk time

807
02:42:34.980 --> 02:42:36.960
That I've been set up nationally

808
02:42:38.550 --> 02:42:41.160
They don't have a system in place to know

809
02:42:42.570 --> 02:42:44.070
Quantities of demand.

810
02:42:45.780 --> 02:42:56.880
And the hospitals in requirement and then demand is increasing. So there isn't a overall large scale system to understand where quantity is

811
02:42:58.770 --> 02:43:10.860
Another area is we're solving is the ability for more people to donate milk and the tracking of that milk and being able to quantify it. I want to receive that the

812
02:43:11.430 --> 02:43:21.270
For profit or nonprofit labs, being able to see that at a national level to understand where supply and demand it so that things can be routed to the right places.

813
02:43:22.650 --> 02:43:25.530
towards a more of a supply chain problem trying to address.

814
02:43:31.635 --> 02:43:32.220
It is

815
02:43:32.610 --> 02:43:33.330
Easy. Look at this.

816
02:43:34.350 --> 02:43:36.450
Is this vagary in the milk bank.

817
02:43:36.450 --> 02:43:42.390
Box or in the lab testing box. I don't. I'm trying to figure out where it is because it's still ahead of the lab testing.

818
02:43:42.720 --> 02:43:44.460
The problem gets resolved and lab.

819
02:43:44.460 --> 02:43:46.140
Testing, as far as I can see.

820
02:43:47.985 --> 02:43:52.500
Yeah, but the milk screening process needs to be tracked also so

821
02:43:53.820 --> 02:44:04.980
If there's a screening process for the mother to be able to have identification that she's being screened and she's able to present that at the lab, the lab tests.

822
02:44:06.570 --> 02:44:09.840
And then is able to then send it further down the supply chain.

823
02:44:10.590 --> 02:44:13.680
Where's that understand where that takes places that

824
02:44:13.680 --> 02:44:15.510
At the milk bank or is that at the lab.

825
02:44:19.140 --> 02:44:26.280
If you look at the diagram. It can be both places. I mean, typically some of the most banks have labs inside them.

826
02:44:27.600 --> 02:44:35.400
Some milk bank. So this collection depots, and then they send it to another lab for testing. So it works both ways.

827
02:44:39.000 --> 02:44:44.490
If you look at the diagram I tried to make it a articulate how the workflow happens

828
02:44:45.450 --> 02:44:46.890
Right. And I'm looking at it, make it

829
02:44:47.490 --> 02:44:49.230
Well, you know, you know, the one thing that I did.

830
02:44:49.410 --> 02:44:51.420
I did sort of here and this was in

831
02:44:51.600 --> 02:44:53.880
The in the conversation thread is that

832
02:44:54.810 --> 02:45:04.080
You know, human milk does good adulterated with with cows milk and there's a profit motive for doing so. So, I mean, that that would suggest that's

833
02:45:04.500 --> 02:45:19.800
At least one aspect of a problem statement that that needs to be resolved, and so I guess my question is, do, do, do you know Anton where that adulteration might happen in the workflow here and and maybe this is what you know maybe the solution that we're talking about.

834
02:45:20.160 --> 02:45:21.510
would address that directly

835
02:45:21.690 --> 02:45:23.430
I mean, that would that would be moving us in the right

836
02:45:23.670 --> 02:45:24.630
In the right direction, then

837
02:45:24.960 --> 02:45:27.390
One of the things about that. That article, though the

838
02:45:27.390 --> 02:45:28.050
Fact that

839
02:45:28.410 --> 02:45:38.370
Milk is getting adulterated and of course there was the big problem in China. That wasn't donor milk, going to a nick you that was consumer milk.

840
02:45:39.540 --> 02:45:41.070
You know, going through stores.

841
02:45:41.280 --> 02:45:45.630
And so that's a different problem. And I want to make sure that we're defining the

842
02:45:46.710 --> 02:45:48.690
Consistently one problem and not

843
02:45:49.170 --> 02:45:50.310
picking and choosing

844
02:45:50.340 --> 02:45:53.190
Curie picking from one problem to add to another.

845
02:45:58.470 --> 02:46:11.430
So, so I may have misread that Jeff, I thought I had read somewhere in in some one of the threads, one of the links that it was human milk that one tested, they found some percentage of cow's milk in

846
02:46:11.460 --> 02:46:12.840
In in the samples.

847
02:46:13.710 --> 02:46:15.030
So I was, I was on the

848
02:46:16.860 --> 02:46:17.550
Rich, but

849
02:46:17.610 --> 02:46:24.930
What I think what Jeff Kirchner on what you're saying is there's a distinction between kind of the informal donor.

850
02:46:26.070 --> 02:46:37.230
Mechanism. So people finding other people through Facebook or friends groups or other things versus an actual donor bank.

851
02:46:38.010 --> 02:46:54.450
And and getting the milk there. And I think oftentimes people don't go through the banks because supplies so shorter, they can't access it as quickly as they they need to. So the contamination piece was seen outside of these formal channels.

852
02:46:56.220 --> 02:47:05.700
Yeah, that was my interpretation and the distinction is important because if we're talking about process that that is in the diagram.

853
02:47:07.380 --> 02:47:17.910
The Nicky was the payer, you know, maybe it actually gets paid through a health care plan. But whatever, as opposed to something that's kind of an informal ad hoc market out there.

854
02:47:18.750 --> 02:47:26.460
And try which trying to control that as a different problem. And I think the Nick you problem as portrayed here because we have the lab.

855
02:47:26.460 --> 02:47:28.530
Testing. I'm not sure.

856
02:47:28.890 --> 02:47:29.880
Is a problem.

857
02:47:30.960 --> 02:47:31.920
And for these

858
02:47:33.000 --> 02:47:45.570
Nonprofit milk banks. Maybe they just need a lab and maybe a lab is more expensive than a than a tracking system, but I don't know that because of the physical

859
02:47:45.630 --> 02:47:47.520
You can product for solving it.

860
02:47:48.390 --> 02:47:48.990
Were the width of

861
02:47:49.110 --> 02:47:57.750
Can understand the quantities are. That's the problem. Each one of the problems we're trying to solve is making sure everyone is tracking the product.

862
02:47:58.350 --> 02:48:10.560
And understanding the quantity at the different milk bank in a you can't see at a high level, where, how much you know Frank is holding. So there is an awake but need

863
02:48:12.030 --> 02:48:15.060
To be able to tap into that and know where quantities are

864
02:48:18.570 --> 02:48:21.390
Be a huge problem to solve. So as I

865
02:48:21.480 --> 02:48:22.170
So as I

866
02:48:22.260 --> 02:48:25.410
Hear it then what what I think the problem then is Nick us

867
02:48:25.740 --> 02:48:26.700
Have a need for the

868
02:48:26.730 --> 02:48:27.480
For the milk.

869
02:48:27.870 --> 02:48:32.460
But they have no way to identify where that milk can be sourced from, is that correct

870
02:48:34.380 --> 02:48:40.830
Yes. And then the milk banks themselves have a problem understanding the quantitative that each one is holding

871
02:48:42.720 --> 02:48:54.090
And as the number of milk banks are being developed increasing you have more need that is needed for donor milk to be put into those milk. Thanks.

872
02:48:55.980 --> 02:49:04.740
Trying to figure out a way to construct a constructive way to entice people to be able to donate more into the

873
02:49:06.870 --> 02:49:13.140
That's where we looked at a token system to be able to, you know, or a reward system that can be tied

874
02:49:14.400 --> 02:49:23.190
To the don't donors, being able to give milk and being able to track that at every milk bank that it's being donated

875
02:49:26.250 --> 02:49:39.000
So, so this this we're spinning a whole bunch of different potential solutions, but the solution use described to me sounds like a dating site, you're just trying to match the

876
02:49:40.350 --> 02:49:42.930
The milk suppliers with the milk commanders.

877
02:49:44.430 --> 02:49:47.760
Yeah, that that's sort of how I read that. Yeah, I would agree, Jeff.

878
02:49:52.140 --> 02:49:52.290
We're

879
02:49:52.920 --> 02:49:59.670
Just could be any kind of central website where people post. Hey, I have this much milk. It's certified by this lab.

880
02:50:00.420 --> 02:50:00.780
And here.

881
02:50:00.930 --> 02:50:04.110
Price and somebody else says I'm looking for this much milk.

882
02:50:04.560 --> 02:50:06.690
near me. And here's what I'm willing to pay.

883
02:50:09.630 --> 02:50:16.410
You want to go ahead, Jeff. Jeff, if you want to go ahead and build this solution yourself, please feel free to go build this dating website.

884
02:50:17.490 --> 02:50:18.870
Going to be done on a database.

885
02:50:21.030 --> 02:50:23.580
I'm just trying to make sure there's a business case for what we're

886
02:50:23.580 --> 02:50:26.400
Doing so that this becomes valuable and not

887
02:50:33.060 --> 02:50:35.130
Just. Can I just open the conversation up to

888
02:50:35.130 --> 02:50:40.590
Others on the call to see if they have any input on the comment so far.

889
02:50:43.500 --> 02:50:45.060
Well, I'm gonna drop off if I got

890
02:50:47.880 --> 02:50:49.410
One question before you go one question.

891
02:50:52.260 --> 02:50:53.550
So what the milk or everything

892
02:50:53.850 --> 02:50:54.750
That's being tracked

893
02:50:55.050 --> 02:50:56.910
Is the temperature of it.

894
02:50:56.940 --> 02:50:58.740
Come into play as well like

895
02:50:59.220 --> 02:51:01.470
Does it have to be kept at a certain temperature that needs to be tracked

896
02:51:02.310 --> 02:51:04.320
invalidated. Yes, that's right, yeah.

897
02:51:05.610 --> 02:51:08.190
So you also thinking about throwing an IOT devices, it

898
02:51:11.280 --> 02:51:12.600
Yeah, potentially, I mean,

899
02:51:12.600 --> 02:51:17.070
You know some of the nonprofit my banks really don't have the capacity to

900
02:51:18.330 --> 02:51:27.330
Do some of that. So, you know, being able to give them the ability to have technology that can track temperature level.

901
02:51:28.890 --> 02:51:41.010
Humidity input that would be a boon would be really good for them. But you know, I think what I was trying to do was to get the president of human milk bank of North America.

902
02:51:41.760 --> 02:51:52.320
To join this group to give her kind of input, which would be great. But, you know, I've been trying. I don't know if you want to try and reach out

903
02:51:54.870 --> 02:51:58.830
To make them today. Yeah, I can try and reach out to me.

904
02:51:59.040 --> 02:52:01.830
Directly following this call.

905
02:52:03.420 --> 02:52:03.720
And

906
02:52:05.460 --> 02:52:10.200
make that connection, I also want to kind of challenge that dating site.

907
02:52:11.550 --> 02:52:12.150
Concept of

908
02:52:12.540 --> 02:52:13.650
Just regarding

909
02:52:14.190 --> 02:52:17.790
You know, we have we have different banks, right, that might not

910
02:52:18.150 --> 02:52:23.670
Be using this processes are the same, or maybe have

911
02:52:24.030 --> 02:52:28.920
Established trust between them. We would want to validate

912
02:52:30.090 --> 02:52:33.690
You know all them all the donors have their blood tests.

913
02:52:33.900 --> 02:52:45.600
And meet certain criteria and that the milk that they hold also is meeting you know the supply chain requirements that that john and as far as temperature and whatnot.

914
02:52:46.140 --> 02:52:59.910
So I think it's a little bit more complex and I do see the the distributed ledger no traceability immutability being an asset in those relationships to provide

915
02:53:00.480 --> 02:53:13.980
visibility across donors on the, the quantity. And then also, as I mentioned, to try and create visibility on to the which would help bring additional time

916
02:53:19.950 --> 02:53:20.490
So, yeah.

917
02:53:20.640 --> 02:53:23.400
I would agree. I think Providence is is a factor her definitely

918
02:53:23.430 --> 02:53:25.500
So that, so that would be something to consider.

919
02:53:31.740 --> 02:53:33.540
Think, Jeff, you brought that up in our last call as well.

920
02:53:34.410 --> 02:53:36.570
As files are governance miles that need to be

921
02:53:36.840 --> 02:53:39.390
Implemented profitable for instance kind of go into

922
02:53:39.420 --> 02:53:41.070
Place to Victoria on the same page.

923
02:53:45.090 --> 02:53:47.100
Provenance and traceability.

924
02:53:48.120 --> 02:53:53.730
I was thinking in terms of Providence and traceability that this reminds me a lot of

925
02:53:55.380 --> 02:53:58.290
Initially, as the project, which wasn't very successful.

926
02:53:59.880 --> 02:54:03.540
Using blockchain technology and distributed Ledger's for

927
02:54:04.770 --> 02:54:05.280
Diamonds.

928
02:54:06.720 --> 02:54:07.110
Diamonds.

929
02:54:11.520 --> 02:54:15.930
Well that's system doesn't actually work for blood diamonds that only works for certified cut diamonds

930
02:54:21.870 --> 02:54:22.980
No, I mean to

931
02:54:25.920 --> 02:54:26.970
Have blood diamonds

932
02:54:27.540 --> 02:54:30.900
Yeah, but once a diamonds cut. You have no idea where it came from.

933
02:54:40.530 --> 02:54:50.820
Then that's your, your kind of going back to your previous comment about how you actually attach the asset to the block chain. If it's a physical thing.

934
02:54:53.190 --> 02:54:56.310
Right. I mean, you can be ever ledger solution.

935
02:54:57.480 --> 02:55:10.470
Basically uses sort of only to track certified diamonds which can be identified uniquely because of the physical properties of every diamond is unique one and they're all cut

936
02:55:11.340 --> 02:55:12.750
But you can't tell.

937
02:55:13.110 --> 02:55:15.360
A cut diamond where it came from.

938
02:55:15.870 --> 02:55:20.130
Once it's cut the way they try to track right now.

939
02:55:21.450 --> 02:55:38.730
The rough diamonds, the uncut diamonds as uncut diamonds are putting a lockbox and they're and they're labeled. And so just a labeling issue. But that's all subject to the ability to associate the diamond with the label. But there's no way to

940
02:55:40.020 --> 02:55:41.160
Break down because

941
02:55:42.000 --> 02:55:46.590
You can't go by. Wait, there's no way to know once you open the box.

942
02:55:47.370 --> 02:55:50.760
If you're mixing in some blood diamonds with some regular diamonds

943
02:55:51.600 --> 02:55:52.830
The bleier knows

944
02:55:52.920 --> 02:55:54.090
That he's got a lock.

945
02:55:54.090 --> 02:55:55.860
Box. The by

946
02:55:55.920 --> 02:55:57.000
Meaning the cutter.

947
02:55:57.450 --> 02:56:08.610
Will know that he's got blood diamonds or not. But once he cuts them. No one can tell. So if he wants to use blood diamonds, because you can get a better deal on him and he mixes them in with a lot. There's no way to stop that.

948
02:56:11.400 --> 02:56:20.460
I think here we've got a biological sample. So they got the Barker that they're putting on it at the time of analysis.

949
02:56:21.450 --> 02:56:33.720
So if they really wanted to check whether or not that barcode match that sample. They could just we run the analysis and it's the analysis matches. They know that it's the same sample with they have a question.

950
02:56:36.780 --> 02:56:45.900
Well, here. Yeah, but here we have the the benefit of if you're doing if you're doing the lab testing in the lab labeling it and telling you that it's it's good product. It's all

951
02:56:46.200 --> 02:56:54.630
Actual natural mother's milk and it complies with whatever you know bacteria requirements, etc. It is. And then they seal it and label it.

952
02:56:56.250 --> 02:57:13.470
I don't know what the issue is in them, sending it to someone else. Now there's a tip that temperature issue. But these are all separate solvable problems they're not doesn't just because we add a bunch of individual problems together doesn't mean it's a black chain solution.

953
02:57:15.930 --> 02:57:21.720
Well, I think maybe we kind of need to move past that and just

954
02:57:22.950 --> 02:57:25.650
And just say that yes, we do have a blockchain.

955
02:57:26.940 --> 02:57:32.160
Problem that we need to sell because we have a company that truly has that problem and they're asking us to solve it.

956
02:57:32.580 --> 02:57:50.610
Using blockchain. And they kind of know their ecosystem that block chain is going to be the solution. So maybe we can just kind of move past is watching the solution and move on. Do okay how do we continue to build to solve their problems because they haven't to problem.

957
02:57:51.900 --> 02:57:54.360
Solve the problem and let us the regular database and

958
02:57:54.360 --> 02:57:56.100
Simulate as a simulation.

959
02:57:57.300 --> 02:58:00.540
And then you'd realize that you've solved the problem. And you don't have to go any further.

960
02:58:01.260 --> 02:58:03.900
Yeah, but this one I disagree with me because I mean

961
02:58:03.960 --> 02:58:04.380
Because do

962
02:58:04.650 --> 02:58:17.250
What they're asking for is this accountability record of a solid audit trail that one. If there's an outbreak in seconds, kind of like a Walmart did when he did a test for the avocados is to find out in seconds.

963
02:58:17.700 --> 02:58:19.140
Where the contamination came from.

964
02:58:19.500 --> 02:58:20.580
The right now. The challenge is

965
02:58:20.670 --> 02:58:27.480
One that under the supply where everything is. But to if if there is an outbreak, it will take them a long time because we're central database.

966
02:58:27.930 --> 02:58:35.160
Or everybody central database and every look look store of where's this contamination is and then stop and pull from shelf almost like

967
02:58:35.460 --> 02:58:41.700
It was an outbreak with Tylenol and their medicine, we do. It's got a label on it. It's got sealed. It's been stamped that's in a box.

968
02:58:42.060 --> 02:58:54.870
What you've heard and saying hey talent. I was pulling boxes from the shells because of an examination. Now, the question comes down to how long did it take them to figure out that they had a problem with the tunnel or medicine so

969
02:58:54.960 --> 02:58:58.140
You look at the case yet Jan, I agree with what you're what you're saying what you're

970
02:58:58.560 --> 02:59:04.170
arguing for is a centralized database and whether it's a block chain or

971
02:59:04.980 --> 02:59:12.720
SQL database with solve the problem, as long as everyone was contributing to the database. The reason you would want to use a block chain versus an SQL.

972
02:59:13.650 --> 02:59:30.000
No SQL database is if you thought that somebody was actually going to try to corrupt it intentionally and I don't know that this market is big enough and lucrative enough that you're going to have that problem that you could use normal security controls.

973
02:59:31.170 --> 02:59:33.480
You know, which are used on things like visa.

974
02:59:34.920 --> 02:59:43.860
And and you have the database, you'd have the information all there in one place a lot more inexpensively than having to go the blockchain.

975
02:59:44.490 --> 02:59:44.760
No.

976
02:59:44.970 --> 02:59:46.860
Here on that. But what happens when you

977
02:59:47.460 --> 02:59:47.850
Do this.

978
02:59:49.050 --> 02:59:50.940
Yeah, who would do that. Who would maintain it.

979
02:59:53.640 --> 02:59:54.600
In the block chain.

980
02:59:55.080 --> 02:59:59.310
You still need somebody to somebody who's gonna have to pay for this. It's not going to be free.

981
03:00:02.520 --> 03:00:08.580
That's a problem that you have in either case all the all the issues that were raised in these various threads on email.

982
03:00:08.910 --> 03:00:13.860
Applied whether it's a block chain or not people seem to think that because it's black chain. It's free.

983
03:00:13.950 --> 03:00:14.640
It is not

984
03:00:15.930 --> 03:00:17.400
It's not free, but it may be

985
03:00:17.400 --> 03:00:20.880
Able to have that connection with all these distribution centers.

986
03:00:21.720 --> 03:00:26.130
That's what the challenges right now to be able to actually see into everything say it's like well

987
03:00:26.160 --> 03:00:30.420
You get them all together, they can do it in a central database, not

988
03:00:30.960 --> 03:00:31.830
In the same room.

989
03:00:32.250 --> 03:00:33.750
But think about this. What if we can

990
03:00:36.000 --> 03:00:36.570
Go ahead.

991
03:00:37.800 --> 03:00:46.560
Yeah, so I think the problem had justice. What we're trying to do is give the milk bank, the ability to have a software that we've maintained by non

992
03:00:47.190 --> 03:00:54.870
Not a single source available to them and they're able to write information into the amount of quantity that they're carrying.

993
03:00:55.350 --> 03:01:06.570
So that a national organization can pick and do analytics around this and be able to understand where the Carnegie doc and be able to provide that as a service to the hospital systems.

994
03:01:07.140 --> 03:01:08.010
And who's going to run

995
03:01:08.100 --> 03:01:12.330
A blockchain. Who's gonna orchestrated when there's a code release.

996
03:01:12.360 --> 03:01:27.990
That's where we when we build the system we get we get organizations to contribute. We know that the health systems and the hospitals themselves want to know the availability of this. So, let them contribute into a fund that makes them.

997
03:01:29.430 --> 03:01:44.070
Have the solution, which gives them access to understanding quantity aware it so from the traceability behind it. And that's what I was envisioning was going to happen further down the line and I already placed up to merge to ask

998
03:01:45.090 --> 03:01:57.780
You know, maybe human milk bank of North America could be able to find donations or whatever funding and can from the hospital that it's working with to be able to provide this service.

999
03:02:00.480 --> 03:02:00.840
At

1000
03:02:02.520 --> 03:02:16.260
80 million get out requirement in the United States, and it's growing. And so I don't understand where you think the money's not going to come from the price of milk is going to go up, you're going to find

1001
03:02:17.040 --> 03:02:24.930
Stuff that the everywhere and the hospitals are going to get gained even more money by using the solution, they can find a

1002
03:02:26.310 --> 03:02:34.530
lower price product available in different areas of state and they can get that shipped over immediately.

1003
03:02:34.980 --> 03:02:39.900
I have no I have nothing against any of the things that you're saying all the things you're saying are

1004
03:02:39.960 --> 03:02:42.630
Perfectly reasonable solution. All I'm saying is

1005
03:02:42.840 --> 03:02:45.960
It's more costly to do it with a black chain and

1006
03:02:46.020 --> 03:02:50.280
There's no need for a blockchain. You can do everything you've said with an ordinary

1007
03:02:50.280 --> 03:02:51.000
Database

1008
03:02:52.050 --> 03:02:52.500
And I don't know.

1009
03:02:52.590 --> 03:02:52.770
Why

1010
03:02:54.900 --> 03:02:58.110
Why did I hyper ledger right now there's

1011
03:02:58.200 --> 03:03:02.880
Plenty of other don't require a block chain where you know that there's people there's actual

1012
03:03:03.120 --> 03:03:05.280
People spending good money right now.

1013
03:03:05.280 --> 03:03:11.010
What like diamonds like tracking tracking certified diamonds like tracking pharmaceuticals.

1014
03:03:12.420 --> 03:03:14.340
Why would. Why would be the thing

1015
03:03:15.330 --> 03:03:19.590
It's not a big enough market that that you don't have this kind of counterfeiting, but you can't

1016
03:03:20.730 --> 03:03:23.580
I thought we thought were developing a nonprofit.

1017
03:03:26.580 --> 03:03:27.210
Whether it's not

1018
03:03:28.710 --> 03:03:29.130
Money.

1019
03:03:29.460 --> 03:03:30.210
Somebody got

1020
03:03:31.530 --> 03:03:31.860
Yeah.

1021
03:03:33.870 --> 03:03:35.220
We have to move past it.

1022
03:03:35.520 --> 03:03:41.790
And basically say that we have a company that saying that Blockchain is a solution they want. Let's just build it.

1023
03:03:43.080 --> 03:03:50.820
Just build it at this point it it seems to be the solution. They want you have a company that actually has a need. Let's just build it.

1024
03:03:55.230 --> 03:03:55.680
Must be

1025
03:03:55.980 --> 03:04:09.390
Have some other use case that you're like, this is a use case that I want to put forward that is much better in my mind to build on, then we need to just move on into the bill.

1026
03:04:12.120 --> 03:04:12.465
That's

1027
03:04:12.540 --> 03:04:16.800
A kind of a standard developers approach. Let's start programming and we'll figure out what we're gonna do it.

1028
03:04:16.980 --> 03:04:36.900
Tomorrow, yeah. But Jeff, I think this is, you know, this is slightly different than working in mean we are in experimental lab situation where we have the ability to try. Try new things and see how it works. And I think we should explore the opportunity

1029
03:04:37.980 --> 03:04:46.590
As we do have as Angela said a company is interested in driving this knows the market knows the need and is looking to us to to help

1030
03:04:48.930 --> 03:04:50.010
So with that I

1031
03:04:51.630 --> 03:04:52.530
Did want to kind of

1032
03:04:52.590 --> 03:04:55.950
Take a few minutes to talk about timeline.

1033
03:04:56.970 --> 03:05:03.480
Anton i guess i know that you so that you needed to go. I did have some questions around in the deck.

1034
03:05:04.440 --> 03:05:09.390
Specifically the timeline that you put forward and mentioned

1035
03:05:11.310 --> 03:05:12.630
developer resources.

1036
03:05:13.380 --> 03:05:14.970
In India, and so I just wanted to

1037
03:05:15.750 --> 03:05:16.860
Gauge with you.

1038
03:05:18.510 --> 03:05:22.020
Where, where that to me that timeline and seemed a bit compressed.

1039
03:05:22.860 --> 03:05:24.660
But I was curious to get your feedback.

1040
03:05:26.040 --> 03:05:36.600
Yeah, the other timeline was just something that we did. Internally, we got a third party to give us the timeline and how to stand up a proof of concept.

1041
03:05:38.310 --> 03:05:38.850
Fabric.

1042
03:05:39.930 --> 03:05:40.620
Hyper ledger.

1043
03:05:41.670 --> 03:05:45.990
System. So yeah, please don't better my. That was just an internal thing.

1044
03:05:47.130 --> 03:05:55.860
What we just provided you guys was like another review of the problem and then the architecture that we identified and

1045
03:05:56.460 --> 03:06:03.480
You know, it's really up to you guys, whether you take this project are our priorities on developing our software and selling it to me.

1046
03:06:04.440 --> 03:06:25.620
And we already in that process. So we were just providing this as a as a template for something that block chain to be utilized for help build this for the national don't fact when we, when we talk to the human milk bank of North America, she identified the problem.

1047
03:06:26.850 --> 03:06:42.390
But we are unable to build without ourselves. So that's why we kind of send it over to you guys, but it's totally up to you guys really decided to run with it or not. For us, we can provide you are support and what are the data we can we can make introductions.

1048
03:06:43.560 --> 03:06:45.240
To the right parties to get advice.

1049
03:06:46.590 --> 03:06:48.330
It's totally up to you guys were the color.

1050
03:06:49.890 --> 03:06:52.440
Or not for us. We're not going to be going down that

1051
03:06:54.120 --> 03:06:54.780
As a company

1052
03:06:56.550 --> 03:06:56.880
Okay.

1053
03:06:57.330 --> 03:06:58.650
I mean, I think.

1054
03:06:58.980 --> 03:07:01.830
I can only speak for myself and I think

1055
03:07:01.980 --> 03:07:05.970
Angela's on the same page from what I'm hearing is that we would like this.

1056
03:07:07.320 --> 03:07:07.680
But

1057
03:07:08.880 --> 03:07:14.490
And so the the timeline that I put together very tentatively I'm sharing my screen. This is in the business.

1058
03:07:14.490 --> 03:07:32.430
Keys is, is basically targeting end of the year to have something built with kind of an iterative development frame in mind. I think my understanding of what we would want to do next is to really

1059
03:07:33.510 --> 03:07:42.540
Start building out the specific requirements for the proof of concept and digging a little bit deeper into how we can start engaging

1060
03:07:43.800 --> 03:07:45.300
With the development community.

1061
03:07:46.530 --> 03:07:49.230
Any comments on on that.

1062
03:07:53.400 --> 03:07:54.720
I don't have a comment on the

1063
03:07:54.750 --> 03:07:57.660
Timeline, but I have a question.

1064
03:07:59.400 --> 03:08:14.550
On the bill, so I added generous. Last night we have that we already have. I had a temperature control. I'm going to add to the donors last testing date. So that can be part of their

1065
03:08:16.050 --> 03:08:17.070
Description, if you will.

1066
03:08:18.570 --> 03:08:25.920
But the front end of this is going to be really important and how people actually interact with it because

1067
03:08:27.060 --> 03:08:29.610
On the build everything is the JSON call

1068
03:08:31.110 --> 03:08:36.480
So my question to Anton is, I know you already have a run in app for

1069
03:08:38.220 --> 03:08:43.260
What you've built previously so are your developers able to

1070
03:08:44.400 --> 03:08:53.580
Know, once the code goes up for the actual watching itself. Are they able to go ahead and grab that goes JSON calls and build a fun into it.

1071
03:08:55.230 --> 03:08:55.920
We can do that.

1072
03:08:57.150 --> 03:08:57.450
Will be

1073
03:08:58.860 --> 03:08:59.130
OK.

1074
03:09:05.820 --> 03:09:07.950
Any other questions. I know we're getting close to

1075
03:09:16.020 --> 03:09:16.770
Somebody

1076
03:09:20.070 --> 03:09:26.040
So, so this is rich. So it would be great if we got this these discussions moved over to

1077
03:09:27.630 --> 03:09:38.640
To rocket chat and. And the reason for that is, it'd be great if we can get some folks from some of the other channels, particularly the fabric channel sort of review some of this stuff.

1078
03:09:39.690 --> 03:09:44.460
Because I'm I suspect though they'll lend themselves some really good insight.

1079
03:09:45.150 --> 03:10:02.520
Into what we're looking to do here. It's great to have it on an email thread, but that really gets limited to the folks that are on that thread. I really hope to see that we can get this across multiple domain. So we get some different sort of fast that it insights from from folks.

1080
03:10:03.330 --> 03:10:10.890
Yeah, that makes sense. And I didn't go through the business case and try and add aspects of from

1081
03:10:12.360 --> 03:10:15.690
From the thread that I thought were valuable. And so I've

1082
03:10:15.690 --> 03:10:16.680
Been been pushing

1083
03:10:19.680 --> 03:10:24.390
I don't know, rich, what you think about this as we could just put this out to the fabric.

1084
03:10:24.960 --> 03:10:37.920
Channel. I think I do want to highlight probably more specifically those two goals that Anton talked about about, you know, visibility across donors and then hoping to engage more more donors with with the

1085
03:10:39.270 --> 03:10:44.160
Ability to see quantity to really lay that out in the business case to make that

1086
03:10:44.160 --> 03:10:44.880
Clear because

1087
03:10:45.660 --> 03:10:46.590
You know there are

1088
03:10:46.770 --> 03:10:57.300
A variety of aspects to this, but this is really what we want to focus on. And then we could post this and the various channels and see what sort of feedback we get

1089
03:10:59.670 --> 03:11:11.040
Yeah. I think that'd be great. I mean, it would be really interesting to hear some other perspectives from these other domains to their insight on this and and maybe some direction.

1090
03:11:13.860 --> 03:11:24.465
All right, so I'll follow up with Naomi and I'll try and clean up the business case based off the conversation we had today, get that into rocket chat and then also if

1091
03:11:24.780 --> 03:11:32.910
Threads start building an email, I will try and get people to defer to you. The, the rocket chat platform in order to to

1092
03:11:34.380 --> 03:11:44.610
Have it there. If people to have additional questions. I love for those also be posted in rocket chat so that we can. I can start collecting those and we can address them because I think

1093
03:11:45.120 --> 03:11:59.250
The more questions. We have, the easier it'll be to start identifying requirements and digging into certain aspects. So please do keep thinking about questions you have regarding the workflow that we can bring to the table for for next conversation.

1094
03:12:02.340 --> 03:12:02.940
Anything else

1095
03:12:06.270 --> 03:12:07.740
Good good discussion.

1096
03:12:08.310 --> 03:12:08.760
Absolutely.

1097
03:12:10.260 --> 03:12:12.210
Well, thank you everybody for your time.

1098
03:12:12.480 --> 03:12:13.050
Really appreciate

1099
03:12:15.570 --> 03:12:17.100
Speaker and a couple weeks. Right.