 All right. Good afternoon, everyone. I'm sorry about the technical glitch that we just experienced. So my name is Chaturavidyan again. I'm happy to present you with one of the well-received custom web application that we developed back in 2020 when COVID-19 was a big thing. So before moving into the demonstration, let me show you some two stories. So the first story is, so John tested positive for COVID-19, not our John, someone else. And John was in contact with Bob and Morton H in the daytime. And Morton H had to be with Morton S in the evening. Morton H bought some groceries on the way home. And it was the cashier of the store. So that's the first story. And the second story, Leo tested positive for COVID-19. Leo met Lars in the daytime. Lars bought some groceries on the way home. And it was the cashier of the store. So imagine having hundreds of these kind of stories per day, which involves hundreds or thousands of people, maybe per story. And this was one of the biggest problems governments had back in 2020 when tracing COVID-19 cases and their contacts. So they can effectively quarantine the possible COVID-19 contacts of cases. So this is when governments decided that we can't do this on paper. So we might need some digital solution for that. So naturally, they kind of turns into his and ask for a digital solution for this one. So then the DHS to implement us, they analyze these kind of stories. And they realize that, OK, this can be easily solved with the tracker program. So we can define two programs, where one would capture the COVID-19 cases. And then another program where it would capture the COVID-19 contacts. And then we can create relationships between contacts and cases. So that effectively created a digital solution for tracking the cases and the contacts. So this is something that has been done during that time. And I have an example tracker capture program, which kind of meaning the same thing. So I have pre-registered my COVID-19 case, which is John in this case. And then I have another program. So I have basically two programs here, case-based surveillance and then contact registration and follow. So under the case program, I have John registered. And under the contact registration, I have everyone else registered here, Nick Modnich, Modnich, and Bob. And I haven't done the two people from the next story. So I will go ahead and register them to show you how we would have done that. So then here I have a new COVID-19 case with Leo. So I will just switch to the case-based surveillance and do a registration. For the local case ID, I will just use the name because it's easy. And first name, last name, I will just use Leo. And I can continue. And then I have another person who is a contact. And his name is Lars. So I will go back and register Lars and save it. And now I have all the people that needs to be registered. So I mean, this might be done in massive scale when we are practicing in an actual environment. So now, based on the second story, Lars has a contact with Leo. So I can simply add a relationship here. And Leo is the case. So I will just search for Leo. And I can add Leo as a relationship for Lars. And then it also says that Lars has been in contact with Nick. So then I can add another relationship. And in this case, Nick's contact is not a case yet. So I will search in the contact registration and follow-up program. Nick, and I can add him as well. So now, we have all the data required on DHI's group. But does it really solve the problem? I mean, it's in a tabular form. And we have everyone in the database. And all the relationships are created. But still, we can't figure it out that Nick is in the both traces. I mean, he might be in more risk than others. So we can't come into conclusions like that by just looking at tabular data. So that's when we decided that we need more visualizations that effectively visualize these kind of data, especially the relationships, in a graphical manner. So that's when we developed this application called relationship tracing. So this can be used for any kind of relationship tracing use case, not just for COVID-19 contact tracing. So with this application, we can save multiple visualizations. So for instance, I can go ahead and create a new visualization here. So I will just name it as new visualization. And the relationship that I would like to track here is the COVID-19 contacts and cases. So I can select that one. And then after the third step, I get the ability to create or add new track identity templates. So where I can essentially define the graph nodes. So I will go ahead and create the track identity template for cases here. So the template name would be case. And I can select the color for my graph node. And the program from where this track identity instance would come is COVID-19 case based surveillance. And then I can optionally add the node label to this graph. So I will just use first name because it's easy to track. And then I have the graph node for the cases. And then I will add the graph node for the contacts. And then the program is going to be the COVID-19 contract registration and follow-up. And I will add the node label here, which is going to be the first name again. And finally, at the fourth step, I can define the edges of the graph. And from will be from, I mean, the template from will be the case. And template for to will be the contacts. And then I can do more fine tunings here. I can hide the instances with no relationships. And also I can opt into have bi-directional arrows. I mean, that's your preference. And then I can simply say my visualization. And once we are behind the visualization dashboard, we get the ability to select the enrollment start date and enrollment end date. This is important because there can be thousands of cases. So we can shoot limit the number of nodes that we will be displaying on the dashboard so it is more manageable. So by default, it's going to select one month range here. So I'm going to go ahead and click Update. And now we can see that it visualizes all the contacts and traces in a more presentable manner and in a more traceable manner. And we also get the options to click on one of the contact or trace, contact or case, and view more information like date of birth and several other track identity attributes. And also we provide the ability to open this profile on track capture. So we can do other edits. So back in Sri Lanka, addition to these capabilities, we even had the capability to trace by mobile number. So as you know, mobile operators can track your location not precisely up to 20 meters security. So government provided us with data from mobile operators so that we can trace people based on the mobile number. So if you register the track identity instances with mobile number included as a track identity attribute, we could simply do a search and find all the locations that he or she has visited during the past couple of weeks. Yeah, so that's about the contact tracing application or the relationship tracing application. Any questions? No questions. Thanks. I'll just one question. Pick up one. Thanks for a very nice app. I just want to say, usually don't pick up the groceries. That's my wife. We can change that for the next presentation. Nobody is very nice. And I'm just curious, one thing is visualizing these things on a graph like it just did there. But when you have all this information in terms of relationships and so on, are you able to create something more actionable for contract tracers? Like could you produce a list that they could print out and when they're supposed to call people? Or could you take this further and help contract tracers more beyond just showing them a visual like that? Did you get into that kind of activities as well? Yeah, for the app that we use in Sri Lanka, we had that feature. So we can select one of the case or a contact and trace up to, let's say, we want to trace up to five levels now. So that capability was there. But we had to rely on the web API for doing that. But possibly we could improve those things by running graph algorithms directly on the database itself. I'm sure that we can write these BFS or DFS directly on using postgres functions. So those kind of possibilities were there, but we did not go into that level. We just relied on the REST API for doing that kind of crisis. Any questions? Someone just said, nice. Thank you. Good. So last presentation, then we all can go for swimming. Let me quickly just show. OK, so just a bit of background. So this app, what I'm going to try to present is about cause of death with the doublet, including the ICD-11. You can all hear me, right? So the concept behind was like the doublet had created the repository where people can actually search the ICD-11 from an API standpoint view, and then they can select it up. And in DHS2, there were many countries where they were developing their own custom form and all the things for the cause of death module, where you have frame A, frame B, where you have to select all the cause, and then click on underlining cause of things. And then you have to create a dashboard and all the things. We also have a metadata package for MCCOD, Medical Certificate of Cause of Death. And in multiple countries, they were making it at different level. One were using custom app, one were using custom forms. So then we can say, how best we can try to help countries to solve this problem? So what we tried to do in collaboration with WHQ, that is Vietnam built a generic cause of death app, which can be installed in any DHS2 system. And then you can try to do all the data entry analysis and all the things, and also export easily. So you don't really require a programmer or anything for you can try to reset all these things up. So first thing what I'll try to demonstrate to you is already installed application, and then I can go around how people can actually configure this one up. I'm not going to go into much details of all the things, but just show few key variables and all. So this is cause of death app in DHS2. We just installed. Like you go to the app hub and download and install cause of death app. That's basically it. And after you configure all the things up, I'll just go for data entry for now. So I'm in this one particular facilities. This is a custom app. This is based on tracker. There was lots of argument why you have a choose tracker because you also want to enable the sharing between cause of death and CRV system so that they can get the death certificate, but the Ministry of Health can actually give the medical certificate so it can be used together. In the data entry app, so you just do the registration, there are two things. So people don't really have to know DHS2 tracker, like enrollment, incident date, and all kind of things. So here is just like data of reported and data of death. This is a system ID which is automatically generated based on people who have configured it, give us name, last name, mail, and things. And then this is frame A, frame B, which is very specified. WH also say like you never change frame A. So these are all the different options what you have. We implement this system in multiple countries. Bhutan was the one of things and Maldives was trying to start. In this one, so when I click on each cell, so this ICD coding tool is in somewhere else. It's not in your server. It is going and talking to the WHO hosted ICD coding services where now if I want to select, I'm not a ICD 11 coder. I just know heart attack, shark attack or heart attack. So heart attack. So then it gives you the stuff, all the details. And people can actually check what all the different things are. So you can just select one of the things based on it. And then say. So then you can get most of the things on here. Then based on the ICD coding, we actually categorize the things in the chapter, the grouping, or other visualization purposes. If this is since it's a child and male, so you have less options. If it is a female, then you'll get the different options. And then if it's a greater than some age, you'll get also the maternal deaths and the other things in here. So I'm not going to go more into details. And this is also the medical certificate. It's again customizable where people can actually just choose which field to be showed, what are the different things. They can include the logo by themselves. And if people want to have their own particular format, they can try to include that one. After doing the data entry, the whole purpose of this app was everything should be in the same app. Data entry, an account export, where people want to analyze the data locally, dashboards, and also the translation, all the things. So it's all combined into one particular place. So in the Adversition app, once they have installed, they want to also change the certificate. Like you just say, you want to change the logo, or you want to do all the things that you can try to deal with it. If you want to add additional fields in your item, that can also be possible. Now I'm going to the dashboard. So this is a dashboard which is customizable, which is based on you have to run the analytics to get to all this dashboard. But it's not using program indicator. We are actually using the analytics, API analytics, to get all this information so that people, if they delete the program indicators in the management section, this won't affect. So you have mortality by cause. You can just select, OK, I don't want to use the TB. So then you can try to deal with all the different things. So if you want to include more fields, so then you can get all. And based on this, all the requirement was given to us by WHSQ, and I want to include all these fields in here. And then the things we'll get, I don't know, as it goes wrong. These data are the dummy data. We just entered just to show this graph and charts, mortality by noncommunicable diseases, mortality by frequent cause of death, by ICD that chapters. So all these things are in here. Again, TB, malaria, and all the things. And all the age breakups and all the things is based on the people who have done the data entry. Quickly, the translation. There are multiple types of translations. So first thing is on the data element side that we already know, each and every data element can be translated into many languages. This is for the app screen itself. Like in DHS2, we have two things, right? One is app, what you see on the screen, and then one is on the database side. Database side has already been handled. These are all the apps that want. So these are all the variables. So English, and if you don't have your language, so you can select your language from here. So we have listed all different kind of versions of the language. So sorry? Yep. That was the first one, I guess. So different type of Arabic. So you have all the things. So just say let's take Arabic app, and then you do your translation by yourself. This is only done by for the people who have the admin control, or that's a bit super user who can try to deal with it. Once you're saved, so then all your modules are there. That includes, and I've got export, what we just see in the screen, the dashboard items, like in the installation attribute. These are all the key fields, which we have incurred. So then you can add your own language and translate these keys into your language. Sometimes we are also managing to give few key translation. But then they say, no, no, this translation is wrong. Like we did it in Cambodia. Like one person entered the data. No, no, this is not really OK. This is something else. So then you want to change. You can also change it. So those are all the different fields. And these are all the buttons and icons, what you see. So all those things can be translated, like new registration search. So it's up to what you want to try to deal with it. And then people who know about Anacord, like these are the things where you want to try to export a particular data. This will take a bit more time, because we import a lot of data for all different kind of variables. So this will basically disaggregate the data by ICD code and the age and gender breakup, which can be downloaded into an Excel. And then using the Anacord options, you can try to deal with it, all the fields. That's basically the Anacord format, where in the top line you have this age breakup. And in the column or in the row is the ICD code for the whole country, and basically like this one. So this is the code, and it's the sex, and then all and the age breakup. This is the Anacord format, which you want to download and use it for your Anacord analysis. No, no, no, but this is exact for Anacord, because Anacord is, they have this particular format, and it has to be exactly like this one. We cannot change anything. This was, but you can also export the data into other place. You can also use all these things in your event report, online listing app, and all the things. It's still there. You just want to combine these features inside of the app so that end user don't have to go to other place to deal with many other things. Quickly, I just want to show you before the time's run out. Sorry? Yes, yes, I'll show you. I'll show you. Let me just stop present and present again. Just give me one second. So if you can just see, this one is the installation process. Too small, make it a bit bigger. Is it OK? So here, what it happens, when you first time install, you have a basic installation, which includes everything, default installation. You don't have to customize anything. But we always just say, don't do that one. Do the custom installation for a few reasons. The first thing is, the first time, you have to set up the, sorry, but the first thing is you have to set up the various ICD code, the tooling ICD code tool is loaded. This is the global platform, which is basically the ICT.wcho.int. That's the ICD coding tool where it is located. But if you have used ICD code in your own Docker or the server, then you just give the URL for that particular places. This is the Docker level installation. So when you click on, it will give you all the different details. After you select that one, then you can just choose whether you want custom or default. Just like going for the custom one. So when you click on custom, what happens is, you can just select. In your DHS2, you already have Tractor Program, where you already have first name, last name defined. You already have your gender and the age defined. So we don't want, when we install, this to be replicated. Because I've seen in many places, you have age for HIV, age for TB, gender for HIV. I said, no, you have to use the same attribute for all the programs. Just don't create multiple attributes. There's the same principle around here. So you select, you choose what is that field is, whether maybe it's called first name instead of last name. It's the family name or anything. So you can choose that one, date of birth, age, and all the things. And then you can add your additional field. For example, in Bhutan and other places, they want to include investigator name and all different kind of things. So then you can add your own additional field in your custom form or in your patient attribute. And then the next section is the Form A, which cannot be changed, but you can add additional data element. For example, where this person is there, the entire details of the investigator, the address, the phone number, where it was done. So you can add additional data element, but you cannot remove any of this data element. So that has been one of the things. In some places, they are allowed to, this is in frame B. In frame B, you have this surgery, manner of death, the infant deaths and maternal death, which are optional. But now they're saying it's not optional. Everyone should need to include all these things. But you are free to add additional options like double H or MCH or any other fields that you want to include in your data elements. You are free to add all those things. And then as you create a DHSU tracker program, you need to assign that one to where, whether it is only the hospitals or only in your provincial hospitals, the central level hospital, you choose where the medical costs of death coders are located. And other feature, other thing which is missing is, in many of the installation, is the groups who can actually change, who can view, who can do the data entry. And these are always, some time has been missed in most of things. So that's why like we haven't created this one, you have to select which are the user belong to admin group, which are the user are on the capture group and which are the user on view group. Once you have done all these things, then like you just like install, it will install all the different components into your local DHSU. And that's when you get the screen or the demo which I showed you as an app. The first time when you install, it will be blank, it will automatically take you on there. So then you have to choose, if it is a custom, if it's a default installation, then that means in your DHSU, there is no tracker program. So in your DHSU, if there is a tracker program, I always suggest don't go for default installation because you have to create all these different fields. That's basically it, presentation from me. Exact file, so any questions? Sorry? Okay, so that's in the installation round here. Let me quickly go around, okay. I can show it to you because it's not here yet or like in the online, because online we already put it up. Like here we have an add button when we're selection. So when you click, either you can select, like what you're seeing around here in this particular area is list of all the attributes what you have in your own DHSU. So you can select this one or if you just say, oh, I don't have this attribute, I want to add attribute. When you click on this add button, the app will take directly to the attribute section or data element section. So if the data element is already there, you can select it. But if the data element is not there, then you can click on add, it will take you to data element add manage the app. There you can add it up. Yes. Like for example, round here, this one is in frame A. So you can add additional section, but you cannot change the cost of that A or these sections. But you can add like say, the malaria section into here. This is a wrong things. You don't add malaria section to cost of that, but like anything, okay? And then when you click on add, it will give you the option to select your data element, which you want to add, which you want to add into the WSCOD module. So here there is no need of programmer or in things, it's just like one person who understands the cost of that. So that person can actually include all the things. Yes. One quick second. I will share this presentation and it's an online system. Stop presenting, just one second. Sharing. No, like I'll do this one. I'll also share this one in the Google chat and as well as the in the email. Let's give you one second. So if you just go for this place with the link, which I said BHS2.world slash WSCOD. So that will give you, the username password is just there. So you can just like type the username password, COD, let's go demo, and demo at one, two, three, four. So there is a resources round here, which is a basically word document, which describes the list of all the different things, which you can download. Yes, and also you can select the cost of that app and play around. The verbal autopsy, or you could talk about verbal autopsy, right? The verbal autopsy is not, because like that's not dealing with, the only main thing what we are working right now is with medical certificate of cost of that, which is linked with ICD-11. That was the whole functionality. But the WHO HQ people are actually thinking around how best we can try to use the same approach for verbal autopsy and also for the mobility. And for other area. But this app was only focusing on to help the coders to enter these details into DHIS2 and how best they can try to simplify installation procedure and analytics and then the export process. John, can you hear me? This is Nenath. Yeah, hi Nenath. Hi, just I'm not sure whether I picked up the question, but if the question was related to Iris, I just wanted to add. So this is Nenath Kostancek from WHO classification terminologies team. So we have been collaborating with John in the development of this. That as part of the new release of the API for ICD-11 in the next year, we envisaged to include also a new tool, which we call DORIS, for automated selection of underlying course. And we are exploring with John and team to have this also embedded in the workflow of the app. So at the moment when you look at the workflow, as John demonstrated, the underlying cause of death assignment would be manual in accordance with the form. And the new tool which we are developing is basically a digitalization of the ICD-11 mortality coding rules so that you can consider using this tool for making, for automated selection of the underlying cause. And of course there would be different modalities individually, certificate by certificate. But I think the main option for deployment would be a kind of batch processing option where you run a bunch of coded certificates through the app, which will be part of the API release. Similar to what John has demonstrated with the Anacode 3, which is the tool for analyzing ICD-11 or ICD coded data for that effect. So that will be an additional feature. We are also working on electronic, WHO electronic death certificate, which includes some of these plausibility checks which John already has implemented in the app so that because we can leverage their number of new features which were not there before. So at the moment this is basically the electronic version of the paper, WHO paper-based death certificate, but we will have release of the electronic death certificate and also embedded here, which will leverage a number of these plausibility checks and other features which we can do now. Over, thank you. Is that okay? Any more questions? Good, Nenath. Thanks, thanks a lot. Thank you. Just Nenath, if you can say it wrong. Sure. There's one more question from the participants. Hi, thank you. About the Doris, we already saw the Anacort-3 import of the ICD-11, the Bluetooth app, and that's actually really a very good work. But the transition, if the earlier we have the process of death in ICD-10, whether that is possible to convert it into ICD-11 because in country, in Bangladesh, I am from Bangladesh, so there is ICD-10 and SOML both is in the system. So theoretically, this can be convertible, but whether it is technically viable option or not. Yeah, I think in order to ensure comparability of data sets, obviously, as you indicated, it will be important to have a crosswalk. So usually our recommendation there is to make use of the mappings we already provide on the ICD-11 website. If you can, I can post the link. I don't see the chat, but I will share it with John so that it can be distributed. So what we basically recommend countries or users to use is any kind of mapping should be done based on the maps which we already provide. However, these maps are quite detailed. So you will see that we are mapping there the 14,000 ICD-10 codes to the 17,000 statistical codes. You have an ICD-11, but ICD-11, as you have seen, has much more granularity. So the kind of entities, so it's not only a classification, it's also terminology. So the clinician will find all the detail there, the entities are actually running up to 130,000 if you include synonyms and clinical terms which are not codable entities, but they are sitting under the respective codable entities which are used for statistical reporting. So the map will provide you these crosswalks between ICD-10 and ICD-11. However, it is very important that before you start any kind of mapping work to really be clear for what purpose you do use the map and maybe you should also consider running some kind of frequency analysis on the actual used codes in your dataset vis-à-vis ICD-10 so that you don't do mapping or crosswalk based on our maps for the full scope but really for those whatever, 1,000 or 2,000 codes which really matter and which explain whatever 90% or 95% of the cases in the particular country if you look at it from a mortality perspective or from a morbidity perspective. So specifying the use case and doing a kind of frequency analysis before you start the mapping using the generics maps we provide on the website would be our recommendation. I hope that clarifies over. Yeah, that's okay. Thanks. Thanks, Danab. Thanks, participants. It's all okay. So it's a whole long day today. So take some rest. So we'll see you tomorrow. Oh, tonight for the dinner. Yes, there is a gala dinner and then after the gala dinner for the session is tomorrow morning 9 o'clock. Okay. Thanks. Thanks a lot.