 All right, so let me shift the screen. Okay, so as you know, every day, the first 10 minutes, we are gonna dedicate them to make a quick recap visualization of what we did the previous day and some re-martyrs, but I'm sure you are already bored of listening too, but we feel obliged. So if you remember correctly, yesterday we were working on configuring the server. We analyzed what is the metadata package we're using that we have adapted the COVID-19 model, so 20 nowadays. And we have prepared our device. So we can work on the exercises that we'll have today and tomorrow, on the day after tomorrow. So you have been asked to submit an exercise. We'll see later on some numbers on that. So let us remind you that we're gonna have question and answer sessions every day from nine to 10. Thank you all that came this morning. We usually have also in the afternoon at the last hour, so from one to two, but today's not happening because we will have the chance to listen to the Ghana Health Service, who will be talking about the implementation in the country. I think Kuame will be here. I need to, but yeah, it's gonna be at one if I'm correct, I'm gonna show the agenda now. And another reminder is please make sure you fill the attendance every day when you log in into the academy site. There is a check. I think you have to display attendance. Yes, please make so. Alice is gonna remind you every time she has a chance. It is really important. It counts for 10% of your grade. So please do that every day. Also some of you feel it in the form of feedback that is presented in the academy site every day. That is really valuable information for us. So please do that every day after the sessions. Feel free to add comments. It's anonymous, so we cannot see. If you need to tell us some bad things, it's okay. We really, really appreciate that. It makes us improve. And I think so far only one person has registered for the presentation on Friday. If you know on Friday from 10 to 1120, we are gonna have a space dedicated for you where you should present your implementation, your projects, what are you doing. And in case you wanna do this, please switch any of us and we'll make sure we allocate you a space there. Some statistics. So this was initially prepared to show the activity in the community, but in the end because we're using this lack, it's been really active. So thank you very much for that. And in terms of exercises, we have received out of the 83 people that attend yesterday, so they check in the Academy site, 42. So it's halfway. Please do not drag on them, try to do them when we finish the session or enjoy the hour we have in the morning for us to help you because we're gonna keep adding more and more exercises. And if you're not finishing the one before, I think you might struggle with the ones we'll be presenting today and then the ones from tomorrow. So do not hesitate to come to us during the sessions so we can help you finish the exercises. I don't know if there are some questions we're gonna be checking. I cannot check unfortunately the slack, but I'm sure the other facilitators are doing. So in case you have some questions, and if not, I'm gonna present the agenda we have for today. It's this one. So currently we're in the second row and now we're gonna have half an hour of program rules. Again, we're gonna be following the same instructor as yesterday, a bit of theory at the beginning, and then the exercise will give you probably not enough time for you to finish them, but you can enjoy the sessions afterwards or do them after doing the evening or in the afternoon, whenever you are. And then come back to us the next day. Again, session, a little break, session, a little break. Visual configurations will be the same. A bit of theory, exercise, a little break, visual data entry, an exercise, a break. And there you will see that we have 45 minutes where we will have a lot of facilitators. So what we're gonna do is we're gonna make a smaller rooms in Zoom, like 10 people, a bit less maybe, will be allocated in each room and we will have one facilitator in each room. So in this exercise, we're gonna be trying to give you support really one-on-one, simulated like if we're in a real academy, in real life, I mean, not digital, and we will be going to your table, asking your question, what's going on, what are the issues you're having with the exercises. So ideally, you should use that 45 minutes to complete all the exercises you have pending. And then we're gonna have the, the kind of health services present in their deployment, followed by the expert labs where Dominique or other colleagues will be taking your questions. Can I, sorry, Jaime, can I jump in here quickly? Absolutely. So hi everyone, just to let you know that as Jaime had said, gonna have service will do a presentation on the TB deployment in Ghana and the HIV deployment as well. So it will be a 30 minutes presentation. Then following this presentation from 130 to 230, they accepted to be the main facilitator of our experts lounge. So for those who have never tried the experts lounge, it's a very interesting session. It's basically a one-hour session where Oswald and Kwame from GHS will be available and there will be available, not only to answer your questions related to the presentation, but also if you are based in West Africa, Central Africa, and you want to get some tips from experts on your own implementation and your own projects, there will be available to reply to these questions. So what will happen is that we have a channel on Slack. I'm sure you already saw it. It's called experts lounge from Africa. And I invite each of you from now actually to already start asking questions there. So basically the team from Ghana Health Service will read the questions that you raised on the experts lounge for Africa and they will reply to them live on Zoom. So you are also invited to join this session from 1.30 to 2.30, but once again, any question you may have, we encourage you to ask them directly on Slack on the experts lounge for Africa channel. And also it's our great pleasure to let you know that the same format will be available for Asia continents. So if you are based in Asia and you want to have some tips, ask questions to experts based in Asia as well. Pamod Marakoun, who is one of the lead from Hisp Skilanka will be available on Friday morning, morning for us at least from 9 a.m. to 10 a.m. CET. But we will let you know once the Slack channel will be ready so that you will be able to start asking questions to Pamod before Friday. That's it. Thank you so much. And we're looking forward to see you during this experts lounge today. Thank you. Thank you, Alias. Thank you very much. Okay, thank you. Someone has just replied on Slack. I think it's Abdul. I'm sorry, I didn't have the chance. It was very quick. Okay. Marta, could you share the screen with the presentation? Just for me, it's a bit complicated with only one screen. I was about to ask you that on a private message. Yes, one second. Jaime, if you can say next slide when you want to see the next slide. I try to read your silence, but sometimes... Okay, okay. I'll do that. I'll do that. Okay, so thank you very much, everyone, for being here. I could I give a session on problem rules? So we're 67, I think it's a good number. So next slide please, Marta. So this session, it's gonna last 30 minutes. And as I was explaining, 15 minutes of really quick theory and 15 minutes of exercise. Where we will give you time, we'll explain the exercise and we expect you to do the exercise. If you have no time, no worries. You can always come back to the question and answer sessions. So by the end of the session, the participants should know what problem rules are, how to use them and how to set them up. Even though we consider that you already know about problem rules, we're gonna be giving a crash course because this academy is not focusing on this, but we want to make a quick refreshment. And then what we would like to stress is a bit the difference between the Android and the web version. So whenever you define or you design a DHS implementation, you will need to know that if you're targeting mobile, you should use one kind of problem rules. If you're using web, you should use another one. But there is a way in case you're gonna be using both to have problem rules that are compatible with both systems. And this is what we're gonna be trying to cover here really quickly. And we're gonna be adding references for you to check later, because unfortunately in 15 minutes, we cannot make a full course of problem rules. So next slide. Here, just to wake you up a little bit, I'm gonna give you 30 seconds to think in these two scenarios, what would you do? So wake your brain up and try to think what happens with the phone there and what happens with the traffic later. Okay, so in real, in a class, I would ask you and I would ask you to raise your hand and let me know what are you thinking, but it's not time. So I hope you thought a little bit about it. And what happens is that basically, next slide please. You are evaluating a situation and you're performing an action. So in the first, in the left side with the phone, you're saying, okay, my phone is running out of battery. So I'm gonna connect the charger. On the right side, you have seen a traffic light, which is red. Sorry if they're color blinds, but the upper one is red. So it means I have to stop. Evaluation and action. These are the key concepts that we need to think about when designing prone rules. Next. So this principle is implementing the HSUV or the prone rules. So we evaluate the current state of the data entry and we respond with a series of effects. Again, think always like what happens at this moment, what I want to produce the outcome and what happens, we can define by the input. So in the middle column here and the context, because the context can also affect the way I'm treating this evaluation before performing the action. So before I was talking about traffic lights, I was talking about devices, but now if we go to a real scenario, so a DHS to a real example, we could say for example, I would like to have a prone rule that calculates the score of the facility based on some checks. Imagine we have an entry form, we check things and I want at the end to get a score. This is a prone rule because we're evaluating something and we're performing an action. The same could be the second one that has maybe more sense for you. If the user that is entering data has selected mail, I want to hide the pregnancy status in the form. Doesn't make sense that I have the pregnancy if the patient is a male. We could also leave it, but in order to help the daytime caller or the person entering the data on the phone, this is something that could be helpful. And the next one, for example, if the patient has a more globin' really low, show a warning to the nurse. In the document we provided yesterday, you will see that there are some, the prone rules that are covering this in this program. So feel free to go there. Thanks Martin, excellent. So when we talk about prone rules, we're gonna divide this mystical concept into three items that we'll be working on and we're gonna explain really quickly. But the first one is the rule variable, the rule expression and the rule actions. So again, evaluation and action. And I have put you here above if the patient has a more globin' really low, show warning to the nurse. If you think in the first part of the sentence, the one that is underlined in reddish, if the patient has a more globin' really low, this is the evaluation. And then we perform an action which is show a warning to the nurse. If you see here, we have the more globin' that I have linked and it's a rule variable because it's something we evaluated. So we'll see now what is a rule variable. I'm gonna set, I have a set of slides here, four, five, I think, which says reference on the title. This means that I'm gonna be going to them really, really quickly because we don't have the time. But it's for you to have them. And in case you wanna come back to them later on or in case you need to give a training, you will always have them. So go a bit before, yeah, no, go a bit before, Marta. Yeah, I'm gonna, yes, yeah. Because I'm gonna explain to you. So just really quickly, we have promo variables and more globin' in our real example. In the traffic light will be red because my light is red. So the promo variables, basically what they do is they capture a value from one of these things that I have included here. So it could be a data element from this event, a track entity attribute that someone was asking this morning in Slack. And the last one, which is here, calculated value. This is in case you need to operate with a value that is not directly taken from the data entry, but it's something you're computing in the first real VHS to example, I told you, give me a score according to the number of checks. So I am adding these checks, so I will create a promo variable that counts the number of checks, okay? Next, yeah. So in order to define promo variables, you will need to go to the maintenance program and promo variables, and there you will feel this information. When you define a promo variable, you need to put in a program that is gonna be used, in which program will be used, you need to put the name, and then the source type, which makes reference to the previous slide. So basically we're gonna be defining it if it comes from another data element from an attribute, or it's a calculated value as I explained. Again, if we go back to the real examples in life, so my traffic light is red in this sense, I'm taking, I would put program traffic, the name could be led of the traffic light, and the data element is the one that is the light, okay? In the HS2 we'll see now, so next one. Now if we go back to the three circles, we were talking about the problem has these three bubbles, let's say, and one is gonna be the evaluation, and one is gonna be the action. These things, you are gonna define them in the maintenance program and program rules. Don't worry, you're gonna be seeing this, and in the exercise we are asking you to do, you will have to perform this task, we're giving you some help afterwards. So when you go to the maintenance program for a rule, you will see there you have to fill in the first list, you can put some details of the program rule, you can put the name, so the program, in case you wanna limit it to the stage, some additional information, and then the priority. The priority, not fully covered here, but just for you to know, that whenever you are having several problem rules and you need some of them to be executed before the other ones, you need to use this priority. If I go back to the example of the checks and calculating the score, we will need to make sure that we are checking distance before we can compute. Okay, so in these terms, we will need to use the priority. So, next, please. The second thing we need to define is the evaluation. Again, if my traffic light is red, if my phone has no battery, if the amount of lobbying is low, so we are trying to evaluate something that needs to give us a true or false statement. If we don't get a true or false, it's something that we are not properly defining the expression. So in this case, if a model of lobbying is low, we have defined what low is, because we have our medical requirements, we know what is low, what is high, but we could not say, we need to know what we have defined as yes or no. So in the traffic light, is it red, yes or no? You could tell me, yeah, but if it's orange, well, if it's orange, it is not red. Next, please. So as a reference, these are the things that you can use in Android. We will see later on a chart summarizing everything. So I'm not gonna go through them. Next, please. And last part of the current rule, so we have defined a bit the details of the current rule, then we have evaluated, we have defined the expression we want to be evaluated, and then we have the action. Evaluation, we have only one. It's true or false. And the last one is the actions, and we could have several actions because we can perform several actions in the traffic light, a stop, a drink, whatever, in a mobile being, we're showing a message to the nurse, but we could compute several actions. In this case, you will define them here, and please next slide. These are the available actions you have in Android. As you will see, pretty much everything it's covered, except the last one that we will cover really, I mean, we'll go through it really slightly on day four, I think. But just for you to know that these are the actions that you could trigger according to an evaluation. So for example, you could assign something, you could show a message, et cetera. So this is the chart that you should memorize, kind of, or at least half as a reference, but basically it's important that you know that the prone rules. So this concept that I have spent in 10 minutes might be a bit, I know it's a bit quick, but if you're already new, I hope it's a refreshment and it brings back to your brain what we're talking about. It's important to know that the prone rules are computed in a different way, in web and in Android. And in the near future, this will not be necessary because we will be using the same rule engine, but at the moment, it is not the case. So when you are designing a program that it needs to be used in the web and in Android version, you should check this link that we have here, the prone rules supporting in Android capture app, where we have collected the main discrepancies. So when you go and you design the program or your system, you know what is important to how to adapt both. So are they compatible in both systems? There are some questions popping up. I will reply to them, sorry, when we finish this. So let's create a prone rule. So that was the theory. I know it's a cross course and I hope it was at least to bring you a bit of, sorry, message, okay, to bring back to your brain what our prone rules are. And now we're gonna see, what are we asking you in the exercise? So if we go to the next slide, set of slides, which is two, two exercise prone rules. Yeah, no worries. I would recommend that you all download these slides. So you have them in your DHS2 folder. So whenever you need to explain this to some people or whenever you need to go back because you're designing your system, have them as a set of resources that you can have. Okay, so in the exercise, Marta, go two slides ahead please. Yeah, so this is the introduction. In the program that you are using that you work on yesterday, there is a new temperature data element in the phase one symptoms has been added. It should be here if there are no symptoms or the fever is no and this has already been implemented. However, if the fever is yes, the temperature should be verified to avoid discrepancies. So we are asking you and don't worry we're coming with a little bit more help down but the student you are supposed to make a prone rule that in case of registering fever, if the temperature value is lower than 37 an error should be displayed because this is an impossible state. I'm gonna roll back and explain that quickly again. I am someone who's encoding with the phone because a COVID patient has just arrived and I have measured his or her temperature and I have marked that this person and I have checked the temperature of this person and I have decided that he or she has fever. So in my program, in the Android device I'm putting fever yes. Whenever I check fever yes, a box underneath is gonna be displayed that asks me for the temperature of the fever. So there I can put and this has already been for you, it's already there. But in this box, if I put for example, 32 degrees which is really low and it's not fever the program should display a message saying this is wrong because you have told me that fever yes and we know that fever is about 37 and you're telling me now that the fever is 32 degrees Celsius. So this is not possible. So you are supposed to implement a proven rule that avoids the user being able to reach this state. Marta, if you go to the next slide please. We're gonna see that this is what we're asking you. On the left side, you're gonna be seeing what you have currently in your program and on the right side, you have what we're asking you. If you see on the left side, the data encoder has put fever yes but the temperature 23, this is a mistake. So on the right side, you are supposed to have fever yes and now you see it's 35, it's still under 37. So this is incorrect still and a message is displayed. Please make sure the measure table is correct. So what we're gonna ask you is to verify that your proven rules is correct, the variables, the proven variable, sorry and you have to define the proven rule. The three stages we talk about details, the proven rule expression and the proven rule actions. In the next two, three slides, you have a help, a big help actually, where you can see what you're supposed to do but Marta, if you can go next quickly, we can explain. Here you can check the proven rule variable which is called temperature. Please make sure that this is there already, it should be. Check a bit late to see what is going on with this variable and the next slide is basically what we're expecting you to do. If you see here, we have three slides, three images. One is the definition of the proven rule. The second is the expression and the third one is the action. So this is what we need you to implement. I think you have now like 17 minutes, no, sorry, 13 minutes. So please work on it and we're gonna be here to help you. Thank you very much. I know it was quick, but I hope it was enough for you to get rolling.