 Okay, well, good morning and welcome again. Now we are recording. I feel like a TV news person. So, so just the reminders that we have QS sessions before and after the academy this the time there is a slow time you to see plus one, please join for for the issue for sharing your issues or learning from others. So, reminders, please check your attendance. Remember to mark your attendance. Also, I think Martin said today that the attendance remains open 24 hours. So if you watch the session later, you can also mark your attendance and get that 10%. It's not cheating as long as you have watched the session. Please share your feedback. We do learn from your feedback and we try to improve based on your feedback. So please dedicate two minutes to the feedback before leaving the session. We will remind you today end of day before closing. And then remember that on Friday we have a session for sharing or networking for all of you to connect and talk to each other. And we are asking the participants. We thank you Martin 23 hours from now. Not 12 hours from now. Okay. For the attendance, you can still check your attendance. So Friday we have a session for for for We have a session for sharing experiences. We have a session for networking. For now we have one participant we have Bridget from South Africa was volunteer to present as the Syrian Syrian implementation we are very, very excited to see that and to learn from that implementation. And we would like to have more people sharing your projects so please send us a message or an email. So it's like email here anywhere. In any case we will open microphones and ask you for your projects but we think it's better if you can prepare a bit and have a slot there. So please don't be shy. We want to know from you and we will, we would like to follow up afterwards and after the Academy so it's good if we know what are you doing on your projects. So now the recap from yesterday, we talked about program rules, visual configurations visual data entry we hope you enjoyed it we hope you liked it. And I didn't talk about the feedback sorry so I want to share that. First of all, we have seen that you have you have started supporting each other. You answer questions in the in the groups in the breakout zoom in the breakout rooms. You were helping each other so we think that's right we want to encourage to keep doing it on slide if you see a question from a colleague that you know the answer. Go ahead and answer sometimes we are not enough people to answer all questions we try to or sometimes we are slow so don't don't worry. I mean don't hesitate on answering the questions from your colleagues making suggestions if you have faced the same problem so that's very welcome we are very happy. Thank you for doing that. So we have got some comments on the feedback that we go to fast. Yes, so this is the issue of having the Academy condensed in three hours a day. We will try to compensate with materials recordings interactive sessions that we will evaluate at the end of the session and decide if this at the end of the Academy, if this has to be longer we will try to change the format based on your feedback but for now. We keep trying to compensate with with documentation and materials. We have asked for examples of program rules we have been asked, we invite you to explore your student program has a lot of examples that work. So please explore the configuration explore the effect in the app. Change them break them. You also have the description in the metadata file so that was the purpose of giving you that we hope you can explore them there. We have been also asked by step by step presented slides in the presentations, we are doing a demo in which we almost reproduce the exercise and that is recorded so we really hope you can have a look at that. Because the materials are not prepared as a tutorial itself are prepared as a support for a presentation so we hope by watching the recording and seeing the materials it helps. And we have been asked to have an experience sharing a networking session. That's Friday, please join on Friday please share your project. We are going to do that on Friday. And we will try to explain better the exercises we have been told to explain them better so we will try to make it better today. And we have been also suggested to follow a different approach like all sessions before and then all exercises. That's actually not recommended for online courses if they have to be interactive they have to be. Yeah, interactive is the word and dynamic. So that's why we are combining everything we give you short theory exercise theory exercise just to keep your brains connected and interested with their session so. Again, at the end of the Academy we will evaluate with the Academy team they see this Academy and they see all other online Academy so slowly slowly. We are getting better in this new digital world. Oh hi may I didn't see this that's great. So it's like it's working well great we have 1246 messages rate. So following up the exercises we are a bit low in submissions we have started grading so you will get your results during today and tomorrow for the ones submitted already. So please submit your exercises please let us know if you cannot submit your exercises or if you have any issues because yeah we are still missing 30 people from day one. 40 average from day two so please please submit your exercises we want to grade them. And then I think this is the one from yesterday let's see how do we end up today today. East and West Africa kind of leading the process I think this is Uganda and Rwanda is it hi man. And it's this Sierra Leone I don't know I'm not big buddy and so who is here. In Nigeria because the dot is a bit big. The server the server now is green and with the Nigerian flag I think or at least it was like this yesterday. Okay. Very good very good. So just wrap up for today. I mean for today we are going to see program indicators. We are going to see Jose will will present maps everything about maps for everything to sessions about the geography special representations and then we will see the data sets. So first and last sessions for today are very simple. I think the ones in the middle are a bit more complex but I think you will like them. So before starting. That's that's all. And then. And I don't know where anyone with a hymen do you usually make questions wrongs in this. Just started okay I'm five minutes late. So no no. I think we should go straight away because. Yeah, let's start. Okay. You have questions we can just break. It's always, you know, so I think we have had issues with the submission sorry I'm going to take two more minutes, because the interface is a bit special. So I think if you go to today assignments. Some people say I only see one exercise. You have to navigate the top bar for seeing the other exercises program rules, visual configuration, visual data entry, you can also use the arrows. And we can start at what time do I have to finish. Okay. So, program indicators and legends in the highest to what are we going to learn in this session. We assume you know program indicators as we, as we said, in the world, as we have been doing during all the sessions we want to show you how to display the program indicators in the app. Which ones will be, or will make sense actually to be displayed. And so it's really, it should be fairly simple. So program indicators, which program indicators are displayed in the app with. Yeah, with the right information. We display or we use the indicators in the domain of the track entity instance, talking about tracker. And so what does that mean, it means that the indicator can be calculated with the data of the track entity instance in this enrollment. What's an example of an indicator you drop for for two seconds. The ones that are in the domain of a track entity instance or can be calculated with the values from the enrollment. For example, at a weight gain of a patient or, or, yeah, the weight gain of a patient, how is the child growing. What would not make sense in the app, the, at this moment, the average weight gain of all patients in my program that cannot be calculated in the domain of one enrollment right so. So those ones are what we call program level program indicators. So we are not using those ones we are focusing in the TI and the enrollment. So where are the indicators displayed and how to display them. As you know already in the track entity instance dashboard we have the indicators. So there is one tab called indicators, your indicators will be displayed there. And for the indicators to come or to appear in that section, you need to tick them as display informed in the program indicator maintenance configuration, I will demo this in a minute so don't worry. What is and is not available and usually a relation types do not make sense because they make sense when we grow up in the hierarchy and again we are in the domain of the track entity instance this is information for the health worker, looking at the track entity instance but the last value. If you are using a data element that is repeated in different stages you can use last value and that will work. Last value of blood pressure. I don't know that is checked regularly. And then all data elements and constants are supported. Now we are talking about when you create an indicator variables. There are four that are not supported this is all documented in the same document that we have been recommending these days. So you need count program stage ID program stage name and sink date are not available. I don't know if Victor is in the call but please jump if not correct. This is from the documentation, then all functions and the two functions. You can use them they will all work except that relationship count function. The basic period boundaries just do not make sense in the domain of one enrollment, so they will not apply. Now, I don't know if you have paid attention that to this, that this value is called in green. This one has no color so how do we do that we do that with the legends, the legends are also rendered in the Android app. So you can find them on their mind and maintenance orders. I'm going to demo this in a minute so no problem. No, don't worry. And I will also explain you why we need to pay attention to the boundaries and expected values. And so, this is all, actually, or indicators. It's very simple because we understand that you can create program indicators we are just trying to show you how to display them in there. For that, we can we can go to the app. So let me share the app. Sorry, shouldn't be ready but because of the preview session my account is not. I'm putting them on mode before sharing. Sorry about this one minute. Okay, one. Yes, please. What's the flag now. So then, I don't recognize the flag. I think it was then. Okay, so I want to open my student program you see you have some more programs today that's for the sessions for maps, but I'm going to open our known program I'm going to open one track entity instance I want to go to indicators, and we don't have indicators. Okay, so let's have a look in the server. The first thing I want you to have a look. Sorry, is the legend so we go to others. Legend. We have already created a legend for you that you will use all of us will use the same legend, but let's explore it together. This legend. Accepts three values because we have created an indicator that we will see in a minute that evaluates the risk of a patient that has been exposed to COVID. So we say we have three risk levels 123 being three, the highest risk. And so why, what, what did I want you to know about the boundaries right now. And we are fixing this for the next version the Android app is a bit confused when we get a value in in one of the of the actual boundary. The SIS to that's not the SIS to that's not if we say here one and here one point one so that the Android app is not confused. The SIS to legends are confused they need the same and the end point and the same starting point for their periods. Otherwise, the UI will tell you there are gaps and this is not correct so that's fine. I don't know what you're doing in this case. I know my indicate my indicator will always have a numeric values like integers. So I know it will never be one point one. So now one will be allocated here and two will be allocated here and there is no calm problem. We're going to fix this so that they are always inclusive. But for now it's, it's how it works. So this is the legend risk level. I'm 19 with three values. I have a same three colors. And you are welcome to explore and create legends. So the next step is to go to the program indicator. I'm going to work in the one for my program, but you have the indicator already in your program I'm explaining the exercise actually already. So this is the indicator I opened the indicator and there are two steps that you have to do. I'm going to mark as display inform, which is already there. So I probably didn't undo on my practice, and then assign a risk level. So your legend, you will find it like this, but you need to display inform, assign the legend and say, so when you come out to the app and sync, which I should not need because it was already there 1410 minutes. Oh, I didn't show you but you can explore but the, the, the, the expression is a bit of a, it's a nested Boolean expression with the two condition. So that's why we don't ask you to create it but it's actually checking if it's high level risk, if not, medium level risk, if not lower level risk. We have configured this, and you will find it already done but you are welcome to play as long as if you have the same result. So this information is here to enter values in the exposure risk. So if the patient is a head worker, even if he's not visiting or exposed to a positive case, I think someone has been playing with the legend because they should be read. But that's okay. Actually it was confused when we checked. This should be read. I'm going to change it for the exercise but right now what is happening is correct. So for you it will be okay. One should be read. This is a high risk. If we change his exposure or her exposure, because there are three, three options and health care is a health care worker, which means high risk has visited a health care facility 14 days prior to symptoms upset on set that would be a medium risk. This has been in contact with confirmed case in the last 14 days that would be high risk and no risk will be like the three are no. And you have to answer to the three of them. This is how we have configured the program indicator. So the three of them need to have a value. Now this should be a low risk. And the medium risk would be that the patient visited a facility, but it's not a health care worker is not has not been in contact with a positive case. And I just want you not to be confused if you don't see the indicator because when the indicators have no values or nothing to add. They are not displayed. So if there is, if the expression doesn't return any value, the indicator will not display. So, I see a raise hand Eric one sec, let's, let's open the exercise so that we can leave it in the screen for you, but actually that's the exercise you need to find your program indicator. So you need to set the risk level for your program assigned the legend that now it will be read will be high risk and green will be low risk. And make sure it's displayed in the Android app, and you need to submit to screenshots, one with with two different values we just want to know that the legend works. So time for the exercise I'm going to leave this. In the screen you're you're seeing my screen right all this gets your screen. I'm going to leave this slide in the in the screen and let's let's try to address the questions. So hi everyone good morning afternoon or, or evening. Yeah, I'm ready to to go through the special considerations. So let me then share my screen. Okay, can you see my screen now. Yes, we can. Okay. So this session is to talk about we're going to talk about we're going to discuss how we can like record a how we can collect resources in using the app that has GPS coordinates on it. So basically in the access to we have like, like five kind of resources that can have that can contain GPS coordinates right. So one is the track entity instances, the enrollment events, data element and attributes, and then a unit, well, there are six that I mean. So within the app, we can like collect also all this information within within the app. Okay, and we're going to go through the process that the configuration that we need to have in the server in order to collect data GPS coordinates at the target entity instance level or events or that or a romance as well. So let's get started how what are the kind of coordinates that we can collect. So we have two polygons and points, you know, polygons we can like collect like an area. That is normally is very useful for when we need to have like an investigation of a particular disease in a particular area, or, like, in this case, like in the COVID related what are if there are like kind of COVID areas. So, in this case, polygons only applies to the eyes enrollment and events. Okay, while the points apply to the rest of the of the of the resources. Okay, so this is the kind of the, the, the two type of coordinates that we can that we can call it with with our mobile app. So for the target entity instances how we can set up like the configuration in the server. So then, in a way, in a way that then we can collect the, the, we can link GPS coordinates to a target entity. So here we need to go to the to the target entity type. In this case, the type that we are working through all the course, so the academy is the person. Okay, and then there is a field that these features type which is a which we can which can have this kind of these values, non value point and polygons. Okay, so in this case, we just want to select a point we need to. Yeah, so it's going to display, like here, the coordinates for a point and a polygon then we need to go, you know, to, to, to click like in several points of a map. And then we need to see to see how in a moment. So, then this is the, the, the screenshot. This is a screen that when we are creating a targeted instance will display. So we see here that these are the coordinates for the person. Again, because we have here marked the targeted the feature type of the targeted type as a point. We can like, we can like then collect this as my current location. Okay, in the case I click on this image over here. Okay, and I can or I can send or I can select the location in a map. So if I click here, it will show up like a map running on map box. I can just, I can just zoom in or some out and just select any coordinates there in the map. Okay, so, I mean, what is your case, for example, your case of this is that we have also in our, in our COVID case is the, in our cases where does the person live. Okay, so here I can, I can record where the location where the person. So also we can have the coordinates at the Roman level. In this case, we need to go to the, to the tracker program. And then in the, in the Roman details. Sorry, this should be in Roman details. Then in Roman details, we have also the feature type and we, we can select again the point or polygon, and then it will be rendering like this. Okay, instead of the, the coordinates of a person will show the coordinates. So there are no much difference in the Android app is right now if you are collecting GPS at the track entity level or the enrollment level. But this is maybe important in the, in the, in the server size, because then you can run different kind of analysis and you can use different kind of layers in the, in the maps. Okay. So for the, for the exercise today we are going to use the, just the target entity, entity instances coordinates but you need to know that the enrollment can also have coordinates. Jose, sorry. And some people are saying that they can hear you a bit low for me it's fine but if anyone else can you please, well, can you talk a bit with the microphone with closer for me it's fine but maybe some people are having. Okay, it's better now. Okay, please relax. Okay, thanks. Okay. So, then the events. Here for the events we need to go to the, to the, the stage details of the, of the program stage. And also, then there is a feature type field here we can select also the type of coordinates that we would like to display. And this works for events that belong to a tracker program or events for a single event for a single event program. Okay, with no registration. Okay, and then whenever I create an event it will show up it will be displayed here. Again, I can, it can be the current location or can open a map. Okay, and then we can have, we can have data element and attributes in this case I need to define that element or an attribute with the value type as coordinate. So, for example, we can, some examples that have been working on in the past is a, I can like have a program stage that is a travel where the patient that try to record where the patient has trouble to and then I can have like a, like a element to record that to collect that information GPS point of the, of the troubles of the person. Okay. And it works the same for attributes and that elements and that I need to belong to a program stage and attribute needs to belong to to a two enrollment. And last, the last one is the unit attribute. In this case, also you know that the of course the units also can have GPS coordinates, and then we can use an attribute or that element, which, which value type is, is, is an original unit. And then, during the enrollment or the events process of it's in data in an event, it will show like, like, it will display, like the ordinary tree of your search or unit. Okay, so in this case in mind that you will have to collect the location of the patient, instead of having of being a GPS coordinates, you, you are recording for example you're collecting the villages of a country as a unit. So then it will display like in this case the Sierra Leone hierarchy level with the country that these trees and the facilities, and you can like select level by level. Okay, and remember what is important here is to keep in mind that this works for the search or units. Okay, it will take the search or unit tree. Yeah, that's it for the for collection. So I'm going to run now like a quick example. There's something that you need to do in your exercise as well. So let me just take my mobile now. Okay. So here, this is the. Well, I think that first. Maybe. Let me show you first. The problem here. maintenance. This is the program that we are that we are using for the exercise contact registration and follow up. So in this case, we are using this program just to collect data that are persons who who may be in contact with a with a code positive cases. Okay. So, if, if I, if I went for example to the track entity type, if I go here to the person, I can see that the future type of the person is point. Okay, that's the reason because then I can collect now the GPS GPS points for for the track entity instances. Okay, so if I opened in the, the, the program here. I can see the contact registration and follow up. Okay, so I can see that the, the targeted types as persons. The enrollment, I don't have the, the, the feature type in enrollment. So you see it, no value. Okay, no feature type here because I, again, I call it in GPS coordinates at the track entity type level. These are the attributes, nothing new. And then the, the, the, the program stages here, the content information is where this stage, it will like show up where the, the, the content has happened with the, with the person and the positive code, the in this positive case. Okay. And in this case also we have here the, the, the feature type as point. So basically in this program we can call it, we can collect GPS coordinates at the track entity instance level and the, and then the, the, at the even level. Okay, so now let me go through the, through the application itself. Okay, so this is a program here. Okay, I click on it. Okay, and let's say that I just want to, to add a new contact. So I am here typing. Okay. Search for it. So I click on the, on the plus. Okay, and then these are the, the, the coordinates. And so click, click, if I click here, it will, it will show my current location, but if I click on the map, it will show, it will show a map. Okay, so, so let's say that I am here. Leave me here. Okay, then I can collect then some other attributes, the, like for example, the image. So I can take a picture of myself right now at the something that you need to do in your exercise. Okay, here we go. Okay, and I can continue with this. I think that I don't need, I can say that I am like a friend of the, of the, of the in this case. Okay, and then. Okay, so now this is in terms of like collecting data, right. Okay, but then. So how we can visualize coordinates in the test too. Okay, so for isolation coordinates. Once that we have collected coordinates, we have like so, like we can display all those coordinates in a map. But in this case, so far we have in this version, we can show like tracking the things that's in a map we can show enrollments we can show events. We can show data elements or attributes yet. Okay, this is going to be ready into the dot for in this version to be policing in April 2021. And the units we cannot see the, the, yet we cannot, we are not able to to see the boundaries of the units or points for for units. Okay, maybe this can be ready. Well, I don't know it's in the roadmap, but we still don't know when this can be ready. So the way that this is working and again I'm going through the demo. So, so we hear the load. Okay, so in this case as all these track entity instances has GPS coordinates associated to them. So I can click on these three buttons over here. And then I can show them in a map. This option only exist only is being presented to the user if the TIS has GPS coordinates linked to them, or in the track entity instance or in the enrollment or in the events. Okay, so show this in a map. Okay, and then this is all the pictures that we have with all the, with all the TIS that have been recorded. Okay, so you can see here this carousel you can move through this carousel. Okay, and you can like I select any of them and it will like it will like open the TI here for you. Okay, so within the map you can also force like search perform any search so you can select the female sample, and it will show only the only the the female TIS. Okay, what is important is also the map layers. Okay, in the map layers we can like change the by the base map. So we have also satellite view. So if I click the satellite view apply. So this will render. This will change the base map. Okay, we can also show this. We have the map layer. So this is useful in the case that you have like many, many COVID cases in so you can like zoom out a little bit and you can see how the different areas is trying to collapse. Okay. And, and then as I said before, we can also render in the enrollment. So we have even if we don't have the enrollment for the coordinates for enrollment. We have the options here. So if I click this option, I will. This will show up the map with taking into consideration the coordinates for the enrollment. But also the, the, the, the events. So GPS for the events in this case for this particular program, the, the, the contact information is a program stage. So I can click here on apply. Okay. Let me just remove also the coordinates. Okay, so this is the, the coordinates of the events that I have. Okay, and I also can, can, can move through them. And I can see the events if I click on the, on this card over here. Okay, I can combine different layers as well. So if I can show up like the coordinates as well and with the satellite view, if I want. Okay, now, yes. Okay, so now in the map we are like showing like all together. Okay, so it's also, it's also possible. And, and then we have like a other map layers, but this is probably we can explain this better in the, in the, in the next session of the relationships because then we can also display relationships in maps. Okay, but I think that we can like, we can go through this like in the, in the next session. Okay. So, I think that's all for, for, for maps. So let me then go back to, to my presentation. I don't know how I'm doing with the time. Okay, you have 10 minutes left. Okay. So, yeah, with the presentation that's it. And then maybe we can go through the exercise now. Okay, so let me open this one. So what you have to do is very simple, I would say. So, within this exercise, you, you are going to be able to know how to add coordinates to attract it into the instance. Okay, the same that I have done. How to visualize GPS coordinates in the, in the, in the application and how to use different map layers. So basically what I have done in the last 15 minutes. So what we're asking for you to do is like, you have access to this, to this program as well. Okay, the contact tracing registration. So you have to enter three cases within your country, maybe in your country city with different locations. Okay. So in the program is a contact registration and follow up. Okay. And then what you have to do is like other picture to the image attribute. Okay, so you know that we have an image attribute. You can select a picture you have in your phone previously collected or you can take a picture of yourself the same way as I have done. Okay. And then it will be rendering in, in the map are in the, and as the profile of the, of the TI as well. Okay, visualize your case in a map. Okay, and once that you are able to seem to visualize your cases, you can see also your cases within this with the server. So for the exercise, what do you need to do then for the exercise. We are, we are asking you to submit for screenshots. Okay, so three of them with the, with this map, map screenshots showing the, the three TI cards in the course. Okay, so you have to select, you're going to ask three days. One is going to be one card. So you have to select one card and see, and, and, and see where the card is in the show where it is in the map. Okay, so you have to do this per card. And then the others trying to combine all together so play a little bit with a zoom out and zoom in on the, on the map view and try to have like already as you have created in the same screen. Okay, can you maybe share the screen again with the device and explain what do you mean with the three screenshots of the match or in the TIs. Okay, so I'm saying that you are going to create three TIs. So it's one picture with the one picture per TI like in this case this TI with this, with this image over here. Next one. In this case is Jaime Bosque. Okay. Next one. Victor. Okay. So three images, one image, one screenshot per TI, and then you have to just zoom, zoom out a little bit so so you can see all the, all the, all the TIs in the, in the same screen. Perfect. Yeah, thank you. Thank you. Let's see if there are questions. So, Jose, we had a question in Slack. I told them to wait until the, the, this time of exercises. I'm going to read it out loud so everyone here is aware, but the demo was asking what is the difference between no value unknown in feature type. I think that there are no difference in, in their reality. I would say the same. I think it's just by default, it's no value, which means known, right? Yeah. So if it is known you cannot collect any, any coordinates. Anyway, yeah. There is another question from Bridget. Are we able to download the map from Android or is it only visualization. So far it's visualization but then with MacBooks. It's possible also, but I don't know if it is working now to what extent. So yeah, if you, if you are online and then you, you are rendering a map online and then you move to offline, it should be the mouse should be there. Yes, if it's a Bridget, maybe you can give us some details on what kind of download you mean. Because the map will work if you go offline, but we don't know if you mean like extracting or something like that. George Maguire was also asking if we are supposed to use the same program and everybody there, but for you all to know, yes, please use the share program. This has been created because later on when everything is there I think we hope that we will show a very beautiful map showing all the TIs that you have created. But yes, this, this program was created so you're supposed to use the share one, the contact reason. There is another question for Jose. So, I'm sorry, I did not get well the difference between point and polygon for the TI or event. Okay, so. And we have sorry so that we do both together Jose to one was asking on program stage there is feature type polygon how does that work so maybe some refresh on polygons. Yeah, so, so basically a polygon, a GPS point you have to select just just a point in the map so you have to click on a map or your current location. Okay, with a latitude and latitude. In a polygon, do you need to. You need to define like several coordinates, you need to mark several coordinates, and then we'll show up, it will show up an area. Maybe I can show an example because we have created other programming in the server that deal with polygons. So, let me go through this. I don't have a lot of stuff now but So there is a this I have created this program that you also have access to cobit area. Okay, there's a problem just to to get the purpose of this program is just a matter of adding cobit areas to the, to the, to the picture of the programs. So, for example, I have I can like create a new one. So in this case, you see the coordinates for the area is polygon. Okay, so if there is a polygon, it will only show a map icon here because of course you cannot render in a in a polygon your current location. Okay, because you are in a latitude on YouTube. So you click in the map, and then you can like just start to to click on the map and they will start to display an area. Okay, when you are done, you click on asset. Okay, and then do we have an area, a set of a point and then you can display this in. So in fact, if save it. In fact, if you go now to the to this program and then you, you're showing them up. You can see like, you can see like different polyons that have just created. Okay. So please remember that what you need to do is that you need to go to the or even the, the, if you want to, to get to collect this this information at the event level. So you, you, you have to do this here in the in the future type of the event in the of the program state market as a polygon. If it is in the track entity type, you have to go to the track entity type. So let me do that. In this case, I created an area to get to the type and the future type of that of that. Track entity type is, is polygon. We have, I think more questions. And so it was asked again about the submissions or maybe before closing we can repeat that. There was an error that he is looking at another confirmation that we are using the contact registration program. Yes. George was asking contact registration and follow a feature type is blank. It should be point so I checked the program was it and it's pointing the enrollment details. So I'm not sure where George is looking at. Hopefully it's fine. It's pointing the enrollments. I guess I think that I, I don't move it. It shouldn't be. It's pointing the, in the enrollment that maybe I save it when I was doing. It's in the details. It's a point. Yeah, but they are collecting data in the track entity type. Okay, then this one is point. Yeah, so I don't want to touch. So it's a track entity type person, which is the future type is point. If we have both if we have the track entity type as point and enrollment as point, then it will be kind of weird within the entire because they, they will see like to change the program GPS to different field for the GPS for storing a GPS coordinates in the same screen. Okay, then do you change the program because it was a point. Yes, I change the problem. Yes. So, Brian, yes, we are using the contact registration and follow up program. Yes. I think he's getting a lot of 500 errors when he tries to sync, which might be similar to the problems for Jamaica. And we have anyone monitoring. Can we use same picture for the three T I, well, you can, but it would look better if you are right, but yes, you can. It will not be incorrect. You can take different angles. Yes, Jose. I'm taking the errors on the server. It seems that Samica rose and so are having the same. I'm trying to see what's going on. Yeah, it's happening to me as well now with the data has created. I think this is related to the picture. I don't know. Okay, let me register one. Yeah, whenever I try to post up the ice. I'm getting the 500s as well. I'm taking also from from my device and the server. So I try to troubleshoot if you're getting this first this patient, we will, I mean, it's fine as long as you keep recording on the device at one point you will be able to push them to the server should be should be fine. And for the exercise. Do you just need to, to, again, do you just need to submit three is for screenshots. Okay. So we're going to start told you what is going on in the server and then what when we had a solution for that we let you know when so you can synchronize with a server. But you don't need to synchronize with a server for this. Yeah. So can you. Sorry, Jose, can you explain again the submission. Yeah. So, what you need to do is like units in this program in the, in the contact registration and follow up program. You need to enter three cases. Okay, three COVID cases. You need to add them also a picture. Okay, so there is an attribute that is which feature type is an image. So that attribute you need to collect a picture that can be a photo that you take at the moment, the same data as I did before, or can be an image that this has is already is already in the phone. Okay, then. Then one you have created the three, the three days. Okay, you need to visualize those days in a map. Okay, so then what, what do you need to do is like a four screenshots. Okay, one per the eye. So let me change. Let me go through the into the through the map here. Okay, so one per day that you that you have created. So you, you see the cards here and the the I. Okay, then you go to the next one that you have created. So all the screen shot. In this case, hi, hi me. And then all the rest can shoot. So see a screenshot one for today. And then the last one, you need to come out of it. And try to have tried to display all the all the days in the same screen and then you take a screenshot of all this. Okay, there are two questions in this live channel. I can take the second one. Yes. So, the question says, can you add coordinates to an option set. For instance, if you have the fine towns or villages as an option. And then you want to map based on the option selected what would be the best way to handle the finding city town village for a track and program to be able to map results. That's a very good question. And it's something that is to is walking towards being able to respond right now. If your hierarchy has the city towns or villages as part of the hierarchy. I would suggest you to use the or you need value type for the data element. If you are the host of the bar in the presentation. You configure your data element as, or you need value type and then it will offer to the user. The hierarchy and if you have the code, the or units mapped with the right locations, then you will be able to display in the map. In the, in general in the as to in the maps up in the web, you will be able to display the data elements or attributes of type or unit in the map. In the app, you will be able to do this in the next version released in able to display the points that correspond to all units that has been captured have been captured as data elements or attributes. The question there is aggregating based on those or units and not on the capture or unit. But that's that's on the roadmap, and but that needs to be this if for further information I would suggest we go to the community and check with the team analytics. But now for the origin of your question about the option set. So meaning, I imagine you don't have that the level of detail that you want to collect for the locations in the hierarchy for some reason. I might be wrong but I tried this sometime back horse correct me and I don't think there is a direct way to link an option in an option set with a coordinate. This is a common problem that that many implementation has when they are like. Sometimes it's like they, you know, they have like 10,000 villages 20,000 villages. And they are not in the hierarchy. Yes, there is some people use worker work rounds but like the thing is you can find ways but to display it in the map. It's, it's, it's a bit challenging. And there is another question Jose on Robert at the enrollment for catchment area and travel history data capture. It's also possible to pick the location coordinates from the entities residence address and specify travel destination respectively I think dealing with coordinates zooming and mapping changing my players can be cumbersome. So I'm not really understanding the question Robert I don't know how safe you want to read it in case you understand the question. So for tell history data capture what we normally do is we have a program stage that can be repeatable. That's one option. And then in that program stage, you have a data element that is type of GPS coordinates. So if the person was traveling to, I don't know for different areas. So you can have like four events and then with even day that even they means that for example where the pace where the person when the person went there. And then at the time of GPS coordinates that can show up the diamond or the, or the even coordinates as well that can show where where the patient in about where the patient was. So normally how we are dealing with double history. I thought the break was at 1130 but the break was at 1120. Thank you. What should I then start with. I would suggest that it's super interesting all the questions that we're getting if you don't mind keep them for the last session we're having when we have questions and answers, because if not the extension can be too too much for the sessions that are supposed to be super short. So we give a four minutes break till 35, and then we start at 35 with five minutes delay. If you don't mind. Okay, and we're going to check the server on the meanwhile. So please be here. Okay. Okay, so we continue now with a with the relationships. And then while the center we're talking to the seven and see what is going on. Okay, let me share my screen. You can you can see my screen now. So, let's get started then. So relationships. Well, as you know, since 231 to 32, the relationships has been completely changing the in the in the server side. So now we have like, you can define relationship types that link that can link. Events with enrollments events with the eyes enrollment with enrollments. Okay, so now in the server and we are going to see this in a moment. We can like to find a several types with different resources. Okay, the eyes enrollments or or events. And in the app right now, in this version to three, we only did our domain is going to be only between track it into things. Okay. So this means that if you are like, for example, a, you know, defining a relationship type between an event and API right now, this is not going to work in the app. We plan to have that way we plan to have this relationship between events and enrollment for the next version. And we will see, but in the current version to three. We are the domain, our domain is the target entity. Okay. Also, there are no constraints of any program this means that, for example, you can like a, you can see a relationship between the eyes that belong to different problems. There are no constraints regarding your units, you can create a relationship between between a track it entity instances that has been enrolled in different units. And also, there are no constraints and this is one is very important. There are no constraints of track it entity types. This means that you can like, you can create relationships, which track it into the type is different. For example, we can like, as we saw in exercise before, we can like a great relationship between a person at an area, if you want. Okay, in this case are two different track it entity types, personal area that belongs to two different problems. Okay, so if we want to visualize the, the, the relationships of a particular track entity instance, we have to go to the two to this tab over here relationships. And this is what is being rendered in them. So in this case, Jaime Bosque has like, for example, a relationship with with Jose Garcia Munoz with me, and with Marta Villa. Okay, so we can see here that this is the, I'm going to see how we configure this in the server in a moment. This is the label for the relationship. And this is the, the, the track entity instance that Jaime is linked to. So Jose Garcia Munoz and Marta Villa. Okay, we can also navigate the relationships and remove the relationships. Okay, if we go to this clip, it will click on the, it will click on the clip. Yes. And then we can, we go to this screen that give us information about the, the, about Jose Garcia Munoz, some, some of my data, and the, and then the, the, the programs that Jose is enrolled to. Okay. So then how, how we define this, this in the server. And this is working, this is working this way till 233 plus, we are now, as you know, we are running 234. Okay, so, most of the relationship that you're going to create are going to be bidirectional. This means that if you have a relationship between someone, if Jaime Bosque is in contact with Jose, then Jose is also in contact with Jaime. And then you have to integrate the relationship in the both sides. Okay. And then what we need to define in the, in the server is the, the, the, which is the, the type of the relationship. In this case, we, I mean, we, we only, this is only work for track entity instances. So this is what we need to, to, to add in the, in the, in the server. We need to mark that this is bidirectional and this is the label that appears. Okay, this person has been in contact with this person has been in contact with regardless where from where we are starting the relationship is going to be labeled as the same with the same text. Okay. And so basically the relationships types, you have to define this in the, in the, or the maintenance program relationship type. Okay. And we're going to see this in a moment and always don't forget the same settings. This happens to me, this happens to everyone when, when people, the relationship types also has certain settings. So, by default, if you are not a super user, the same sentence that you are creating, probably they're going to see private. Okay. That means that no one, but you can see the relationship or kind of create a relationship. So don't forget the same settings if you need to create a relationship type. And then if you need to create more relationships for a particular targeted instance, a matter of going to this, going to this, to this step over here and there is a button. You have to click on the button and click on the relationship type that you would like to add to this particular. Again, we can have as many relationship types as we want. Okay, there are no limitations. There is no limitation for this. Okay, so I think this is like, it's going to be more easier easier if we show this in a demo. So then let me go through my Android device. Okay, we are again in the, in the, in the contact rest registration and follow up. And the use case here is like, there may be like a, you know, an index COVID case. And then, for example, he made that I was having a hosting an illegal party at his home. And then we went there everyone went there and then we, we got COVID. And that part. Okay. So then Jaime could will be the, the, the, the in this case. Okay, so I am opening my, my program over here I'm selecting Jaime, the card Jaime. Okay, if I go to relationships, then I can see these, these relations will over here. Okay, that I have, that I have already created. So I can't remove them. Like, for example, I was going to remove Marta Villa. So I click on the, on the red icon over here. So, and it will remove it. So I can navigate if I just want to go through to Jose Garcia Munoz. So I have to click here on the clip. Okay, and it will show the, the, the, my information, the information of my TI with the, with the problems that I am enrolled to. Okay, so I have to, I can click on the program and I can, I can navigate my TI as usual. But let's go back. Okay, let's go back to Jaime. Okay, what happened if I, if I want to add a new relationship here, like I remove Marta what happened if I want to add her. Okay, so I have to click on the plus. Okay, and these are the, the, now the, because I define it like other, other relationship type that we're going to see this in a moment in the server side. Okay, so I have to click on the has been in contact with them. Okay, and this is work as usual. So as the relationship type is between TI's and person that targeted type person is being shared across different programs. Then here on the top, I have to select the program that the person is registered in this case is counter extension and follow up. Okay, so here I have my, the TI is again, and then if I want to add Marta again as my, as my contact. So I just select Marta. It is added here. Okay, so other thing that I can do is just, I can click on the plus button again. And this happens many times because in mind that then you don't have the person registered in your mobile. Okay, but you know that, okay, maybe there is other person young Smith that is not in the in the in my device, but has been also contacted by Jaime. I can look for young Smith in mind that you have like in this case we only have five but in mind that we have like, I don't know, like hundreds of of the ice. So I can, I can try to ask for John. Okay, we don't have any young here but we can create as well as John from the, from the relationship as well. So I click on the plus. Let this. Okay, and I'm going to what that is point. This is young Smith. I'm going to enter in the data here. Things are complete. Okay, and now if I'm going to, to, again to the relationship that high, that high may has, I can see that the, the job has been added. So in this tab, we can like add relationship from of the eyes that already exists in my device. Or I can start to read this in the server, or I can create a new, a new, a new tie from here as well, if it is not in the server or in the, on the, or in the device. Okay. Last, what I can do as well is like a you see here this button over here that is the map. So I can show also relationship I can show in a map what is the if this again if this person has GPS coordinates that they have. I can show them in a map as well with the relationship rate. So I click on the, on the map over here. Okay. And I can see the information. Okay, so this is Jaime, and you can see now that you can also navigate the relationships. Jose has been in contact with Jaime. Marta Villa has been in contact with Jaime, John has been in contact with Jaime. Okay, and this is the, this is in this case. Okay. So how we can define this in the, in the server size. So then let's go back to the server then. So in the server again, we need to go through maintenance. Okay, maintenance program. And then relationship type. Okay, and we are using this one has been in contact with. So this is the name. I have to mark that this is my directional so I can navigate from both sides of the of the of the of the relationship. It's very important also for analytics in the server side, because if it is bi-directional, I can like use, you know, I can count the ice in both sides as well. How many, how many days has been caught up with Jaime has been caught up with Jose both sides of the relationship will work for for analysis as well. Okay, but what is important is this from constraint here you have the multiple options that you know. Okay, but as we explained before, remember that we need to select always the track identity instance you will want to have this working for 100. Okay, the track identity type person. And then the program. Okay, in this case, the from underwear are the same from person to person. Okay, but then we can as I said before, we can be more creative and we can I have. For example, these other relationship belongs to to the area. Okay, and in this case, let me open this one. Okay, this is also bi-directional, but then the track identity instances here are different. One is the, the track entity, the track entity type is an area and belongs to this program. And then these the last part of the relationship is a person or targeted type person that belongs to this program. And so in this case we are combining different targeted types and different problems. This is also this also works. Okay, but it's important is this to be a specific instance in both in both parts. Again, for this version, next version into four and two five, hopefully we we are also supporting a romance and events over here. Okay, so that's the reason because now I can also if I go back to my mobile. I can also navigate, for example, the areas. And I can say, like, for example, this rural area. I can watch the relationships. And I can see that already contains like some people over here and I can display this in a map as well. Okay, so then I can see that the Pablo, this guy here belongs to this to this to this area. I can navigate and Victor to I can navigate. I can navigate the cases to the area. Okay. And also, but I will say it's really, it's really cool, but we have now kind of a bug in the in the, in the, in the app that we're going to solve. But also we can, as we said before, in the in the previous session, what we can do is that we can like show this in the polygons in this case in the, okay, as a map in this case we show polygons. Okay, I have three polygons. And then I can go to my players. And also I can, I can render relationships. So the map layers I have, I mean, I can change the base map to satellite views. I can show enrollment coordinates I can show event coordinates. I can show the hit my player but also I can show relationships in this map as well. So if I click belong to the area also will show the relationships here. Okay, so you can see basically it is like, in the map you can see like, you can see information about different targeted types, different targeted instances and how do do how you can render and go together. Okay, but now there is kind of this kind of baggage is still on the beta version, but hopefully for everyone to provide a bug fix for this in the, in the next release. Okay, when we are like showing the TIs showing the relationships in the, like in a global map. Okay, so that's all for the explanation and then the exercise what you need to do. Let me go to this. So basically the goal is now how to define relationship types to be rendered in Android that we have that we have seen how to do this in the server side. So we're going to understand how to we can add relationship between the ice, the ice in this case of the same time of the same track entity type, and how to render, how to show the relationships in a in a map. Okay, so what you need to do is like the three case that you have created in the previous session. So you need to open the, the, the, the problem, the contact registration and follow up program and create two relationships. Okay, you will have, you have of those three cases that you have created you have to say one as the in this case. And then you have to create two relationships between the other two cases and the in this case. Okay, same as I have done with with Jaime. So in this case, in my case, my example Jaime was in this case. And then you need to visualize your relationships in the map. Unfortunately, until we got the problems of the server solve, we cannot sync with the server. Okay, but it doesn't matter for the exercises. Okay. Because for the exercise, what you need to do is, I think it's very simple is just to meet one screenshot of the map showing the relationship that you have created. Okay, so that must show show like, yeah, two relationships and three days. Okay, so let me show you again with my in my mobile. I need to go to the counter station follow up here. Okay, and you have to to determine what is your in this case. And then in the relationships, you see, you will see you have to create two relationships within this case, and then display those in a map and the screenshot that I am asking you to submit this is one. So that's all for me. Any questions. Jose, we had some questions in the in the chat. I told them to wait till the exercises. We can read them now. If we don't have time we will be replying to them in the question and session happening at one. But we have I'm going to go from up to bottom but this if I miss something that we know. Can I put rules at the value for a coordinate of a T attribute. Well, yes, I guess so. Yes, because of the end is having like a, I have never done that. I don't know if Martha or Jaime you have experienced in this but in theory yes because of the end is having like a value to a to a to a to an attribute. So that is that yes. I have not. Sorry, I have a camera off. I have not tried either but as you're saying I think it should work. We can test this question was by Peter Ricketts. Peter if you actually have tried or you want to try it please feel free to do it. And let us know we will also be trying on our side just to see but I think they should be no problem. Peter as well who says, can you define a relationship to show resource, sorry, to show source to contact. This would be useful visualizing contact tracing source to contact I mean this is if I understand this your question properly this is more or less what we have here. Right in this case, we can see that this is the in this case over here. And they're like these three cases are linked to that in this case. Okay, so it's a matter of and then there are limitations regarding the number of ratios that you can have so maybe this. This ti is also related to other ti that is here. It is, it is not a problem. Yeah, but this is more or less what we can do in the in the maps for contact tracing. Yes, but this is by directional. So I guess he means to have only one direction. Yes, I don't apply in this case. But yeah, so you have to then in the server. You go to the this one. So you have to about this. I mean, so all the, normally older relationships that I have created in the past I'll always be directional but yes, if you don't need it, you have to check this. Can I just make a comment on the previous question that I tried but I was muted. Can a problem will set the value for coordinate of a ti attribute. And I don't know. So the answer is what Jose said, I think so we have not tried. So please, if you try, let us know. But I'm just thinking, shouldn't this link in with your previous question about assigning coordinates to the options of an option set. I think it's complex configuration but you just hinted here the idea of with program rules based on the option of the options set assigned the value so maybe this is what you are thinking. And, and you will need the many program rules if it's about many locations that can have an issue in performance but I will explore I think it's a very smart option that you may need one program rule to link each value in the option set with the coordinate you want to assign. But why not. Also, please excuse us there are some issues with the server. We know you're having synchronization issues. It's, it's okay to report but we are aware. We are working on it to see what's going on. We will let you know so in case you want to report it's okay but you don't need to tell us every time there's a sink issue we are aware of it. So we will let you know once it's properly working. Thanks. Yeah, you can use it real to the exercise anyway because the problem is like when posting. You can create because for creating not the I it's not, it is not an issue. Now, it's only when sending the idea to the server. There was a question from Milton as well was saying unseen to coordinate entities. So when he's trying to register I think Jose you explained this, but maybe it's worth to go again through it. So whenever someone wants to enroll a person, it says the coordinates of the person and the enrollment coordinates. I just posted a picture on the Slack, but I think it's when you explained that there's coordinates assigned both to the TI and to the enrollment. Okay, so yes, then let me share the screen. Okay, yeah. So, um, yes. So, you can like to find like a coordinate that are the track identity type level. Okay, or the, or the, or the enrollment level. Okay, so normally if you have both, it's going to be weird because in the same screen for that entry, you're going to have both fields once, one, one after the other. Right. So, um, so for example in the track entity type here the person. Okay, with the future type of the person is point. This means that whenever I am collecting data, it will show up this, this in the, when you're creating a new TI, it will show this field here coordinates for the person. Okay, that it is a longitude. So if we also have in my program, if we also have the in the room for the program. If we also have now has changed to point again, someone is changing this to point because I just removed it. So, if we have also here the future type as point. Okay, then what is going to happen is that it will display also this way here you will have the this text enrollment coordinates, all together. So you will have in the same screen, enrollment coordinates and the coordinates for the person. Okay, so we normally only need one. Okay, so that's the reason because I am trying to remove this here. I don't know what is not being safe. Okay, now, now you sing with a meta tagging you will see that the, the, the enrollment coordinates will disappear. You normally only need one. There are no difference in the, in the application if you use the track entity type coordinates or the, or the enrollment coordinates so far there are no different. This may have an impact then in analytics, because the analytics in the server side is different if you have something defined as a track entity things as level. Track entity type level because then you can have the track entity things that's enrolled in many other programs. Or if it is an enrollment program it is the connaissance link to enroll in a program so it is only two going to show only the, the, the, in the map only that the eyes that are enrolled in in that particular Okay, so this is doesn't matter in much in the, in the, in the application but it matters for the analysis in the server. I think is break time. Maybe I can go, I don't know if we have now because no one can can seem to the server so Yeah, no, I will say that we take the because we're, we can take 10 minutes break this break is the longest is 15, but let's show it to 10 minutes. Okay, according to the agenda you should be back at 1215. So in 10 minutes, and then we will have the session of aggregate data. Who's going to be facilitated by Marcia and in the meanwhile we're going to be working on the server. Don't worry you can do the exercises because as hostess said you don't need to sync. So you can do the exercises on local and we'll let you know once the server is fully performing. You can do it. Yes, yes, yes. So you're. We are. Okay, so welcome back everyone. I hope you are finding interesting decisions for today. I'm seeing a lot of questions in the chat that I hope can wait till our questions and answer session at one in 40 minutes we will try to go through the chat and make sure we don't leave any there but now we need to change the topic of it and talk about data sets and validation rules in the This is the first Academy that we make with the data sets. Jose and Jaime, by the way, I realized we didn't have them last year. And, and it's going to be a very simple session again my two sessions today are simple, where we just want to explain you how the data sets translate into the app. So, as we said the first day, data sets aggregated model is just integrated with the other models as with the look of an activity list. This is what we call an activity list. So, the way we identify the data sets is because they have the data sets work. Yeah, easy right in the, in the list. And same access principles capture or you need sharing settings according to to how the server is configured with view only or capture and view permissions. So it will just read the configuration of your server. And icons and colors also apply to data sets so you can configure the colors and the icons for your data sets. So I showed you this on the demo the other day. And, but just to go through it again at the sections on your data sets will be rendered as tabs. And then the tables for each section will put will be displayed one after the other on each tab. You navigate the tabs horizontally you navigate the the tables inside the tabs or the sections vertically. And then if you swipe right or left on the header, you are going to change sections but if you swipe here, you're going to be navigating the form we will see this in the demo in a minute. And you can adjust the width of the column you are not seeing this in the current tab. We lost it in the last version that was a mistake. And we have added it for the next one, but ideally, or in theory, you can adjust the week. You can adjust the width of the column. For whatever makes sense the text will always be complete. So it will be longer height, the height will be bigger if, if you make it smaller. Yeah, and I think that's that's the only thing that it's quite simple we render as a table and then the fields are there and you can have as many combinations category combinations as as you define in your data is to say we have a details tab as in the events or in the track entities so in details we usually show the status in this case a data set can only be either complete or open We saw the period this data set is daily that's why the period is a day and then they are you need the capturing or you need to reopen a data set if you have permissions, then you have to go to the three vertical dots menu on the top right corner So validation. So that's how the data sets display in the app and the validation rules are also supported. You don't need to do anything special for your validation rules to run in Android as long as you have them configured in the server they will be executed in the app. We just want to make you aware of which fields are we picking and displaying in the app so we are showing two fields, the description and then the instructions. So the text that you enter there will be displayed so we encourage you to use user friendly text and action oriented text that will help your users solve the error that they are seeing. In this case, in the instruction we are saying, please review your numbers in the case tasted and hospitalized tab so we are telling them where to go and check the numbers and then below you always find the data to review and the values. The description can also be the script description but helping understand what's the problem. So the number of patients hospitalized cannot be higher than the number of patients tested, all admitted patients should be tested so that helps them understand, okay, I have to test it and there must be a mistake. So, so that's how the validation rules work and, as you might know, validation rules can be mandatory or not based on how you configure the data set that you can say, complete only if validation validation passes if you take that. You cannot complete the data set without having a successful execution of the validation rules. If you don't take that, the validation rules are optional and then the user decides if they want to run them or not. So in the next slide we have tried to explain you the two flows and we think this can be useful for you as a reference in the future. This is the parameter in the data set. So if you don't take complete allowed only validation passes, then it means the execution is optional. So when the user says, we will say, okay, this is safe. Do you want to check data quality. So the user can say yes. No, so if the user says no, or if the user says yes but everything is good, then we go to the final screen where we ask the user if they also want to complete the data set. No matter if they say yes or no. If the user says yes and is correct, or if they say no, we allow it to complete. If there is no error. Now, if the user says yes, but there is an error, we explain the error, but the user can still complete because it's not mandatory. And then the user can either decide to fix and start over or just exit without complete, complete an exit without their solving or fixing the error. So if you tick in complete allowed if only validation passes, then when the user says we run the validation rules automatically, and we show the result directly. So if everything is correct, we come straight here and we ask, do you also want to complete. If they say no, we say without completion if they say yes, the data set is completed. However, if there is an error, we show the error but now we don't offer the possibility to complete anyway. So if you want to go back, fix the error, save again. So this is based on your requirements and the use case that you can choose if you want to make it mandatory or not. And then completion. So I think we can directly move to the app. I want to show. So let's make a small demo which will be also illustrated for the exercise. This is our data set. In this case, why are we playing with the server? José or Jaime, can you check while I do the demo with another user that hopefully works if the participants can enter values because the exercise. Yes. One thing that I wanted to mention is that we have changed something in the server so before you can do anything and for those that we're having issues. Please do a synchronization before you do this exercise like this you do. You have the latest configuration there was that you were reporting where should be fixed. And I'm going to check at the same time with you. Let's see if I can with my user. It is supposed to be super user. This user has the whole hierarchy so it will probably take a while. But meanwhile, I think what we can do is we can explore the validation rules. So this is the validation rule that we will be using all of us. Number of hospitalized cannot be higher than number of tested again here the description. And the instruction these two fields will be displayed. And then we have left side right side so in this case. I guess it is working for me fine with a mobile user. With a mobile user. You enter the data set. You register the data set right. Yes, it is. When I try to register I got the error. So if at one point you want me to share the screen. And you can. Do you want the error. The error here validation. So if you if you're falling stick in Lonnie you want me I can share my screen and you directly what to do. Okay, I think what I want to do is. I want to try once with the user and, and if not we use yours. Sorry about this. You will know the highest. We are touching this server where we are many people. AC mobile. You don't see no one. And meanwhile we explore the validation rules. So this is the validation we are going to be using. And then the option set. Sorry, the data set. So this is the daily one is not mandatory. The execution is not mandatory. And it's assigned to all our units so you will all be able to enter data. You want to share. I think so. Oh, wait, coming, coming. Okay, let's try again. I think I opened the wrong one before. Okay, so this is probably the one that I'm a register. I don't know. So this is how the list of data sets work. I'm going to enter anyone. This is what you will have to do in the exercise. I'm going to enter data for today in my unit. So you will all have to enter data in your unit. You will not see the data that we are entering now because you are in a different unit. So I think we were wanting to work on this number of cases tested or hospitalized. Here is how you. With the others I cannot adjust this now, but this would be a very good example for making this column smaller. So I want to force the error of the validation rule. So we know that if I have. More cases hospitalized and tested. The error should be treated. We check the configuration. Remember, it's not mandatory. So the app is going to ask me. Do you want to check data quality? I'm going to say yes. And it's going to be a you have one error. Okay. So this is as we see here. The description. The instruction. And here the data elements that are not correct. So if we fix this now and say it again. Yes, I want to check data quality and now everything looks good. Do you also want to complete? Yes. But this is my data set. Let's see. Thank you. So this is how they will be listed one after the other with the day and the period and the unit. So now let's go to our data set. The validation mandatory so the user cannot complete. If the validation does not happen. And why not? Let's put a corner in the app. We have to. Think. The big changes on the data set. Again, I don't have notifications. So we have to look at this. To know when the. Synchronization is complete. Must be still running. Did I click. The only difference now should we. Well, the color. Yes. Let's enter another one. One for yesterday. So now I enter. The same. I'm going to make the same mistake. So now when I say it's not going to ask, it's going to run. Automatically and then tell me that I have an error and I don't have the option to complete. Anyway. As I had before. Sorry. Well, so I fix it. It is safe. Everything was good. I want to complete. Not here. I'm going to think now from outside. So this is all I had for content and demo. So the exercise is as simple as the presentation. Hopefully you will have time to catch up with your previous exercises as well. So you have more than 15 minutes. 17. What we would like you to do is to open this same data set. And, and force an error. So enter values. Right now is mandatory. The validation because it's the last configuration we did. So, well, it depends on when you sink your metadata, but in any case, the, the, what we are asking for will work anyway, even if you don't think your metadata. So you need to force an error to see the error message of the validation rules and then fix the error and complete. And what we would like you to submit is one screenshot of the data set entry screen. With the wrong values. So showing the error message. And then one screenshot of the data set showing that everything looks good message after you fix the error. That's it. Please share your doubts in them. In this live channel, we will prioritize the questions about the data sets and validation rules for, for this time. Thank you. Thanks, Mark. We have a question from a big Audi. Hi, Marta. Is it possible to flag the value immediately. After it is entered. So I'm supposed to do the data quality check. That is that the cell with the wrong value changed to red, for example. Yeah, no. We don't have that. No, we don't have that the validation rules. We are kind of replicating the way. It works in the highest two other kind of validations like a type value type validation might happen at the moment of the entry. But for the validation rules, we trigger them only when. When the value is when the data set is saved. Yes. Okay. That answers the question. We have another one from Patrick O'Neill who says, I mean, it's more I wish he says, the rendering for aggregated is adjustable to allow one entry field on a screen. The tabular view is good, but some users have issues with the keyboard. Yeah, so this Patrick, thank you for the question. It would be like a list. Because that was the case in the, in the previous app. For instance, let me share this again. Let's just capture up for data sets. We had like, I'm going to pick a simple table. Let's say this one we have one, two, three, four. Wow. One, two, three, four, six, seven, eight. So in this case, it would be eight rows. One with suspected cases in parties suspected cases known clusters suspected cases. So, if that is what you mean, we actually, the HHS 200 that was like that. And the request was to make it tabular. So now we have a tabular and we don't have the other one. But we do have the Jira ticket. Because it was already mentioned in a demo. So, ideally when, when we have space for it, we should be able to offer the possibility to configure probably in the data set or at user level. The display, let's say listing data entry, but it was not very well received before because it was like imagine a morbidity table with five age groups. So each morbidity was listed five times. And then if it's five age groups plus gender, six, then it would be 10 lines per morbidity. So the, the, so it's, it's a, yeah, I guess it's a matter of the use case or the setting or even the preferences of the user. So it's, it could come in the future, but this is not there now. It's not prioritized to be honest to the next version, but it's not out of the long-term roadmap. So I know it's not ideal, but the problem and the reason why I don't do this is that the keyword takes all the screen when you open it. And actually it's not opening right now. It's not opening probably because it's calculated. Is it open for you in the tablet? It's probably calculating that it's going to take the whole screen. So, okay. Yeah. No, for me, it's, I mean, I know it's not ideal, but in the tablets, it looks quite, quite well. Yeah. Not sure about the second screenshot of the data set exercise. So the first screenshot. Please. So the first screenshot would be. This. And the second screenshot would be. We say everything looks good. It's just, we just want you to go through the flow. Through the validation. We just finished evaluating the submissions for exercise one. This morning for the ones that were submitted again, they were about 50 something. So we are missing. Still a lot. But they were very good in general. Going back to Jose, I'm not able to set the relationship. Please help. Yes, I could suggest that we still keep, keep this time for the aggregate. No, if you can. And then we, we answered this kind of questions in the next hour, if possible. Yeah. Okay. Thank you. Thank you. Thank you. Thank you. Thank you.