 And of course, as always, good morning, good afternoon, good evening, depending on where you are. Thanks so much for joining us here at our Hyperledger Healthcare Special Interest Group. This is our general meeting for December 13th of 2019. And as always, please remember that this is a recorded session. And always, and I say this all the time, we do have an antitrust policy in place for the Linux Foundation. And I'll slide over to there. And you should be able to see that. Is everyone seeing my desktop, by the way? Yes. Perfect. So the antitrust policy, basically, if you read through it, it really means just be a good person. There are details that you want to go through. Feel free to follow the URL. And as always, if you have questions, let me know or read the full depth of the antitrust policy for details. So we have a couple of folks that, at least to me, are new. And it'd be great, well actually, most people I think I've met before. But if you're interested in introducing yourself, now would be the time to do so. And actually, John, can we have you introduce yourself? I think you're probably newer to the group. Sure. So my name is John Walker. I live in the San Francisco Bay Area, in East Bay, actually. And I've been working with, obviously, Linux Foundation projects for several years. But this most recent interest in asserted ledgers and permission to blockchain. So I've been working on and with the Hyperleisure Fabric development effort and implementing examples of that. My background is in large enterprise integration projects, semantic web work. So a lot of data quality and data semantics. So I'm interested in the blend of rich data semantics and having those captured where appropriate on distributive ledgers. So that leads me to my work with the SIG patient group. And that's it. Oh, very cool. And John, did you say you work directly in the healthcare space? I've been working in, basically, high tech mostly. And so I'm new to the healthcare space. Oh, great. Well, great to have you. Are you part of a company or a consulting group? I have a small company, a small consulting company based here in San Francisco. I have two partners, so it's a small consulting effort. If you're interested, the reason why I ask is we have a membership directory. I'll bring that up right here and feel free to add your name to the membership directory. Just it's a great way for people to sort of connect and sort of, you know, get together for really for business reasons, sometimes social, but mostly for business reasons. I'll take advantage of that. Thank you. Great. Thanks. And thanks for participating as well. And I don't want to steal your way from the patient subgroup, but we also have a healthcare interoperability subgroup, and they tend to focus on some issues with semantic interoperability. And so, and this is all in the healthcare context. So that may be something of interest to you as well, but don't walk away from the patient subgroup on my account. I'll check it out. Next, I think I've kind of, I've sat in on a couple of their sessions, so I'm trying to, again, just orient myself correctly. Oh, very good. Oh, great to have you. Thanks. I do no comments. I'm sorry, Dennis. I do no comments. Okay. Yeah. Yeah. Yeah. Okay. Is there anyone else on the call that like to introduce themselves that maybe is new or would just like to let everyone know what you do and where you're from? Yeah. Let me do a short introduction. So my name is Ehor and I'm from Ukraine. I'm an investigator. I do participate and as an investigator in clinical trials. And I'm a physician, I'm a doctor. I've been in this field, in the field of clinical trials for about 10 years, more than 10 years. I've been through about 50 clinical trials through this and currently we have in our side about 10 clinical trials. So I'm here for perspective of practical usage of any aspects of the health care that goes to clinical trials and pharmacy and sponsor clinical trials. Excellent. Oh, great to have you. And I think you're going to be speaking with Dennis on the presentation as well, huh? Yep. Fantastic. Well, great to have you on the call. Before we move on, is there anyone else that would like to introduce themselves? Kent, will you say a few words about you? Cool. My name is Kent. I'm in Hong Kong. I studied in the UK. I'm a registered pharmacist and also I did a PhD in Pharmaceutical Research and some training in the pharma industry. Then I went to Japan to do my postdoc and to work on some anti-cancer drugs. And then I realized that I needed to apply for a patent and I had no idea, so I studied law and now I'm studying blockchain because I feel that blockchain can be a tremendous benefit for healthcare and a big game changer. So I'm helping the patient's subgroup to lead the fabric development. And we've recently contributed some simple dev networks on the Hyperledger Labs repo. Thank you. Excellent. Oh, great. Thank you so much and great to have you on the call. Again, Kent, I think we maybe had met some meetings ago and great to have you participating. Thank you so much. Thank you. Alrighty. So is there anyone else that would like to introduce yourself before we move on? Hi, everyone. I'm Alex See and invited me to join you during the presentation and discussion. So I'm a blockchain developer and I'm a CEO of the Blaze Tech. We are working preferably on the public blockchains and have a great expertise in it, but we have Hyperledger and a little bit Corda. So I think we can bring value to the project and first of all, yeah, I would like to know more about the project. Excellent. Well, thank you, Alex See, so for participating as well and welcome and great to have you on the call. Thanks. Alrighty. Well, let's get started. We've got one community announcement I'd like to share, which is our Hyperledger Global Forum and I'll swing over to that very quickly. So that's happening at the beginning of next year also in March. This is in Phoenix, Arizona. And so for anyone that hasn't already thought about getting involved, this is really our Hyperledger sort of a large meeting for the year and we still have opportunity for participation either as a Hyperledger member or non-member and of course as an individual and so forth and so all the information is up on the screen there. One note is dates are changing very soon. So for those that want to get involved, we have just a few more days before the legs start to go up. So okay, with that said, I'll introduce Dennis Koskan. He is our chair of the HC-SIG patient subgroup and he and his team are going to present today on some very interesting work they're doing in the world of e-consent, pharmaceutical e-consent, but I'll just say e-consent and the team is looking to use both Hyperledger fabric and sawtooth in the development of their solution and they have really, they're really moving very, very swiftly. So I'm very excited to present one of our own subgroups here to membership today. And with that said, Dennis, I'm going to fire up our PDF and feel free to sort of take over and as I'll get set up here. Thank you very much, Rich. This is a great opportunity and thanks for the organization. And I think since July this year, we made three steps and it was only possible with the team, with the contribution of individuals. Can you move to the next slide? Sure. So we were always making jokes that Kent is going to sleep and John is waking up. Kent is working in each meeting and John is in California. There's almost 10 hours difference in the group and without these individuals, it was not possible to do the stage we came. Thanks a lot and I take granted this opportunity thanks to the team very much. And I look forward to the next steps and results. This is a great, I put also the LinkedIn profiles in the presentation and we put also the GitHub for the further consideration of our improvement in the hyper-legion labs. To the next one, please. So there are challenges in healthcare and one of them and getting more important is the compliance. I took also an example for the MetTech, which is very much part in Europe. There are so many small and middle companies, not only the bigger providers and especially with the consolidated medical advice regulation from the European Union, there will be lots of other regulative requirements, which makes the life of different providers very difficult. And also the GDPR compliance. I'm talking about Europe because I live in Switzerland and for the whole European Union and region for the pharmaceutical and for the MetTech providers there are challenges. So with the growing compliance, longer time to market and the development cost. To the next one, please. So if we focus on the clinical trials, we have also other challenges, not only the compliance, we have the data interoperability as Rich pointed out. One of our subgroup is also focusing on interoperability and we have a great guy leading the subgroup and we are also communicating and I was also promoting his meetings to our group and data process security for the clinical trials, traceability, scalability and most important integration, data privacy, portability and all together these are the challenges for the clinical trials process and for the providers themselves. So the next one, please. So we made a table to put more visuals for the interested people, how complex and distributed the process in clinical trial is and there's an immense amount of data flow. And for that slide I'll give the word to Ihor. Thank you, Dennis. So with this slide we'd like to present how the clinical trials are built and what they consist of. So the clinical trial process itself may take in some cases up to 20 years but it starts from 7, 10 years up to 15, maximum 20, it's rare cases. So and each clinical trial must consist of different phases, starting from the laboratory phase or pre-clinical phase which would be done in labs and then proceeding to the clinical trials done with humans. So it's starting from phase one and ending phase four and the phase one would be only on healthy individuals without the targeting disease that the drug is used for and the phase two, three and four would be for individuals having the disease where the phase two, sorry, would be the trial where the main dosage would be discovered so there would be several different doses and after the phase two the main idea is to have one or two doses most effective for the particular drug. The phase three would get the maximum number of patients before the FDA approval because all the clinical trials usually have the mission of having the FDA approval and the phase four would be on the market so the drug would be already used and already approved but still for extra issues that could be raised during first phases then this could be solved and done in phase four. So if speaking about the numbers so we would have the patients it's up to but I mean it's just to show numbers so phase two would have up to 800 patients and phase three may have up to 1,000 patients worldwide including in the trial and the number of signs can be up to 100 or 80 in phase two and the duration may differ from two to five years and here if they're talking about the e-consent then you have to understand that all the patients must sign the consent paper or e-consent that matter before entering the clinical trial so you have to understand that it will be up to 1,000 signatures during only one phase of the trial maybe more also you have to count that if there will be change of the version of the protocol during this this will require an extra ICF signing process and this will double the number if the patient is in the trial at that time. Next slide please Rich. So clinical trial is very much distributed and very much time consuming bureaucratic process we analyze the whole clinical trial process and find out the e-consent informed consent process is the most repeating and also time consuming process in the whole chain. The next question is if you have a solution to accelerate the whole flow how they integrate with the existing system whether the legacy systems and we have also in the team discussions how we can achieve that and I think this is also one of the possible strategic objectives of hyperledger community how we can integrate different solution hyperledger solutions in the existing landscape so our solution is the next slide please is the enterprise blockchain so validation of the efficiency better process efficiency with the regulators love cost process and redefine the process with the structure with the governance of the blockchain and we also want to deliver the GDPR compliance here security and data production so in order to do that you have to consolidate and integrate the distributed landscape and close the open end processes which exist in the clinical trial process in the clinical trial ecosystem many times so we want to achieve better compliance security trust automation transparency in mutability with the blocks integration of the stakeholders and deliver to the sponsors investigators and more faster process flow integrated process flow and also put the patients in the middle of the whole process next slide please so we have two examples Kent could you take the first one sure so in my work during in the pharma industry we were working on drug patents and the trend now because the clinical trials take so long typically up to 20 years the full lifetime of the pattern monopoly that most pharma companies are going for pattern extensions so working backwards we we can calculate that typically for blockbuster drugs all the big ones which make the most money that's every day saved that we can make an extra 17 million US dollars on average and so we're trying to use blockchain to make a more efficient system to put the documentation easily to hand and also to create autism all the stability and we think it's a much more efficient process thank you exactly thank you Kent and one of the longest longest clinical trials is in the oncology between 10 to 15 years or 20 years and if you calculate for the sponsors it takes it costs lots of effort and also cost and if we calculated all for optimistic understanding of the clinical trial for oncology drug development 15 years duration and every year 20 to under 20 days and if they give to a clinical trial the Sierra clinical research organization which cost very optimistically 15 000 US dollars per day and if they buy the data from a learner or epic it will also cost another for the patient data amount it all together a very humble number of 100 million USD so if you accelerate the whole clinical trial by cutting the inefficient and also non communicative interfaces you can minimize and cost the effort and the duration of the whole clinical trial minimum 20 percent so you can imagine if you use only for one if for one trial for one drug you will have a saving of 25 million very optimistically for many trials you can say even more and for one drug you have multiple trials for to come to the market next slide please so our value proposition is the distributed plagiarist technology is not a new one we have already in the last 10 years 15 years and with the existing technology and existing challenges we want to develop a non-existing patient-centric solution which is not available at the moment even with the legacy systems we believe that it is merely not really very much the data driver it is very much the documentation driver so with the use of artificial intelligence iot and blockchain all together you can deliver a big benefit to the healthcare industry and we put the patients in the middle and the biggest benefit for the pharma companies it's not only the cost it's also time to market which is very much important in the days of gene therapy and also the whole communication for the patient and the consent of it and the communication is also very important in the days of the regulation with the compliancy and we want to also put that use case in the collaboration with different organizations to see the results next slide please so we have some assumptions with our use case and thanks our team we have the first POC in the in our scope we will give some more details in the next slides we assume that our investigator is a hospital with a patient initial consent hand for that trial we have no other sites and the next challenge for our team is implementing the protocol the clinical trial protocol in the smart contracts so this will be a very time-consuming development for all of us and the different subject matter experts in clinical trials and smart contracts are very much welcome to join us the as you see in the previous slide which iHOR presented the multiple consent cost much of time and based on the adverse event and the protocol changes this consent needs a cure and the patient must be also very much part of the whole blockchain so another big challenge is the include and exclude criteria in the protocol how we implement in the whole process flow for e-consent this is also one of the topics we are discussing now next slide please so this is the scope of the whole and IHOR will talk about the initial scope and for the next steps thank you yeah thank you so I'll be talking only about this mark thread part of this slide so each clinical trial so the patient to enter the clinical trial the first thing he must do and you can as an investigator you cannot do anything else before he does this so he must sign the informed consent it doesn't particularly right now doesn't matter which type of the informed consent he will sign so it must be or paper or e-consent but this is the first thing that the clinical trial for the patient will start with and before that you have to choose particular patients that run so-called pre-screen check and to understand whether the patient is at the first part before signing the informed consent would be good for the clinical trial or not and this is very tricky process because you cannot ask the patient for any new information because it will be a part of the clinical trial and you have to run this pre-screen check with all the all the data that you have at that time and you cannot take any new information enough to to to to to get the new information before signing and starting the screen procedures of the starting the informed consent the pre the pre-screen check would be done by the protocol inclusion exclusion criteria and then after running this pre-screen check this will lead to the next step where the potential candidates will be or chosen for the next step or lost because they do comply with some of already known protocol inclusion inclusion criteria. All this process usually is done by the investigator who is assigned by the sponsor for the particular clinical trial before signing before having the informed consent it must be approved by the IRB the institutional review board and it must give its approval for the process and for the particular version of the protocol in particular version of the informed consent. The e-consent now it is pretty rare thing so it is used currently in the clinical trials we do use in for example in our current 10 trials only in one trial we do use an e-consent but still the signature process of putting the signature on the paper is done by hand so the e-consent here is used mostly for capturing the whole process how long does it take for the patient to read the consent that the patient had any questions and so on but as for now it's a very rare thing to happen and the most more than 90 percent of the clinical trials here in Europe in Ukraine particularly but also in Europe they mostly more than 90 percent use only the paper versions of the informed consent and the whole process is being distributed only by the paper so afterwards you have to document everything that was done each question that was raised and all the time was spent during all the visits before the patient signed the informed consent and during the signing of the informed consent so the idea of having the e-consent not only on the blockchain but any e-consent is very new and still it is very rarely used but as we understand and as we see in the next five years I think the majority of the clinical trials will use the e-consent thank you thank you next slide please so this was the existing scope and we want to reach mid of 2020 the other process which is defined in the pictures and the most important two challenges are the implementation of the protocol into smart contracts and in the transactions and the whole integration between this process frequency next slide please so we are also orienting our solution to the existing audiences we have target audiences in pharma investigators cros patient data providers and patient recruiters very important and we want to also have the possibility have the implementation in all these possible sponsors and possible implementations and we also understand their requirements very much that's why we need it took almost two months the previous slide the pictures we have to understand the existing landscape and the requirements of the different stakeholders next slide please so can't can you sure so we are currently attempting to pursue this scope with a sawtooth and fabric and the our our developments can be used not just within clinical trials but also in general in a general healthcare setting but also can be extended in a consumer consent setting as well so this is quite I would say progressive because I've I've never seen fabric compared directly against sawtooth and a lot of people say you can't do that and we we have we are very lucky because we have fabric and sawtooth developers on the team so we decided in the end let's just try and see and see what are the advantages of managers problems and maybe we can actually have some sort of a hybrid so I met I met Brian Bellendorf the CEO of Hyperledger he came to Hong Kong I think maybe two months ago and he was saying that the future of Hyperledger is going to be a hybrid of the different platforms and with that in mind I think this will be a really really interesting project to maybe compare and contrast but also maybe try and attempt that hybrid as a future possibility thank you thank you next slide please so based on that use case which we want to compare defined and fixed scope and compare in two frameworks the first solution the big picture was defined by Alex Alex can you take the word yeah hello hello can you hear me yes I can I can hear at least yeah good so this is this is a diagram shows blockchain architecture how clinical trial works and it includes all many meaningful components which work with EHR models and serial data in the also EET data all this information is moved to clinical trial and the process it according to according to workflow developed by smart contract and also it is all is managed and driven from web client side and just to follow consensus between all participants in this network all the notes in this blockchain network interact to each other so thank you thank you next slide please can you take the word please and count together have the trunk in your first sure so in looking at the basically addressing this the overall use case looking at it from a fabric perspective we thought we could take advantage of the channels the channel capability and basically subdivide the visibility of the different operating entities in this case we basically there would be a patient the data management an oversight a regulatory an investigator a CRO or clinical research organization and the sponsor and those each of those entities were orgs would have their own certificates of authority so basically they would have their own authentication and authors really authorization onto the channel onto the channels and so we would be able to separate we were able to leverage fabrics architecture again to separate out the different data requirements basically in the separation of visibility and so by writing the contract for the different roles the appropriate parties would be able to to see just there you know their part in the overall trial consent and we would be able to provide as we can see in the the oversight role acts visibility across all channels so that was the idea to to leverage kind of again this inherent design capability that's in sawtooth and obviously via the smart contracts we're able to if you look at the the bottom of the diagram we're able to control access right of any data or or any user via via the security in smart contracts so we're able to basically separate out just those events and data that are associated with the the consent onto the channels and not have a I don't have to worry about kind of the mix and match of authentication either from other legacy systems or other ongoing data and process flows so that was kind of the design premium that we saw with with fabric Jen so I just wanted to point out some of the salient features for example with fabric there was a feature called private data collection where data that gets put on the in the ledger can have a preset lifetime and after that expiry date the data gets deleted so this is quite unusual for blockchain in general and for GDPR compliance and for the patient's willingness to comply and and joining the trial this feature is very very important to us in in this design and so we envisage that at the beginning in the middle in the patient channel the channel the first layer that will come as a private data collection and with the fabric architecture in the back end we use couch DB and the each node will have each peer will have its own couch database but within the database it will be segregated so that each channel will have its not only have its own container but the private data service itself will be segregated and another feature of the private data collection is that the data can data throughput can be increased a lot because you can self-certify in that the anything you any transaction you put through the private data service gets does not need to go through the order or require other endorse endorses so we see that at the beginning now we're just looking at a register simple register system and then we get to advance to more complex smart contracts but if we try and think further ahead then IOT and patient monitoring is going to be a big feature in healthcare and that high volume of data throughput is going to require some modification thank you thank you Kent thank you John maybe just a small remark from our discussions we see the hyper ledger the blockchain now the back end we see as a middleware in the architecture and we are looking to also the indivision in the future keep the blockchain in the middle for the whole communication and transformation and it is also important about the GDPR compliance the data must not kept in the blockchain itself and if you have you cannot change it you click you are not allowed to keep in the blockchain article 19 so this these are the two considerations we discuss in the architecture and then I give the work to Alex for the software architecture thank you I'm sorry rich next slide please thank you yeah so here we described it in a simple way how our solution would look like using hyper ledger to the blockchain framework so this is the gram as simple as possible and it includes all many many components so from left side you may see different clients can interact to Satus node which is a part of blockchain network and all these clients it doesn't matter what the eyes are mobile application or website or IT device etc so each client interacts with our current component which provides API it is not a blockchain part but raise them back end that implements business logic and this on this component interacts directly to blockchain components like validator in Satus this is main component that provides consensus between all blockchain nodes in the network and every validator has its own set of smart contracts to this component some of them are standard Satus components with specific configuration like consensus engine settings and here on this diagram you may see two custom smart contracts developer develop it particularly to cover a constant use case in Satus first component is responsible to manage and provide permissions that is to data so this component is responsible to create accounts and link to specific roles and permissions and the second smart contract is basically responsible to manage data related to patient and counseling and of course every Satus node is a part of the blockchain network that consists of similar nodes thank you we need to present Alex and Grogoire which are the main contributors for the solution of softtooth and we want to go over to the demo because they produce they they delivered the first version of the poke the only thing is we initially planned 20 minutes for the presentation 20 minutes for the demo and 20 minutes for the Q&A and the question is we have only 13 minutes left should we go to Q&A or should we go to demo or we can have another session for the demo at Q&A Dennis give me a few minutes to show me a proof of concept it will not take too much time I will be sure no problem but we can go over to Q&A to collect the feedbacks and remarks and also recommendations from the call attenders our objective of today for to create a discussion platform all together let me skip the demo part today Alex and go to the Q&A okay okay looks reasonable yeah I agree with you and Alex Rich what do you say yeah I think we should probably move to Q&A and we can always have a demo set up for one of the next upcoming HCC general meetings sir sir wonderful thank you so the questions to the community and the participants are open yeah this is actually an excellent presentation so thank you very much for all the work you guys put in pulling this together it really shows in a sense how you can leverage blockchain into a clinical trial process which is quite nice um specifically I did have a couple of questions I can see the way the fabric the design was laid out conceptually I'll say the use of channels from your point of view is primarily to uh quote segregate different application flows you know the patient flow that you can send and so on which is very consistent and then you talk about the private data advantages and so on I assume when you look at um in a sense integrating data between the channels you're really looking at that at the um I'll quote the application client layer um which is you know above the smart contract layer so it's not contract to contract that's really the client agent level is that correct yes at the moment sorry sorry go ahead please go ahead okay um so we have another um fabric contributor called Anil and he has experience in fintech exactly replicating this architecture before fintech setting and uh Jim you're right at the moment uh they are using uh a higher an outside layer that's one of the problems which we want to ideally keep the data inside the blockchain network and when they're trying to figure out how to do that at the moment so any suggestions we really don't have great solutions for what I call update interoperability use cases you know you can throw away channel hopping you know the the double sided transaction for bitcoin kind of thing get rid of that exactly generic solution we don't have anything there the only two other quickies one is every time you do a blockchain architecture um there's a difference between what I call a logical network and a physical network in the physical network you throw it out there and say okay who are actually going to where is this thing going to run who are the host organizations they're actually going to host nodes on the network for peers but then separate from that you actually have a logical organization that has nothing to do with the actual physical operation of the blockchain if you will and I don't actually see sort of I didn't see a slide for that but I know that in a sense conceptually that exists so I'll say you know who knows who the hosting organizations are and the peers and all that other stuff physically say in my fabric example but above that you would say hey here's all the labs we want to integrate and all the other organizations but that's a logical layer does that make sense that there's sort of a closed slide that doesn't show that from a deployment architecture perspective yes yes I think we're going to have to face the deployment when we get there without that slide what happens is people get confused because they go it happens all the time to me people always go oh so I'm gonna have to run a blockchain in my office here no no no no you're not you're not to be a an organization hosting the chain you're not gonna be a peer but you are on the network as an organization just not at the physical level you're a logical organization if you will and then the only other thing I'll ask is do you guys have any generators you're using for any of the different layers in here you know for as an example the rest apis and stuff like that have you looked at using any generators in the fabric case not yet no not yet okay all right well thank you thank you this has been awesome wonderful thank you Jim very very good comments thank you Jim for the uh feedback any other questions guys so we have still nine minutes we can go to demo okay so let's start from them yeah sorry so can we finish it in 18 seconds yes I think so okay can you share your screen yes I'm requesting remote control yep here we go you should have access can you see my desktop can you see my desktop uh not yet no no one second so it looks like so it looks like we may have a I hear lots of uh so we may want to hold off on the uh the demo I'm getting an air message on my side for sharing so I mean we may we may want to hold off on the demo Dennis and Saul next time uh it shows me that I cannot uh share my screen because another person sharing yeah let me let me try to stop share on my side and then okay Alex try again on your side just just out of curiosity okay there we go okay perfect uh can you see yes yes we do see okay so uh let me show you our proof of concept this is um result of our work of our team and that is iterative process and we will do past two and this proof of concept is version number two and there is room we have two iterations but basically uh this proof of concept colors uh first part of a consent uh let's assume we have three participants uh in uh a consent like a hospital patient and the investigator who will perform clinical trials and uh every uh uh participant has their own uh role and the permissions to operate with the data so uh I already registered one hospital in a blockchain when this is in hospital and also I registered one patient patient list uh and also registered one uh investigator participant blockchain if you click on investigator list when I see that uh there is only one and uh now uh to uh uh uh perform a consent uh uh flow we need uh uh we need to register uh a HR role in hospital for patients and after that uh uh investigator should get such a data make uh perform uh exclude and include uh criteria uh steps and import data to uh his database and uh make a final change of this data and uh uh uh uh as uh uh approve this data for for the clinical trials so uh for the moment uh in current implementation uh all HR roles are ordered by uh hospital and patients in health uh for this case patient should grant permissions grant hospital permissions to uh uh rate his own data uh add uh data uh and uh share his own data uh with uh uh as in this is a party just a third party members like investigator for this case we uh uh operate this patient click hospital list choose uh uh hospital we want to grant permissions and grant him uh uh uh read uh uh read uh uh permissions to uh uh uh to HR data uh grant uh right permissions to HR data and we also grant uh uh uh uh uh grant permissions to share uh uh the patient's data with the party members after that uh hospital uh can uh create uh uh new HR role uh for the patient for instance uh operate this hospital click on register HR data uh enter uh link ID for the patient and set a few uh mandatory uh parameters and click adjust to and so uh hospital can check uh data for this patient you will see four shortcuts this is the cross rail zone that uh before and uh last one on the side that recently art is that uh hospital should grant permissions to investigator to retrieve uh data in this patient click create uh access to share data button and finally investigator can uh get uh retrieve some data from hospital uh he investigator uh uh choose uh appropriate hospital and click uh get uh share data and he see uh uh HR roles uh related to the patient who uh uh granted permission to share his data with investigator after that we uh uh uh um so so alex this is rich so we're we're just coming up to the top of the hour i think well we just need to sort of hold on the demo here uh because we need to close out uh before the next session begins at at the top of the hour so so thank you so much alex and uh and denis and in the rest of the uh the team for the uh the patient uh subgroup for the hyper ledger special interest group phenomenal job this is one of the rare instances where i think we're going to really see some amazing results coming out of uh out of the subgroup thank you so much everybody uh and i just want to let you know as we reach the top of the hour uh we're we're not quite clear as to whether or not we're going to be able to do our next uh meeting at the end of the month by virtue of the fact that we have the christmas holiday coming up but please stay posted we will let you know in advance of that uh we are at the top of the hour thanks everybody uh we'll see you in either a couple of weeks or after the holidays and if that's the case have a great holiday season and we will talk to you very soon thank you so much thank you all right thank you happy holidays thank you happy holidays happy holidays