WEBVTT

1
00:04:00.150 --> 00:04:00.690
I just want

2
00:04:02.670 --> 00:04:03.360
Hi.

3
00:04:03.690 --> 00:04:12.150
I just wanted to let you know because I need to unfortunately travel while being on this call Rose was kind enough to

4
00:04:13.980 --> 00:04:21.420
Decided to run the call. So she will be facilitating the call if that's okay with everybody.

5
00:05:08.280 --> 00:05:09.180
We're probably not. Yeah.

6
00:05:10.290 --> 00:05:12.900
Let's give people about two more minutes to join.

7
00:05:14.130 --> 00:05:16.680
Hi, I just hopped on its Bobby

8
00:05:33.570 --> 00:05:33.750
And

9
00:05:43.050 --> 00:05:43.800
Now,

10
00:06:07.380 --> 00:06:08.550
Hello this is row Sherman

11
00:06:08.550 --> 00:06:09.600
From bright red joining

12
00:06:26.280 --> 00:06:27.210
It's probably

13
00:06:27.330 --> 00:06:28.290
Oh no, it's not me.

14
00:06:28.860 --> 00:06:29.880
Because I hear the noise is

15
00:06:30.390 --> 00:06:31.080
OK, we have

16
00:06:31.110 --> 00:06:33.030
15 participants, I suggest we

17
00:06:33.030 --> 00:06:33.660
Started

18
00:06:34.980 --> 00:06:36.015
So let me

19
00:06:36.015 --> 00:06:37.680
Start with saying that

20
00:06:38.580 --> 00:06:50.310
This meeting this subject and it's antitrust policy, which means that none of the information that is shared during the meeting should be in any way.

21
00:06:52.680 --> 00:06:53.490
In any way.

22
00:06:55.080 --> 00:07:04.020
Well you you should be given the opportunity to comment on the development of any requirements. Regardless, which whether they are member

23
00:07:04.110 --> 00:07:05.790
Your members of Linux Foundation or

24
00:07:05.790 --> 00:07:06.150
Not

25
00:07:07.770 --> 00:07:08.370
You

26
00:07:09.450 --> 00:07:09.780
And

27
00:07:11.580 --> 00:07:14.520
If you have any questions I've asked you, or legal advisor.

28
00:07:14.520 --> 00:07:16.080
Or us

29
00:07:16.500 --> 00:07:26.370
Or email Linux Foundation. If you are a member of Linux Foundation and then next foundation to anti drug policy can be found at dub.

30
00:07:26.850 --> 00:07:28.050
dub dot dot

31
00:07:28.080 --> 00:07:29.610
org slash anti trust.

32
00:07:31.380 --> 00:07:36.930
With that it was a quick reminder of the anti trust policy.

33
00:07:38.280 --> 00:07:39.540
I suggest we moved to

34
00:07:39.540 --> 00:07:41.250
The next point, which is

35
00:07:41.940 --> 00:07:42.480
Roses.

36
00:07:43.830 --> 00:07:44.940
Summary of the pole.

37
00:07:49.530 --> 00:07:50.910
Great I thanks

38
00:07:51.630 --> 00:07:54.420
Also, just quickly checking for sound quality.

39
00:07:55.200 --> 00:07:57.990
I haven't air con on which may or may not interfere

40
00:07:57.990 --> 00:08:01.890
With the noise is this a clear connection for everybody.

41
00:08:02.940 --> 00:08:03.180
Yeah.

42
00:08:03.870 --> 00:08:04.740
Yes, we're all fine.

43
00:08:04.800 --> 00:08:05.460
Okay, great.

44
00:08:06.900 --> 00:08:12.600
Anyway, wonderful. So, good day to everybody, and thank you to all who

45
00:08:12.630 --> 00:08:16.710
Participated in the creation, the

46
00:08:17.580 --> 00:08:21.300
Organization of the admin and then of course the

47
00:08:21.300 --> 00:08:23.490
Filling in of the survey we

48
00:08:23.520 --> 00:08:24.030
Have

49
00:08:25.650 --> 00:08:26.970
So far,

50
00:08:29.310 --> 00:08:33.000
respondents who have come in. Actually, I take that back. We have 10

51
00:08:34.110 --> 00:08:40.860
respondents who have filled in their surveys. So if you haven't filled one. And yet, and would like

52
00:08:40.920 --> 00:08:42.450
To welcome you to

53
00:08:42.540 --> 00:08:53.010
Please go in and add to that that said it's a very good beginning to get an idea of the group. What we're going to focus on, there's a lot of information in it.

54
00:08:53.100 --> 00:08:56.460
So rather than drone on about it, I think.

55
00:08:56.520 --> 00:08:57.180
What we're going to

56
00:08:57.210 --> 00:08:58.020
Would be best.

57
00:08:58.080 --> 00:09:01.200
But people can feedback in if they would like a different idea.

58
00:09:01.740 --> 00:09:03.060
Is first

59
00:09:03.180 --> 00:09:04.860
Just do a quick overview of

60
00:09:05.190 --> 00:09:17.910
The types of profiles of people, very briefly, who are in this group, just so we started to get a sense. I'm redacting names and affiliations, unless you want me to actually

61
00:09:17.910 --> 00:09:22.110
Tell names and affiliations. So actually, this would be a great moment, which way would you

62
00:09:22.110 --> 00:09:23.160
Like to go forward.

63
00:09:23.160 --> 00:09:24.960
And similarly,

64
00:09:25.260 --> 00:09:36.600
For the version of the results that are going to be distributed. Would you rather be redacted version or one with names and affiliations and people could chime in, about what the right way forward is on that this would be the best moment to do it.

65
00:09:38.370 --> 00:09:39.300
Please know that

66
00:09:41.970 --> 00:09:42.180
They

67
00:09:45.510 --> 00:09:45.840
Will

68
00:09:52.530 --> 00:09:53.340
Then we

69
00:09:53.370 --> 00:09:54.900
Can go through with

70
00:10:07.590 --> 00:10:08.070
I think that's

71
00:10:10.380 --> 00:10:10.740
It's

72
00:10:12.510 --> 00:10:19.890
Not you probably needs to do that either at a bad connection or her computer is struggling with she's

73
00:10:20.520 --> 00:10:20.850
Voice

74
00:10:24.510 --> 00:10:26.430
Can understand anything you're saying Marta.

75
00:10:27.240 --> 00:10:29.880
Talking it's it's really bad.

76
00:10:37.860 --> 00:10:38.190
Maybe

77
00:10:39.930 --> 00:10:42.060
He is there a chat feature.

78
00:10:45.540 --> 00:10:45.990
Yes.

79
00:10:49.980 --> 00:10:50.310
Ah,

80
00:10:52.710 --> 00:10:56.250
Sadly, that was sadly Bartow. We can't hear you anymore.

81
00:10:59.340 --> 00:10:59.970
Okay.

82
00:11:03.450 --> 00:11:04.710
Hello, we can

83
00:11:04.920 --> 00:11:05.520
We can

84
00:11:05.610 --> 00:11:06.630
Really hear you.

85
00:11:12.390 --> 00:11:13.500
I'm going to check back tomorrow.

86
00:11:32.400 --> 00:11:34.200
Okay. Mark just into everyone

87
00:11:35.370 --> 00:11:36.900
Names for privacy.

88
00:11:36.930 --> 00:11:38.940
Protection. Okay.

89
00:11:39.030 --> 00:11:40.440
I will defer to Marta.

90
00:11:41.940 --> 00:11:42.510
Okay.

91
00:11:45.480 --> 00:11:45.990
Okay.

92
00:11:46.080 --> 00:11:47.160
Martha has chatting to the

93
00:11:50.550 --> 00:11:51.360
Hell, we can't

94
00:11:54.150 --> 00:11:54.930
Hear me

95
00:11:55.740 --> 00:11:56.250
Fairly

96
00:11:58.830 --> 00:11:59.490
Yes.

97
00:12:08.370 --> 00:12:11.040
March. Unfortunately we can't hear you, though, but we did

98
00:12:11.220 --> 00:12:13.500
I did see your chat that

99
00:12:13.830 --> 00:12:22.830
We should keep the names removed for privacy protection. So we will we will defer to that. All right.

100
00:12:24.090 --> 00:12:24.570
Okay.

101
00:12:25.110 --> 00:12:25.410
All right.

102
00:12:25.440 --> 00:12:27.300
I think that's what we will decide to do

103
00:12:27.480 --> 00:12:36.870
Okay. So going back to the debrief on it. There's, there's a lot of content in here and i think it's it's potentially worth

104
00:12:37.260 --> 00:12:44.850
Doing just to brief summary, but I'd be very interested to collaborate with anyone who'd like to do a little bit more

105
00:12:45.570 --> 00:12:58.050
rigorous analysis of the results and perhaps present them in a more rigorous way. So it would be great if anybody would be interested to collaborate together and that for sharing with the group.

106
00:12:58.560 --> 00:13:06.030
But I can give a quick debrief on the profiles of who's responded, as well as perhaps just jump directly to

107
00:13:06.030 --> 00:13:07.080
Global Forum.

108
00:13:07.200 --> 00:13:13.500
Because it is the one thing that has a really pretty closed and pending timeline on it.

109
00:13:14.370 --> 00:13:24.870
Then we can pause and see where we're at and see if we want to work back into other priorities of the group or just pause on that for the moment and focus on the thing with the tight timeline for this week. What does everyone think

110
00:13:30.675 --> 00:13:35.730
Hi it's Bobby. I think that's a great idea. Since the form is coming up so quickly.

111
00:13:38.790 --> 00:13:44.970
Okay. Anyone else have been a different opinion. I guess I'll try the going once, going twice.

112
00:13:48.630 --> 00:13:49.230
Okay.

113
00:13:50.250 --> 00:14:03.150
All right, so we'll start with that. And again, just reiterating that the, the results are pretty much in a raw form at the moment and would really benefit from I think a more formal

114
00:14:03.780 --> 00:14:19.920
Not terribly difficult but formal analysis in the spirit of it being a collective here if anybody would like to jump in at this phase to work on it, something over the next week to make it a bit of a smoother presentation that we could have

115
00:14:21.090 --> 00:14:27.840
You know, not just raw information form, this would be a great time to jump in about that anytime on the call, but

116
00:14:28.080 --> 00:14:28.860
Now it but I

117
00:14:29.310 --> 00:14:36.330
Rose, I can because if the survey is still alive and people are going to still be putting in their information.

118
00:14:36.870 --> 00:14:48.990
I can do that in some type of newsletter real quick to just like keep up with. How many people are answering and the gist of it and you and I can work together on that during the week to get something so that people can just like look at the results.

119
00:14:49.350 --> 00:14:50.550
Okay, that sounds great.

120
00:14:51.480 --> 00:15:10.380
Okay Okay super. Alright, so a quick summary from the general of why and why are people here. And also, Bobby. If you want to present any of this, we can always switch and you could present part of the the raw information as well. It's really a collective group effort here.

121
00:15:11.310 --> 00:15:13.140
No, go ahead. You're fine. Okay.

122
00:15:14.160 --> 00:15:17.640
So in terms of the general area we've got

123
00:15:20.610 --> 00:15:28.350
A mix of people, but many of them have actually done project work with hyper ledger.

124
00:15:29.400 --> 00:15:40.740
So, for example, and current project, which I think is most interesting of our like, who are we working with here. There's a lot. There's a number of proof of concepts and pilot applications built

125
00:15:41.940 --> 00:15:55.590
Another one has done multiple projects at different stages will. Another one is exploring hyper ledger fabric quilt in Indy. Another one's completed one project and went to production, and it's doing a few more proof of concepts.

126
00:15:57.390 --> 00:16:02.790
There's a developer even early stage fabric prototype and then

127
00:16:04.290 --> 00:16:15.810
An internal online shop based on fabric composer used in production, and they're creating an offer for a public sector entity do create management and then there's myself.

128
00:16:16.440 --> 00:16:27.780
Which is a little bit different. We actually translate between complex multi stakeholder situations so we we don't build we we help specify and make sure that all types of entities are

129
00:16:29.610 --> 00:16:45.120
Represented so that the product does what it needs for operations, but mostly it seems almost everyone involved to your has at least a proof of concept, if not a full fledged project at multiple stage going on in terms of resources.

130
00:16:46.560 --> 00:16:47.640
We're

131
00:16:49.410 --> 00:16:53.340
Peer Learning is coming up use cases and policy.

132
00:16:55.470 --> 00:17:04.260
Documentation keeping it up to date and technical support so its a mix of things in terms of the sorts of resources.

133
00:17:05.700 --> 00:17:15.810
But they the collaboration and use cases and exchange keeps coming up over and over again. So it seems that in terms of the focus areas, there's interest across all of them.

134
00:17:16.290 --> 00:17:24.630
And while the focus areas are very interesting today in the interest of time, like we discussed earlier, let's just jump to the global forum.

135
00:17:26.130 --> 00:17:27.180
And that will also

136
00:17:28.200 --> 00:17:47.910
Merged into Dr. Moon years presentation. So in terms of the interest in the forum. We have 1234567 potential attendees who are interested

137
00:17:49.020 --> 00:17:56.250
Of which 12345 are willing and interested to actually contribute at the forum.

138
00:17:57.570 --> 00:18:19.590
There's a greater number. I would say 123456789 who would be quite interested to contribute remotely. So this seems to be that there's there's broad interest almost universal in building out some offering or two for the upcoming forum.

139
00:18:20.670 --> 00:18:37.140
In terms of topics. I think we're going to have to work as a group, because we have a wildly diverse extremely interested and a very high appetite for most every topic I

140
00:18:38.280 --> 00:18:50.130
Mean, almost all topics listed on the technical side had at least somebody interested and a majority of them had out of 11 respondents

141
00:18:51.300 --> 00:19:16.170
Are 10 1011 respondents at least four four to five is trending and pretty average, the ones that had a bit more. We're smart contracts with seven and best practices, which also had seven. So, and let's say six on interface. So of all of those. Those are the ones with a slight bit more interest.

142
00:19:18.000 --> 00:19:24.210
In terms of operations, again, a wildly interesting group here that

143
00:19:25.560 --> 00:19:29.220
Found much of the topics quite interesting.

144
00:19:29.280 --> 00:19:36.060
Almost everybody wanted and use your case studies. Almost everyone wanted role of government, as well as governance of

145
00:19:37.470 --> 00:19:43.800
Economics of using blockchain use cases, again, very popular and then

146
00:19:45.630 --> 00:20:06.390
Scattering but still strong on healthcare social impact and initiatives are cases for blocks. So it's pieces and use cases. I think pretty much the same. So we're seeing a lot of cluster in use cases and the role of government and governance. So I think that if we're going to do a second

147
00:20:07.410 --> 00:20:11.610
Broader offering for the forum on top of the

148
00:20:12.420 --> 00:20:14.100
extraordinary efforts at smart to

149
00:20:14.100 --> 00:20:14.520
Buy

150
00:20:14.550 --> 00:20:15.120
It would be

151
00:20:15.180 --> 00:20:19.710
A use case or role of government type of thing or a

152
00:20:19.860 --> 00:20:21.150
technical topic in which

153
00:20:21.150 --> 00:20:33.630
Those who are better place to contribute should to look for direction because there seems to be broad interest across the board. I'm going to pause here because that's enough information, I think, to get a conversation going over

154
00:20:38.970 --> 00:20:42.030
Well, new form. So you them. And when we look at it. This is what he is when he's

155
00:20:43.620 --> 00:20:45.600
Been on there are two kinds of

156
00:20:47.130 --> 00:20:48.810
Participation that we can have

157
00:20:50.010 --> 00:20:55.380
One is more of a presentation on our forum and then

158
00:20:56.610 --> 00:21:02.010
The other was conducting a detailed workshop and the President was a demo.

159
00:21:04.200 --> 00:21:04.770
So,

160
00:21:05.820 --> 00:21:08.910
And initially, when you're looking at it. The focus was

161
00:21:10.170 --> 00:21:14.790
All the way this initial in the email that I sent it probably we're looking at

162
00:21:15.930 --> 00:21:16.860
A presentation.

163
00:21:18.210 --> 00:21:24.240
Actually, most of the content will be coming. And so the very first question is that how do we want to kind of

164
00:21:25.290 --> 00:21:27.990
What format to be participating

165
00:21:29.070 --> 00:21:34.290
On one solution is given the diversity of people involved.

166
00:21:35.370 --> 00:21:37.440
To kind of come up with the kennels

167
00:21:38.670 --> 00:21:41.910
Should that we can have a more of a panel discussion between like people

168
00:21:43.410 --> 00:21:46.860
That would be one suggestion or coming up with the format.

169
00:21:48.090 --> 00:21:56.880
Unless we want. We have increased in that running a workshop in that workshop would certainly be, how could come up with

170
00:21:58.920 --> 00:22:15.330
Use cases and as a blockchain. So when you have typical way of innovation in growing design thinking. But when you talk about blockchain. You have to take a bit of a different approach. And maybe that could be a collaborative workshop which is a much longer.

171
00:22:17.160 --> 00:22:26.220
Matt, you present first and then you go into breakout sessions. So the very first question is what format will we want to participate in

172
00:22:33.540 --> 00:22:37.830
While others think this is rose again I'm going to chime in and and raise

173
00:22:39.180 --> 00:22:40.680
A variant on

174
00:22:40.770 --> 00:22:44.730
On Dr Munoz question which is might be

175
00:22:44.760 --> 00:22:46.020
Interested perhaps

176
00:22:46.080 --> 00:22:47.250
In proposing.

177
00:22:47.880 --> 00:22:49.275
To sessions.

178
00:22:52.740 --> 00:22:54.600
To keep under consideration is a

179
00:22:54.810 --> 00:22:57.060
Doctor Monier has a very

180
00:22:57.060 --> 00:22:57.840
Comprehensive

181
00:22:58.980 --> 00:23:00.900
uzel for a presentation.

182
00:23:02.580 --> 00:23:05.280
Heavily showcases

183
00:23:05.340 --> 00:23:08.700
The work of his team, which I think will be personally

184
00:23:08.730 --> 00:23:09.900
Extremely interesting and

185
00:23:09.900 --> 00:23:10.800
Very valuable.

186
00:23:12.060 --> 00:23:25.890
To the extent that it might be difficult. And I'd be interested. Dr moody and your thoughts for uninvolved parties who are part of the work group to really be able to contribute to that as its as its a contained

187
00:23:26.010 --> 00:23:39.690
Top actually write to me or interpreters, basically it was going towards that direction, but I tried to kind of restraint it because the way I was trying to put forward was

188
00:23:40.560 --> 00:23:54.330
That the first talk about what our government use cases. What are the pains in government that can be solved by a blockchain. What does blockchain bring to the table when we talk about government transformation.

189
00:23:55.380 --> 00:24:10.530
And just to kind of give some weighted based on the work that has already being done. I said, Let's bring one case that the and the case study could be the device yesterday. So the way I was trying to write this proposal was

190
00:24:11.580 --> 00:24:14.880
That most of the presentation should be around.

191
00:24:15.960 --> 00:24:22.650
How to go about identifying candidate use cases blockchain and add value.

192
00:24:25.440 --> 00:24:36.600
What could be those use cases and then a case study. So that's what, that's how I was doing it because otherwise, if I would have just wonder the case study. Then there was kind of as you were saying it was just

193
00:24:38.340 --> 00:24:38.730
Waiting

194
00:24:40.320 --> 00:24:42.210
And this is Leonard high if one

195
00:24:42.390 --> 00:24:47.160
I am very happy. You said that Dr minia because literally you are showcase and

196
00:24:48.240 --> 00:24:50.070
As I think we all agree very

197
00:24:50.070 --> 00:24:55.050
complete set of pain points and lessons learned from your great

198
00:24:55.050 --> 00:24:55.710
Initiative.

199
00:24:56.370 --> 00:24:57.930
And I think everyone will be

200
00:24:58.110 --> 00:25:03.960
Very interested in that because it provides invaluable information to anyone who presents who

201
00:25:05.220 --> 00:25:08.640
Who is pleasant at at the Forum. So thanks for saying so.

202
00:25:14.880 --> 00:25:24.840
On the other side, as it always is saying, I think that is enough for content that can come out in this form, we can consider having more than one essentially

203
00:25:25.950 --> 00:25:30.930
I was really keen, maybe because of the diversity that we have in the girl who have

204
00:25:32.820 --> 00:25:34.710
Panel topic without again.

205
00:25:36.120 --> 00:25:37.140
Presentation topic.

206
00:25:38.760 --> 00:25:47.490
Yes, I think as well said if we can accommodate two sessions, of course, absolutely. We can certainly cover a lot more material.

207
00:25:49.440 --> 00:25:51.540
Addition get more lessons learned from

208
00:25:51.600 --> 00:26:00.030
Other interesting, interested parties. So yeah, if we do have the time. Let's look to see if that's going to be a successful format for this.

209
00:26:11.520 --> 00:26:13.230
While others gathered their thoughts.

210
00:26:13.530 --> 00:26:14.790
This is Rose here.

211
00:26:16.200 --> 00:26:19.920
I still think that that might be a sensible thing.

212
00:26:19.920 --> 00:26:21.270
To do rather than

213
00:26:22.200 --> 00:26:26.460
constrain the amount of time available to really properly.

214
00:26:26.460 --> 00:26:27.240
Showcase

215
00:26:27.300 --> 00:26:28.380
Smart Dubai's

216
00:26:29.820 --> 00:26:32.250
Just because we're sitting in on the fascinating.

217
00:26:32.250 --> 00:26:46.710
Presentation from our last call that easily could encompass presentation slot amply, you know, and really still just scratch the surface and it would be a shame to deprive the audience of

218
00:26:46.800 --> 00:26:49.020
Really having that opportunity to understand this.

219
00:26:49.020 --> 00:26:58.170
Comprehensive internal linking project because we're trying to achieve too many things in one session when we could

220
00:26:58.530 --> 00:26:59.400
Consider

221
00:27:00.015 --> 00:27:06.570
breaking it into two that have different functions. And then we have a bit more breathing room. But what to others think

222
00:27:07.830 --> 00:27:09.150
Any other inputs here.

223
00:27:13.950 --> 00:27:16.410
So just to be clear, this is regarding a session.

224
00:27:18.990 --> 00:27:20.550
The upcoming global forum.

225
00:27:22.440 --> 00:27:23.370
Hyper ledger.

226
00:27:23.580 --> 00:27:26.070
Yeah, yeah. So this is. Yeah. So if

227
00:27:27.420 --> 00:27:38.190
For those who completed the survey. It was the third major section of the survey and it's been brought up before Marta introduce this early on that there

228
00:27:38.730 --> 00:27:40.740
Is Global Forum coming up in December.

229
00:27:40.740 --> 00:27:41.550
Right, right, right.

230
00:27:41.850 --> 00:27:46.770
And the due date for proposals is, I believe, I want to say like the

231
00:27:46.770 --> 00:27:48.720
1313 yes

232
00:27:49.980 --> 00:27:51.390
If we wish to

233
00:27:51.450 --> 00:27:52.410
Propose

234
00:27:54.135 --> 00:27:54.780
A

235
00:27:55.710 --> 00:27:57.240
You know, anything we really need

236
00:27:57.240 --> 00:27:58.380
To decide now.

237
00:27:58.650 --> 00:28:00.690
And then get on it next week.

238
00:28:01.020 --> 00:28:01.830
So,

239
00:28:01.890 --> 00:28:06.720
Today is the day to decide what we'd like to do anything in addition to

240
00:28:07.770 --> 00:28:11.640
The presentation suggestion, and if so,

241
00:28:11.760 --> 00:28:20.190
What would that look like a panel is when idea that would require panelist, and also require a write up of what this would involve so over to everyone.

242
00:28:21.810 --> 00:28:24.960
Yeah, I mean I was gonna suggest if I was thinking, if it is in this

243
00:28:24.960 --> 00:28:25.800
Context.

244
00:28:26.310 --> 00:28:27.390
You might also

245
00:28:27.420 --> 00:28:32.310
plan on doing a workshop or an unconference

246
00:28:33.630 --> 00:28:38.610
Both for after the Global Forum. If everyone's traveling to the same place.

247
00:28:40.200 --> 00:28:46.440
If there's not necessarily room somehow in the agenda for the conference at least people that have

248
00:28:47.895 --> 00:28:50.520
This similar interests that have traveled all that week.

249
00:28:50.580 --> 00:28:51.300
Get together.

250
00:28:53.190 --> 00:28:56.250
Yeah, that's a great idea. And actually a workshop

251
00:28:56.880 --> 00:28:57.840
Or in conference.

252
00:28:57.900 --> 00:28:59.640
Oh, sorry doctrine, but here is

253
00:28:59.790 --> 00:29:00.330
An external

254
00:29:01.380 --> 00:29:03.300
Yeah yeah it's acceptable to we could actually

255
00:29:03.300 --> 00:29:08.160
Proposed that brand have it in the actual the actual agenda of the forum.

256
00:29:08.490 --> 00:29:13.020
So, but the question here is, of course, this isn't working group made

257
00:29:13.020 --> 00:29:25.200
Up of people with interests. This today would be the last feasible moment to come together around any of these ideas. So this is the moment to step forward.

258
00:29:25.200 --> 00:29:25.560
And

259
00:29:25.650 --> 00:29:27.030
Start making a plan if we'd like.

260
00:29:27.030 --> 00:29:27.570
To make one

261
00:29:28.800 --> 00:29:42.600
Yeah. And I think, again, I think that the workshops of natives propose can be initially built around the predominant areas of interest, we've we've basically

262
00:29:43.680 --> 00:29:51.570
glean from the survey that that and yet completion, so we could start using the highest nominated devoted

263
00:29:52.680 --> 00:30:01.530
Categories and see how we can flesh it out to provide interesting workshops for that second session to give us a good stop.

264
00:30:03.930 --> 00:30:14.940
Yeah, I just want to note that this, this group, kind of like the healthcare group is different than other groups in Hyper ledger, in the sense that it's coming from subject matter expertise.

265
00:30:16.860 --> 00:30:21.060
As opposed to coming from a technical community with an open source project.

266
00:30:22.200 --> 00:30:29.070
And you know ultimately the goal of hyper ledger projects is to produce code so

267
00:30:30.630 --> 00:30:37.230
There's a particular challenge for a group that starting from subject matter expertise in terms of finding out where to start.

268
00:30:38.130 --> 00:30:38.580
So,

269
00:30:39.570 --> 00:30:40.530
It's not uncommon.

270
00:30:43.500 --> 00:30:49.140
Something on this the way I understood the description of what a workshop

271
00:30:51.090 --> 00:31:02.310
It changed the nature is that it is led by some people were you are willing to engage the audience of the workshop and then go into breakout sessions.

272
00:31:03.330 --> 00:31:09.780
That is how it has because it is defined in the, you know, in the template shake that is the case.

273
00:31:11.070 --> 00:31:15.630
May be interesting works up could be that

274
00:31:17.250 --> 00:31:18.960
We can a

275
00:31:19.980 --> 00:31:23.430
Different players who have been involved in locking you

276
00:31:24.960 --> 00:31:30.120
Come and discuss the kinds of challenges or digital transformation that Washington song.

277
00:31:31.200 --> 00:31:40.830
And then I do read about a lot of how we can do design thinking sort of blockchain concept with first you kind of build the network and the network constraints.

278
00:31:41.550 --> 00:31:48.510
And then you come out me though you know he can go through the design thinking is given the time that is available in the workshop

279
00:31:48.930 --> 00:32:07.650
It may make sense to school and gives the audience and kind of people identify there won't be any ideas in these groups and then the Kindle consolidate those findings and come up with a summary or an action plan out of that workshop that it makes sense as a little child.

280
00:32:11.580 --> 00:32:12.330
I mean, I say,

281
00:32:13.140 --> 00:32:13.410
Oh,

282
00:32:13.860 --> 00:32:15.180
Go ahead. No, you go.

283
00:32:15.600 --> 00:32:17.340
As gonna say no. I think so.

284
00:32:19.560 --> 00:32:21.030
You know, being that we've been

285
00:32:21.060 --> 00:32:25.770
I've been selling a we've been offering a block chain.

286
00:32:27.570 --> 00:32:28.380
Related

287
00:32:28.710 --> 00:32:40.230
Tool for about four years and the amount of the amount of people that in touch with who don't quite understand it or how to apply it or don't.

288
00:32:40.260 --> 00:32:42.360
Don't understand the transition and thinking

289
00:32:43.470 --> 00:32:53.310
I mean this this is mainly what what I find is that they don't understand the transition and thinking between between hierarchies and decentralization

290
00:32:54.330 --> 00:32:55.050
There's sort of this

291
00:32:55.800 --> 00:32:57.270
Transition and thinking of

292
00:32:57.330 --> 00:33:03.720
From hierarchies to holler keys and being able to balance that and finding the right use cases. So I think that

293
00:33:04.740 --> 00:33:09.480
Giving giving people tools to be able to help others navigate

294
00:33:10.950 --> 00:33:15.270
How to do that. I mean, because that's essentially what you're talking about your experience, right.

295
00:33:17.280 --> 00:33:19.470
I think that's, that's really important.

296
00:33:22.110 --> 00:33:29.190
Certainly, see the same thing and health care, but where healthcare is Paul archaic too smart cities.

297
00:33:32.700 --> 00:33:35.400
You know there's there's a lot of connectivity there.

298
00:33:39.000 --> 00:33:48.600
So you know it's it's it's an. It's an interesting problem. And that's something that I've been trying to figure out how to solve is how do you get people to understand this relationship.

299
00:33:49.380 --> 00:34:00.690
Between you know hierarchical thinking and design of systems and the fact that we live in a hierarchy. And if we externalize the

300
00:34:02.040 --> 00:34:04.110
The flow of entropy

301
00:34:05.520 --> 00:34:11.370
For things in the system that we don't take care of you know the winds up coming back into the system in ways we don't intend

302
00:34:12.420 --> 00:34:13.170
So it's

303
00:34:14.430 --> 00:34:18.390
We have this opportunity. That's what one of the things that block chain and

304
00:34:22.830 --> 00:34:35.280
Pushing intelligence to the edge of the network and you know it's it's. These are all subjects that most people have not even considered in business or in city administration. I just

305
00:34:36.030 --> 00:34:40.320
Just did a workshop at the global tech jam, which was part of the NIST

306
00:34:41.550 --> 00:34:44.730
Smart Cities will global smart cities initiative.

307
00:34:45.150 --> 00:34:45.600
And they had

308
00:34:45.750 --> 00:34:47.040
People from all over the world.

309
00:34:47.310 --> 00:34:49.020
Talking about all of these issues.

310
00:34:49.680 --> 00:34:52.080
You know, they already have working groups.

311
00:34:53.220 --> 00:34:55.740
And super groups actually that span. Some of those

312
00:34:55.740 --> 00:34:56.340
Working Group.

313
00:34:57.270 --> 00:34:58.680
They may even have

314
00:34:58.770 --> 00:35:00.720
Some, some experience.

315
00:35:00.840 --> 00:35:07.440
That's both tapping into and I'd love to get these those groups together because that's another huge body of people

316
00:35:09.570 --> 00:35:10.680
Professionals and

317
00:35:11.580 --> 00:35:13.800
educators who have an interest in this space.

318
00:35:17.160 --> 00:35:24.000
And you know, we definitely want to expand the audience in whatever direction as we can. So I'd like to try to do that as well.

319
00:35:26.910 --> 00:35:32.640
Fantastic, given the the the curl realities of time as

320
00:35:35.400 --> 00:35:37.920
The facto timekeeper today as

321
00:35:37.920 --> 00:35:45.810
Martyrs is unable to be clearly heard, so I'm holding the baton. Thank you everyone for that permission.

322
00:35:46.500 --> 00:35:47.460
If anyone else want

323
00:35:48.450 --> 00:35:49.440
They can, they can

324
00:35:49.800 --> 00:35:53.070
You know request. I see. I see what he says yeah

325
00:35:53.250 --> 00:36:02.130
But, but the reality is, we've got 30 minutes to decide exactly what we'd like to propose in one week.

326
00:36:02.550 --> 00:36:17.160
Given the people who are here today on the call and their interest capabilities and likelihood of being able to attend or to find an alternative to attend if their, their presence is needed. So

327
00:36:17.850 --> 00:36:25.770
We had a I think pretty a pretty compelling and live proposal hear from Dr. Moon year who thought we could do some sort of

328
00:36:27.240 --> 00:36:42.480
Gathering on the discussion if they use cases is and challenges of digital transformation looking at human centered design within network constraints and whatnot and sharing a kind of a bit of a mix of of experiences.

329
00:36:42.810 --> 00:36:44.370
And then turn that into

330
00:36:44.460 --> 00:36:58.680
A an open discussion with the audience who could share their own experiences with the idea that we'd have a proper tour, who would write up some sort of summary learning document from this. That seems like a pretty valid.

331
00:37:00.540 --> 00:37:12.720
In a way to structure it, but what do people think, and most importantly, are there enough people on this call, who feel like they would have some use cases to share to make this the right way to go forward over

332
00:37:31.980 --> 00:37:35.760
Going once, going twice going three times.

333
00:37:37.110 --> 00:37:37.590
Okay.

334
00:37:40.230 --> 00:37:48.630
As it seems like no one has resonated with this is something that might be the correct structure for them.

335
00:37:49.170 --> 00:38:07.560
Does anyone else have any alternative ideas of what they would like to work on to present something at the summit or forum or in spite of having interest, perhaps, would we like to, then maybe transition over and defer to dr Munoz vision and maybe revert to the original idea of a

336
00:38:08.580 --> 00:38:14.580
Single presentation probably heavily focused on the great work of smart Dubai. What do people think

337
00:38:20.760 --> 00:38:23.910
I think that's a great idea can time constraint.

338
00:38:31.110 --> 00:38:32.550
How long are the sessions.

339
00:38:32.610 --> 00:38:34.380
At at the forum.

340
00:38:43.980 --> 00:38:44.550
Situational

341
00:38:47.790 --> 00:38:51.510
And disrupting the email while we can discuss the other point

342
00:38:54.180 --> 00:38:54.540
That

343
00:38:54.630 --> 00:38:55.770
The fact that you've already got

344
00:38:55.770 --> 00:39:01.200
Something made is is helpful and if, if we want to

345
00:39:01.290 --> 00:39:02.670
Because it's going to take some time.

346
00:39:04.380 --> 00:39:06.750
To get some more engagement in the group and

347
00:39:09.060 --> 00:39:11.970
To bring in people who have experience. I mean, if we want

348
00:39:12.270 --> 00:39:12.360
To

349
00:39:12.720 --> 00:39:15.120
Find out other experience to add to

350
00:39:15.390 --> 00:39:16.350
The presentation that

351
00:39:17.250 --> 00:39:17.550
You

352
00:39:19.230 --> 00:39:27.510
Just add just give you the details. There is therefore type. So one is a breakout session, which is typically 14 minutes in length.

353
00:39:28.260 --> 00:39:41.130
And if you're proposing a panel discussion in this breakout session. Then again, it's 40 minutes and you need to be ever maximum off one moderator and panelists. The other is a think tank.

354
00:39:42.150 --> 00:39:49.830
Which is a discussion forum with somebody special imitating only 20% of the time with 80% audience interaction.

355
00:39:50.940 --> 00:39:59.190
The third is a workshop which is a facilitated discussion around deployments that team of the workshop will be introduced.

356
00:39:59.730 --> 00:40:08.010
You end up to three additional facilitators will give attendees topics for discussion attendees will then break out into smaller groups to discuss

357
00:40:08.580 --> 00:40:18.150
Or share their experience and talks with one another, culminating with a report out back to the group with a summary of the lessons learned. Next step and best practices, etc.

358
00:40:18.960 --> 00:40:27.000
And the last one is a demo theater where you can showcase your hyper ledger power deputation in enlightening talk format 10 to 15 minutes

359
00:40:27.720 --> 00:40:36.420
Now the workshop, they do. I don't see a time for the workshop, but I believe it should be much longer than the 14 minutes given for the breakout session.

360
00:40:42.990 --> 00:40:47.010
So we have either the think tank discussion forum or the breakout session, which are 40 minutes

361
00:40:48.075 --> 00:40:49.290
40 minutes

362
00:40:52.110 --> 00:40:55.560
Seems to the workshop is more than that. Maybe a couple of hours. I don't know.

363
00:40:56.190 --> 00:40:56.730
Okay.

364
00:40:58.350 --> 00:40:58.680
Here's

365
00:41:00.360 --> 00:41:06.390
A call here feels like there's a reasonable odds that they would actually attend the forum.

366
00:41:10.020 --> 00:41:10.560
I will

367
00:41:14.490 --> 00:41:15.120
Be attending

368
00:41:17.370 --> 00:41:18.330
Hello, Marcus.

369
00:41:19.590 --> 00:41:20.460
Anyone else

370
00:41:31.200 --> 00:41:33.960
Okay, well, working from the fact that we have

371
00:41:35.400 --> 00:41:37.860
Two or three attendees on being

372
00:41:39.150 --> 00:41:50.940
Who's got a very comprehensive proposal Marcus and I may attend depending on whether it would be useful for any of the things the screw proposes, but only in that case.

373
00:41:53.160 --> 00:41:54.780
Marcus. Do you

374
00:41:54.870 --> 00:41:56.250
Have any interest.

375
00:41:56.400 --> 00:42:03.870
To be a presenter, and I apologize if you put this in the in the survey, but I

376
00:42:05.460 --> 00:42:08.190
Wouldn't mind feeding in about whether you have any interest about

377
00:42:08.190 --> 00:42:12.720
Presenting are shaping or if you aim to go shrewdly to participate and learn

378
00:42:14.220 --> 00:42:24.180
would not mind them being a presenter will putting in one or two conflict post status. Anyways, I would not mind.

379
00:42:26.580 --> 00:42:29.400
Perhaps then you'd like to speak a bit more about

380
00:42:31.860 --> 00:42:37.710
Your background or context or what you might be thinking, start throwing that around with the group a bit

381
00:42:39.690 --> 00:42:40.920
Organization, by the way, sorry.

382
00:42:41.550 --> 00:42:42.930
It's for eyes.

383
00:42:46.890 --> 00:42:47.640
Would you do

384
00:42:47.790 --> 00:42:49.710
What, what does your organization do

385
00:42:50.550 --> 00:42:51.510
Software.

386
00:42:51.720 --> 00:42:54.270
Development consultancy company.

387
00:42:56.130 --> 00:42:57.030
Therefore I'm

388
00:42:57.720 --> 00:42:58.350
From the

389
00:42:59.040 --> 00:42:59.880
vendor side.

390
00:43:01.950 --> 00:43:02.250
And

391
00:43:09.300 --> 00:43:09.540
From

392
00:43:10.440 --> 00:43:12.345
The same city well conference will be

393
00:43:17.580 --> 00:43:17.790
Sure.

394
00:43:18.750 --> 00:43:23.550
And yeah, we'll have a technical talk presenting this

395
00:43:24.870 --> 00:43:25.410
Channel.

396
00:43:25.440 --> 00:43:26.850
online shop, we've made.

397
00:43:27.900 --> 00:43:33.030
And will also probably present this management information system.

398
00:43:33.030 --> 00:43:33.870
We are about

399
00:43:33.930 --> 00:43:35.070
To implement

400
00:43:35.850 --> 00:43:43.680
Or a government agency, but there are still waiting on confirmation, whether the project will actually be happening. And also, if

401
00:43:44.040 --> 00:43:48.180
Customers comfortable presenting his

402
00:43:48.525 --> 00:43:51.930
Case on in this forum.

403
00:43:53.250 --> 00:43:59.850
But other than that, I'm if it's if if if any have to the group or to the presenter.

404
00:44:01.440 --> 00:44:05.550
Happily work, but the group to make something happen.

405
00:44:09.960 --> 00:44:16.980
Great. I don't know how many people are using the zoom group chat, but martyrs actively participating in the chat.

406
00:44:18.930 --> 00:44:22.470
She will be attending and she would be happy to help shape and other

407
00:44:22.470 --> 00:44:23.340
Submission

408
00:44:23.430 --> 00:44:30.900
If there are people and if if we pick a topic and she's saying, for example, privacy analysis of government use cases or

409
00:44:30.900 --> 00:44:33.630
Something so if if

410
00:44:35.040 --> 00:44:39.030
What Martha is suggesting privacy in their lessons of government use gift.

411
00:44:40.290 --> 00:44:55.500
giving her the expertise, also, that is an excellent panel discussion also. So if we want to have a panel discussion, maybe visa. Is that ok with one is we're talking about blockchain use cases. And the second part could be a bad

412
00:44:56.850 --> 00:45:07.020
Maybe Marta can more rated and we're talking about privacy and you know DDP issues and even when it comes to block chain.

413
00:45:12.210 --> 00:45:14.070
I can add to that milestone. This

414
00:45:14.760 --> 00:45:16.500
That was a popular subject.

415
00:45:17.250 --> 00:45:28.740
I did a workshop on block chain and smart cities, which was followed by data and privacy and almost no one moved and there was more people who are you know people added to the room.

416
00:45:29.370 --> 00:45:31.170
When they got to the data and privacy.

417
00:45:31.470 --> 00:45:33.570
Session. So it's definitely a particular subject.

418
00:45:38.430 --> 00:45:41.850
Terrific. What is also excited and says, I'm for doing it.

419
00:45:43.020 --> 00:45:57.810
Seems like you. I think that's we have a topic, then I guess we should be talking about. We should be talking about you know paneled a panel of privacy in government use cases previously analysis government use cases.

420
00:46:00.300 --> 00:46:13.260
The panel requires at least one female panelists. So if martyr. Does the owners, we feel that we can fill that requirement. Also, and we have reviewed may have a few of the people from the group.

421
00:46:18.750 --> 00:46:19.260
Great.

422
00:46:21.330 --> 00:46:24.360
In the interest of time, perhaps

423
00:46:26.880 --> 00:46:27.660
We

424
00:46:27.690 --> 00:46:33.360
Looking at our timing here. I know Dr. Moody, or you need to present and update us

425
00:46:34.800 --> 00:46:45.840
As well as we need to figure out who would like to collaborate together on the privacy analysis of government use case topic which marvelously was suggested by Marta.

426
00:46:48.375 --> 00:46:52.560
Shall we have a show of hands of who would like to continue this discussion offline.

427
00:46:54.120 --> 00:46:57.060
And then move on to the next phase. What you people think

428
00:47:01.410 --> 00:47:06.420
At least identify who would our panelists who would like to be a panelist on that, if this is a battle.

429
00:47:08.820 --> 00:47:12.240
And then we can start writing it up because we only have this week to submit

430
00:47:14.610 --> 00:47:15.120
Indeed,

431
00:47:16.440 --> 00:47:24.360
Also calling out that Marcus has already nominated a you you Parliament MEP as a potential panel participant.

432
00:47:29.880 --> 00:47:37.890
Alright, well, I think that, at minimum, it sounds like Dr Monier you're interested, Marcus you're interested Marta is interested

433
00:47:38.340 --> 00:47:40.830
I'd be happy to contribute.

434
00:47:40.890 --> 00:47:42.540
To some of the thinking on this.

435
00:47:43.050 --> 00:47:45.510
Does anybody else want to be

436
00:47:45.810 --> 00:47:48.510
Part of this, the formation of the submission

437
00:47:48.540 --> 00:47:50.100
Irrespective of your attendance.

438
00:48:04.200 --> 00:48:12.540
Going once, going twice. Alright, well, we'll continue the discussion, then I think through chat and email, perhaps a secondary call if that's nice.

439
00:48:13.680 --> 00:48:15.300
Email would be best. I think to get

440
00:48:15.300 --> 00:48:16.980
Going and it looks like we have our core

441
00:48:16.980 --> 00:48:18.180
Group here who would like

442
00:48:18.105 --> 00:48:19.530
To the page.

443
00:48:20.490 --> 00:48:26.670
So with no more ado, please. Let's move on to the rest of our very interesting adjust

444
00:48:28.380 --> 00:48:30.540
My one question is on the

445
00:48:32.880 --> 00:48:41.130
On the breakout session. What, what is that up, or do you guys suggest some changes to that. Secondly,

446
00:48:42.330 --> 00:48:47.580
If I am presenting for the new co presenter and who will be the problem, we can have up to one couple mentors.

447
00:48:52.500 --> 00:48:57.870
Do you feel that it would be helpful to have a co presenter, because I know that is an optional thing.

448
00:48:59.190 --> 00:48:59.370
Yet

449
00:49:05.790 --> 00:49:08.610
Another perspective or somebody who can choose

450
00:49:20.760 --> 00:49:26.190
If I may, I think that you are really truly the expert on smart Dubai and

451
00:49:26.220 --> 00:49:28.530
Again could easily fill the time

452
00:49:30.120 --> 00:49:30.600
In more

453
00:49:31.260 --> 00:49:32.310
With what you have learned

454
00:49:33.150 --> 00:49:38.370
Is that, like, there's not other efforts going on and other places. They're just not here yet so

455
00:49:39.870 --> 00:49:40.920
This is our first time.

456
00:49:43.200 --> 00:49:49.920
What I do is, for now, I just went submit it and that if we will change later on. And if it

457
00:50:05.190 --> 00:50:06.030
sounds excellent.

458
00:50:07.110 --> 00:50:11.880
Munoz there anything else that you would like to delve into as part of your

459
00:50:12.450 --> 00:50:12.780
Time.

460
00:50:15.420 --> 00:50:17.340
Is anything on this little we have to

461
00:50:19.140 --> 00:50:24.510
Start writing up so I guess in the next few days related. I had a presentation for the

462
00:50:25.680 --> 00:50:33.120
Which was a pretty long one, but don't have much time. And this was on the policy framework, but I guess I'll just

463
00:50:34.290 --> 00:50:42.540
Since we have shocked time and just take five minutes and we came out very high level overview of what policy considerations should there be

464
00:50:44.460 --> 00:50:47.160
When we are talking about blockchain and public sector.

465
00:50:55.230 --> 00:50:55.950
Proceed with that.

466
00:50:59.790 --> 00:51:02.310
Figured out how to share my slide that

467
00:51:07.140 --> 00:51:09.900
There's a little button that says share screen perhaps

468
00:51:37.980 --> 00:51:39.930
My block chain. Excellent.

469
00:51:40.620 --> 00:51:54.750
Okay, so basically, when we started the journey we quickly realized that we need to have retained policies, when it comes to block chain and some of those policies could be

470
00:51:56.370 --> 00:52:08.520
really specific to our environment, but a lot of them had to do with when we are going to deploy a block chain at enterprise level or at a government level. So what should we be looking at

471
00:52:09.900 --> 00:52:17.760
The. So last year we can have were developed was with IBM for developed a very high level policy framework.

472
00:52:19.380 --> 00:52:35.460
And now, actually, we're working with the WC to come up with detailed policies, you know, we're deep dive and come up with very detailed policies, some of those policies are specific to our environment. But a lot of these policy.

473
00:52:36.720 --> 00:52:40.920
Will be common to whichever whichever government entity is going ahead.

474
00:52:42.120 --> 00:52:46.680
And deploying block chain across so that maybe have a lot of crystal, the group.

475
00:52:47.790 --> 00:53:08.520
But we realized that probably they will be see pillars for this policy framework. One is at. I want the foundational capabilities. What should the platform be which enabling services. So those would be very specific to one environment. The other is around governance and technology.

476
00:53:09.990 --> 00:53:15.270
So much will areas would be like ownership and membership of these networks.

477
00:53:16.410 --> 00:53:20.340
Architecture and standards, which would be specific to a particular network.

478
00:53:21.930 --> 00:53:25.440
security, privacy and risk management for these

479
00:53:27.750 --> 00:53:28.860
often use cases.

480
00:53:30.330 --> 00:53:35.130
The fifth one is against specific to a particular environment, which is funding and accounting

481
00:53:36.240 --> 00:53:44.220
The six days. Very interesting, which is dispute resolutions and which becomes very interesting it once you go cross jurisdiction.

482
00:53:45.510 --> 00:54:02.310
THE 70s communication and adoption policies. And finally, last but not least, the global reach federal international networks cross border use cases. So we have to come up with any detail policies, at least in these areas.

483
00:54:03.480 --> 00:54:11.070
And, you know, large enterprise why you don't a city or a government wide block strategy.

484
00:54:12.660 --> 00:54:14.580
So some of the examples.

485
00:54:16.560 --> 00:54:19.470
When we talk about organization design and

486
00:54:20.700 --> 00:54:24.990
Your oneness and that we have, of course, the ownership and the membership polishing.

487
00:54:27.060 --> 00:54:34.020
Ownership of the business processes that implementation maintenance of the network, network maintaining the network registries.

488
00:54:35.370 --> 00:54:43.140
The other is member onboarding off boarding policies and the roles and responsibilities of the members network.

489
00:54:44.790 --> 00:54:58.950
On the architected and standards ways of course every environment will have to come up with blockchain technology blueprint, we had a very detailed blockchain technology blueprint that implemented so adherence to that the standards have to come up

490
00:55:00.660 --> 00:55:03.540
Plus the other related standards.

491
00:55:04.740 --> 00:55:11.100
You know, digital identity plays a key role in most of these use cases. So what are the underlying standards there.

492
00:55:12.510 --> 00:55:24.210
On the security, privacy and risk management. We have to have became policies on ensuring criticism of the transactions with in case of blockchain. We may even have to look at

493
00:55:25.680 --> 00:55:28.020
how you're going to handle transferable so

494
00:55:29.310 --> 00:55:32.580
A lot of jurisdictions would not have address that.

495
00:55:33.780 --> 00:55:36.210
Then the principles of inspection or the thing

496
00:55:37.800 --> 00:55:43.680
Managed violations and risk management principles which will be dependent. So blocks in network.

497
00:55:45.150 --> 00:55:53.880
Was under the funding and account policies cross sector, you know, players from the inspectors. How would you find an account for these

498
00:55:54.960 --> 00:55:55.470
Networks.

499
00:55:56.610 --> 00:55:58.620
And finally have the dispute resolution.

500
00:56:00.270 --> 00:56:01.950
Guidelines to legal recourse.

501
00:56:03.660 --> 00:56:10.710
In case a smart contracts. How do you handle. We're just legal recourse comes in so detailed policies have to come in and that area.

502
00:56:12.090 --> 00:56:18.930
On the organization designed the communication interruption side of course approach for communicating

503
00:56:20.250 --> 00:56:24.450
Key capabilities needed in the public sector for blockchain adoption rate to work on that.

504
00:56:25.560 --> 00:56:32.490
Great at and applause for migrating all use cases to block chain. And now we have a very clear objective of

505
00:56:33.840 --> 00:56:42.300
Pretty much training every applicable transaction on blockchain by 2020 so we have to have a very aggressive approach towards that.

506
00:56:43.350 --> 00:56:47.910
Then completion certificate in approaches and principal across

507
00:56:49.080 --> 00:56:56.700
One network versus multiple networks and then integration, this becomes probably the biggest and the most interesting

508
00:56:57.930 --> 00:56:58.590
Question.

509
00:57:00.120 --> 00:57:04.380
In a government situation one network work versus multiple networks.

510
00:57:05.850 --> 00:57:13.020
Depending on in my set myself also depending on which side of the bed I wake up in the morning I, are you one way or the other.

511
00:57:14.040 --> 00:57:22.800
Says marriage and the marriage and of course some of the extra come up with detail for the season that we have seen videos example we have seen

512
00:57:23.520 --> 00:57:34.020
Players like yourself and others. We are multiple networks and reward seems examples of, let's say, let's try and being me as a, you know, somebody has built up one large network.

513
00:57:35.280 --> 00:57:44.940
On there. So that's a very interesting point, then the foundational capabilities of your platform. And then it makes services around it.

514
00:57:47.040 --> 00:57:51.600
They would be centralized platform versus entity specific approaches.

515
00:57:52.710 --> 00:58:08.760
And finally on the global reach side expanding these use cases to international participants, they would be a lot of cross border use cases, especially when you bring in create finance and you created building in remittance global travel

516
00:58:09.930 --> 00:58:18.960
These kind of use cases are very cross water and even for us. I mean, a lot of times, especially by as many unique

517
00:58:20.190 --> 00:58:30.300
Place in one perspective that majority of the people here are expatriates so even if I have to bring in a document and a test that document that

518
00:58:31.500 --> 00:58:37.440
other jurisdictions, get involved and pretty much every aspect of a citizen journey in the way

519
00:58:40.350 --> 00:58:41.550
So this is even this

520
00:58:43.290 --> 00:58:45.810
High level policy framework event about

521
00:58:47.340 --> 00:58:50.250
Defining detail policies. Any idea.

522
00:58:52.080 --> 00:58:55.350
What is the objective overview. What are the guiding principles.

523
00:58:57.390 --> 00:58:59.520
That we are going to address so

524
00:59:00.840 --> 00:59:03.750
We don't have that much time left in the cause.

525
00:59:05.970 --> 00:59:14.130
Let me take, let's say one policies so we can they find let's say ownership and membership. So, we define the objective that

526
00:59:15.360 --> 00:59:18.150
Defined approach and which entity even define the network's

527
00:59:20.340 --> 00:59:25.470
One approach that we took us probably instead of one network what in multiple networks.

528
00:59:27.090 --> 00:59:32.730
Which are more sectoral networks and every sector has a sector head which becomes a nodal entity.

529
00:59:33.780 --> 00:59:34.620
And then

530
00:59:35.970 --> 00:59:44.640
You define principles on which actually entity will own the network defined principles on defining members for the network enrollment approach for this networks.

531
00:59:45.660 --> 00:59:47.070
Then the policy and overview

532
00:59:48.750 --> 00:59:50.100
How you do behind the facts of

533
00:59:52.710 --> 00:59:57.840
What the network be private permission network what regulation will be quiet.

534
00:59:59.940 --> 01:00:11.850
So they're kind of on the old recites and then the define detail guiding principles, who would the North northern entity be who would be the owner entities and what kind of member entities and be there.

535
01:00:14.820 --> 01:00:16.830
And then the key metrics on

536
01:00:18.720 --> 01:00:20.790
On various policy principles.

537
01:00:23.190 --> 01:00:32.610
around that. So this was, this is who are the so we can have said, Okay, let's take the ownership part. So in our first approach. What we did was we divided

538
01:00:33.330 --> 01:00:47.400
Everything into like 11 or 12 sectors all citizen journeys and identified an anchor entity for each sector and started anything sector networks, but I have seen certain metrics and

539
01:00:49.050 --> 01:00:50.250
Going beyond this and

540
01:00:51.600 --> 01:00:54.600
Building larger networks, also. So what we'll do that.

541
01:00:56.550 --> 01:00:56.880
And

542
01:00:58.740 --> 01:01:01.440
We then have more ownership and membership.

543
01:01:04.110 --> 01:01:12.780
So I guess we're out of time, so I'm just kind of wanted to share that this is how we went ahead with developing a very high level.

544
01:01:14.340 --> 01:01:24.690
Framework for these policies and my understanding is that every other jurisdiction every of the city or country government that is looking at

545
01:01:26.250 --> 01:01:33.900
The moment level, you know, across the board, locked in implementation would have to come up with such a deep end.

546
01:01:35.190 --> 01:01:37.110
Not only a framework but detail policies.

547
01:01:38.220 --> 01:01:49.230
And my objective was to kind of learn from the forum if others have come up or implemented for this year. So we can do some knowledge that is

548
01:02:00.450 --> 01:02:01.350
Thank you document.

549
01:02:02.460 --> 01:02:03.240
70 slide.

550
01:02:04.260 --> 01:02:06.930
slide deck, but I don't think you're trying to present

551
01:02:10.980 --> 01:02:13.440
Might be a very good idea so that we can

552
01:02:14.130 --> 01:02:15.300
Learn at a

553
01:02:15.420 --> 01:02:16.650
reasonable pace.

554
01:02:16.710 --> 01:02:18.600
As obviously scratching.

555
01:02:18.690 --> 01:02:20.430
The surface of an enormous amount

556
01:02:26.550 --> 01:02:27.780
All right. Shall we consider this

557
01:02:27.930 --> 01:02:29.100
User, as it were.

558
01:02:30.600 --> 01:02:34.620
What may be coming in an upcoming soon presentation.

559
01:02:34.890 --> 01:02:41.190
Here, I guess, because we only have 10 minutes left, so I couldn't have gone through the slide deck. So let's do this in

560
01:02:42.225 --> 01:02:44.310
How we are doing the next sessions and what

561
01:02:46.290 --> 01:02:50.910
They've been one of the following questions. If I have 30 minutes or something, making them.

562
01:02:59.460 --> 01:03:02.730
That seems like a good way and rational way forward.

563
01:03:04.380 --> 01:03:07.350
All right, I will start to just bring us together.

564
01:03:19.140 --> 01:03:23.730
Well, it seems like no one has set like that. They're not interested. I think this is

565
01:03:23.910 --> 01:03:24.660
Quite interesting

566
01:03:26.310 --> 01:03:27.540
To see a good interested so

567
01:03:30.210 --> 01:03:30.660
I'm sure

568
01:03:33.840 --> 01:03:36.525
I put a link into the chat for that this

569
01:03:37.410 --> 01:03:42.480
Program, the global city teams challenge and they've got

570
01:03:44.040 --> 01:03:45.750
50 or 80 cities.

571
01:03:46.680 --> 01:03:50.010
Largely in the US, but some around the world.

572
01:03:51.510 --> 01:03:53.700
In Asia, Japan, Korea,

573
01:03:55.080 --> 01:03:59.280
And I've and I've been in touch. You know, in doing the research for that other workshop I did.

574
01:03:59.790 --> 01:04:01.290
With some other folks.

575
01:04:02.310 --> 01:04:07.260
In other cities. So, I mean, I'm happy to in the background. I've sent you a connection request that

576
01:04:08.190 --> 01:04:08.610
Near but

577
01:04:10.350 --> 01:04:12.480
If you want to find some more, you know,

578
01:04:13.080 --> 01:04:16.710
Examples to pull in, there's an opportunity there. So,

579
01:04:19.440 --> 01:04:20.190
That's great, Nate.

580
01:04:20.250 --> 01:04:23.130
Would you then like to participate in the development

581
01:04:23.160 --> 01:04:29.340
Of the proposal for the summit, as you might have some great ideas of who else to bring in

582
01:04:29.820 --> 01:04:38.100
I can participate at that level. I know that I won't be able to be there, but I can certainly help him and connecting some dots and things like that so

583
01:04:39.120 --> 01:04:39.600
Terrific.

584
01:04:43.200 --> 01:04:52.050
All right, well, noting the time with everyone's leave and as, like, I suppose organizer coordinator today. So thank you.

585
01:04:52.890 --> 01:05:13.470
This has been actually a fairly action packed and productive session in which we've determined that there will be two submissions. One is already quite complete Sparky by the other one is going to be on privacy and there will be a subset, who will organize this week.

586
01:05:14.550 --> 01:05:23.430
And put something together that I'm sure we'll be extremely interesting and productive. We also got a high level overview of

587
01:05:24.570 --> 01:05:35.670
What is happening on policy and smart Dubai and look forward to having a more proper focus session around that when we have the ability that time aside. But I think for the moment.

588
01:05:36.690 --> 01:05:47.550
We're going well, but also Bobby will be, I presume, helping to share the surveys, it seems that folks are interested, Justin, seeing the raw data.

589
01:05:48.060 --> 01:06:03.900
With redacted names which I suppose is fine for the moment, but once we've worked through our immediate priorities to get out our submissions, the global summit, we can really start to dig into order people's interest areas and start building out presumably

590
01:06:04.920 --> 01:06:07.260
Further agendas for the group so

591
01:06:07.530 --> 01:06:10.260
That's over and out from my perspective, if anyone else.

592
01:06:10.350 --> 01:06:14.250
Like to chime in. Before we go along. This would be a great time today.

593
01:06:15.150 --> 01:06:15.540
You may

594
01:06:16.920 --> 01:06:17.850
Want to get one thing

595
01:06:18.930 --> 01:06:21.840
Really like to see if we can

596
01:06:23.160 --> 01:06:31.680
Try to identify some interesting clause for the fuel. She gonna think that we can work together on

597
01:06:33.930 --> 01:06:37.980
Lots of ideas. If the phone can kind of identifying something weird

598
01:06:45.330 --> 01:06:46.020
Well, noted

599
01:06:48.090 --> 01:06:49.770
Shall we say goodbye for the moment.

600
01:06:50.670 --> 01:06:51.090
Until

601
01:06:52.500 --> 01:06:53.970
By everyone and looking forward to

602
01:06:53.970 --> 01:06:55.590
Collaborate. Thank you so much.

603
01:59:06.210 --> 01:59:08.700
Hey everybody this is Melissa here.

604
01:59:09.720 --> 01:59:19.950
Just waiting for folks to get on and we'll get going here shortly. Thanks for thanks for joining us this morning or afternoon or evening, wherever you are.

605
02:02:07.980 --> 02:02:08.970
For joining us this morning.

606
02:02:17.520 --> 02:02:21.090
So right at nine o'clock. We're going to give folks a couple more minutes.

607
02:02:23.220 --> 02:02:36.300
I'm going to share my screen so that folks can see the antitrust policy or start with here and then I just reminder for folks that if they're not speaking to please meet their phones.

608
02:02:36.840 --> 02:02:47.610
Just to help us with background noise and the agenda is in the chat box as well. If anyone wants to review that before we get going here.

609
02:03:20.400 --> 02:03:29.490
Yes, I can't ask while we're waiting, I think I see some new folks on the line. Does anyone have any initial, initial questions before we get going.

610
02:03:43.170 --> 02:03:45.510
Tony little online. Hey, Tony. How's it going,

611
02:03:47.100 --> 02:03:49.050
Good, how are you okay

612
02:03:52.590 --> 02:03:55.530
Just waiting for my little one to arrive here. Any, any day now.

613
02:03:55.860 --> 02:03:58.860
I was just gonna say how are things going on. You got to be good and close

614
02:04:01.020 --> 02:04:07.140
Yeah, yeah, the engines revenue here at you contractions yesterday and we're, we're getting close. So we're excited here.

615
02:04:07.680 --> 02:04:09.630
All right, fingers crossed. Best of luck.

616
02:04:11.190 --> 02:04:11.640
Thank you, sir.

617
02:04:24.120 --> 02:04:33.990
All right, well, why don't we get going. Just to start out of want to read this. Just as a reminder for folks. So the antitrust policy for the Linux Foundation.

618
02:04:34.620 --> 02:04:44.250
The meetings involve participation by industry competitors and it is the intention of the Linux Foundation to conduct all of these activities in accordance with applicable antitrust and competition was

619
02:04:44.760 --> 02:04:54.930
It is therefore extremely important that attendees adhere to meeting agendas and be aware of and not participate in any activities that are prohibited under applicable US Federal

620
02:04:55.320 --> 02:04:57.630
Or foreign and to trust in competition loss.

621
02:04:58.470 --> 02:05:09.120
Examples of types of action that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation antitrust policy available at

622
02:05:09.960 --> 02:05:21.060
This URL. I'll put it in the chat box as well. If 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

623
02:05:21.810 --> 02:05:30.210
Grove of the firm of guests mirror up to grow LP, which provides legal counsel to the Linux Foundation.

624
02:05:33.360 --> 02:05:33.780
That's

625
02:05:35.250 --> 02:05:42.870
The URL here as just for for folks that are our new online really quick.

626
02:05:44.190 --> 02:05:52.920
Summary. So this is the the patient sub group meeting for the hyper ledger healthcare working group.

627
02:05:54.180 --> 02:06:02.160
And we this is our fourth meeting. So getting getting this off the ground and we've been really having

628
02:06:02.610 --> 02:06:24.390
Some pretty good conversations just around particular use cases that we are interested in and kind of defining a problem statement that we're we're looking to tackle. Tackle as a group. Ultimately the goal is for us to basically start with conversations around use cases and

629
02:06:25.890 --> 02:06:36.990
And requirements and build something eventually that will help contribute you moving development in the block chain space for it is particularly around healthcare and the patient centered

630
02:06:38.400 --> 02:06:41.250
Perspective and for folks that are

631
02:06:43.440 --> 02:06:50.520
More and have been involved from the beginning. Does anyone have anything to add, as far as context setting for for this up group.

632
02:06:59.010 --> 02:06:59.340
Great.

633
02:07:02.400 --> 02:07:10.680
And then we do so for today really what we're going to want to be focusing on is the conversations that we've had so far is really defining this

634
02:07:11.460 --> 02:07:23.010
This problem statement regarding connecting data longitudinally across silos in the healthcare sector with the patient at the center of that that effort and

635
02:07:23.460 --> 02:07:42.690
What we are hoping to do today is just to review the business case that we have so far and and start discussing a little bit more power going to start teasing out from that larger problem statement, the specific use cases that we can then

636
02:07:44.520 --> 02:07:54.120
Take a break down and more into requirements and dig a little bit deeper in I think we have Tony on the line, Tony seen online as well. He was

637
02:07:54.480 --> 02:08:10.890
On the call last week and we had some conversation about kind of workflows that maybe we want to explore and so I'll turn it over to Tony to kind of put his ideas out there and we can use that as kind of a starting point for that that conversation.

638
02:08:12.180 --> 02:08:18.300
And then, of course, we'll just wrap up and talk about actually made his next steps. Any questions on that.

639
02:08:22.530 --> 02:08:34.290
So I do see some new folks on the call. And I just like to open up the floor. If anyone would like to introduce themselves and let us know kind of what your interest is in the group and what

640
02:08:44.880 --> 02:08:46.710
It's a mighty quiet group this morning.

641
02:08:49.860 --> 02:08:52.290
Everybody still trying to recover from July 4

642
02:08:55.260 --> 02:09:01.875
I'LL SAY HI, THIS IS JOHN with University of California Davis and

643
02:09:03.210 --> 02:09:07.050
Thanks for letting me join the group we're developing some courses.

644
02:09:08.130 --> 02:09:09.990
In this area, and

645
02:09:11.400 --> 02:09:16.050
I appreciate the the interaction. So that's my background.

646
02:09:19.980 --> 02:09:22.740
Actually did my first year of college and UC Davis, so

647
02:09:23.190 --> 02:09:23.490
Cool.

648
02:09:23.820 --> 02:09:25.290
That's amazing. I love that.

649
02:09:25.320 --> 02:09:28.620
That location that University. Welcome. Thank you.

650
02:09:31.890 --> 02:09:33.240
Hi Kate founder

651
02:09:34.620 --> 02:09:40.230
And I'm from excellent health and thank you for putting this together, enjoying the conversation.

652
02:09:44.820 --> 02:09:51.360
Welcome T. Can I ask, is there anything in particular that brings you to the group or areas of interest, where you

653
02:09:54.855 --> 02:10:10.170
Actually have been looking at a project with Oracle Enterprise blockchain and just now it's, you know, some some meetings where we're thinking through what might be a pilot or a project, very early on with Oracle

654
02:10:11.910 --> 02:10:12.930
Great, thank you.

655
02:10:14.970 --> 02:10:19.560
Hi this is john Riley and with CNC blatche and advisory I'm in West Palm Beach, Florida.

656
02:10:20.040 --> 02:10:29.670
And I'm on board because I'm working with some hospitals down here that are about to look at doing an executive roundtable on blockchain. I recently spoke at a healthcare conference for them.

657
02:10:30.180 --> 02:10:39.390
And now they're really just getting their feet wet, so being able to share information like this. So what's going on that can benefit them is it's very helpful to me in those conversations

658
02:10:45.390 --> 02:10:47.010
Thank you. JOHN, welcome. Thank you.

659
02:10:58.650 --> 02:11:06.495
Gentlemen, I'm with a company called Black rich technology and my interest is in the cyber security piece of all this, how do you

660
02:11:11.910 --> 02:11:13.800
Definitely a critical one.

661
02:11:17.670 --> 02:11:19.230
And then I don't know.

662
02:11:20.340 --> 02:11:30.480
If people would like to hear some other introductions and we have Tony little rich black who have been part of the group for a while. Would you guys like to give a quick interest as well.

663
02:11:33.030 --> 02:11:34.410
Sure, sure. I can start

664
02:11:35.190 --> 02:11:48.180
That's okay. Go forum, Tony. Thank you, rich, but Tony little here. I'm a physician by training and technologist by trade, I work for optimum, which is part of the United Health group.

665
02:11:49.200 --> 02:11:56.670
Here at optimum. We have been in the process of evaluating and creating a block chain solutions for almost three years.

666
02:11:57.660 --> 02:12:07.950
It's a long process to get to a point in which you can do a proof of value and we were doing that right now with a few other payers. When I say other players. I mean, United Healthcare, and then

667
02:12:09.060 --> 02:12:20.850
Humana multi plan also included in there as Quest Diagnostics which is technically a provider, but we're doing a pilot on

668
02:12:22.590 --> 02:12:28.590
How to manage or better manage provider data and the healthcare space amongst mostly payers, as I mentioned,

669
02:12:30.000 --> 02:12:35.490
And we hope to have a white paper out on it by the end of the year, we do have production level data running

670
02:12:36.630 --> 02:12:45.660
And are very excited about not just that use case, of course, but how block chain could potentially create a utility for block or healthcare data.

671
02:12:46.350 --> 02:12:59.850
That can be used by the entire industry. So it's good to be here and and be involved and I really appreciate all the inputs. There's lots of new and exciting things going on here, impossible to keep track of it all. This is one way to to get a little slice of that.

672
02:13:03.720 --> 02:13:07.260
And also add Tony is going to be a dad again very soon.

673
02:13:08.220 --> 02:13:09.090
graduations right

674
02:13:12.075 --> 02:13:20.280
So my name is Rich black so i'm also sort of a Seattle area person. My backgrounds and systems and software engineering

675
02:13:21.030 --> 02:13:31.410
I spent 10 years at Microsoft. Sometime ago transitioned over to do D military and did some work in that space for a while and then probably the past 10 years

676
02:13:32.040 --> 02:13:42.330
Focused our engineering in the healthcare space and then the past few years started looking into applications of black chain in healthcare.

677
02:13:43.260 --> 02:13:53.400
And so at the moment where we've got a small start up that we're working on doing some patient facing work in block chain space for the sake of health care.

678
02:13:54.330 --> 02:14:04.620
We're doing some stuff out on the Olympic Peninsula with a couple of providers. And yeah, this is a great group to work in probably been part of this working group for

679
02:14:05.820 --> 02:14:20.160
About a year or so. Oh, and then Tony and I also managed the Seattle area hyper ledger meetup too, which is great because it we get it nice cross section of hyper ledger folks beyond the healthcare space, particularly

680
02:14:21.030 --> 02:14:30.270
But really, really excited about versus work here. She's doing a great job and trying to get the communities spun up and coordinated and and this is a very exciting time.

681
02:14:36.510 --> 02:14:38.190
Stephen or Angela.

682
02:14:44.400 --> 02:14:46.140
Trying to find the mute button. The Jews.

683
02:14:47.850 --> 02:14:48.210
Stephen

684
02:14:50.220 --> 02:14:59.070
I'm a software engineer. I work with cognitive in San Diego, so just south of Seattle downing and Glenn sunshine.

685
02:15:00.720 --> 02:15:04.890
We are focuses on interoperability standards.

686
02:15:06.510 --> 02:15:29.910
Were very interested in how we can build terminologies and HL seven technologies like fire and expose those through other standard interfaces like smart on fire with blockchain. I think this is use case that we're talking here or will be talking, I hope.

687
02:15:31.260 --> 02:15:34.410
Is going to surface. A lot of the

688
02:15:35.910 --> 02:15:44.790
A lot of the ways that both ph si P i and hipaa will will guide.

689
02:15:45.870 --> 02:15:56.460
Or influence the kinds of technologies that we use and and hopefully we can do this in an interoperable way so that the data can be shared on a wide

690
02:15:56.460 --> 02:16:02.130
Basis, even though maybe the data in the back end is is proprietary

691
02:16:03.450 --> 02:16:05.520
It's still be nice to

692
02:16:06.540 --> 02:16:08.490
Have it surface and

693
02:16:09.630 --> 02:16:09.960
You know,

694
02:16:10.020 --> 02:16:14.130
Some kind of fire resource using SNO med or like or arts

695
02:16:14.130 --> 02:16:19.950
Alarm so that it can it can be used by a wider audience. So

696
02:16:20.550 --> 02:16:21.660
That's our interest here.

697
02:16:22.290 --> 02:16:24.810
we're new to block chain, although we're trying to catch up.

698
02:16:26.910 --> 02:16:40.260
And it's a moving target block chain or hyper ledger one point to just came out then with that things like private data and side DBS and all kinds of very interesting things that actually

699
02:16:41.040 --> 02:16:41.190
Are

700
02:16:41.220 --> 02:16:42.840
Part of our conversation here.

701
02:16:43.350 --> 02:16:47.790
So yeah, looking forward to sharing and learning from everybody here. Thanks so much.

702
02:16:50.010 --> 02:17:00.960
Stephen and since we're pretty small group today to just want to give everyone an opportunity to speak so I co Walid on the on the call will lead to try to introduce yourself.

703
02:17:09.570 --> 02:17:11.250
Courtney, I just joined late. I'm sorry.

704
02:17:11.910 --> 02:17:13.470
I can't hear me.

705
02:17:16.110 --> 02:17:22.320
Yes, I was actually just checking and I see a while lead on the call and wanted to see if they wanted to introduce themselves.

706
02:17:22.650 --> 02:17:25.440
But it looks like maybe they're prefer to see on us.

707
02:17:28.380 --> 02:17:41.310
So I would, Angela. I would love it and we're just doing introductions, since we're pretty small group today and we have some some new folks on the line. Would you like to introduce yourself and just speak a little bit about what brings you to the to the group.

708
02:17:43.980 --> 02:18:02.880
My name is Dr. Until a Courtney and I'm part of the company name, address, to biotech, and we're trying to create a test for cancer, and we're startup launched out of UC Davis and I have a special interest in machine learning.

709
02:18:04.650 --> 02:18:22.290
And of course blockchain is sort of that natural progression to their head and found the project year and it seemed to tie really well with some of the pain point that we are having as a healthcare startup and that is

710
02:18:23.670 --> 02:18:24.930
Getting data to train on

711
02:18:26.400 --> 02:18:30.420
Because running a clinical trial is extremely expensive.

712
02:18:31.470 --> 02:18:51.360
And so if you can find open source data to train algorithm gone. It is so much better. But data is not data, you have to have the right data. And so being able to actually get the data from the patient specifically that you need to obtain the information from

713
02:18:52.680 --> 02:18:59.340
Is really challenging, but this is a perfect use case for blockchain. Try to solve. I

714
02:19:04.080 --> 02:19:13.980
Thank you so much. Angela and we have john Dolan on who is also based out of UC Davis So sounds like you, you have a little Dave is contingent on the line, which is

715
02:19:14.910 --> 02:19:15.540
Hey, Angela.

716
02:19:23.040 --> 02:19:24.600
Would you like to introduce yourself.

717
02:19:30.180 --> 02:19:32.580
Oh, okay. Muslim just sent

718
02:19:34.350 --> 02:19:34.710
A

719
02:19:35.280 --> 02:19:36.450
Chat to everybody.

720
02:19:38.490 --> 02:19:45.270
And the computer science student in Germany and I'm actually in the library and unfortunately can't speak and doing my thesis about blockchain and healthcare.

721
02:19:45.810 --> 02:19:55.860
Very cool. Well, thank you for, for joining and we're very excited to have you, especially in large contingent of sneeze. It's exciting to have folks with

722
02:19:56.670 --> 02:20:09.510
With technical backgrounds that can help drive build and insights into projects like this. So thank you so much for joining and let us know if you have any questions, and

723
02:20:10.680 --> 02:20:13.560
If there's anything in particular that you're looking to get out of the group.

724
02:20:15.690 --> 02:20:16.470
Pamela errors.

725
02:20:27.600 --> 02:20:28.770
This is Jeff Stallman

726
02:20:29.040 --> 02:20:29.580
Please get

727
02:20:34.980 --> 02:20:41.340
Our focus is actually an payments across block chains were expecting.

728
02:20:42.780 --> 02:20:46.350
A plethora of kind of enterprise silos, if you will.

729
02:20:48.270 --> 02:20:59.850
But we don't think that each silo need should have its own currency and we don't think that fiat currencies are a very good way to make payments when you have black chain because you're gonna make instantaneous payments.

730
02:21:01.200 --> 02:21:15.240
If you use a crypto currency and so we're looking to develop tools to facilitate payment across block chains using a single currency, which would in our mind would probably be a stable value currency.

731
02:21:15.960 --> 02:21:17.070
So that we don't have to

732
02:21:17.340 --> 02:21:18.090
Treasures of

733
02:21:18.360 --> 02:21:25.140
major companies wouldn't have to worry about the risk of volatility, it would just be worth $1 or Euro or whatever and

734
02:21:26.160 --> 02:21:31.980
Whatever that crypto currency is we'd be able to allow payments across different silos.

735
02:21:38.910 --> 02:21:44.820
Wonderful. Thank you, Jeff. I appreciate. That's an interesting perspective and definitely something that

736
02:21:46.020 --> 02:21:46.800
needs attention.

737
02:21:49.260 --> 02:21:58.230
It says, so this is this is rich. Hey, Jeff, are you gonna what what are you planning to use. What's your technology stack that you're putting to us, or is it too soon to ask

738
02:22:01.830 --> 02:22:05.130
I it's too soon right now. I mean, one of our

739
02:22:06.330 --> 02:22:11.760
What we have we have a bunch of issues that I don't see current solutions for that were

740
02:22:13.065 --> 02:22:22.710
Either developing ourselves are hoping someone else will develop a week and leverage. I mean, we expect these will all be open source tools because that's I think the appropriate way to do it, but

741
02:22:23.310 --> 02:22:23.700
Right.

742
02:22:23.910 --> 02:22:29.490
There's, I asked. I asked because hyper ledger, the hyper ledger prizes, just in general, tend

743
02:22:29.520 --> 02:22:32.040
Tend to avoid the cryptocurrency space.

744
02:22:33.270 --> 02:22:36.720
And it's always kind of interesting to see how how we're going to find ways to

745
02:22:37.080 --> 02:22:40.800
Integrate going forward because yeah we're big believers that

746
02:22:42.000 --> 02:22:47.700
payment model is going to make make a lot of sense, sooner or later, it's just interesting to see how we're going to do integration.

747
02:22:48.225 --> 02:22:51.060
Using some external source with

748
02:22:51.300 --> 02:22:53.460
With the projects that we have through hyper ledger.

749
02:22:53.910 --> 02:22:57.750
Yeah, I, I just see there's there's a coming train wreck.

750
02:23:00.060 --> 02:23:02.190
Will be there were the solution, you know,

751
02:23:03.090 --> 02:23:18.660
Solution for it so that it doesn't doesn't and even and even the currency, we may end up having to put out our own currency, but as a stable value currency that will be back by assets. It's not like so profit making thing where we're looking for the

752
02:23:19.380 --> 02:23:23.670
You know the value of the currency to soar. That's exactly what we don't want. So

753
02:23:24.540 --> 02:23:26.220
Right. Right. Okay. The

754
02:23:26.400 --> 02:23:28.470
Economics is is to be determined.

755
02:23:29.670 --> 02:23:33.180
Excellent. Thanks. I'm gonna have to say it. Yeah, someone has a say when when

756
02:23:35.970 --> 02:23:41.520
Yeah, I think that I agree 100% there that there's going to be an intersection between

757
02:23:43.980 --> 02:23:50.490
Certainly in the pit and the payer space here. We've been looking very closely at what it would mean to use

758
02:23:51.750 --> 02:23:53.970
A token and a network amongst participants.

759
02:23:57.030 --> 02:24:04.770
As an incentive model for participation also potentially, what would the classical he called payment or settlement. So the interesting

760
02:24:05.790 --> 02:24:12.330
What you come up with. And if there are ways of connecting. Obviously there are a lot of people working on ways in the public space to

761
02:24:13.590 --> 02:24:15.180
Trade tokens lower cost.

762
02:24:17.250 --> 02:24:20.640
And there are some stable coins out there, some of them, not so

763
02:24:22.380 --> 02:24:23.280
Not so stable.

764
02:24:25.650 --> 02:24:28.560
Not only not so stable, but not so back necessarily backlash.

765
02:24:29.940 --> 02:24:30.180
But

766
02:24:30.510 --> 02:24:31.890
Yeah, the interesting to hear what you come up with

767
02:24:36.960 --> 02:24:41.370
Jacqueline question if you've gotten much buying already on that and that theory of using the tokens.

768
02:24:47.880 --> 02:24:51.180
Are you directing a question when you're directing this is Jeffrey we'd write me

769
02:24:51.540 --> 02:25:00.180
Yeah, I mean, I've got the gentleman that was speaking about using Victor tokens. Keep the tokens as a payment. Yes. Have they started get much by in

770
02:25:01.170 --> 02:25:11.430
Say from an adoption levels. I think that's the challenge of even the educational part of seeing of telling people how it would work is I think the the hump to overcome as well.

771
02:25:12.285 --> 02:25:24.660
Well, I think once once any kind of system gets implemented that supports payment, it will become obvious shortly.

772
02:25:25.140 --> 02:25:35.130
And those payments would be could be facilitated by a crypto currency because you could then use chain code or smart contract, depending on which black chain you're operating on

773
02:25:36.780 --> 02:25:41.520
To have it automated and you know easily recorded you

774
02:25:41.520 --> 02:25:56.190
Save invoicing and, you know, waiting for payments and stuff, you know, slow pace type situations, it would you so much easier to use a cryptocurrency if you use the crypto currency, though, when you create one for paying you know

775
02:25:57.810 --> 02:25:58.560
Providers

776
02:25:59.520 --> 02:26:04.560
Then you have another than you, you need another one to pay you know for your

777
02:26:06.000 --> 02:26:09.900
File so you know your supplies. When you buy stuff from Staples.

778
02:26:10.320 --> 02:26:17.940
And you need another one to pay you know pay for something else that's obviously Hip, hip hop to stockpile multiple crypto is would make no sense.

779
02:26:18.540 --> 02:26:31.770
That we see that there will be a need for a single or if not a single least, you know, maybe a handful of stable value currencies maybe denominated in dollars euros or yen, whatever.

780
02:26:32.430 --> 02:26:41.610
Different ones to fuss, so that you could make payments to to everybody, you know, without having to stockpile a multiplicity of currencies.

781
02:26:42.225 --> 02:26:49.620
No, I agree with you i mean i think it's it's definitely good solution. I think for me the challenge. I mean, even to explain it to some executives at a conference.

782
02:26:50.100 --> 02:26:58.770
They were so just hooked on bitcoin and as soon as you're talking about, hey, you can set it up to where you can pay for services and tokens. That's all they kept focusing on

783
02:26:59.130 --> 02:27:08.190
We're all we have to get into bitcoin and it was that challenge of overcoming that education side of it doesn't necessarily that's just one part of what you could use it for

784
02:27:08.490 --> 02:27:13.530
Yeah, well, I think, I think it to make the case you have to emphasize using a stable value.

785
02:27:13.530 --> 02:27:13.920
Grant.

786
02:27:14.310 --> 02:27:26.490
I agree and and we, I know a lot about stable value currencies and I'm actually quite confident that we can do that because we'll just have a standing offer to buy or sell at $1

787
02:27:27.480 --> 02:27:28.200
For example,

788
02:27:29.490 --> 02:27:31.710
The economics and we'd have to have with us the chance

789
02:27:32.100 --> 02:27:43.440
Have transaction costs because there's gotta be something to support the infrastructure. But even though the volumes of dollars might get large, it's not a very large infrastructure. It just has to be incredibly scalable, because if you figure

790
02:27:44.160 --> 02:28:02.880
That you're doing, let's say 10,000 transactions, a day on this on a pair solution and you're doing you know 10,000 transactions, a day, and these are arbitrary numbers on, you know, to pay for your business supplies and you're, you know, all these different

791
02:28:05.400 --> 02:28:10.620
Silos applications, you're gonna have to support the this the sum of all of those as far as

792
02:28:10.650 --> 02:28:10.980
Ours.

793
02:28:12.570 --> 02:28:13.080
Absolutely.

794
02:28:14.430 --> 02:28:17.970
We're gonna be micro payments. So you don't want to have transaction costs that

795
02:28:18.780 --> 02:28:20.220
Make your micro payments double

796
02:28:21.120 --> 02:28:25.560
Exactly. No, I agree with you. I think it's great. I love to hear the progress of that.

797
02:28:26.010 --> 02:28:26.400
All right.

798
02:28:27.750 --> 02:28:29.580
Yeah, and rich. Thank you. You

799
02:28:29.880 --> 02:28:30.780
Just put the

800
02:28:31.950 --> 02:28:40.470
Rocket chat link in the in the chat box here. So this is our mode of communication between

801
02:28:41.460 --> 02:28:42.180
Group members.

802
02:28:42.360 --> 02:28:44.340
Kind of between our meetings so

803
02:28:44.940 --> 02:28:59.280
Really encourage folks to join the rocket chat channel and engage in conversation there. We haven't had a lot of engagement so far with this group, but I think that as we get going. It'll be a great resource for us. So please

804
02:28:59.340 --> 02:28:59.790
Take old

805
02:29:00.270 --> 02:29:02.550
Rich, did you want to add anything there before he moved on.

806
02:29:03.210 --> 02:29:12.840
Yeah, for anyone that hasn't gotten familiar with rocket chat in order to get spun up on that, you have to have a Linux Foundation account, which is a freebie.

807
02:29:13.590 --> 02:29:21.900
So yeah, this is a great conversation that we were just having about cryptocurrency and I'd love to have that recorded somewhere. So that's what

808
02:29:22.470 --> 02:29:25.620
I was thinking, Man, this would be great up on rocket chat so we can have this sort of

809
02:29:25.860 --> 02:29:28.800
indelible and keep the conversation spun

810
02:29:29.850 --> 02:29:38.730
Around this because it's going to be fascinating. Going forward, and it will be a great reference for us as we we use it as a way to look back in reference so

811
02:29:39.480 --> 02:29:48.150
highly encourage everyone to go to a rocket chat. I know some of the folks on the on the list here are already set up on there. So thanks very much for that.

812
02:29:49.740 --> 02:29:56.490
Awesome. Okay, so kind of moving forward. One of the things that came out from last week's meeting and I think

813
02:29:56.910 --> 02:30:05.820
Will will become more of a neat as we move forward is somewhere to be able to build on thoughts and ideas and and kind of move our

814
02:30:06.450 --> 02:30:29.430
Our business case forward as we are constructing this concept and there is a wiki through the Linux Foundation that I've unfortunately I don't have a very technical background. So I found it a bit difficult to engage with. And so as an alternative. I actually created a Github repository.

815
02:30:30.210 --> 02:30:40.290
To kind of continue our conversations between meetings on on the business case. And so I will. I'm sharing the the link in the chat box right now.

816
02:30:40.740 --> 02:30:49.440
I will have to warn you that it's likely that we might need to move this back under the Linux Foundation umbrella and I'm working with, right, who is

817
02:30:50.520 --> 02:30:53.610
As I don't know his title, but he has been helping with kind of the

818
02:30:55.125 --> 02:31:14.010
Coordination and kind of logistics of how to engage with the community for for me in the suburb has been a great resource. So we are having conversations around that. But I didn't want to maybe I can share my screen just very, very quickly here to show this.

819
02:31:16.590 --> 02:31:17.130
To you guys

820
02:31:21.180 --> 02:31:30.360
So this is the the subgroup repo and i think i hope that everybody has access to to edit.

821
02:31:30.870 --> 02:31:40.500
The wiki, wiki is found here and we have links here to the community calendar rocket chat and the meeting recordings and then

822
02:31:41.070 --> 02:31:50.190
To change that text, but over here on this side, this is really where I've started building out our, our business case and our problem statement.

823
02:31:50.850 --> 02:32:07.890
And so this is just, I think, instead of sending out notes after a remeeting which you're kind of just static and then people forget about them and they're not really flexible or iterative. The idea would be that people could come here and and put in ideas and start

824
02:32:08.070 --> 02:32:08.580
A kind of

825
02:32:08.880 --> 02:32:19.860
Working through this together. So I encourage folks to take a look at what we have so far, and also to make edits as they seem appropriate or put an ideas or

826
02:32:20.160 --> 02:32:21.030
However, they

827
02:32:21.060 --> 02:32:22.290
They think would be

828
02:32:22.890 --> 02:32:34.050
Would be best. I would ask that if you do make any edits that there's a footnote option for commenting on the changes that you've made.

829
02:32:35.370 --> 02:32:50.520
Down here. So if you can just do that, that'll help us track kind of changes that are made. And so that's just a logistics a piece that might be. I was hoping it would be helpful for our collaboration, any feedback or

830
02:32:50.520 --> 02:32:51.000
Questions.

831
02:33:05.970 --> 02:33:15.420
This is fresh. Yeah, this looks really good. I'm looking forward to finding a good fit for for capturing some of the conversations that we have and documenting them.

832
02:33:16.380 --> 02:33:23.400
The yeah the Linux Foundation wiki is a little more difficult to work with. So, this, this, I hope, will be the gold standard going forward.

833
02:33:25.380 --> 02:33:26.850
Thanks for touching my taper rich

834
02:33:28.800 --> 02:33:29.010
That's

835
02:33:31.800 --> 02:33:33.000
Gotta submitted that but

836
02:33:36.525 --> 02:33:44.550
We're working together. So on that note, well, I guess, any anybody else on feedback or comments there.

837
02:33:46.890 --> 02:33:53.430
So that looks good. So I just want to interject. So, where you going to do a summary for from last week's meaning because I wasn't not

838
02:33:54.015 --> 02:34:04.950
Yeah, actually, what I did was a kind of put that let me share my screen again because I think it's actually I incorporated at all here. Thank you for for that reminder

839
02:34:16.890 --> 02:34:27.090
Okay, so really what we focused on last week since there were a lot of new folks on on the call was just kind of providing that context that

840
02:34:31.800 --> 02:34:50.790
Provide providing context around just the overall structure of the Linux Foundation. I have related projects the healthcare working group and then the the sub groups, which include this group. There's a peer group that Tony is heavily engaged with and then also sounds like in your

841
02:34:52.470 --> 02:34:53.520
Group will also be

842
02:34:53.520 --> 02:35:05.610
springing up so set context. And then we really kind of work through the problem statement. Once again, thinking about how we connect with the patient in the center and how it connect longitudinal data.

843
02:35:06.930 --> 02:35:20.100
Across the different silos to help them form diagnostics and treatment and what can I think we do. One of the biggest takeaways from last week's meeting was that you know of this like large problem statement.

844
02:35:21.300 --> 02:35:34.860
And thinking about really an individual own health data record that there were kind of chew major use cases to explore and then from there, we could break those down into more I guess I've struck from that even even

845
02:35:34.980 --> 02:35:36.630
More specific questions that we

846
02:35:42.390 --> 02:35:43.470
Did you have a comment.

847
02:35:48.750 --> 02:35:52.170
That was just feedback. Okay. And then those

848
02:35:52.200 --> 02:36:10.350
Those two that were pulled out. We're clinical trials and then sharing data across healthcare entities. So a couple of examples that came up were, you know, if you go to the emergency room. How can an individual brain relevant data with them to that visit and then, you know, in an

849
02:36:10.860 --> 02:36:13.290
In an incident where you're seeing multiple

850
02:36:13.290 --> 02:36:16.500
Providers across your golden in an

851
02:36:16.560 --> 02:36:18.990
Out of network providers, how do you track your

852
02:36:18.990 --> 02:36:20.850
Information there.

853
02:36:22.020 --> 02:36:28.260
So these are and then from, you know, this is kind of a compilation of

854
02:36:29.430 --> 02:36:46.410
Other maybe Stephen, I think we're. These were your ideas, specifically around for each kind of sub use case. And, you know, these are the areas that we want to dig into some improv interoperability Providence data standards data right and flow consent and data.

855
02:36:47.820 --> 02:36:48.360
And

856
02:36:50.190 --> 02:36:52.920
Just kind of thoughts about how we would kind of

857
02:36:53.100 --> 02:36:55.980
user journeys are start mapping those things out.

858
02:36:57.240 --> 02:37:03.870
Just a quick point. I'm sorry. Didn't review the notes. It's not Providence its provenance PR

859
02:37:06.930 --> 02:37:16.050
Two different meetings, very close, but two different meanings. So the source of information. So with my lab was done by third. Oh, so it was a done by

860
02:37:18.090 --> 02:37:21.180
These kinds of things will allow us to

861
02:37:22.230 --> 02:37:23.250
Have the

862
02:37:27.060 --> 02:37:27.480
Thank you.

863
02:37:29.220 --> 02:37:35.100
So yeah, I think that, you know, when you get down to the detail with the devil.

864
02:37:37.350 --> 02:37:41.550
Is that you really kind of looking at how you can apply

865
02:37:44.820 --> 02:37:45.600
Apply

866
02:37:46.620 --> 02:37:49.230
Privacy and

867
02:37:50.580 --> 02:37:51.660
Scalable

868
02:37:52.980 --> 02:38:07.140
Permissions or or different permissions to to data and who holds that data. And so I mean just the very simple example that we talked about where the patient is in

869
02:38:07.980 --> 02:38:19.680
Is in the is in at their at their general practice doctor and the doctor says, well, what you've got you've got this problem, we need to

870
02:38:21.150 --> 02:38:25.050
We need to take a blood sample and do do a panel on it.

871
02:38:26.280 --> 02:38:27.990
And so

872
02:38:29.370 --> 02:38:33.600
The point being here is that the the patient.

873
02:38:35.340 --> 02:38:47.970
Who would be identifiable in the block chain system would provide permission to the doctor to take the blood sample and send it to the laboratory.

874
02:38:48.600 --> 02:38:59.880
And you know we've talked a couple of times about who owns that permission, who owns that data that if we say that the patient knows it, but has given as deferred

875
02:39:00.435 --> 02:39:08.580
Permission to the doctor to own that data until the doctor comes back and gives them back and then provides them with analysis of that data.

876
02:39:09.720 --> 02:39:13.860
Then the doctor will get the signature so digital signature.

877
02:39:15.060 --> 02:39:15.870
Take the blood

878
02:39:17.670 --> 02:39:27.120
And then send it to the lab and the lab and receive the blood sample with an anonymous talking or economic data ownership.

879
02:39:28.230 --> 02:39:32.730
Maybe the patients may be the doctors, probably the patients, or both.

880
02:39:35.100 --> 02:39:40.800
And do the process and then provide the data back to

881
02:39:42.150 --> 02:39:53.430
To the, to the doctor. The interesting thing is, who, where is that data. Is it is it is an inner repository that the doctor than accesses

882
02:39:54.030 --> 02:40:05.910
If it is, is there are the restrictions on that, on that data. Of course, there are because the patient hasn't hasn't made that data public or has only made a public to the doctor.

883
02:40:07.470 --> 02:40:12.090
And then we got into these other cases as well. The doctor then comes back either data goes back to the doctor.

884
02:40:12.420 --> 02:40:20.820
The doctor then provides analysis to other data of the lab results to the patient and at that time the patient becomes full owner

885
02:40:21.390 --> 02:40:31.950
Of that information or record has been entered that the doctor has as as seeing the data and has given that analysis to the patient.

886
02:40:32.700 --> 02:40:44.310
And just sort of working through just even that really small little use case brings up a lot of different things up a lot of issues even on the happy path for essence.

887
02:40:45.450 --> 02:40:47.490
If in the panel we discussed

888
02:40:48.570 --> 02:40:49.410
If the patient.

889
02:40:51.600 --> 02:41:04.320
Had maybe an anomaly. Maybe so. Maybe he bowl in the panel. How would that what we're would how would that, how would that be reporting. I mean, that's got to be reported to the CDC.

890
02:41:05.070 --> 02:41:21.030
Or if the patient had an accident. In the meantime, I was taken to the hospital was unconscious and this data was there and the emergency room needed all the data that they, how are they access all of that data. How does the patient can identify how do we

891
02:41:21.690 --> 02:41:22.740
immutably

892
02:41:24.360 --> 02:41:26.910
Identify the patient in them provide anonymity.

893
02:41:27.450 --> 02:41:30.330
Well, to all data that's associated that wars, the data cap.

894
02:41:30.690 --> 02:41:32.580
If data is like a di calm image.

895
02:41:33.780 --> 02:41:39.990
You know, do we do we keep that data in a central repository kept he kept on the blockchain it's it's way too big.

896
02:41:41.010 --> 02:41:56.850
So what kind of consensus mechanisms we have Mayo Clinic recently did a paper on you know we use now proof of work proof of stake, maybe the consensus mechanism here is proof of interoperability.

897
02:41:58.230 --> 02:42:07.590
These are all kinds of questions that just even this little scenario sort of raises as to how we use blockchain to to control access and and

898
02:42:07.980 --> 02:42:08.850
To share the data.

899
02:42:11.550 --> 02:42:24.570
Seems to me that they're, they're really two fundamental pieces here that need to be worked out before that model will be successful. And I think most of the pilots that have tried to do something like this run into those two really big problems. One is

900
02:42:25.980 --> 02:42:33.840
Identity, making sure that the patient on the other end of the at the user on the app, the death is they say they actually are.

901
02:42:35.010 --> 02:42:35.700
In the second

902
02:42:39.810 --> 02:42:41.610
To we're not out of my head.

903
02:42:43.320 --> 02:42:43.500
But

904
02:42:43.530 --> 02:42:52.260
There are two. That's certainly the fun. That's certainly the first one that the second is wallet key management. Right. So how do you create a convenient experience for managing

905
02:42:53.640 --> 02:42:59.640
Keys. If your ideas to put the patient at the center, then they have to have it a custodian somehow

906
02:43:01.260 --> 02:43:06.300
Of that and and so those are the two things I think that are that are kind of being worked on and are challenging because

907
02:43:06.900 --> 02:43:15.300
It has not convenient than than those use cases kind of fall apart. And that's part of it, just the maturity of the technology, maybe and maybe you can't solve it at the same time, but

908
02:43:15.720 --> 02:43:23.640
Most of the folks that I know who sort of delved into this space end up going to one of those two and try and work on solving them first, just based on my experience.

909
02:43:24.570 --> 02:43:27.240
Yeah, I think, I think we can almost ignore

910
02:43:27.540 --> 02:43:33.120
The master patient index and how we identify the patient. I think some other people will solve that.

911
02:43:34.890 --> 02:43:37.890
I think that it has to be some kind of an immutable.

912
02:43:39.480 --> 02:43:51.270
Identity. Right now, we're working with fingerprints and recognition and please provide you know means to identify yourself through the system.

913
02:43:51.720 --> 02:44:02.370
In a variety of different ways of writing different places and very convenient way. I don't think that the wallet seems to be an abstraction of

914
02:44:03.240 --> 02:44:11.100
who you actually are, and may contain information about different cryptographic keys that you haven't different block chains are different silos.

915
02:44:12.120 --> 02:44:19.320
So that to me is is really the most interesting part is, is the transition of ownership or

916
02:44:20.130 --> 02:44:29.220
The evolution of permissions is the data makes its way just even from the doctor to the lab and the back of the doctrine to the patient.

917
02:44:30.000 --> 02:44:40.230
How how things like code can be used to create a system that that monitors and provides protection.

918
02:44:41.130 --> 02:44:56.700
For that chain of command to be to be transferred as it moves through the system for doing versus if we're talking about clinical trials. If you have, you may not want your blood to be used in clinical trial.

919
02:44:58.020 --> 02:45:02.730
And but you may not even want to know that you have refused to

920
02:45:02.940 --> 02:45:05.010
Provide the permission to access

921
02:45:05.580 --> 02:45:16.200
Your blood because the assumption them would be you had either that you had some some some some data there that that wasn't wasn't wouldn't shouldn't be shared.

922
02:45:16.560 --> 02:45:32.850
So maybe you do have, we have some kind of a substance abuse problem. So, you know, maybe, maybe not even want to surface. The fact that the data existed. These kinds of questions. I think in the ones that are going to be the nuts and bolts of how we shared it

923
02:45:35.220 --> 02:45:39.510
Yeah, I agree. I think we're sorry. Go ahead. No, go ahead.

924
02:45:42.090 --> 02:45:48.180
I was gonna say is, essentially, I agree with you, 100% and that the block chain itself and that

925
02:45:49.740 --> 02:46:00.780
That ledger that were would be shared amongst enough participants has been proven to be reliable and have data. The data security associated with it. Security is high enough that

926
02:46:01.860 --> 02:46:06.000
It would provide trust in a space like health care if you have the right mix of participants.

927
02:46:07.170 --> 02:46:20.700
Again, I think, to unlock that the usefulness of that data is to my point was that these other things need to be figured out before you can get an actual use case that it would would work of an example is I have a friend who is

928
02:46:22.080 --> 02:46:32.250
Doing work and had this concept of longitudinal health record for a big health system in the south and after meeting with their executives and all of the technical folks.

929
02:46:33.420 --> 02:46:42.000
Had to pivot really to working on self sovereign identity and healthcare first simply because it was impossible to implement the use case without that

930
02:46:42.450 --> 02:46:50.160
So they went, you know, that's where he's pivoted to and he's in the process of working on that with them. But then I agree with you completely. It would be really great to see this sort of

931
02:46:50.940 --> 02:47:03.180
Level of consent associated with an ownership and tracking that we don't have today. And I think the blockchain will unlock that I think we're just, you know, still working on the plumbing here and it's all very exciting.

932
02:47:05.730 --> 02:47:20.730
Yeah, and I just had a couple of things and to add from the, the scientists, again, the data side that you know when you're looking at health care data and you're looking to actually use it to to make any sort of

933
02:47:22.800 --> 02:47:24.240
Medicine based model.

934
02:47:26.490 --> 02:47:28.710
You need the complete

935
02:47:29.790 --> 02:47:37.260
Picture, which means that you can't have the ability for someone to say here's my for example lab work.

936
02:47:38.370 --> 02:47:52.320
But don't don't disclose that I have. Well, that, you know, could be really important so far as medicine is concerned and and research and trying to

937
02:47:52.800 --> 02:47:59.790
Unravel and solve a problem because things that you think wouldn't actually make a difference.

938
02:48:00.750 --> 02:48:05.910
Could make a huge difference because these things are all modulating the body so you end up getting a long answer.

939
02:48:06.540 --> 02:48:19.650
Because that that very bit of information was eliminated. So I think if we kind of think back as to why someone would want to withhold that is because they don't want it associated with themselves. Right.

940
02:48:20.760 --> 02:48:27.750
I don't want you to know that I have. Well, if you completely D identify the data.

941
02:48:29.010 --> 02:48:42.960
Then it doesn't matter if all of that is disclosed and now the data is basically staying true to its face this ground truth right which is what's needed when you're training models that the ground truth so

942
02:48:44.280 --> 02:48:58.890
Kind of looking at the parts that are available to us that already exists, it maybe we can put into play. We have zero knowledge proof that you know we can actually have that individual and have them.

943
02:48:59.910 --> 02:49:15.150
Become a hash, but their hash is now a zero knowledge proof has the that they can disclose the data and the information, but you never know who it's coming from that who they truly are never really gets disclose that once their

944
02:49:16.140 --> 02:49:27.930
patient information is de identified and hip. I have a safe harbor 18 points that needs to be hit in order to de identified data once the data is the identify then

945
02:49:29.070 --> 02:49:40.050
It doesn't, you don't have to change the ground truth because the zero knowledge proof basically keeps it from coming back to that individual as being that person, and I think we can

946
02:49:41.070 --> 02:49:43.590
Maybe build around that capability.

947
02:49:45.210 --> 02:49:47.700
Yeah, I think that I was looking at a

948
02:49:49.170 --> 02:49:59.550
Little less clinic centric and little less clinical trial century from the data, maybe what needs to be protected by the individual from there. From there from their

949
02:50:01.110 --> 02:50:12.570
Their, their employer or somebody I think there's a lot of cases where medical clinical data about the individual needs to be protected in non clinical environment, since all

950
02:50:14.550 --> 02:50:14.790
That

951
02:50:15.150 --> 02:50:17.610
In the clinical trials, I probably want to

952
02:50:17.610 --> 02:50:17.940
Have

953
02:50:18.330 --> 02:50:19.620
You know, a longitudinal

954
02:50:21.360 --> 02:50:23.760
Are probably in anything. Yeah.

955
02:50:23.820 --> 02:50:25.290
When you're disclosing it you

956
02:50:25.290 --> 02:50:27.180
Really to be safe and

957
02:50:27.630 --> 02:50:29.640
Secure and data.

958
02:50:30.120 --> 02:50:43.005
You really just want that individual to know that it is you right even though they may not know who you are if you're using it in different contexts outside of your

959
02:50:44.460 --> 02:50:48.990
Patient doctor interactions of what's K, you know, they already know is

960
02:50:50.190 --> 02:51:03.300
That if you have a zero knowledge proofs and you're in the insurance company doesn't know it's you insurance company can't put it together. If you know the identified Twitter' by a safe harbor 18 point

961
02:51:05.040 --> 02:51:07.890
It's hard for them to actually get it back is visual

962
02:51:09.210 --> 02:51:15.030
I think it's one of the challenges with the whole model route self sovereign identity and healthcare, it's, it's a real challenge, but

963
02:51:15.690 --> 02:51:22.410
I mean, you could set you could see where you could set up something where I could have many public keys that might all mean me. And if I'm the one who's

964
02:51:22.860 --> 02:51:29.430
The sovereign owning got identity, then you don't have to store, who I am on the chain you just would have these keys and then I would be the master of who

965
02:51:30.120 --> 02:51:37.785
Belong to me right granted out but the the other challenges and in those instances where it's an emergency and you're lying unconscious

966
02:51:38.400 --> 02:51:44.670
You have to make sure you have to wait a break the glass. Right, so that the provider can actually get at your records and so like

967
02:51:45.090 --> 02:51:53.640
There are many different use cases here that all sort of stem back to how do you make sure that, you know, the patient has identified when they want to be.

968
02:51:54.150 --> 02:52:00.300
And they're identified when they should be, but they have no way of proving that they are who they say they are because they're lying unconscious

969
02:52:00.690 --> 02:52:10.350
And they want to wait and make it so that they can be anonymous. These are the things that are the nuts and bolts. I think of what we need to get to, to make healthcare data use one a block chain or a reference to it.

970
02:52:12.060 --> 02:52:16.260
So one other thing that came up in the meeting last week was such a roof.

971
02:52:17.130 --> 02:52:23.730
I believe it was her name suggested that maybe once we had some of these use cases.

972
02:52:24.510 --> 02:52:26.010
Drawn out a little bit that we

973
02:52:26.010 --> 02:52:36.120
could engage with the identity working group at hyper ledger to see what they're doing, get their feedback and

974
02:52:37.590 --> 02:52:54.900
You know leverage what ever they've been working on in their, their knowledge. So I don't know what people think about that. And I guess before we get there, Richard. Just wanted to make sure we you'd asked about kind of a review of the past meeting.

975
02:52:56.130 --> 02:53:01.710
That give you a sense of kind of what we discussed it. Does anyone have any questions about about that.

976
02:53:03.690 --> 02:53:08.730
Yeah, I think I'm okay with it. Yeah, this is good. Thanks. Yeah.

977
02:53:10.470 --> 02:53:11.520
And so regarding

978
02:53:11.730 --> 02:53:21.540
Kind of engaging the identity group, our thoughts last week where, you know, we need to kind of think through kind of like Stephen laid out, you know, walking through

979
02:53:23.130 --> 02:53:40.800
A workflow, a user journey to kind of build that out and have something a little bit more robust before we engaged folks from from that team such a route that has already contacted Nate about potentially making connections there, but any, any thoughts on that.

980
02:53:48.690 --> 02:53:59.880
But I think at least my understanding of hyper ledger is that the individual would be identified by an MSP I remember service provider.

981
02:54:00.780 --> 02:54:13.650
The MSP is the one that validates that this person is who they say they are and provides them with cryptographic key that they use within the chain to identify themselves.

982
02:54:14.580 --> 02:54:26.880
And this is used to validate the data. This is useful for riders patients and everybody that's in the block chain because this is permission block chain. Right. So I think that the

983
02:54:27.990 --> 02:54:31.650
Point of identifying who is patient

984
02:54:33.210 --> 02:54:46.110
Can to some degree be deferred to the MSP and how the MSP does that job. Once that's done, then the person is de identified or anonymized

985
02:54:47.220 --> 02:54:57.870
As a, as an individual that only the MSP can say, oh, this certificate or this hash belongs to this actual individual it's

986
02:54:57.870 --> 02:54:58.740
Called today.

987
02:54:59.790 --> 02:55:22.590
So by that and I think that if we start at that point, then we can use the identity works the identity groups work to provide that that that login or that association of an individual to a certificate or the creation of the certificate through the MSP and

988
02:55:23.790 --> 02:55:26.160
I mean, Tony. Does that sound like like

989
02:55:27.390 --> 02:55:29.700
Does that make sense to people are my just

990
02:55:30.390 --> 02:55:37.320
Understanding. One of the challenges I see that's well that's beautiful, that the challenge. I see is how is it different than today, I guess you know that

991
02:55:37.590 --> 02:55:44.250
The EMR system creates and medical record number that is associated with a particular silo and and many other silos in the country have any idea what that number means

992
02:55:44.790 --> 02:55:52.410
There's always you're able to tie it back somehow to this station 11th own that identity and ported so that the next health system they run into

993
02:55:53.220 --> 02:56:00.000
They're able to share it, and the doctor can see the records and you we've moved the needle right so i don't i don't know exactly right.

994
02:56:00.480 --> 02:56:09.630
But there's there's so many forks and that logic. I could go a number of different ways. But I think ultimately no use cases as a patient, I would like to have a medical records.

995
02:56:10.230 --> 02:56:18.150
That was easy to carry around on my phone. Somehow that I could transport between health systems throughout the world, whatever it is.

996
02:56:18.630 --> 02:56:24.480
That of getting trouble anywhere. The doctors around me have the right information to treat me as best as they can.

997
02:56:25.020 --> 02:56:36.090
And if we can get there somehow with blockchain at providing a utility can make that happen. And that's what we need to get at night. I'm just not expert enough and all the identity stuff going on to notice before before there yet, but the tools.

998
02:56:42.525 --> 02:56:45.900
To do a quick time check. We've got six minutes left.

999
02:56:47.790 --> 02:56:52.620
Any, any final thoughts, Angela. I know that we've had a little bit of correspondence

1000
02:56:53.070 --> 02:56:55.500
This week, and didn't know if you wanted to bring any

1001
02:56:55.980 --> 02:56:59.640
Any thoughts to the to the group before we started talking about next steps.

1002
02:57:00.480 --> 02:57:11.430
And yeah, I wanted to try if we could clarify what we're building what our in game is so far as are we building something that's going to be open source.

1003
02:57:12.150 --> 02:57:22.680
For everyone as in the Linux Foundation that we're working under are we building a fee based model and the end as in the crypto conversation that we just had where

1004
02:57:23.430 --> 02:57:38.610
Individuals are and have to pay in order to access the super fenders, you're thinking rebuilding like what, what is our in game bills here, I just wanted to see if we could clarify that a little bit more. And I say that because make the difference.

1005
02:57:40.950 --> 02:57:43.710
When you're doing sort of the bill.

1006
02:57:45.540 --> 02:57:55.410
And sue you know some of the open source models that you can use, whether you're building something that is paid thing, then you have to pay a license fee that kind of you.

1007
02:57:56.130 --> 02:58:07.440
Some of these open source algorithm for people who have is, is it going to be open source itself, you can go ahead and continue to build off that algorithm. So, just wondering

1008
02:58:10.290 --> 02:58:13.170
Rich and Tony, I don't know, since you guys have been

1009
02:58:13.260 --> 02:58:15.660
Kind of engaged in Hyper ledger.

1010
02:58:16.170 --> 02:58:17.430
For longer than

1011
02:58:17.520 --> 02:58:19.260
Most people I think here.

1012
02:58:20.700 --> 02:58:22.380
Any insights there.

1013
02:58:24.750 --> 02:58:33.000
So, so I as far as a paid model. Good. Those are paid product, I'd be a little careful and we may want to double check with

1014
02:58:34.110 --> 02:58:42.150
Linux Foundation and how how that might operate. I will say, I've spent some time in in a different working group.

1015
02:58:43.080 --> 02:58:55.500
That that it was also sort of open source nonprofit on and this was in the interoperability space and healthcare and it was very hard to try to

1016
02:58:56.280 --> 02:59:13.710
Structure any kind of solution that was closed source and got in any way privatized. So I just offhand. My gut would be, I don't know if this will be the white proper working group for a private solution, necessarily. I personally sort of see this as

1017
02:59:13.950 --> 02:59:25.650
A great opportunity for a lot of us to get together and strategize on structure and solution I particularly I'm a very visual person. So I look for an architecture.

1018
02:59:26.520 --> 02:59:34.710
But I would I would imagine that we could take it pretty far down the road in an open forum and then it's individuals want to sort of take this

1019
02:59:35.610 --> 02:59:51.450
Take this private I suspect they could probably do that, but I don't think we would want to do that under the auspices of the Linux Foundation that said we could, you know, Marissa, we could probably check with hyper ledger proper and ask them, you know the the sort of question.

1020
02:59:54.420 --> 03:00:03.120
This is a lie. I agree with that. I think if it's open source, we can come up with models that other people can add value to

1021
03:00:04.080 --> 03:00:18.090
But if it's not, then we have to stay around forever and keep maintaining it and making sure that it works and add value. And that's a lifetime commitment. I don't know that we need to do that. I think you just need to get it going and then let others add value to

1022
03:00:21.690 --> 03:00:28.410
And the most important thing is it's very political. Whatever you come up with this political so if you

1023
03:00:30.180 --> 03:00:37.650
Buy not charging a lot of the politics is you can manage it. If you charge you can I don't believe you can.

1024
03:00:38.400 --> 03:00:39.210
Not at this point.

1025
03:00:40.980 --> 03:00:41.730
Yeah, I agree.

1026
03:00:42.270 --> 03:00:43.770
Okay there. I guess we're

1027
03:00:43.830 --> 03:00:48.060
We're all in agreement that this is going to be open source, what we're building

1028
03:00:49.380 --> 03:00:52.710
And as an action item I can follow up with

1029
03:00:54.000 --> 03:01:01.170
With Tracy and Ryan, see if there's any sort of guidance there or insights to bring back to the group.

1030
03:01:02.070 --> 03:01:03.540
Okay, can I can I

1031
03:01:06.960 --> 03:01:07.980
Will come up with a good analogy.

1032
03:01:07.980 --> 03:01:22.590
Might be what for example the da Vinci project is done for fire what they're really doing is looking at particular use cases, figuring out what an implementation might look like writing and implementation guide essentially a tool that others could use to start from then bring it forward.

1033
03:01:22.620 --> 03:01:32.310
To the community to see if there are others who want to use it, or could use it the idea of just developing standards on top of the standard blockchain might be a standard, at least in some ways, or their standards being built.

1034
03:01:33.210 --> 03:01:37.230
Sort of bad and improve upon that and that particular context, which in this case would be

1035
03:01:38.580 --> 03:01:40.590
Putting the patient at the center of their healthcare data.

1036
03:01:41.730 --> 03:01:43.530
That's just way my my brain thinks about it.

1037
03:01:46.110 --> 03:01:46.350
Yeah.

1038
03:01:48.210 --> 03:01:53.730
It would provide that foundation and keep us out of the politics that were referenced earlier and

1039
03:01:55.170 --> 03:02:03.960
Condemn be used for whatever purposes, both paid and and continued development in the open source side but it pulls us pulls this team out of that conflict.

1040
03:02:05.280 --> 03:02:06.660
And you're in. Did you have one other point

1041
03:02:08.070 --> 03:02:20.250
I did. I just wanted to point out to them. I don't know if we have a link to the article that that we were looking at where Britain National Health Service and he is

1042
03:02:21.210 --> 03:02:30.600
There. A little bit ahead of us on solving this problem, mostly because they have a centralized health care service, which means they're only dealing with one medical record.

1043
03:02:31.410 --> 03:02:45.660
A database where we have you know a multitude of different ones, but they in sort of in the future, which is where they are ahead of us in solving this problem they have chosen to work with private car.

1044
03:02:46.770 --> 03:02:55.110
Company that de identified data and they can open source their medical healthcare data and this kind of ties in with

1045
03:02:57.450 --> 03:03:02.970
The fact that they have one health care record, if you will, for the entire country.

1046
03:03:04.500 --> 03:03:17.220
That you know solutions can be come upon much faster because they can open source it so maybe we can link up to that article that everyone could, you could drop that in. Maybe into the wiki or

1047
03:03:20.460 --> 03:03:21.510
In the chat window here.

1048
03:03:21.510 --> 03:03:28.320
And then I'll also create like a resources page on the wiki and put it there for for folks to take a look

1049
03:03:28.950 --> 03:03:29.370
So,

1050
03:03:30.390 --> 03:03:30.510
Good.

1051
03:03:31.530 --> 03:03:35.340
steps ahead of them. So maybe if we can kind of look at where they are.

1052
03:03:36.420 --> 03:03:43.440
That would kind of help us sort of focusing on where we'll be knowing that we have a multitude of different healthcare records.

1053
03:03:44.790 --> 03:03:50.190
In different places where they just have one centralized but they're still moving in the same direction.

1054
03:03:52.290 --> 03:03:55.230
My get the group kind of all thinking in the same direction.

1055
03:03:58.440 --> 03:04:03.750
So really quick. Our next steps. I know we're a few minutes over. But our next meeting is

1056
03:04:03.750 --> 03:04:05.160
Scheduled for the 20th

1057
03:04:06.960 --> 03:04:10.470
What are people thinking for for next steps.

1058
03:04:12.720 --> 03:04:19.440
Have ideas but wanted to hear from the group of people, are there certain things that people wanted to kind of drive to in the next meeting.

1059
03:04:27.390 --> 03:04:34.410
So to Stevens Point that he put in the chat box actually agree with that that you know we need to start kind

1060
03:04:34.410 --> 03:04:34.650
Of

1061
03:04:36.540 --> 03:04:53.760
Riches, you said kind of abstracting from that broader problem statement and to some of the, the concrete use cases are more detail use cases that can then kind of we can start working in and really thinking through, through the process for so that would

1062
03:04:53.790 --> 03:04:59.760
Be where I would like to take the next meeting is kind of where you know I was hoping we get you today.

1063
03:04:59.760 --> 03:05:04.590
But I think we had some really good conversation if that works for everybody. That's what we'll plan.

1064
03:05:08.100 --> 03:05:08.400
Sounds

1065
03:05:10.950 --> 03:05:13.620
Great, thank you guys so much for your time. I really appreciate it.

1066
03:05:13.830 --> 03:05:14.190
And

1067
03:05:14.850 --> 03:05:15.570
I'll be sending out

1068
03:05:15.900 --> 03:05:18.630
An update. Once I get the wiki with the notes and everything so

1069
03:05:19.050 --> 03:05:19.710
Thank you.

1070
03:05:20.040 --> 03:05:20.880
Have a great weekend.

1071
03:05:23.430 --> 03:05:24.210
Bye everyone.