 All right, so welcome back. We're gonna start the second session of the day one. We're gonna be discussing about the metadata. We are going to be used the whole week. And for this, we have our lovely colleague, Victoria, who's gonna be presenting because she's part of the WHO or packages team, et cetera. She can introduce us also, Victoria, floors yours. And then whenever you're done, I will be back here to take that's when you leave. Well, quick introduction. Hi, everyone, I'm Victoria. I work in the implementation team. And as Jaime said, we are like, especially in the package team, let's say, what we informally call it, which is like I'm on the many things. It's also responsible to put out the metadata packages based on the global guidelines that our counterparts and stakeholders release. So yeah, I'm not an IT person. I am more on the health content side of things, but yeah, happy to be here with you all. Okay, so you go directly there. So okay, so super quick introduction, just to get you acquainted a little bit on how these packages work a little bit. So what we normally do as a WHO collaborating center, we receive the global guidance that our counterparts in this case, the WHO of course, but could be UNICEF, could be CDC, could be other different organizations. It doesn't necessarily have to be WHO. And we get these guidance and we try to kind of translate them like you translate for French, Spanish and other languages. The text in the guidance needs to be somehow translated into metadata packages. So we try to turn them into logical data points that people can collect either in aggregate or tracker. And these feeds, it feeds into the national or local, depending on the implementation, HMI systems, that I mean, you might have seen it, if you're more acquainted with the HIS overall, there are like plenty of countries that are already using this data as too, as a national HMI system. And these packages that we put out are very flexible. We put out a baseline package, let's say, that reflects the global guidance that we receive. But these packages can be then expanded, changed and in general, modified to better mirror the local environments and the local necessities of the countries. Next please. So this is just a quick graph to make you understand how the life cycle of a package works for us. So once we receive the package, in this case, for example, it was because we are using the case surveillance for COVID, in this case, it was like the global surveillance for COVID that it was based on the guidance that was released in March 2020 back then. We received these requirements and then we start configuring things and we start getting feedback and testing from our counterparts. Of course, in this case, the WHO team, but also we start checking out with our HISP networks, with other countries that we know have had similar implementations. And once we start releasing and disseminating these packages, of course, it's a continuous development of packages. So we start checking in with the countries that have implemented it. We start checking in with our HISP counterparts and such. And we start learning from their implementations so we know how to guide other implementation better in some cases, but also to see what's working and what not in these packages so we can constantly try to improve them. Next. Yes. So just to give you also a quick overview of how we release our packages. Normally, you can find them in the website, in the link that you have down there, in the metadata package download. We normally put out always a design document and an installation guide for every package. And these design documents is normally kind of justifying the way the things have been configured. Like in this is why things look that way, what's the logic behind things and how people maybe some suggestions on how countries in general, like even private people that are doing implementation for their organization or project can change and adapt things to better mirror their context. Then in the largest majority, but it's a continuous development as well. Like we have also training materials so that you can have either training of trainers or you can just train people who are going to collect this information. So you can have a round implementation of thing. And then you have the metadata package that is based also on the different versions of the HHS that you can implement. We normally support by default three, the bus three versions, let's say. And then you have the references that it's like a flat file, let's say, where you can have just a general quick glance overview of all the metadata that you have in the package. So you can have a quick idea of how you might want to edit or expand or remove the metadata that comes with the core baseline packages. Next please. So as you see, we have put out for COVID, the COVID surveillance and the COVID vaccination tool kits. You see down there in the maps, it has been uptaken definitely widely and in a very short time. And the HHS has expanded a lot in the meantime. And yes, you see like the surveillance is using more than 40 countries, a vaccination toolkit as well. Like it has expanded a lot lately. And yes, it just can be used as a baseline upon which countries can develop their own either surveillance. So you can accelerate your case detection, you can report cases and such, but also the vaccination toolkit. So you can strengthen the immunization system, but also kind of like leverage the local expertise. So you can expand on the topic, let's say. And then finally, next please. Just to give you an overview of how the packages, the metadata packages for the COVID in general, since the economy is going to be based on surveillance, but just to give you an idea of how things are structured within the COVID-19 data, we have our surveillance branch where you have your integrated disease surveillance, the IDSR that it's aggregated. And then you have the case-based surveillance for COVID, the contact tracing. So you can just follow up the different cases that you are tracking. And of course, the point of entry. So you can have a surveillance of all the people that are coming in and out within a country, be it at the airport, be it like on-road, any kind of point of entry from a country. And then on the other branch, we have the vaccination where we have the logistic side of things. So we have a quick aggregate metadata package for stock. And then you have the vaccination. So you can either have the core vaccination for aggregate, is where you have just like a wrap-up of the core indicators for to like follow up your vaccination activities or it's still in French, but it's the AFI, so the adverse event surveillance, that it's a trucker. And then of course, you have the e-registry vaccination that is again a trucker that you can use to add their integrated AFI, but like in general to follow up the vaccination activities, we like longitudinal data on each of every patient. Next. And here just like a quick overview of what you can find by default in the COVID surveillance, that metadata package. So as I said, you have the point of entry. So you have the overview of the movements of people. You have the contact tracing. So you can just like check out who is touching what, when, how, and you can just like improve your general, yeah, let's say prevention and prevention and controlling like the activities of the infection. Then you have your surveillance module. So you can just like track longitudinally your patients from entry in the cohort up until the their outcome. And then together with that, you have by default always some predefined dashboards that are just like a guideline for you with some predefined graphs, tables that you can just use to adapt that your dashboards are at local level. And of course, with the default in dashboards, you also have like a lot of maps normally for at least the computer side of things that you can use to check better like the distribution, especially if you have like point of entry and contact tracing, you might want to see where these cases are. And but most importantly, when you are using the metadata packages as they are but even edited, you will have the possibility to then download other packages and use these packages to analyze your data but most importantly to triangulate your data to have a better follow-up of the situation but I have an integrated follow-up of the situation be it for COVID but could be for any other package could be HIV and TB, could be any other package. And so you can just like that see and better organize your activity depending on the general overview that you might get from this dashboard of the current situation in your country or in your project. So yeah, that was just like a very quick overview. We have plenty of links and source and resources where you can find the metadata packages. And yeah, I mean, I go back to Jaime but I'm like lagging here behind the scene. So if you have any questions specifically on metadata packages, please feel free to like write a comment or question in the chat and I'll try to answer. So thank you very much. Thank you, Victoria. Thank you very much. One second, I'm gonna put my camera. Yes. Okay, so Victoria has given you a very quick overview of what they do. In the past, we used to have, for this training we used to have malaria, the malaria package because it contained everything we wanted but since pandemic started like two years ago we decided that it was gonna be better idea to have something that we are more used to. And that's the reason we're using the COVID-19 digital package prepared by the Victoria and her team. And the reason we use this package because it contains everything we might need in the training and you will see how we use pretty much the package she explained and I will be showing you here but also sometimes we cannot use the single package and we have to use other things. So basically for the sake of this training what we can see that the COVID-19 DHS-2 is divided in this as Victoria quickly explained where we have basically one to track aggregate to count aggregate numbers then we have something related to events and then we have track. And if we go like this we will see that the main problem we are gonna be using during the training is the last one, case-based surveillance because it contains pretty much everything that we will need for this training. So in this tracker program you will be able or it's been prepared to be used with program rules. It's been used for, it can be used for relationships. It can use for geolocation of data, a visual entry, et cetera, et cetera. So at one point when we give you access to the server later today you will be able to tweak this program according to your needs or according to whatever we have to do and submit the exercises. We cannot do everything in this program. For example, this program is a tracker program and this academy even though it's mainly focused on tracker we want you to see also aggregate. And that's the reason we have here as you can see I don't know if you can see let me see if I can put my, this one. So you can see here we will be also using these for aggregate which we call support programs and then we have also contact tracing and you will see what. This note actually you can dismiss because we are actually using 100%. I was not sure we could do this but since the package release almost a year ago, I think of September I will maybe come from this later. At one point we had to make a little modification on the program so it could suit all our needs for the training but now we are following 100% the official model. So whatever you see or you find on the system is basically just the program import and you will be having one program for each of you where you can make all these modifications. Victoria is playing quickly but let me go very quickly again through this and because I will refer later to a document where you can find more information about this but basically we have this, the case-based surveillance where we enroll on track suspected cases. And most of you have already followed a tracker training either with us or somewhere else and you are used to set up the training. This was a requirement for this academy. So in this case, you will be making changes or this tracker program. And then we have these ones that I, well, this one I will not cover because you will see later on why we will be using it and then the aggregate. One of these sessions, which I think is happening tomorrow or not on Wednesday, you will be using aggregate and I said you cannot use it. So you will be using this. Victoria said we have a lot of documentation where you can find this much deeply or explain much for detail. So these slides are being, I already published so if you could go to the learning platform you can download the slides but also in the public agenda you will be able to access these links. It's not that we're linking here something that is not publicly available but in case you have issues finding these documents on our system you can go here and download them directly. So basically here we have the official documentation in these two links. And here we have added one thing we call the 1.2 metadata navigation file. This is a document that you can download. It's a Google document and basically it contains the information on this document but summarized and the idea is that you download it and whenever you are making or you are deciding which changes you want to make in your program in order to submit the exercises use this navigation file to mark things you want. For example, I will explain in the next session but at one point we will be asking you to set some attributes for this tracker program in a specific way. So if you want you can have this document you don't have to print it if you don't want but you can have on the screen of your computer laptop whatever and you can be there marking for example highlighted in yellow. So these are the ones that you're gonna be choosing et cetera et cetera. So navigation file here this is not something you can find on the official documentation but it's something that actually it's built out of this document. So you have it here and if I'm not mistaken yes you have it also on the agenda. So please download it because might be useful for following this training. So going a bit more into the details and trying to bring these packages from the extra concept developed by the WHO and then by Victoria the team if we see what are we doing with this program basically this is the case verse of variance workflow. And it's been taken out of this document that you have here. If you will click here you will see much further details everything like this but I want us to present this very quickly because we will go afterwards like in different, let's say little parts of these workflow steps and then we'll see how this has been transformed from the concepts to the HIS2 and we'll see where are we gonna be making changes so where are we gonna be registering patients and so basically this is for the workflow. I don't know if some of you have got COVID-19 it's you know what it is where is this is basically what happens is that a patient will be registered in order to determine if he or she is COVID positive some lab requests will be made where samples are taken via nose, via the mouth, etc. And then this contact is usually the contact first of all is registered, sorry then we go to the lab request and then we can feel it more information you can feel I think it's in case you're putting forward we can feel more information and at one point here we will see how we can relate and we will see later to different other contacts in case we want to follow, etc. We can check the outcome and then we can see more things. Don't worry this is gonna be explained later in much better details I think when you have access to the system probably you will understand much more if you have not played with these packets before. So if we have here so the first thing we're gonna do is when the patient arrives we are gonna enroll him or her in the system and this is some information we're gonna be collecting. This is basically based on the WUHO recommendations and these are the things we collect in the system and on the first exercise that you will be doing it's for example decide which ones you will be using. Again, we give you a package and this package is for you to play. We have based this package in the WUHO but then we are assuming that you want to treat the system according to your needs you can build it out of a simulation you can imagine whatever and for example you could say for me age cannot be important for example, so you will be able to play with this and actually we encourage you to play with this so you see how making changes in the system reflects in Android and can have specific behaviors that you might expect in web but you might not expect in Android and you will see this in the next two sessions. So basically we have the enrollment where we have defined so much which we want to collect from that patient and then we have different stages. If you have been working before with tracker programs or you have been setting tracker programs before that you should have because what's our request mandatory requisites to access this training you know that tracker programs have stages apart from the enrollment and some of those stages can be repeatable and if it would be in a live session I will be asking you to raise your hands if you can tell me why you think this is repeatable. So I'm gonna give you now three seconds or five or 10 to think. So we have these four stages. We have the first one clean clean examination exposures and then we have a stage two and three which are repeatable and then we have the health outcome. So I'm gonna give you now some seconds to try to think why would you think and maybe if you want you can reply on the chat that the stage two and the stage three are repeatable. What are your thoughts on that? Why do you think that these are states that should be or can be repeatable and it's not a normal state, it's not repeatable. Okay, yeah. That's very good. I cannot pronounce your name. I don't know if you have a short name for that but Murali Krishnayel Kurti, exactly. I think you are right. Yeah, you can call me Murali. Okay, that's better. Thanks, Murali. Yeah, so exactly. Well, samples might get going. Don't stress it, yes, but also it's a, I mean, a patient can get COVID several times. We might need to perform the lab several times because it didn't work, it got lost. It was not conclusive. We need to check, I don't know what is the procedure in your country where I'm based now with this Belgium. Sometimes we're supposed to take a test on the day three and then another one on the day 10, let's stress it out. So this is repeatable. And if you see here, what we have done in these slides, so if you see now here, what I'm doing is I'm taking kind of this workflow, presenting you here and this is something you can see in the document, this you can see in the document and then we have this, which this is an image, well, a graph that we have built. When we try to map, so here on the left side, you see the program, let's say, but we have tried to make like a legend on how is this map to our details to model. So for example, here in this blue, we have a program. So when we access the system, you will find the COVID-19 case versus less program, but you also have this other program. So this program inside of each program, we have one enrollment because we're tracking. So if it's a proper program, it has an enrollment. And then we have a stages. So you can see here in a bit darker blue. So we have the enrollment and we have these ones. We have some of these ones we have tried to represent here like repeatable because of the question I asked and most of you replied properly. So lab requests can be several repeatable stage, the same for the results. And then we have one outcome. Inside of each program stage or inside the enrollment, we have sections that contains data elements on the tracker to me. So when we perform the enrollment, I'm going now back two slides or three ahead. If we go back here, these are the attributes that we have. So these are the things that will be contained here for the stage one, I'm going back one stage. This is the things we have. So for example, the stage one, I'm going to read it quickly but basically clinical examination exposures. So in these stage, we will record clinical symptoms and exposures, which include this. So symptoms, what is the health status of the person, et cetera. We have this, this one and this one. I will not cover them all because I think you get the point kind of. So more links for this. So if you go here, you can find the full description and documentation, the official one that we have include also in the links before, but we also have linking the agenda. And we have made this 1.2 metadata file that we encourage you to download and have it next to you. So you can write down, maybe put on the Google. You can make comments or in words, whatever you use, library office, open office. So you can have a document where you see what are the changes you're making and later on you can see how this reflects the data note. And then we have also included here this YouTube playlist where these packages are being explained. I think this, yeah, 10 videos. If you have time or you want to understand much better why this or how to use these packages, it's a very good resource. So you can find it here, it will link to YouTube. And with that, we're almost concluding because this is the word of the day. It was explained on day zero and I'm going to repeat it now here. As you know, we are tracking the attendance and the attendance adds up to a 10% of your final score. And the way we track your attendance, it's by marking what we call the word of the day. This means that in the learning platform, at one point, I think on the left side, you have different sections and one of them will be the word of the day for today. So every day you will be presenting some slides and at one point doing those slides, you will be having what we call the word of the day. So today it's open source. So you need to remember these words and you need to, well, remember and write it on the form that it's available on the OpenEDX learning platform. It doesn't matter if you use capitals, non-capitals, whatever you can put open source with first capital, everything capital whatever. Once you submit it, if the word is correct, it will be added. So today is like, so it's 10% so it's a 2% if you put this word today. Open source. This word is available, I think up to 24 hours after the slides. Maybe I have to confirm this later, but basically this means that if you watch these videos on Thursday, when you try to put the word of the day for today, Monday, so day one of the Academy, it will not be working because it's overexpired. And the reason we do this is because we try to push you to follow the Academy more or less every day as we have planned. So we give you 24 hours since we released the videos or the sessions, like this, you don't have to do everything because we have found out that when you try to do everything, the end opens, sorry. Ah, yeah, sorry. Yes, thank you, Omar. So as I was saying, we try to push you to, we encourage you to do this every day, like this you are more likely to succeed at the end of the Academy. If you leave everything for the last day, probably you will have more difficulties. In any case, if you follow everything next week or on Thursday or Friday, well, you are just losing the 10% so don't worry so much. Okay, so someone is asking me what is the deal? I'm gonna stop the recording now because that's the end of the session. I will answer now some questions but this is gonna be out of here. So let me stop the recording.