 Okay, so welcome back. First day session number three. We have been seen on the first session a bit demo by Marta explaining everything about the the application, the Android application. On the second session we have been seen a bit more the concept of why are we using what first of all the VHS to model of the package we're going to we're going to be using during this week. Then we spend how this was up to details to and now we are starting to get our hands dirty. So we have 45 minutes. And in this session. You are already going to be doing some stuff on the system you will be given access to the server. You will have to start performing some changes that afterwards you're going to be seeing on your Android device. Important to know is that this session. So we have an exercise, which we have divided into sessions so we have this session now and then 10 or 15 minutes break and then we have another session. And then in that session, you will have to use your Android device to see the changes you have made on the server. First server, second Android. I'm going to be talking about the server and you probably will be asking me here on the slack everywhere, how can I access server. Please be patient, I'm going to assert the credentials later on on slack. So when I finish talking, because I want you to pay attention to what I'm saying, and I know if I give you the access you will be accessing and you will not be listening to me. Yes, wait for the next I'm going to give you 20 minutes of quick introduction, and then I'll share the potentials I'll share the URL of the server and you can start playing. Each of you will be given to one account, but we are not giving you specifically to each of you so we will be sharing a spreadsheet with your name, your admin password your Android password and the specific organization that you have to use for this training. Please use only the one you have been assigned, do not use because you will have access so one of the first things we will use to change the password, but please stay in touch with what we have given you and don't mess with other people's system. We know it's not the ideal way of doing things but we don't have a capacity to build one server for each of you. So we have a server with different programs and you have access to specific programs, but at the beginning you will be given the list of users, and here you can. Let's see. Also important to know that this session does not contain an exercise you have to submit. So it does not mean you don't have to follow this session. It's very important because this session. This is the foundation of all the exercise you will be doing during the next days of the academy. So if you fail to do this session or this exercise properly, you will not be able to continue with the next exercises. Let's say we are building blocks, and this is the foundation the base block where we are going to start where we're starting from before putting the other ones. This is the foundation but still you have to follow. Okay, so by the end of the session, 45 minutes, let's say I'm going to be talking for 1020 max. You should be able to log in the server with your credentials. You can explore the program. I was telling you in the session before that we have built this program from the WTO recommendation. You can use it according to your needs or wishes, and you will set up the mobile user. This is the mobile user that we will be using in the next session. So having said this. Let me. Yeah, start with this one second. I'm going to put this like this. Yes, exactly. I told you already, but please listen to me before you start playing with it. You're having time afterwards. Again, we have divided all the sessions of the academy in a bit of theory and then practice, we give you time after the theory for you to practice. So, don't worry, you're going to have time to do everything I'm trying to explain. So this is the server you're going to be accessing to academy.android.dhs too and when you access you're going to find this typical most of you have already seen this before. The dhs to default login screen might be that someone has put a ray of luck. It doesn't matter. But here you will have to put your username and your password. This I'm going to share. Now in the next time when I finish talking in Slack, so you will be given the two users. If you have problems with any of these please use Slack to tag me or one in the in the questions say I'm having issues with access to server and we'll see what's going on. You should have access. We have tested it but just in case something went wrong. And the password. The first thing you have to do is the password. And this is one of the things that we are going to follow during the whole training. We will be talking on the last day about security in Android. In dhs to and specifically in Android. And we will be trying to follow best security practices. In a case we have already not follow the proper security practices because we have not we should not share what we're going to be doing. It's a master file with a lot of passwords, but I think it's very complicated logistically to send you each of you the password independently. So, because we're not doing this right, please fix it for us. So the first thing you do is when you access the server with your admin account, change the password. Everybody can mess with your exercises with your programs etc. So access the system. When I give you the credentials and the first thing is change the password. Most of you should know how to change the password. If you don't know how to change the password. It's quite easy. Just once you have access code here on the upper right corner you will have your initials. It's going to be s a so student admin, if I'm not mistaken. And here, if you go to account, you will be able to change these things so for example you can put the old password that you have to provide from the file machine and then the new You know that in the issue you need to provide lowercase. Number and special character. This is the fourth thing that your password have must contain and I think maybe six or eight characters. I'm not very sure about it. But well, if you put the password and it's not valid, it will tell you that it's not valid and you have to put a value. But please do this. The first thing you do I'm going to say it again. Well, once I say the password list, but please remember this. So, when I give you access to the server. You know how to use. I mean, most of you should have follow tracker training before coming to this academy. And you know how to reach these programs. So basically by going up here to the list of applications. Yeah, so if you go here, you should be able to see all the applications and by going there commentators you will see a list of programs. Here you should see only one program. The reason you see more here is because I'm using my account which has a little bit more credentials than yours. But here for example, if you have given given the student 125. You will find here ST 125 ST comes from a student. So you will have ST 125 COVID-19 case based surveillance. Okay. And what we asked you to do is to start exploring this program. If you have set up a tracker program before you know that you have different things here. If I go back to the presentation before. Remember I was talking about enrollment where you have to put the attributes. You can see here then we have program stages some of the repeatable so explore a little bit assistance to see how this program is if you have never played with COVID-19 program before. And if you have downloaded the 1.2 metadata navigation file, you will see that what you see on the screen is what you see. I mean when you see on this is what you see on the file. Imagine at one point you decide to remove some attributes because you don't want to collect these attributes. So what you can do is you could come here to the attribute list, remove those attributes, and then you could come to your doc file, remove them. So it's much like this you can understand well from this piece of paper what have to set up and then you see these changes reflected on Android when we access it. When you're setting the attributes, as I'm saying now, you will see here, I don't know how is the problem because I don't know why hard, but there are things that you can choose to be displaying the list. You can make mandatory the attributes, you can allow dates the future in case it's a type of date attribute and then you have it searchable in case you want to have a set up and then the render data. These things basically by defining these different checks, you will see that it has an impact on how Android displays the thing. For example, if, and I'm going to go to searchable. If I mark, for example, age at searchable on my Android device, the same way as it could be in this issue, but I'm going to focus my session on Android, you will see that here when I go to Android. Here I will find the age attribute as searchable. This probably not very convenient because it's very unlikely that I'm going to be using age as a searchable field, but if you decide to use it because you won't. It's up to you. I'm going now to this one display list when you access the program as Marta was doing in the first session, you will have a list of the eyes. At these days, you will see me this under the screen is quite small, but we try to feed as much information as possible. So what will be seen there on your Android TI list is this is this is the type of here. Basically there's three plus one attributes will be displayed. So, and the first ones. So for example, if I will have marked here age country of origin and date of birth as the first ones as display list, even though there's another one here, this will not be shown in the TI list. I'm not showing you here that the list, but it's something that I want you to play with so you see the differences is the things that are you going to see in the little boxes of the TI list. I'm going to put in plus one, because if there is an attribute of the image that you're going to be using just like this going to be a picture of the patient of the COVID surveillance case. This is the picture that is going to be displayed next as a round icon next to the TI list on the left side of the TI list. Three plus one, because it's three attributes, and in case there is an image, it's going to be displaying also the image. However, if you would have two images, only the first one with this name why because I'm doing doesn't know if you want to use the first second so it's okay I'm assuming the first one you are using is the one you want to be displayed as the profile picture. And here I'm putting the rendering time is covered in another session, you will see this tomorrow I think in the visual configuration. We'll have on the last day, some specific recommendations for Android. Sorry, no, I have, I have forgotten to make sure that they're here. Some of you will ask or have already asked, maybe you have not found in documentation but it's something that it's important to remark. Some searchable attributes. And you will see that when you access the TA, the program, you are forced to search before entering a new case. Some of you find this a bit annoying, and you don't like it you say why cannot I start putting in putting patients and sending them to the server I need to search. So just to let you know, the story of this is that at the beginning, Android application did not impose the searching before entering, but now it does. And the reason it does is because we found, and it was requested by by different implementations that if we don't lose do this, there is, there can be a lot of duplicates in the system. And then you're going to be in the page. Hi, my boss case, so you want to input me. Instead of searching before you will say okay new patient, I was kept up about you feel the information that you say to the server and the server might complain this patient is already there. If you perform a search before what Android does is like will search locally, if you have internet connection will also search on the server. And if it finds the patient in this case because we're talking about persons, patients, it will say hi my boss case already present, you are asked to download it and then you can feel more information about it. So, I'm reading policy searches, because we were asked to do it. Okay. To avoid duplicates, but it's not something that we decided to do it was not like this in the beginning but then it became like this because many people or many different implementation as for it to avoid duplicates because if not they had to perform some clean tasks in the system, etc. So, as I was saying on Friday we will have a specific session sessions on DHS to recommendations when going mobile. But some of the things we will recommend. It's basically limit the amount one Android by default with a lot of specific data and these are numbers we have trick according to what we think are the base, the standard ones that try to balance performance with usability with data overload, etc. So these are the ones you will see later on during the week how you can change them if you want. But one of the things we found out that is likely to be one of the big problems is that when you create an Android user. You are not having in mind that this is an Android user and you have been using DHS to for months, years, decades, maybe even. And you are used to set the system, the user with maybe a lot of information and you don't realize that this has a big impact in Android. So, here we're saying this is not specific for Android, but the thing is in Android is going to have a big impact in your either security and performance. So one of the things we asked you to do, and it's the first exercise of the session now, you will have to limit the scope, the programs and the organization unit that this Android user is going to be using. So, in the spreadsheet that I will share later on, you will have been assigned one admin user, one Android user and one organization unit. So you have to limit the use of this user to the specific organization unit. If you don't do this. And this, again, we will explain it on what's going to happen is that Android, because the nature of being offline and how it might work in the future. So what happens that Andres is okay, I'm going to download everything that this user might need to use in the field. And if this user has been assigned to several organization units will download 500 TIs per organization unit per program and 1000 events per organization unit per program. So if you have 10 multiplied it these 10 times. And you are with Android, you are very likely to have one user assigned to one specific your organization unit, and this is what we're asking you to do in the exercise. So, in order to do this, when you're what you will have to do is first of all, you will have to change the password, you have changed the password of your Android user. Sorry, of your admin user, but because you have also been assigned a mobile user, you will need to change the password of that user. Similarly, you would choose a different one from the admin, because this is a good practice as well. You don't have to touch the roles because this already predefined by us but what you need to do is you need to make sure you change the organization unit to the one you have been assigned and you can leave the whole country if you want for search. And that's not have an impact on your, on your. Also, because we're going to be working with assigning permissions by user group, make sure that on this mobile user you add that user to the specific group. I'm going to rephrase this if it's not very clear imagine that I have been assigned the student 125. So with my admin account, I will connect to the system, I will change the password of my admin user. Then I will access the user a student or Android 125. I will change the password. I will not do anything with the road because it's done. I will go on the spreadsheet to see which is the organization unit that this 125 have been assigned. I will do this and then I will add this group 125 to the user 125. This is explain again what's at the end but I wanted to go through it here again. In your specific program, you have a program per per student here, make sure you assign the program to the specific organization unit. And that you assign it to the user group. Actually this back is not already present because we have updated the server last Friday. So feel free to assign this program either to the user or to the user group. We usually recommend doing this by user groups, but if you prefer to use a user directly, it's already fine. And now, sorry one second. It is your turn. You have 20 minutes, a bit more. You have now until one to work on the system. I'm going to leave this screen here. I'm going to be answering questions. If you have either on the chat or on Slack, but basically I'm going to share now on Slack, and I will put it here as well on the chat. The file where you can find your organization unit, your two users, etc. Sorry, let me open it. So that's it. Okay, so so what do you have to do in this 20 minutes you have left a bit more and actually then we will have to break I will come back to I will come back to say this a bit later. But basically what you need to do is this. I have a race plan but you need to make sure you set up your user properly. And then that your program is also configured properly. I'm going to be asking you as well. Even though it says optional here, could be good if you can go to play with different searchable attributes, because then if you remove the ones you have by default. And you put different ones you will see in the next session we're going to be explaining how to connect with Android, you will see how it has an impact. And even though I will be showing you some of my slides containing the Android screen shot for you will be different because you have tricked the system in a different way. So if you're free to play with whatever you want in the program is very unlikely you're going to break it. So if you want to change the attributes of your program change whatever you want. In terms of displaying the order, the ones you want to display the ones you want to collect or not collect. The ones you want to make searchable, etc, etc. And you will see the next session when we play Android how it has an impact. You can also see it already on the on the DHS to web application. But I will be focusing on Android. So in order to make the videos a bit shorter, I'm going to stop this recording because the session is explained. Basically, I've shared this file on Slack on the zoom chat. I'm not recording but I'm going to be remaining here. I will remain here on the, on the, I mean, on the, on the zoom. So, so I'll be here. Same questions in case you have, you might have, or you case in case you have friends with your with the with excess. Thanks for the recording.