DAML Smart Contracts, COVID-19, & Verifiable Credentials Webinar

Captions as YouTube publishes them, usually machine-generated, so names such as Daml and Canton can be misheard.

1. 0:03

   good morning everyone thank you very much for deciding to spend your time with us uh welcome today we have a very interesting session for you the topic for today is especially pertinent during this session we'll zoom in to review some of the challenges and opportunities that exist uh when it comes to processing and sharing diagnostic test information and other other information of course across

2. 0:27

   multiple entities these could be health clinics labs state local agencies such as the cdc uh insurance firms and of course consumers such as ourselves who need access timely and relevant you know access to uh the information that we that different institutions have on record uh about us so we'll present during the session today a view of what emerging technologies such as smart contracts and verifiable credentials uh promise as a solution uh we are also

3. 1:00

   very excited to show uh during this during this session a live demo of an end-to-end kovic 19 testing and vaccination process using demo smart contracts and trends and verifiable credentials using forensic uh we'll also bring out why this is not just uh healthcare on another healthcare on blockchain kind of a session by bringing out some of the unique advantages and innovative ways you could deploy such a solution uh you know for yourselves obviously

4. 1:29

   uh there's a lot that goes into making such a solution real but i'm sure you'll immediately see the benefits that the technology and such a solution presents especially from an operational efficiency and customer experience perspective um i'll i'm recording the webinar so i'll share the recording with with you after the after the session um and now uh let me welcome our speakers first off

5. 1:54

   uh bart kant ceo of rt ledges uh who created the wonderful uh demo and solution that we are going to see today but would you like to introduce yourself absolutely thanks manisha good morning good afternoon good evening so my name is bart kent i'm the founder of rethink ledgers which is an independent consulting firm in the blockchain dlt and centralized ledger space so my background goes already back a number of years in 2014 i was really focused from the very beginning

6. 2:27

   on blockchain solutions while i was a consultant with capgemini doing digital transformation mostly in the financial services sector and that evolved uh greatly when i joined ibm and became a co-lead of the ibm blockchain services organization so i have a lot of experience working on implementing blockchain related solutions mostly in the financial services sector but also in the health care sector and as an independent consultant you know really was

7. 2:57

   intrigued but what was happening to us all of us during covet and that's triggered me to build a little prototype incorporating some of the newer technologies like demo uh like uh the solution from intrinsic around verifiable credentials and hope to share that with you here on this webinar perfect thanks bart um and now i'd like to welcome uh riley hughes uh ceo of trinsic uh trinsic's verified credentials app has been used in the solution that we're going to see shortly um riley uh would you like to say

8. 3:29

   something yeah sure so hi everybody um riley hughes um happy to be talking about verifiable credentials and how they can be used and integrated with other blockchain solutions today um my background is i got kind of a start in verifiable credentials and self-sovereign identity um after i was working at a at an impact investing uh firm and was trying to assess impact on the investments we were making but it was really hard because you know we want to assess impact in

9. 4:01

   terms of people and that requires identity and and in the in parts of the world that we were deploying these investments it was difficult to measure accurately the investment impact that we were making um because of the identity problem so it led me to uh talk with somebody named phil windley who was the chair of a a nonprofit called the sovereign foundation and i ended up being the first employee hired there um

10. 4:26

    aside from of course the the original founders of that project and so i was at the sovereign foundation for a couple of years until i um started trinsic with two other co-founders to try to make it easy to integrate self-sovereign identity and verifiable credentials into any application and and that's what we're seeing here so um happy to be here to talk about it perfect thank you riley and now i'd like to welcome corey todaro my colleague from digital asset he's our he's a healthcare expert as well and

11. 4:58

    he's going to be sharing his insights on some of the challenges and opportunities he sees in the healthcare healthcare space uh corey would you like to say hello all right thanks manish hello everyone um i'm corey tadaro i'm senior product manager for healthcare here at digital asset where i eat a drink and sleep demo for healthcare working on specific industry tooling working with clients and healthcare enterprises on using daml to to solve

12. 5:24

    acute business problems uh and working uh in a variety of areas uh past six months of course a lot of attention has been drawn to covid um really excited to uh to be looking at the demo today to be able to share the demo with you that bart and riley have worked on and to talk about some of the broader issues around healthcare challenges and regulation and demo tooling perfect thank you corey uh so of course you know we'll be keeping the uh session very interactive um so feel free to send in your

13. 5:57

    questions via the q a panel or even the chat and we'll address them uh during the session um so with that corey let's start with you um about some of the challenges that exist uh in the healthcare you know technology space today um this is the part where i usually start to wax um about all the woes uh within the healthcare industry being a veteran of healthcare operations myself

14. 6:22

    having spent over a decade in in hospital uh hospital operations i.t and strategy in the provider sector there's no shortage of war stories around some of the what i'll call wonky workflows in healthcare and what what we mean by wonky workflows are cumbersome business processes that require hands-off of information timely information and response with a range of counterparties be that insurance companies claims clearinghouses patients

15. 6:54

    fellow providers and practitioners whether that be affiliated or simply adjacent within a market the process the delivery the processing the payment of health care is very cumbersome with the lots of handoffs lots of fundamental data interoperability issues and this has only been exacerbated in the last decade by the drive for ironically digital transformation within healthcare the proliferation of digital tools does

16. 7:26

    not guarantee smooth workflows and so we we see now that business processes are often additionally complicated by uninteroperable data systems data formats messaging specifications and or tooling so the presence of a digital tool um within a healthcare ecosystem does not necessarily guarantee or even lend itself um to uh to smooth workflows to improve deficiency often we find we

17. 7:58

    have to adapt manual workflows to accommodate uh new technology and so the fundamental problem is that workflows are not shared at best we have automated workflows within our boundaries of an enterprise or our domain and we essentially pass messaging traffic uh over the transformer under the door slipping envelopes under the door to each other to pass information and waiting for them to come back and and the ultimate price that we pay for this uh for this level of dysfunction um in smooth

18. 8:28

    smoothly operating and automated workflows and healthcare um is is for the operators themselves um costly uh manual work um the fax machine and the in and the pager still reigns supreme in many health care settings um in the u.s uh and elsewhere um but i think the most important cost that we uh that we see in healthcare from this kind of workflow is the uh the friction that the patient experiences um in in delivery of health care being able to follow getting

19. 8:58

    courses of care being able to understand their financial obligations towards their care being able to make smart decisions about their own health and their receipt of health care is often blocked by this and so we see that critical processes ending up broken and we radically increase the risk of things going wrong of lost revenue of poor patient experience all of which contribute uh to our overall sense

20. 9:24

    of what's wrong with health care today and so go ahead manish yeah no i wanted to mention risk of privacy and other regulatory compliance with people absolutely um of course i mean one of the reasons why it's so cumbersome is that uh healthcare data is so highly regulated as it should be because it it speaks to very intimate and personal aspects of our lives and our families lives

21. 9:47

    and so any any provider any entity who handles such sensitive personal health information of course is required uh to meet uh you know a range of regulatory requirements around the movement of that data the security of that data encryption etc and so um one of the reasons i i'm so passionate about demo um is that it it is essential tooling um for bridging islands within uh and between enterprises specifically in healthcare we can

22. 10:19

    leverage what we call smart contracts or or demo multi-party workflows written in demo to create a shared workflow so that my systems are interoperable with their systems within a very well-defined and regulated uh workflow and what that means is from a damn perspective in terms of damo language is parties can agree to a workflow where parties rights and obligations are precisely defined

23. 10:49

    the ability to view data the ability to change data the ability to advance a workflow is all defined on a party-by-party basis and so we can strictly regulate not only the privacy of the data while also automating the workflow around the handling of that information and so we can create transparent real-time views around a workflow so that we're not waiting on the envelope to slip under the door to know what the next step in the process is um

24. 11:20

    we can more seamlessly communicate and bring value to patients providers and payers um in in in fundamentally new business practices and so we can reduce the risk of exposure uh of sensitive health information we can increase the data transparency within those precisely defined contexts that the dama language enforces and ultimately to build a real-time information flow between within large uh complex healthcare enterprises and of course between healthcare enterprises where

25. 11:53

    it's essential healthcare is never delivered by a single entity it often involves a multiplicity of parties and damol is the ideal tool for that what i'm excited about today is looking at how those inherent characteristics and the inherent advantages of damo can be applied specifically to the coveted space and combined with technical innovation like verifiable credentials and so when i think about demo driven healthcare of which today's topic and demo will be a great example we want to break down data silos and

26. 12:25

    drive fundamental workflow and data interoperability there are a lot of messaging formats in in in health care if if it's financially related that's usually an x12 edi message if if if it's clinical data repository we're talking about fire hl7 we have code sets for everything in healthcare from diagnosis codes to pharma codes to condition codes we have messaging specifications for continuity of care demo can sit at the heart of a lot of these messaging formats

27. 12:58

    translate messages from a one specific messaging format into a workflow and generate a new message in a different format on the other side and so gamble can become a indisposable tool for for bridging the chasm between existing technology stacks and messaging formats within healthcare so that we can engineer more responsive systems for the benefit of the patient ultimately and for the operators who have to handle uh and deliver health care on a

28. 13:30

    day-to-day basis yeah and just just a quick uh comment on the point of data silos or data islands between different entities or even within an enterprise when there are multiple applications that share data with each other today i think the story of software has always been about abstracting and making it easy and going to the next level of software that makes a lot of things that we do today kind of redundant somebody still does it

29. 13:55

    but it's relegated to the relegated to some somebody else you know similarly i think when we do uh when we are used to taking multiple data sets consolidating them staging them cleaning them all of that stuff um you know kind of demo sort of makes that uh you know abstracts over or on top of that complexity i think so that's uh that's one way i mean it raises the issue of interoperability to the level of workflow where i want to know who am i interacting with what do i need to do what do they need to do

30. 14:26

    that's what demo code actually looks like when we write smart contracts in daml and so we can abstract away the lower level systems which produce a report or to reach a certain calculation around the value or the cost of a given episode of care and bring that seamlessly into an automated workflow without having to re-engineer the entire system and so the the ability for demo to incorporate through uh through through api and through messaging specifications is really

31. 14:56

    um i think the secret sauce uh for a lot of healthcare applications i'm excited to explore that more today awesome awesome yeah so with that i think let's uh quickly uh touch upon what demo is because that's going to be covered in the uh in the demo today and then but feel free to jump in as well uh but corey do you want to uh do the intro quickly sure uh well damol of course is a language it's a language for writing multi-party workflows in a secure and reliable way deterministic way

32. 15:22

    but it's also a runtime for for processing um these kinds of smart contracts for these workflows and so damil um is when we write gammel we we end up with a demo application which runs on the open source demo runtime and uh can communicate with systems uh with uis frontends et cetera through something called the demo ledger api and json api we can also integrate demo into a variety of what we call persistence layers that can be of course what the topic of the day is around blockchain and distributed ledger

33. 15:56

    a wide range of blockchains and distributed ledgers vmware hyperledger fabric sawtooth theseu but also importantly um databases uh whether that's postgrass amazon aurora amazon qldb which are fundamentally centralized databases and what makes a demo unique is that we separate the writing of your application from the choice of underlying persistence layer and one of the most important reasons for that of course is is is regulation uh and privacy

34. 16:26

    um making sure that medical data meets the regulatory or your your application which utilizes medical data or accesses sensitive phi can meet the regulatory requirements for whatever location you might happen to be in it's important that the the solution designer have the choice of persistence layer to meet those kinds of functional and non-functional requirements neither the customer demands uh and or

35. 16:52

    regulatory bodies demand and so that that choice of underlying persistence layer is a crucial aspect of damo but these are all of the the rather components that make up what we call a demo driven solution yeah and if i can maybe jump in right so so i became aware of demo about a year ago and really started to spend a little bit of investigation and learning around the tool set and you know it was very clear from the very beginning that this was you know because it's a business driven modeling language

36. 17:25

    it could be one applied to a number of different use cases uh but then secondly it also helped me to you know make an important decision you know push an important decision down the road right what is going to be my data store of this application is it going to go the blockchain way or is it going to go the decentralized ledger way or is it going to be deployed on you know a simple database

37. 17:50

    and kind of make not having to make that choice and building a solution you know was really valuable to me when i when i picked demo to build this uh prototype solution that we'll demonstrate uh here shortly yeah and uh at the beginning of the session i said uh you know that this is not just uh another healthcare on blockchain kind of a session so that's uh one of the things is if you see here the interoperability of one demo

38. 18:18

    instance with another demo network for example this is what uh brings out a very key difference so for example you know you need not rely on a blockchain or uh you know a use case that allows you to interact with other external entities in order to develop such an application because of the benefits that corey mentioned you know synchronize your workflows have multiple applications

39. 18:42

    within a company access a common single source of data without having to constantly reconcile reconcile it um all of those the workflow within inside an enterprise can be developed using dml and deployed on a database for example because within an enterprise you may not want to deploy a blockchain but at the same time that same workflow can be extended so then it works on a workflow across

40. 19:06

    two different entities you know for example bart's workflow that we'll show today um if that is on a blockchain then your workflow within the enterprise can easily interoperate with it so that's uh i think that's one of the big big benefits with separating the smart contract layer from the blockchain layer okay so with that um yeah so um a couple of last week bart published a very nice blog on on demo.com so around this topic

41. 19:39

    and this diagram is actually taken from there so it shows the uh the current landscape and the data islands and the challenge that bart set out to solve you know with this demo so why do you want to describe this a little bit and then yeah absolutely and kind of uh what i'm trying to do here in the next few minutes is kind of apply all of the challenges that corey talked about to

42. 20:01

    you know the opportunities that particularly exist in the covet 19 situation so cover 19 happened to all of us and it was actually by being part of the coveted credit initial credentials initiative so cci which is uh and a work group uh basically a global community of more than 300 individuals over 100 companies that you know all came together and looked at what technology can we use to basically enhance privacy in this

43. 20:33

    difficult situation of of uh getting some of the credentials out there it could be testing could be in the future uh vaccines uh we all you know kind of had a lot of discussions around immunity proofs and being part of that initiative kind of drove me to build a solution uh based on demo based on verifiable credentials and trying to address some of these challenges here right so in the us we have over uh several thousands of health clinics uh there's a lot of

44. 21:02

    software providers you know we all know the pain about you know dealing not only with the health system but then also the insurance side of things and then we all uh look at the news and look at the reports of you know what are what is the situation and you know many issues have appeared over the last couple months you know think about florida where there was a dispute about the data uh just recently uh about incorrect or

45. 21:27

    delayed data that was coming through and so trying to come up with a prototype solution this is you know something that obviously needs to be further involved and takes a lot of the context of the legal aspects uh that needs to be aware but you know trying to get real-time information between all of these different data islands into a single solution is what drove me to to build uh this prototype um and from that perspective you know the the second big challenge

46. 21:57

    and i i i started explaining that a little bit more is right around you know what is the data store for a solution like this right when we talk about privacy and authentication you know we need to store somewhere the data and being able to defer that decision around should i use a blockchain should i use hyperledger fabric cord bezo or uh go the more centralized way in this particular situation i've you know made the decision because my my use case was driven by you know getting the right data to the state

47. 22:29

    agencies on doing it a much more centralized way and centralized could be a simple database uh it could be a centralized ledger like aws qldb or it could be project dabble which is an centralized ledger based infrastructure that was provided by the team from digital assets and and allowed me to quickly deploy uh my my demo codes together with the ui and and making the solution a quick deployment so that's kind of where you know i was able to leverage

48. 23:09

    a lot of the kind of capabilities that were available uh around damo and then kind of took it upon myself to integrate it with uh kind of the next uh technology component is verifiable credentials uh which riley can talk a little bit more about and you know what intrinsic offers yeah so we look at the workflow of how it was used but riley do you want to quickly outline essentially what are verified credentials first for people who are new to the concept

49. 23:39

    and then maybe a little bit about how intrinsic does it yeah absolutely so verifiable credentials are a a w3c standard for uh issuing and verifying essentially digital uh certificates right so think think about the things that you put in your wallet um and how easy it is to use them to prove things about yourself in the real world you know i can take out my driver's license and prove that my name is riley uh and and you know that i am of a certain age and

50. 24:11

    and all those things and and people can trust that with a high degree of trust but there's no way to do that online and verifiable credentials solve that problem um in in by by really mirroring the way it's done in the real world so if you see the diagram on the slide in front of you you'll see that there is an issuer uh and and they issue a credential to a person and then uh the person when they need to

51. 24:35

    use the credential can share a verification with uh what we call a verifier and as long as the verifier trusts the person that issued it then this system works really well uh and they can and and that's the case because these these credentials are uh temper evident uh the word tamper proof is on there for simplicity's sake but um really they're they're tamper evident so the verifier can tell if

52. 24:58

    they've been tampered with they can instantly verify it and uniquely the credential is held solely with the person or the subject of the credential so verifiable credentials work really really nicely when you don't necessarily want to store all of the data on a blockchain right if if we're talking about personal health information for example um you know it's probably not something that you want to just uh you know basically encrypt and put on a

53. 25:31

    public blockchain like ethereum that's that's uh you know tamper-proof and um and that sort of thing right because because the implications of of that data being compromised are really severe and so verifiable credentials provide a way um to keep everything off ledger there's only essentially keys that are put on the public ledger for encryption's sake and public keys for the issuer and that type

54. 25:54

    of thing but there's not even a reference or a hash of the credentials on the ledger it's completely off ledger solution um so that you can do these verifications instantaneously and it also works really nicely for putting the person as the point of integration between multiple kind of um services right um and then and then because they're w3c standard they are uh standardized and interoperable between different implementations um so i don't know bart do you have anything to add to that uh anything that i missed specifically

55. 26:27

    about you know when you were looking into verifiable credentials that um yeah i thought it was a yeah a great yeah and again new technology right so we're early adopters here of you know making this use case applicable and i really looked at this as a solution for solving the digital experience in the case of covet 19 testing right so if you look at what is currently happening uh if you go do a test um you know a lot of paperwork that needs to be filled in and then

56. 26:57

    in the best case scenario you get maybe a letter in the mail in most cases only a phone call and so you know looking at you know what is the minimal expected digital experience that everybody is looking for um you know verifiable credentials solve that problem uh and uh could be applied here to kind of you know test results and that could be applied in lots of different use cases of where that could be valuable but it could be further enhanced and in the future around vaccine records

57. 27:30

    uh medical records and so on and so the the concept of verifiable credentials in the healthcare space seems very very promising uh not without its challenges around the regulatory aspect so uh but you know we see a lot of um progress in that aspect as well uh with some some recent uh changes into you know for instance the california law around allowing verifiable credentials for for medical records and and setting up you know a work group to further study what that could mean uh to further digitize health

58. 28:04

    records in the future yeah so nish if you don't mind going to the next slide um i think yeah well just one second i know a few questions have come up and unfortunately i can't access the q a panel while we are in full screen mode so i'm going to go off full screen for a second and see the questions that came up uh just give me one second okay um is it okay if you can uh can you

59. 28:29

    see the screen still uh ready yes okay so let me access the q a if you want to proceed and then i'll i'll go back to full screen soon yeah um i can see the questions um i think the you know the comment that i'll make um here is that i think trinsic and digital asset are really aligned well and and um are comparable in that um trinsic is a full stack self-sovereign identity platform

60. 29:00

    right so we offer a full stack solution for issuing and verifying verifiable credentials as well as digital wallet solutions and and a suite of apis and sdks for developers um but the beautiful thing is that verifiable credentials are just this this uh data standard they don't necessarily need to leverage blockchain although uh we have chosen to leverage blockchain because of its

61. 29:23

    uh various benefits but just like uh daml abstracts away the decision of blockchain versus database etc trinsic likewise um is is sort of a layer above that and so on that previous slide with the issuer and the verifier and the person you can sort of imagine um below that there's there's a layer below that that could be viewed as sort of either a blockchain or a um you know a centralized database or digital wallet or whatever the solution

62. 29:53

    may be but it's flexible enough um that it can support all of those different use cases um and so i guess manish would you like me to answer these questions that were asked or should i should we wait till the end yeah i think one of the questions that came up would be worth uh you know addressing now um question was from india about images you know so what do you do about images and other such information that comes uh that needs to be stored

63. 30:20

    that's a great question so there's there are um uh several kind of approaches uh still there's various approaches because like bart said the technology is new and many of the approaches are for sort of sunny day scenarios right so so maybe doesn't cover all of the edge cases but it solves the problem immediately so with regard to medical images i would say that you know verifiable credentials

64. 30:51

    uh may not support all of the the important edge cases that are required for medical images for example um and that's you know that's okay but but for now images and credentials are typically done using an attachment to the credential that's also stored on the mobile device of the individual with the credential um or hosted in something like ipfs with a hash included in the credential which is resolvable for the verifier so there's several ways that people do it um i've actually haven't seen anybody

65. 31:23

    using verifiable credentials specifically for medical images just because um there's probably a bit more work to do there to cover all of the important cases required for something like uh medical images and uh another question that bart uh you or corey might want to address uh this question and let me go back off full screen i'm sorry for this uh is a question from charles um he says that you know um how are you how are you handling multi-party consensus and all of those

66. 31:54

    things and are you truly leveraging the innate benefits of dlt tech with such a solution uh do you want to have you know comment quickly on that aspect yeah no maybe i can give it a shot here so um you know the question around you know using dlt is is kind of optional here right uh and in the case of you know the the the prototype that you will see shortly kind of the decision was to make it much more centralized than decentralized

67. 32:25

    uh and it based and and that's was based on the fact that you know we're looking at this from a state agency perspective um they need to get kind of all the correct data uh for all of these test results that are happening uh and using kind of some of the curly stages of decentralized tech to accomplish this right i know when i say early stages of decentralized tech is that you know you can use uh digital identifiers dids uh it does not necessarily

68. 32:57

    need to include your security social security number uh but could kind of identified you in a more um uh pseudonymous way uh the the um demo language and all the smart contracts uh are driven by you know uh the who are the the signatories and the observers of that contract and who really can get access of the data versus everybody else uh and and making it widely available um through kind of a more public-type blockchain so there's there's components of dlt uh distributed

69. 33:37

    technology being leveraged but also kind of looks at the practicality and in many cases you know and coming from the blockchain world and having lift you know a lot of uh attempts to decentralize a lot of workflows across lots of business users um you know there's there's there's sometimes not necessarily a need to make everything decentralized uh and operate it uh in a more more or less centralized way uh and solving the solution like that uh

70. 34:09

    for the specific use case yeah i can offer a little bit more as well um the output of the demo runtime is is deterministic um and where that run time is located is is optional it can be run by a single party um on behalf of a lot of users in which case it is uh you know a centralized solution um the output of the demo runtime can also be written to distributed ledger in in which case we have um we have multi-party consensus

71. 34:39

    um over over the lineage um the audit trail of all transactions that have taken place that have been outputted from the from the demo runtime and so you'll see that for example in our fabric integration or in any of our distributed ledger uh applications where there is a governing consensus mechanism uh the runtime outputs um from from one party or from multiple parties can be written to that ledger um where consensus is achieved and so uh damn can work in in in a range of

72. 35:10

    what we call trust environments uh depending upon the appetites of of the client um of of the participants who are utilizing the solution um and of course the the regulatory structures as well that have an influence on that exactly exactly and uh you know just uh a quick thing on this you know the benefits of demo obviously if you see here uh you know bridging data silos um that's one business benefit that

73. 35:33

    we're delivering and um you know like cody mentioned there's a there's a range right so within an enterprise you could deploy your smart contracts on a database per se and the solution that has a load you know high trust requirement or a low trust you know condition between the two different entities can be deployed on the blockchain and the key is that both of those networks interoperate with each other in this case we obviously chose to you know bart chose this method but a

74. 36:04

    combination of this option one and option two is obviously possible and the important thing is that your demo application um written once will work on any of these uh of these underlying persistence layers um so you so the way you write your your demo applications and your demo contracts does not have to take into account the way that the the underlying persistence layer is structured uh and or operates

75. 36:28

    yeah okay so since i cannot see the q a i'm just going to go off full screen one more time okay and i think we can address a couple of other questions maybe down the line because they might be addressed already uh okay so this question i think from rohit um you know innocent from a centralized app configuration and this question is for bart actually uh you know what is the how would you if if you want to migrate

76. 37:00

    to a dlt if need be in the future is it possible or maybe that question is for us actually uh corey so yeah so yes you can um the application uh will work um if you deploy it um to a dlt now if you want to move the um the historical record of all transactions that have taken place um that is a more complex operation it's doable um but it's complicated um and so we have application portability um out of the box that's very simple um you don't have to adapt your application um to move it from a centralized

77. 37:40

    structure to a dlt structure and in fact a lot of our clients will start off with a with an mvp that runs on a stack that their id departments know how to do devops for so that might be something like a postgres database before they move to a newer infrastructure like a dlt moving historical data is is is not an automatic operation and so it does require um some lift there um to to take past records uh and port them over to to a to a new database structure

78. 38:12

    distributed or otherwise yeah and uh obviously i think i see a couple more questions from indira who's a little bit more complex and i'll we'll probably follow up with you offline via email and we can address those um there's just one more question around does damol connect the interoperability layer does that work between different dlts between code and bezu and the answer is

79. 38:35

    yes it does so if you've got a demo application running on a coder network and a demo application running on a fabric network you could absolutely atomically transact across the two networks um so let me go back to full screen and now let's get into the get into the high-level architecture of the solution uh but do you want to uh outline that yeah so created this kind of one slide uh covering all of the major components of of the prototype right so uh participants you will see in the

80. 39:07

    solution are citizens you know people like you and me that want to have a test done or getting vaccine you know obviously the healthcare providers labs are are very important in providing the tests and the solutions and then getting all that information over to a state agency if you look at it from state agencies they already have all of our records anyway they know who are yeah the citizens of their states

81. 39:31

    and then most likely will work with some kind of technical operator so you will see kind of in the solution kind of the operator helping do the administrative part and then of course it can be all linked directly to insurance companies um from uh from a business logic everything that you will see in the solution has been coded in smart contracts using demo uh and you know again it was a

82. 39:57

    decision to get uh kind of the benefits of you know what we all know from a blockchain perspective uh are kind of the key advantages uh but also gave me a very rapid implementation tool uh using some of the apis that are available some of the um and and hiding a lot of the complexity right so if you want to build a solution you want to focus on the business language and not necessarily about kind of all the cryptographically security aspects um and and then included kind of the second set of uh

83. 40:30

    technology from intrinsic uh mobile app uh that i will show case here uh and the underlying technology stack that is supported by intrinsic so based on hyper ledger errors from a communication perspective and then anchoring some of the information into the the sovereign network again none of this information that i will show in in the from from a business perspective end up in a sovereign network it's only the schema it's some of the digital identifiers of the major

84. 41:08

    participants in the network but no transactional data goes into the sovereign network and then from an infrastructure perspective it's deployed on project dabble which allows for quick deployment and and experimentation uh provided by the team from digital asset but you know if you want to port this to amazon amazon quant of ledger database or centralized ledger or any of the other platforms uh

85. 41:34

    there's there's quick tools there's open source uh um components or uh solutions like uh the the distribut uh from the team from uh blocked the blockchain um the team from uh blockchain ledger uh with their sextant platform and so um a lot of options are available there so maybe going to the next slide yeah and but i think we're running out of time also so we're going to get into the demo yeah so

86. 42:04

    i'll just quickly introduce so a network operator will onboard citizens health clinics and state agencies uh once that citizens is on board and accepted they will create a request to the health clinic to get an appointment um test will be done and you will see the interaction between the citizen and health clinic and using then that verb mobile experience uh and the verifiable production credentials going back and forth so

87. 42:33

    that's kind of the the the core of the prototype here so if you allow me to um share my screen yes i'm stopping so then we will kind of take a quick look at screen one all right and hide this so going into uh project dabble i'm gonna log in as the operator and i have deployed one single contract at the initial stage so here see the smart contract reference number the ledger party operator and allows me the operator to set up the party so i'm going to set up

88. 43:26

    alice uh as a citizen and that's now stored into the ledger i'm going to set up a healthcare provider nevant is my healthcare provider here in north carolina so setting up that party and so now these are parties uh on the blog on kind of the ledger uh for uh for using demo so you can also put state agency already deployed to the north carolina state agency so i'm not going to duplicate that and so we're going to log off and log in with alice

89. 44:07

    uh and uh in the interest of time i've i've disabled uh secure authentication but this can be uh um accomplished by using jwt tokens um and so now we see that uh that contract that invite from the operator has been uh assigned to uh alice uh she's gonna accept the invitation we're gonna do a quick uh registration here um it could be very traditional but i decided to implement dids as well and just going to put some dummy information here in the interest of time and

90. 44:44

    get the registration done also given the options right what is your preferred communication pro protocol you know do you still want to get your information over email or a phone call but i'm selecting verifiable credentials and then linking that to the insurance so at this point in time the limited information uh is identified and what i'm going to do now is create a connection and ask for a created connection for the

91. 45:15

    verifiable credentials and i'm going to switch over my screen to uh my iphone before i click the button here so let me share new share and i'm going to go to my iphone and getting quickly onto the network here screen mirroring uh and so now you see here uh my my uh my cell phone uh and i'm gonna just open up um the the um uh the trinsic app so a mobile app on the iphone could be android and you probably cannot see but i'm

92. 46:03

    going to create a connection and that's going to create as a scan code so if i now share my screen and it already captured it and basically kind of makes the invitation to connect from the app to my mobile phone and i'm going to accept it uh and a connection has been created so uh let's go back to the workflow here uh and i'm gonna go back to my screen um and uh i'm going to do a test request since i've you know

93. 46:43

    asked for a connection for doing a test i now select my provider my health care provider and i'm alice i'm doing a request that now creates a new smart contracts in demo and allows me to now log in as a healthcare provider so healthcare provider login login page and now we see alice has requested an connection to their healthcare provider and they're basically are going to um you know uh healthcare provider is going to set up

94. 47:28

    uh that test appointment so we're going to do it for today which is the second i'm going to create a test appointment date um we also can do vaccine appointment dates but uh let's just stick to kova testing here new contract smart contract was created between alice and nov novant uh with the appointment date and now the healthcare provider can do the test so let's do the test information here and put in some basic information the

95. 48:01

    test type was a kova test test number it was negative and we're doing this for the state of north carolina and before i click test i'm going to now switch back to my iphone and share the experience for uh what's happening on my on my wallet and let's see if i still need to you know i have to connect again uh here on screen mirroring now do it again okay and so i'm back into the trinsic

96. 48:46

    app and um going to kind of click the button now for conducting the test and that should trigger here now my first verifiable credential right so you received a credential offer from rethink ledgers and if we look at the information then you see it coming from novant for alice with the state of north carolina uh test number test results and so on and so here now i can click accept

97. 49:24

    and my verifiable credential is uh submitted to my mobile phone as a as as a digital experience of what my test results are so we can do the same thing kind of for about vaccines um i'll skip this workflow but i'll show you one more kind of view on this and that is on the state side so if i log in now as nc nc health the state department for north carolina and sea health and then uh we can see that uh the

98. 50:04

    health agency we can see your screenbar okay all right share my screen again it's going back and forth indeed so i i uh logged in as nc health and now we see that contract between alice um and and um and novant was created with the test results of negative i did one more uh test uh earlier this morning so they can basically see around all of their citizens and all of their health

99. 50:33

    clinics on what uh what what is going on with the testing and from here they can supply their own verifiable credentials though so they can provide uh in the future if there's a concept like immunity proof they could provide as a state agency uh a solution um on their own and saying now is the state of north carolina uh i'll provide you with an immunity proof uh that comes from uh nc the north carolina state agency

100. 51:05

     and again center credentials and that would uh trigger another verifiable credential going directly to the mobile app uh and so if i share this for the last time here on my iphone then screen mirroring right so you received an immunity vc and that was authorized uh by the uh north carolina state health agency for alice on today's today's date and so i can accept that again and then we can look at kind of these um these uh different credentials on the phone uh

101. 51:59

     here as well um embedded and from there on the workflow can be further enhanced too then start sharing it it could be a use case of the airline industry it could be a use case where you want to take a trip and go visit one of the islands in the caribbean and they want to have information about the testing you took and the information uh that was provided you from a state agency perspective so so that's kind of the the prototype um you know obviously uh can be extended a

102. 52:32

     lot further but it uses kind of the two main technology that we're talking about here in this in this webinar demo for building all of the business logic between those different parties and and allowing it to be a secure smart contract platform that can be deployed on any type of ledger uh and then using intrinsic as uh the mechanism to issue verifiable credentials storing them on a mobile phone and then kind of taking it to the next stage over here or

103. 53:06

     sharing it with other interested party that allowed uh to look at that type of information and that you as a as a citizen are in control of so a very different workflow than kind of the current situation where a lot of healthcare providers have their own digital platform their own website uh their own data store and you know having kind of the difficulty situation of you know how

104. 53:30

     do i share that information outside and you know obviously the whole regulatory impact is is is quite important here like hipaa so let me take a stop here and see if there's any other questions uh manish that you think are uh we can we can cover here over the last couple of minutes of this webinar yeah there's a question uh from unchecked says in the demo alice alice's mobile app only connected with rethink ledger agent so how does north carolina agency and

105. 54:00

     novant were able to issue credentials to alice yeah um so in in in this particular uh use case um you know they're making the connection between novant now alice makes the connection between uh themselves and novant uh and at the same time the state agency since they've selected those two options uh those connections are created uh and then uh through the intrinsic platform uh the operator you know that's that's uh basically sitting behind is is uh

106. 54:37

     issuing those credentials now you can further enhance this to make this kind of uh individual connections uh between uh alice and a lot of different uh healthcare systems uh it could be then further enhanced to making connections between north carolina health agency and other state agencies and that will require kind of different connections that need to be established at the very beginning of this that are showcased in this workflow

107. 55:08

     yeah perfect perfect so i think we're almost out of time i'll just um try to recap here a little bit so uh one of the you know key things that uh key takeaways is that you know hopefully you saw that using smart contracts is a way to bridge data islands both within and outside the enterprises so even though we are used to using smart contracts in a traditional blockchain setting

108. 55:32

     think about you know multiple pop-up clinics and uh you know various uh departments within a company that need to share information and have so many data silos you could easily bridge them using tamil and then cross the next hurdle of how to interact on a blockchain over multiple you know between multiple organizations at a later point in time so that's one the second is obviously this provides a great customer experience as well as privacy

109. 55:55

     um finally i think this demo was hosted on project devil which is a managed cloud provided by digital asset uh you know provide security and all of those things um you could also look at a platform called sextant by blockchain technology partners blockchaintp.com uh that's also a very nice managed platform where you could deploy such a network on sawtooth and aws aurora iwsqltv

110. 56:20

     uh you know and as well as bezu so uh you know that's another platform i'll send some of those uh links over in a follow-up email when i send out the recording and um obviously you can get damal at docs.damo.com uh you can learn about forensic at uh intrinsic.id i'll send some more information of course after the webinar and then of course you can contact bart at artylages.com there's also a

111. 56:45

     wonderful video that bart created um you know you can obviously look at this webinar but there's another more detailed youtube video and this link is here but i'll obviously send it out in the follow-up email finally uh you know diagnostic testing is obviously a great segue into a supply chain conversation uh so as you see demand as you see where the testing rates are positive you know where you need more supplies uh you can make the entire supply chain

112. 57:10

     more responsive and that was the subject of a webinar we did a couple of months ago with a company called innovae they had developed a nice ppe supply chain solution um so i'll include a link to that as well in the in the follow up so with that i think any last thoughts uh about uh riley and corey before we and of course uh sorry i wanted to mention there were several questions that remained

113. 57:33

     unanswered uh live but uh we are going to get back to you corey and i will and bart will get together and we'll uh we'll uh you know send out those send out the responses to everybody on the list shortly yeah manisha i just want to just add one more plug here at the end just uh we talked a lot about what this can do for business processes and healthcare institutions but i think that

114. 57:58

     the impact that this will have on individual people's lives or the potential that it will have for individual people and their ability to access services securely and um and easily uh is really um you know can't be overstated and i'm really excited to you know see this technology uh both from the demo side and the verifiable credential side of the evolving perfect yeah i want to encourage everyone this is corey if you're interested in demo applications for for healthcare or other

115. 58:29

     industries please don't hesitate to reach out to us we're happy to explore opportunities and ideas that you might have by building solutions and demo perfect all right uh thank you very much for uh for spending your time uh today with us and hopefully you found the webinar informative obviously if you have any questions definitely reach out i'll include our contact details as well in the follow-up that i send out

116. 58:53

     um and uh thank you very much thanks everybody thank you