 Welcome back to the last session of the day. Any questions we have up to now? If not, we will talk about how to generate output based on multiple program stages. All good. Any feedback should be fine. You can also use this reactions button in Zoom. Thumbs up is there. Any reactions? I'm a bit worried because everyone is silent. Did you all understand everything or you're having issues? All good. Thank you. Thank you so much. All right. Okay, great. Fine. So now let me quickly brief what we have done so far. So we have introduced you what we mean by the DHS to event reports. It's an application where you can get an output of the tracker data and produce a tabular visualization. And I also mentioned that most of the criteria related to configuring the dimensions for analysis remains the same as what we have for pivot table. It's just that you have to be really mindful when you are using this table style and output type. So table style pivot is used when you want to produce an aggregate output and line list when you want to get kind of list out all the track entity instance related data. And then we have two output types which are events and environments. Events is like when we are only concerned about individual events which are like, say, if you have a program stage, still we are only concerned about how many events took place. That's the type of situation when we are using event type output. Whereas enrollment we are using when we are more concerned about the enrollment, individual enrollment and we don't want same event to be counted multiple times. Okay. So we have discussed various types of outputs that we can produce. But one last thing we want to show in event report is how to produce an output based on information that we gather across multiple program stages. Okay. Right. Again, one major limitation we can currently only provide these kind of outputs for line list. Right. Not for events. Okay. Sorry. Not for pivot. Only for line. Say for example, if you want to produce an output which includes data elements from multiple program stages, we can only do that for line list at the moment and you can't produce pivot or aggregate output comparing data elements from different program stages. These only within the pivot within the event report application because if you want to produce some kind of say aggregate output like total number of patients who had a PCR sample and the PCR came as positive. Right. That kind of a single value output if you want to put it in your dashboard. Still there is another way of doing that. That is through using program indicators. Right. That's the only way you can produce that kind of output using a program. But within the pivot, within the event report application, you can only produce a visualization across multiple program stages by using the line list, not using pivot table. Is that clear? Right. There is one question when I try to generate the event reporting DHS to it's stuck at the loading screen after I choose the relevant data and click update button. Also I tried with VPN, but it is still happening. Yeah. So there are multiple reasons why this can happen. If if you are DHS to visualization keeps on loading multiple reasons. Let's start with more local things. Local means like issues that can be from your. So one is that probably your internet connection is too slow. That's one. And number two can be you may be having local browser cache of a previous DHS to output. Right. So like probably you must be familiar with this caching because DHS to use a something called a temporary memory. Right. So previous outputs, you might be storing in your browser. So, so to overcome that you can do you can use this. You can use something called browser cache clean application is one. Right. And then you can you just have to select all and then click on clear all selected items. Right. That's what you can do. That's one reason. So it could be your internet. It could be your browser cache. These are the two common reasons that you are from DHS to side. It could it could be that the output that you are trying to generate could be too big and it requires so much of processing power. So probably your DHS to survey is keeping on processing you out. That's one possibility. And the other possibility is that your DHS to server may not have sufficient resources to cater to many requests. So too many requests could be like simultaneously if you have like multiple people locked in probably like this scenario that we are doing now, but it's quite unlikely like because most of these outputs that we tried to generate was kind of very, you know, like lightweight outputs, but that could also be a reason. So these are the four issues I can think of. So probably if you can clear the browser cache that might work because it happened to me once even today. And I and also you can even try to refresh your browser. Right. It's going back to the visualization. So I hope it is clear what we are what we are trying to do. We are going to be can only use in the event report application generate output, which is a line list type. Right. So let me open visualization. So let's click on favorite. Open. And we'd case based surveillance enrollment summary. This is the one. I click and open. And this is what I get. So let's focus on the left side. Here we see it's nine list. And the output type enrollment. So that means you are only counted once. Right. So let's go back to the one and what's the next thing. Whenever we mentioned enrollment. Okay. Open question for all of you. Whenever we mentioned line list and enrollment. One thing is a single enrollment or track entity instance who was having an enrollment is only counted once. And number two, what will happen if you have a repeatable stage. Anybody. If you have a repeatable stage, what will be the impact. Exactly. Very good. So it's the last event that is taken into consideration of that repeatable stage. Right. So let's focus what we have in this output. So we have the registration date, the symptoms date. And then we have the org unit. And next we have. Few. Tracked entity attributes first names and six. And then we have science and symptoms present or not coming from. And the underlying condition coming from one stage. And then a type of test, which is coming from the second stage. Right. The request. Stage. And then the lab result, which is coming from the third stage. And the health outcome, which is coming from the fourth stage. Okay. So here we have produced a line this. Pulling up data. Which are across program stages. So this is really nice. In case when you want to provide a kind of a. Person's health record. Which can span across multiple stages. So this is a really valuable feature. And something that you might encounter as really handy when you are, when you want to especially provide. Excel based output like an or is, if you want to export data out of this can come in handy. Only limitation is when you have a repeatable program stage. It'll, it'll count or it'll take into consideration the value of the latest event. Any questions. All right. Right. So. Let's see how we can design this table. So again, I'm going to. And then from this side, I will select the pivot table. Not pivot table. It has to be line list. And then the output type has to be not events. It has to be enrollment. And the data. I will select. Or with 19 K space surveillance. And next. I will select. I can select the first stage. I will just select the attributes and the attributes is going to be. We'll take the first name. So name and sex. And then from stage one, we will get the data elements. Underline condition. Double click. And then from stage one, we will get the data elements. Underline condition. Double click. And then. Signs and symptoms. Present or not. This is from the stage. I'm from stage three. We will get type of test. And the lab result. And. Stage four. We will. Obtain. The data element. I would come. So we have now selected all the attributes and data elements which are required to produce this table. Okay. And go all the way up and select. The law media, which is the country. That's it. And I click on update. Okay. So this is kind of an output that you can produce. In DHS to event reports, which spans across a couple of program stages. But here. Another question like, do you see? Like. One important information that is missing. missing when we are producing this kind of information right here and on set of symptoms. What else? Okay, like you will definitely encounter this issue when you are using this in practical scenario and like when your health department is requesting a crucial information and you are not able to produce it. So one thing which is missing here in this table is you cannot obtain the individual event date by default. There are like other ways of obtaining it through the API and all but here you cannot. This is one major issue because sometimes because we are looking at even though we are getting a snapshot like orders of one person's health record, the events that he has undergone in the across the stages may not have happened on the same day. So probably like his PCR test was done on one day and result was available on another day and the outcome was obtained again on I mean like maybe two, three days after. But that is not represented in this table. That's again one limitation and something that you have to keep in mind because if someone asks for that information, you actually cannot produce it in this table. But these are few areas that will be improved in time to come. So I guess that's it. So what I will do next, okay, first of all, are there any questions? Is everything so clear, I don't know. I'm happy if things are really clear but if there are any questions, please ask now or else you can always ask in Slack or chat. If there are no questions, what we will do is like I will quickly do a brief recap. It's just one slide presentation and then you can do the exercise number four and then I will open today's assignments for you. It's a graded assignment which has I think five multiple choice type questions that you will have to answer. I don't think it's not difficult at all. You just have to perform some activities and answer the questions based on the output. Okay, so let me share my last slide. Right, so a quick recap of what we did today. So we discussed about DHS2 event reports. So DHS2 event reports is a very useful application when you are using the DHS2 tracker because especially like this becomes really handy for the operational level. I'm not saying like this is not useful for the country level or the provincial level but for health facility level and probably at district level this can come in really handy because that's where they are worried too much about individual patients. So here we have two table styles in event reports. First is the pivot type which allows you to create aggregate tables based on tracker or event data. And then you have line lists which allows you to create line lists based on tracker or event data. And here we have two output types. We have event type output and the enrollment type output. Event type output shows data from all events within a single program stage which includes repeated events and the enrollment shows data from the most recent event and can combine data across all program stages. And we can only show data from multiple stages using a combination of line list table and an enrollment output type inside event reports application. In addition here also you can configure data based on the three dimensions what, when and where which is very similar to what you already know about pivot table. It's just that in the data dimension you have to do some additional configuration. You can also filter data when you are configuring data items in under the data dimension. And in addition you can also save the outputs as favorites and you can download these outputs as Excel or CSV. Right so that's it what we have for today. Are there any questions word of the day I have already mentioned in case you missed it. It's blackbird. Right so let me quickly open today's attendance. So you know today's attendance today's graded assignment so please few few few notices. Please give us feedback because we take them really seriously and we go through the feedback every day to improve better. So please give us feedback for today's courses that we did and then of course mark the attendance. Let me check whether feedback is open yeah is open for day three. The graded assignment for you shortly. Right the graded assignment should be visible now. So please give us feedback for day three before you leave. Yeah there's one question from Amit difference between program indicator and program attributes and between program sorry sorry difference between program indicator and program attributes and between program attributes and data elements. Okay good question. Program indicators is something new which we have not discussed today. We will be discussing about it tomorrow. But like because you asked about ask this question okay first thing attributes track entity attributes are are kind of semi-permanent or properties of the track entity instance. Right so for example the first name surname gender date of birth right. So these are kind of orders even the telephone number in most countries if it is not something that you change frequently these are considered as something else. There is something called track entity attributes and program attributes. So the difference is track entity attributes are something which are kind of I mean like very unique or something permanent or semi-permanent to that person. But in addition there may be again few properties related to the person. Which are somewhat unique to that program right. So for example say TBID is something unique but like it's not something that person has to carry along with him every time he goes across all the health programs right. It's mostly unique and mostly a attribute which is relevant to that program. Okay so I hope you are you have you it's now clear about what we mean by attributes. Data elements are variables or fields that we are collecting in the tracker program. So these are not kind of semi-permanent or properties of a person right these kept keeps on changing. So like for example data element could be a labored address result labored example type right these keeps on changing and it's I mean this is like when the track entity instance or the person undergoes his journey across the health program on different different days he has events and in that events we collect data. And this data we store in data elements right. So that's the kind of difference between attributes and data elements. So attributes are kind of properties these are permanent or semi-permanent data related to a person whereas data elements collect data about values which can always change. And program indicator so you must be familiar with what we refer to as indicators in aggregate right. So indicator is always we do a calculation. So program indicator you can simply think of a concept where we do some calculations based on properties of tracker data right. So for example if we want to select say like this data element and say we want to calculate I'm starting the sentence as calculate right. So that's the unique thing about program indicator it's always about calculations. So if you want to calculate a property say like females right and a data element who has received the first dose of COVID vaccine right in some areas. So say for example if I want to calculate the females total females who have received first dose of COVID-19 in Laos right. For this we configure a program indicator right. So that's a calculation. So what we actually have to do is like with that program indicator using the pivot table we can generate output okay. So this because you asked the question I mentioned but this we will be discussing in detail tomorrow. So don't get too much confused if you don't understand what a program indicator is. But I hope you understood the basic differences. Okay the word of the day. Yeah of course the word of the day I we have mentioned already is blackbird. Let me type it again here. Any other questions? Okay that's it. So please give us feedback. Please mark the attendance and please do the graded assignments for the day three. If you have forgotten to give us feedback or mark the previous days please do that. So that's it for the day. We will stay online in the Slack if you have any queries. If you don't have any questions so see you tomorrow at the same time. Yeah same time. That's 12 noon Indian standard time. Have a great day. Bye bye.