 Morning, Bob. How are you? Good morning, Wendy. Good morning. How are you? I am doing well. Thank you very much for allowing me to participate in this group. Oh, fantastic. Great to have you. Is this Rich? This is speaking, yes. Hi, Rich. I feel like I had interacted with you a couple years ago. Did you ever apply or interact with Rocky Mountain Poison and Drug Center? No, that does not sound familiar. Okay, then I probably didn't. There is another person named Richard Block who I had interacted with. Oh, interesting. Okay. Yes, so oddly enough, the only Richard Block that I know I believe is a magician. And so I am clearly that person. Got it. But I'm sure there are other Richard Blocks that are out there. I believe there was a chemist from 100 or 200 years ago with the same name or similar name. So a bit unusual. Yeah. Well, great to have you. Yeah, thank you. And so I'm happy to introduce myself to the group today who would like me to do that. Let's hold on that. I want to just, I see people just dialing in right now. So, but we'll do introductions shortly. Good morning, this is Bill All. Good morning, Bill All. How are you doing? Good, good. Is your identity intact? So far, no damage. Okay. But, you know, that keeps me nervous. I'm sorry to hear that. I'm sorry you missed out on the conference. Yeah, I know. I really was hoping to meet you guys. Yeah. So I see your colleague just got online. Good morning, Logan. How are you? Good morning. Good to have you on. And good morning, Bob. Dr. Kali looks like you're on as well. Good morning. Good morning, Richard. And, and Ravish, good morning to Ravish as well. And so, and Vipin, good morning. Good morning. How are you, sir? Very well. Thank you. Have you, have you, have you dialed in before? No, I was invited to, to the patient subgroup, I guess, but not to this particular. Oh, okay. Oh, good. Good to have you. Because I'm the chair of the identity working group in Hypolysis. Oh, I'm looking at the, I'm looking at the name and it's, boy, this looks awfully familiar to me. So welcome. Great to have you. So, well, so that said, let's get started. It is the top of the hour. So first and foremost, good morning to everyone. I'm glad to have you on the call. Everyone should see if you're, if you're on the computer, you should see the agenda in front of you. It's the same agenda that's gone out earlier. So no changes to that. And before we get started, I want to just mention our antitrust policy. It's up on screen. So please review that. The upshot is just be a good person. And so feel free to read that at your leisure. So normally I do ask if someone on the call could please take notes. So would anyone like to volunteer that? Just, just sort of high level notes so that I don't have to sort of stop and write or type as, as, as we're talking. Holy, holy cow. We have a whole bunch of folks. All right. So I didn't hear who it was. So someone, I need a name. Logan, I'll be glad to. Oh, thank you, Logan. Excellent. Oh, hey, good morning, Alan. How are you, sir? I just saw you got on the call too. Good morning. Yeah. No, I wasn't going to arm wrestle for it for the. All right. Thanks. Thank you for that. Well, okay, great. So we do have a couple of new folks on the call. So I'd like to have them walk through introductions. So Wendy was on the call first. So we'll take it off. Wendy, would you like to introduce yourself please? So sure. Hello everyone. My name is Wendy Charles. I work at Denver Health and Denver, Colorado. I have my PhD in health information technology and I am an avid blockchain enthusiast, particularly for hyper ledgers. So my specific interests pertain to academic research and uses of blockchain and higher education as well. Applications for clinical research. Outstanding. And so what, what aspect of hyper ledger are you looking at fabric or sawtooth or indie? Right now, primarily fabric. So for the benefit of the private commission aspect, I, I can't say that I am very familiar with the others except I know that indeed being developed for identity. So I'm eager to learn as well. Excellent. Okay. And, and, and, and just how did you find, find out about us? Yes, I was recommended by John Carpenter of the blockchain, government blockchain association. He recommended that I join. Oh, outstanding. Excellent. All right, well, well, great to have you, Wendy. And, and thanks for calling in. And we'll walk, we'll talk a little bit more about this particular general meeting and how it works shortly. But, let's see, a VIP and since, since you're a little bit more familiar and, and Wendy did mention a little bit about indie, you want to introduce yourself. I don't, I don't know if anyone really knows entirely about you but your service of hyper ledger celebrity here. I don't know about that, but I have been involved in hyper ledger. Since the first, you know, before it was constituted. So I have a long history, but that doesn't make me special. Well, well, you are a very good resource. Go ahead. Yeah, I'm a blockchainist that that means that I basically am involved in so many different aspects of it, but primarily a technologist. And I run a small consulting company, which focuses on technology and business bridging technology strategy. I'm also the chair of the identity working group, and I'm also involved in the security and privacy working group, which is going to meet at 11. So, I thought I was mistakenly dialing in for that, but I am glad to have found the healthcare working group. So I'm just going to listen for now, because those two aspects identity, security and privacy are important to health care, I believe, and I'll just listen to what you guys have talking about. Excellent. Well, first of all, great to have you and it's good that you dialed in when you did. Where were you calling from, by the way, New York City, Manhattan. Okay, East Coast. Okay, good, good. Good to know. Okay, anyone else? It looks like I sort of recognize anyone else, but would anyone else like to introduce themselves? Feel free to do so. Okay. Yeah, everyone, I think we all sort of know each other. Otherwise, I see very familiar names here. And that said, let's continue. So great to have particularly Wendy on the call and Vipin as well. It's always great to have newer members joining us. So, and just as a sort of a background or the way these general meetings work, this is really just sort of a roll up of the work that we do in our ad hoc teams, as well as with our subgroups. And we'll hear from them shortly. And so I sort of run interference and sort of facilitate just to keep things rolling. And then for those of you that are newer, the idea is to sort of slot you into some of the other teams or subgroups where really the rubber sort of hits the road. And we'll talk about that shortly with our leads talking about the work that they're doing. Okay, well, so that said, as far as community announcements go, I don't have anything particular to mention. I do have an interesting opportunity. And we'll talk about that more with Steven Elliott down the road. It tends to focus a little bit more about interoperability. And so we'll talk in that context shortly. So does anyone on the call want to do a shout out for some something that's hyper literature related. Okay, so so let's get into the subgroup updates. So I don't know if Ben is on the call. So we do have a patient member subgroup as vipin had mentioned. And we just recently handed over leads. So some mercy on Ronnie had to step away for work reasons. Ben Gigi took over about about three or four weeks ago, maybe two or three weeks ago. And their group meets every other Friday opposite this Friday at nine o'clock Pacific versus our seven o'clock Pacific time. So our meeting last week was really a discussion about sort of what we wanted to going forward and sort of the backstory is we currently have a donor milk project, which is really interesting. And so the use case for that is when a mother gives birth to a child sometimes prematurely and a mother can't produce milk at the time that the child is born. She's looking for milk resource. And so the group the subgroup was working for quite some time with a company down in Southern California, developing effectively a sort of a special case supply chain to manage the resource and the sourcing for mother's milk. So that has been going going along quite well. And then we lost our customer, which is really also our SME or subject matter expert. And so we've been trying to figure out how to how to sort of reconstitute the project with with a subject matter expert or resource on that end. And that's been the discussion going forward. And as well, there's some talk about maybe bifurcating some of the work in the subgroup to continue to work on the donor milk project to the extent possible. And then to start looking for other opportunities that are more patient facing in the healthcare community using blockchain technologies. So and that may have been partly where where your name came up. And I believe that it may have been Marissa that had contacted you originally regarding that. So, so for anyone that's interested, feel free to contact myself or, of course, if you're familiar with our chat, you can go up on rocket chat and contact either the leads directly or feel free to contact myself and I'll sort of make control of that. Thank you for your introductions. And again, that that subgroup meets every other Friday opposite this Friday, but it says 7am Pacific, it's 9am Pacific. Okay, Ravish, you want to talk about the pear subgroup. I'm sorry, I was not there last week, or the previous week when we had meeting. But just a quick update, we have been kind of reforming, if you will, to kind of redefine the goals for the subgroup. So recently last, from last meeting, we sent out a survey, we collected some information, we're looking at that, and then accordingly deciding on, you know, how we move forward. And I am glad that we, I think it was, it was Wipin, right? Who was the identity chair who was on the call as well? Yes. Yeah, so Wipin, you know, I'm glad that you're here because a number of our discussions keep revolving around, you know, especially from a peer perspective. The identity is the key to start and then, you know, move forward with any of the problem solving that we are talking about. So I would love to collaborate with you to, you know, share your thoughts, what you are thinking and since the identity group is going to be much broader than just healthcare, what kind of things you are thinking about and what can be leveraged by the healthcare pairs, if you will, to help them with the security and privacy. That would be a great conversation. I would love to, you know, have you on our subgroup to talk about that. And on, you know, on the second item, which was the paper that we started with, we are looking to, you know, kind of finish our thought on that and get that going as well. So, which these are the two, you know, key things that we are working through. One is reorganizing to, you know, on the topics that we'll be covering this year. And second is looking at finishing the white papers that we started on regarding blockchain and application to healthcare pairs. Excellent. And how, what's your schedule for meeting? We meet every other Tuesday. And I have, there is a, the SIG Wiki page as well that has the information. It's every two, every other Tuesday and we publish the information, you know, for the meeting. So I, you can go to the healthcare pair subgroup SIG page and you can see the meeting schedule there. Excellent. Okay, great. And so your next meeting is, is it next week Tuesday or a week? It's going to be a week from next. Okay, perfect. Thank you, Ravish. So, so our next subgroup, which is just coming online is the healthcare interoperability subgroup and Steven Elliott. Steven, you want to talk a little bit about that? I see Steven. He's muted. Well, let's see, while Steven, oh, here we go. Am I off? Yeah, there you go. Good morning. Yeah, you're good. I don't know what happened. Technology. We've got the big screen and yeah, anyway, right. So the healthcare interoperability group is as a group that was born from discussions around EMR, electronic medical records and electronic health records and personal medical records and all those other things. And the focus, the result of those conversations were many. One was that there's a specific interest in trying to put an episode of care and the knowledge artifacts that that require that representation on a blockchain and how to do that and do it in the most simple straightforward method possible so we can things like transactions and assets, how those can be interoperable, how consortium of maybe two health systems on a channel can share information in an interoperable way so that the meaning of whatever procedure or treatment or or observation or medication, whatever on the blockchain can be mutually understood between all members, including the patient. Curious enough. And this is just beginning to ramp up. We have everybody's been super busy since the beginning of the year. So we're just beginning to start to put together the charter for this so that we can get some kind of formal representation of what our goals are, which is really just to end up with some code that that shows that we can exchange information between a channel and and how we do that. Things like policies, maybe we'll get into policy of interoperability or whatever. And so we're going to be doing this in a very streamlined bottom up type of fashion, making a lot of assumptions about things like identity and security. We can address those later we just get to the critical issue of how we put this information on a blockchain and and how that what that looks like, whether we need to have additional information on a side chain. All these kinds of questions will be the kinds of questions that will be will be will be addressing and will be the kinds of things that what we want to end up with the end of the day is. We know what the assumptions that we made will have to come back and deal with us but in the meantime, this is what we ended up with them, hopefully was provide a means to a service that other health care interested blockchains may be able to take a look at and adopt totally or take a look at the idea and go in a completely different direction, but at least have some working code at the end of all this to say look, this is what we've got. So we're going to be doing this through use cases. And taking those and building them out describing how they're going to be done. One of the first use cases will probably take a look at will be very simple case of an immunization will take a narrative like a mother and her child, maybe not even the child, maybe just mother. So so we keep things simple. Go to a walk in clinic and get a flu shot. And then weeks later go to their primary care physician and he's able to see or he or she is able to pull that record up and take a look at it and see that that's part of now their their medical history, even though it wasn't part of his. It was done by somebody else so. This will be, I think a bit different than some of the other working groups so the other working groups are focused on larger top down types of issues and this one will be something that we want to take a very thin slice and just work it from the bottom up. And see how what kinds of problems we run into. And what kind of success we can have in getting that done. Part of what we're going to be doing will be working with in our healthcare interoperable SMEs, clinical informatics that may be able to help us represent that we will need people like clinicians but we'll also need coders. So this is a very engineering focused group that would like to, you know, put something down and have a means to show that and how that how it's implemented and get other thoughts on how to expand that and then we'll be build out other types of use cases. That will address maybe different facets like like HIPAA and healthcare and governance and consent management and all those other different types of questions. So yeah, this is hopefully we'll start meeting. Early March depends on how much work we get done this weekend and in the coming days, but yes we're very focused on getting this bootstrapped and looking for anybody that don't need to be a coder, but you know enthusiasm we need documentation we need people that know blockchain so that they know what the peer is what an order is and how health hyperledger actually works. That'll be part of what we'll be doing. Yeah, general announcement hopefully will be coming in the next coming weeks and meetings will start hoping to march. Excellent. Yeah, so this is really exciting and as Stephen points out. So the other subgroups tend to work top down. And this is really more looking at it from a bottom up perspective so top down sort of focusing around sort of deliverables or projects that are sort of customer facing. Whereas, I think what Stephen and his team are developing is something more bottom up which is really services that can be sort of recycled reused in other similar contexts. And so this gets really, really interesting very quickly and so so Stephen the plan then is really I think you're you're in the process right now developing the charter. And as soon as the charter sort of gets complete then then we'll sort of put together a general announcement to membership that's not right. Yep, that sounds about right. Do you need any anyone to help with the charter or is that in hand. Well, I'm going to give it a shot this weekend and then we can distribute it maybe to other people that I don't know so you're still available or some of the others that there are other people want to collaborate on that. Okay, and I see I see Bob is on the call so Bob Collie was was in part instrumental in getting the subgroup spun up as well so I see Bob on the call. Right so yeah we'll get the we're going to we're going to first cut at the draft for that and we'll see where we stand after that and see how we proceed. Excellent. Very excited to hear about this and some of us were at the HIMS conference last week and this was a really interesting sort of discussion point because it's it's pretty evident that there are folks that are very interested in understanding interoperability and how blockchain could help serve interoperability so so this gets really interesting real fast. And then sort of related to this and I shared this with Steven earlier. It's interoperability interoperability related but but not necessarily related to Stevens proposed subgroup. I did see an email cycle and it's up online here. This is an opportunity for what's called an RFI. And it's the interoperability of medical devices data and platforms to enhance patient care and this is a formal RFI that was released. I believe it went out last week I just found out about it yesterday. However, it's interesting because this might be an interesting opportunity for those of us that are interested in applying blockchain technologies to this particular use case. That's why I'm introducing it here because it's because it's in some way related to the interoperability issue. If anyone's interested in sort of following up or participating on that, let me know. I what I'll do is I'll post this URL out on the chat channel. And if we can rally folks around this I'd be happy to help facilitate that. I'm just looking when ours are due date. So we're on our before March 15 so we only have a couple of weeks to act on that so anyway, so this, if anyone's interested or peaks of curiosity, we can sort of follow up on that as well. Okay, let's talk a little bit about our teams so we have in addition to subgroups we also have teams the teams sort of our sort of purpose built to focus on sort of more ephemeral things and so we're right now as probably most of us know, in the process of migrating from an older docu wiki platform to the newer confluence wiki. So aspects of our wiki structure are on confluence and some are still lingering on docu wiki. But what's really great is we have a redesign team that's been sort of working to help facilitate that and Brian here and probably mostly ravish have been working that. Ravish, do you want to maybe give us a little bit of an update on where we are with that effort? Yeah, so what happened was we were not able to get together earlier. I know Jim was trying to reach it. I was trying to reach out to Jim and the schedule didn't work and I was not feeling well this week. However, yesterday we had a meeting. I was planning to join a bit late but could not however I did touch base with David. It looks like they had a good discussion and they looked at various wiki pages and what was decided was Cain is Cain offered. You know, since he's leading these social impacts, I believe he offered he will make changes to that based on looking at various pages and then come come back with all the ideas baked into that page just for us to review. And once we agree on that model, then we can kind of trickle that down to all the SIG pages. That was the overall idea because I think every SIG has their own thought process and there are some goodness in each one of them from different perspective. So that's where we are right now. I believe David is going to schedule another call to kind of get together once Cain gets his updates in his wiki. Excellent. Okay, well good to hear. And yeah, so there's a two-part activity here. And basically if anyone has experience using Confluence, those are sort of the resources we're looking to use right now and feel free to contact Ravish. And so what we're really doing is as we're sort of migrating over to the Confluence platform, we're also trying to sort of establish sort of a more consistent sort of view or feel across SIGs. And the rationale behind that is, and Vipin sort of mentioned this earlier, there's a lot of interactivity sort of cross-cutting between SIGs and particularly working groups as well. And so we want to make that apparent to membership as they may have to sort of work across SIGs in order to get some of their work done. And so to facilitate that, I wanted to make sure that all the SIGs sort of had a common sort of look and feel, not necessarily absolutely the same but similar. So it's easier for membership to sort of transact in a cross-cutting way. And so that's the work that Ravish and his team are doing. And my suspicion is it'll take a little bit of time, but I think we're getting there. So thank you for that, Ravish. Appreciate it. Okay, we also have been doing some work in the academic research space. And I, Logan, yeah, there's a lot of, Logan's on the call. Logan, you want to talk a little bit about that, or do you want me to introduce it, or how do you want it? Yeah, so what was the gentleman's name who was actually driving that effort that we talked to? Yeah, that's Adrian Berg. So I'll give you a little bit of history, and then Logan, maybe you can sort of give us an update. So the academic research group is really just a handful of folks. This sort of kicked off back, and I want to say October or so of last year. And the gist of it is we notice that in healthcare, healthcare tends to be very academically wedded. And so things tend to move in the same way in the academic space as they do for healthcare, meaning that healthcare will look to processes that exist in academia, which means anything new that comes along tends to be vetted through more formal channels, which are white papers or papers that are peer reviewed through journals and approved organizations. So these sort of academic aspects in the healthcare space haven't really been addressed for the use of blockchain technologies quite yet. In part because the technologies are still quite new and that infrastructure hasn't really been completely sort of built out. It is happening, but it's a slow process. And the value of this, of course, is that if we can sort of help manage these academic resources, we'll be able to get some value or validation of blockchain technologies in healthcare by virtue of using the same mechanisms that the healthcare community has been using for years, which is these peer reviewed papers. So this team is really looking at ways to sort of approach this in a way to help sort of vet the process, maybe facilitate the process. So it's easier for people in the healthcare space that are interested in blockchain technologies can do their own due diligence. And they have at their disposal these very well peer reviewed papers to use as resources for making sort of these objective determinations as to whether, you know, any particular platform is better than another platform given their particular use case or context. So that said, we met, I think it was just maybe a week or two ago, and Logan has been involved in sort of summarizing some of the work that we wanted to do going forward. So Logan, do you want to take it from there? Yeah, thanks, Rich. So very specifically, we're focusing in on academic medical centers. It's a very specific term. There's over 100 of them in the US. An academic medical center is defined by three things really. Number one, it's a practicing medical institution. It's usually hospitals that deliver care to people. Number two, it's a teaching facility. In other words, there are med schools, medical schools that are attached or affiliated with those hospital practices. Most importantly, as Rich mentioned, number three, they conduct medical research and they publish. And so having had some experience in this field working with AMCs in the past, we're going to, we've got a list of basically people that we can approach and we're currently defining how we want to approach them to essentially work with them to get some peer reviewed research published. Very specifically, it's of note to Ravish that generic. Oh, what's the word I'm looking for the generic episode of care that I published to you is in effect the same thing that we're going to be approaching academic medical centers with right it's as I think Bilal mentioned or defined in an earlier paper that we jointly worked on. US health care is is quite disparate in terms of how it's delivering health care that you know there's primary care providers specialists hospitals and ERs pharmacists. There's public health institutions, family and caregivers and community resources that all could potentially be involved in delivering of health care. It touches Stevens problem of obviously interoperability. We're very focused on, you know, let's let's approach academic medical centers that already have a significant piece of those deliveries delivery agents if you will, and to figure out how we can work with them to make something that not only can deliver show the value of blockchain, but also engage the patient in a way that this the medical records that are involved in this episode of care are actually count on the patient to be part of those care team roles in delivery. Does that make sense to everyone and I'd love to open this up for comments or questions. So, so excellent summary, Logan and I think you're in the process of putting together sort of a summarizing page or two to sort of baseline the work that's been done thus far and and plans for next steps. I am. So, so when Logan gets that published, we'll make that available to membership. And so anyone that's interested in sort of working on this team of, you know, feel free to contact either myself or Logan or Adrian. And again, you can use the chat channel and contact us directly or feel free to contact me through through email. And I'll make introductions. And yeah, so this gets really interesting. And again, this is just really an interest out of those of us in membership that see the need for, you know, validating or vetting blockchain technologies in the healthcare space, particularly just knowing that healthcare tends to be very established or particular in in their process for evaluating anything new, including technology. So, so we want to try to make that make that engagement as easy and as facile as possible. So that's, that's the purpose of this team here. Okay, well, thanks Logan, I appreciate it. And, and Adrian is often on the call. I know he's not today. And special thanks Adrian for his work as well. Okay, so we'll get to some some old business just for those of you that are fairly new to the group. So if, if you're interested in getting published, consider that we have over 1000 members in this special interest group. Those 1000 members obviously are sort of pre filtered so we know that they have an interest in in healthcare. And further they have interest in blockchain technologies. And even further still, we can make a pretty good assumption that they have an interest in using the helper hyper ledger platforms to do some of that work. So, and the reason why I say that is that's that's over 1000 folks that may be interested in in collaborating with you on a paper that you may be interested in writing. Or they may have a paper that they want to write and that you may want to collaborate with them. And so what we've done is there, we have a page that we put together, which is really, it's sort of crowdsourcing the concept here. And let me see if I can move this out of the way. So I sort of kicked to the kick this off a couple of weeks ago and really this is, this is a kind of a true story. I wrote an article and my editor has that I don't know where it's been published yet. I wrote an article about blockchain technologies. And I thought to myself, you know, this was done, more or less sort of in the vacuum, and yet I still should have. This is his hindsight, which is always 2020 should have thought, well, gee, I've got over 1000 people that I could tap and have them collaborate with me to add real value and extra sort of perspective to to the article. So, so this is a way to sort of get around that issue and to say, hey, if you've got an idea, feel free to use this you can, you know, edit this wiki page directly and make an announcement out on on the chat channel or through our listserv or email, and say, hey, I'm interested in right up writing a paper about X, whatever the topic may be, you can sort of have a thesis of just a kind of one liner to maybe get people interested in what you're what you want to sort of discuss in that article or white paper, and add to that collaborators and then, you know, take it offline. Once you get to a point where you think the, you're ready to go. So this is just really just a simple exercise or a mechanism that allows people to sort of rally around common themes. If you're interested in writing on the topic of hyper ledger in the healthcare space. So this page is as available to you it's through the wiki, you can edit it directly and again feel free to do so. Again, the whole purpose of that is to make it easier for those of us that that are interested in in writing and getting the word out to to sort of the blockchain technologies community. And so that, you know, you can you can help to educate. There are an awful lot of folks out there that still believe blockchain is literally Bitcoin so we need to dispel that. Okay, and then we are also coming up close to the kidney X redesign dialysis prize, which is a competition that is it's national competition. Myself and Alan Bachman have been sort of working this issue. And it's due next week so we're coming up to the end. So Alan and I have been talking. I don't know Alan let's see the last time we got together was was it Monday of this week. Yep. Yep. Okay, so I do have some information to share with well with with the with the group here but although I'll probably take it offline with with Alan but the upshot is I had a very good meeting yesterday with our chief medical officer at Northwest kidney centers and just sort of a quick backgrounder. I know some of you are familiar with with sort of my interest in healthcare but I am active in the kidney care community out here in Seattle kidney care really meaning dialysis or or chronic kidney disease management. And as it just so happens kidney dialysis was invented here in Seattle in 1960 and then in 1962 Northwest kidney centers, which is currently now the third largest not for profit kidney care dialysis center in the United States is also located here in Seattle, as well as an organization that the Northwest kidney centers spun out for the sake of research called the kidney research Institute. They're here in Seattle as well and so when this particular competition arose it seemed seemed like a good idea to try to get involved in that and apply and think about applying blockchain technologies to the kidney care space. So so that said, I had a really excellent conversation with the CMO of Northwest kidney center she had some great insight and ideas on how to sort of apply blockchain technologies to some of the pressure points that exist in particularly in home dialysis, which is where a patient does dialysis at home rather than in in a center. So, so I'll not we'll take it offline but my gut would be I don't know if we're going to have time to get the paper published or put together by our deadline. However, that said, I got a lot of enthusiasm to try to continue this conversation fact. Suzanne, our CMO has really has asked that we find a way to maybe connect with her beyond this particular competition because she sees a lot of value in this thread of discussion. So, but like I said, what we can talk offline a little bit more in depth about some of the specifics. Yeah, I think, I think, you know, I think this is great CVS health is really making some big movements in making improvements for kidney care, doing some IoT things where blockchain can help and some of the conversations you know, you and I have had opened my eyes to, you know, things that we can do to improve the member experience. And I think I took a stab at drafting up a submission already. Oh, wow. Trying to look at the, the why you would want to use blockchain right, you know, it's not just about chain washing solution. It's about, let's have a solid use of blockchain, you know, we're not sprinkling everywhere. But let's focus on just the member experience, right, what can we do for the member without them even realizing that they're using blockchain. Yeah, exactly. And I'll just I'll just very quickly note that Suzanne was really interested in introducing IOTs into that into that sort of technology solution. And she got very excited about that or IOMTs. So IOT is Internet of Things. IOMT is sort of a newer sort of turn of a phrase, Internet of Medical Things. And so, so that that really got her interested. And like I said, I think we there's a potential for sort of longer term discussions. And my suspicion, and I'm probably getting ahead of myself a bit as I imagine we may decide to spin out a subgroup that sort of focuses around this particular use case, because it seems to be so, so full of potential here. So anyway, you know, I'm jumping the gun on that a little bit. But again, thanks Alan for your work and we'll try to talk offline very quickly about the stuff. So, and of course anyone that's on the call that is interested in participating in this, you know, feel free to sort of ping either Alan or myself. I do have notes that I put together that are up on the Google Drive, and I'll push those out through the chat channel, so that anyone can have access to them. Okay, so so moving on so that's exciting. And of course, you know, good things I think are going to come out of that. As well for for people that haven't already our survey, I think extended our survey out an extra week or so. And I believe we're looking at end of month for the survey to close. So I think we have probably about 30 folks that have responded to date, which given that we have over 1000 members that's that's terrible. You know, we should at least have a 10% response rate. And so please if you have not taken the survey yet, please do so. The link is available where you see it up on the thing there. The value really goes to making sure that anything that you're you have a particular interest in is caught or captured in the survey so that we can sort of make changes to the way that this particular SIG works and functions, and that we're doing the things that that you see value, the most value in collectively. Has anyone not taken the survey. Are you willing to say as much. Yes, I haven't taken the survey. Sorry. That's okay, but but you're you're okay I'll give you the pass. But anyone else that's on the call that hasn't taken the survey. You ought to. So, yeah, I'll admit this is when they all admit I haven't done it. But I will. Yeah, and in your, you're fairly new. So I'll give you the pass as well. Okay, so anyone that hasn't. Yeah, please, please do so. It's really is important to us because really, given that we have such such a large membership and a very small sort of vocal group of people that are active in this community. You know, your, your value becomes significant in the direction of and the voice of the special interest group so so they become important that that you do participate. Okay, great. So, so moving on to something that some really interesting news. We did have the hymns conference, which was last week. And I can never remember but it's healthcare information management, something society blah blah blah it's someone who knows what this anyone know what this really is. All right, well anyway, it's a healthcare conference and it focuses around it. That's really sort of the takeaway and it's huge 45,000 people to that to that end. It's sort of the most significant healthcare conference in this context internationally. And so I was, I was lucky enough to go. We had probably a contingent of about 15 or so folks from this healthcare sig that were that participated in the conference. I went through through hyper ledger so I spent most of my time at the hyper ledger booth and and talked at length about, you know, the context of blockchain technologies in healthcare. And of course, hyper ledger isn't particularly healthcare centric, but this particular this particular special interest group happens to be so. As a result, we really serve as an interface to that healthcare community and it was really amazing. From my perspective, given that I had attended last year as well. This past year, the delta between understanding in the healthcare community of blockchain technologies in this one year is absolutely stunning, particularly using the backdrop of healthcare. The progress of healthcare technologies being as glacial as it tends to be. I was very, very surprised at how quickly people have come up to speed on healthcare technology on blockchain technologies in particular. So last year, just to put some context to this. Last year, people came up to us and sort of, you know, what's what's saddle up to us and say, Well, I know I need to know about this thing called blockchain, but what is it. So we were talking at a much more abstract level. And this year, people are fully cognizant of the technologies. And we're asking very, very good questions and have having very good conversations that were much more granular and much more informed than I think most of us had even expected, which is phenomenal. So I'm just just a kind of a quick pass on attendees this morning. I don't know. I know below you sort of lived on the Florida area. I don't know if anyone else actually was on that's on the call was there that could add to it. What I'm going to what I'm hoping to do is a couple of our more active members. And I know it's difficult for them to make this particular call. We'll try to get some some notes together. Two things. However, I'll add that to me are were significant threads of conversation that seem to come up more than once. Number one, use cases we got at we were asked very often very frequently, what are your use cases that you might be wanting to demonstrate. Or do you have use cases that you can share with us. Now to me that's a little unusual, because it seems like you're trying to sort of shoehorn tech blockchain technologies into a specific instance. However, it is, I guess that it was pretty clear to me that we had so many people that were asking about use cases so. So here's I'm going to open this up to a little bit of discussion. I thought we used to have use cases floating around. But let's assume we don't. I'd like to see if we can maybe get a at least an ad hoc team together to maybe start developing healthcare use cases using blockchain technologies. And specifically some of our platforms fabric sawtooth or indie. I just want to participate in that. I, like I said, I, my interest is in trying to serve the need of what I heard in last week's discussions from from conference attendees. This is long enough. I'd love to participate in that. Yeah, so again, like I said, it was very, it was pretty clear to me that this is this, you know, that this seems to be a deficit that that we as a, as a, as a SIG have here. I don't, I don't see tremendous value in it, but I do understand that we learn by example and I think the way that's maybe the proper way to sort of see how these use cases get used is that you know if we if we present enough. If disparate use cases that people may be able to sort of infer from that where there is value where they may see value in blockchain technologies. Again, to me that seems that seems a little bit backwards. But, but again, that's, that's what we're being asked. By the way, the hypothesis community is supposedly assembling a set of use cases. So, instead of doing the work over, I suggest you contact Gordon Graham, who's the technical writer for hyper ledger and who possibly has a handle on this, I'll send him a note as well. Oh, excellent. And, you know, and there was a presentation of a pretty high, pretty high profile use case at the hyper ledger global forum in Basel. It was a big healthcare healthcare sort of service provider who talked about the application of hyper ledger fabric and that is a very extensive and in fact it was a CEO of this particular company. Okay, I don't remember the name right now, but I can dig it up and set it up or set it up on the on the channel. The other couple of things that came up, which mentioned my name one was rubbish talking about the identity use case. I mean identity concerns or identity interests from this group. And I think you guys should come to the identity working group calls as well. I mean, if you can spare some time. It's every alternate Wednesday. The last one was this Wednesday, but so it'll be two weeks from two weeks Wednesday from last Wednesday at noon in New York, which means it's 9am. So, you know, a lot of subjects get talked about. And one of the most interesting ones was about the concerns that this gentleman. I think his name is Stephen was talking about with respect to the caring or interoperating the patient information between different providers, or even different entities in the healthcare ecosystem. The groundwork or a foundation provided by Indy will help you because this is about claims processing and I do not know whether the patient is fully in control of releasing this information, because ostensibly that is the case but in practice, it doesn't seem to be the case, meaning like the doctors seem to be able to exchange information, especially if they are in the same hospital about the patient without express consent. And in this case, the, you know, the Indy case, the claims are controlled by the, by the patient. And we are also starting this project called Envoy, which is about exchanging information on the edge. It's an edge protocol. So, really speaking, the PII, which is personally identifiable information which might include health records. It says should not be deposited on the blockchain but rather in an ancillary system and then exchanged out of band, but the proofs are deposited on the blockchain. So, you know, you can then examine the proof and say that, you know, these things were done. Anyway, instead of going on and on about this, I am basically what I'm saying here is that there is a lot of interesting work going on in other groups that may have bearing on what you guys are talking about. So instead of reinventing everything, you know, we should try to build bridges and try to get information from other groups so that we can bootstrap ourselves. In a much better way. Excellent. Well, good input. And thanks for that, Vipin. And yeah, so for those people that are interested, to Vipin's point, sitting in on his working group meetings would be would be helpful. And of course, also, if you sort of want to wait in, there's also a channel up on rocket chat that you can sort of sort of introduce yourself, sort of wade into the conversation that way as well. So thank you for that, Vipin. Appreciate it. Let's see. So the last point regarding the conference had to do with governance, which really was also a little bit of a surprise. Had more to do with how do you manage a blockchain solution once you've got it implemented. And this tends to be more of a longer term consideration that tends to center on something called DevOps, which is really sort of the ongoing maintenance and upgrade of the solution. So this may be something else that we want to talk more about. I'm mindful of our of our time we're coming up to the top of the hour. So what I think I'm going to do is I'll add this to next our next agenda and pick up pick up the conversation on this point. Two weeks from today, which is our next meeting. So that would be Friday, March 8, which is seven, seven o'clock Pacific time. And again, for those of you that are fairly new, we meet every other week. So every second week on a Friday, seven o'clock Pacific time and in the morning AM 0700. So, and again, you have many sort of many ways to communicate outside of just these meetings. We have the listserv or the email thread that you feel free to make use of. You know, we have some really very, very bright and intelligent folks that that we want to be able to communicate that information to membership. So if you've got an idea or you have questions, feel free to use the listserv. And also, we also have the rocket chat channel, which is available. Really, all you need to do is have make sure your Linux foundation ID is set up so that you can just log in and go from there. With that said, any final comments or thoughts before we close out for the week. Alrighty. Okay, well, good. So thanks everyone. Have a great weekend, and we will see you back here in exactly two weeks. Thank you. Thank you. Thank you. Thank you.