 So if we review our Excel sheet, we've identified our tracked entity attributes already, so you can see, you know, how this as a reference tool is quite helpful, right? We can just go to this and identify exactly what it is that we need to find or potentially create, okay? So if I go back to DHIS2, I'm going to go back to program, this whole screen here, and we have an option tracked entity attribute, okay? So before we were looking at tracked entity types, okay, and we could view them, we could add new ones, okay? If we look at tracked entity attributes, I'm just going to list them. You could also select from the left side menu here, tracked entity attribute, okay? But I'll just click on list or I could select from this menu here, and we get a list of the attributes that exist in the system. Now, once again, I've created all the attributes for you here because when you go to create the program, you know, that way they're all here. Once you create one or two, you know, the process is the exact same for all of the other attributes that you would make, okay? So what we're going to do, we'll just make a couple of these attributes, okay? I know there was some questions about auto generation of these IDs, okay? So I think Brian gave a resource about that, okay? And you saw, I guess you saw when we're entering data for the program, it was auto-generating IDs. So you can do one of two things generally for these with these unique IDs. You can either, you know, have it identified as a unique ID and grab it from maybe a national ID system, or people have maybe a health card or a national health or a national ID card or a passport. You know, some card, some way of identifying them, and you could enter that manually. You could also have a unique ID that is generated automatically, okay? Depending on what you need to do, all right? And then all of these other pieces of information, address, age, date of birth, first name, last name. They're pretty kind of self-explanatory in terms of what they're finding here, all right? So let's take a look at a registration number, for example, just to kind of go over some of the options that would be available if you were to create that. And once again, as I mentioned, you could create one or more IDs and associated with your program. So even if they have a national ID of some sort, I will still create a unique ID for that record separately that's automatically generated to find it. That's kind of user-facing so people can see it to see it right away. All right, so if I go here. So these are already created, so theoretically we don't need to make any more, okay? But I'm just going to make one to go through the process, all right? Same as before. Here, and I'll make a, I'm just adding my initials, okay, to the beginning, because I already have this tracked entity attribute in the system. I'm recreating one that already exists, right? So if I, I don't really want it to be the same as anything that already exists, right? I have a registration number here already, right? So I want to make it unique. So I'll use my initials just for example purposes. Generally, these tracked entity attributes don't have any prefixes, okay? It's just for demonstration purposes. Even if I could just make it different, it's unique just to give it a different name, okay? So we give it a short name, okay? Form name, hopefully this field is recognizable to many of you. This is what the person, the user will see in the registration form itself, right? So we're dealing with tracked entity attributes. This is going to appear in the registration form of the program, all right? So I could just say unique ID to call it something different, okay? I could give it a code, a description. If there's some, there's quite a few fields here. We won't go through everything necessarily, but just to get you in the kind of mindset of how these are made. If it's an option set, you can apply an option set. For example, sex is a attribute, okay? So you could say sex. So it's the sex option set here. The value type, many, many value types, okay? We'll refer you to the documentation, okay? I'll put our resource there so you can go over all of these. This is a unique ID. I'm going to say it's text. For example, it can be a combination of numbers and letters. Aggregation type, okay? Many aggregation types as well. Best source to review these are the documentation. This is a unique ID number, so this is not something that's to be aggregated, okay? But if it was something like a sex or something, you could say count, but it would automatically kind of default to the aggregation type here, okay? Now, there's these options here, unique, okay? So for example, I could say entire system. And what this means is when I make a unique attribute and I say it's unique in the entire system, it means that, you know, when I register somebody with this ID, only one tracked entity instance in the entire system can have this value, okay? So for example, if I'm using a passport number, right? There's only one person in the country that would have that passport number, okay? No one else would share that passport number. If you had a national ID, it would be the same thing, right? Only one person in that particular country would have that national ID if they're assigned, okay? If it's not unique, then you could have multiple values. For example, first name, right? It doesn't make any sense to make that unique because many people could have the same first name, okay? And then it would be kind of erroneous to only allow, you know, the same person or not allow people to register people with the same first name, okay? If I say unique and then I have this, when I select unique, that's where this automatically generated thing comes in. So if I select that, then I have to enter this pattern, okay? And Brian linked some documentation about the pattern. I'll just do an example of one, letters and numbers, for example. Okay, so just have a look at that documentation because there's a lot of ways pattern can be generated. All I'm saying here is generate a random string of x, x represents x represents a letter and the pound sign represents a number. So it's going to generate a random string of two numbers and four, or sorry, two letters and four numbers, okay? But there's a lot of things you can do with this pattern, okay? We're not going to get into all the ins and outs of this, but you can have a look at the documentation a bit more and I'll add some more links on Moodle so they're not just, you know, it's hard to find in the chat. Because there's several things within this that you can kind of refer to, okay? Some other ones that might be interesting, confidential, okay, this is for encryption purposes. You can encrypt these attributes. I'll refer you to the documentation on this one as well. There's a lot that you can do and there's a lot of implications of using this. Many systems, you know, don't use it because of the implications that exist. It's a bit limited the way it's implemented now because once I select it as confidential, I can't search. I can't use it to search. So, but it does encrypt it in the database. So there's kind of some pros and cons there that we won't get into now necessarily. Okay. So there's a lot of a lot of things that we can do here, but the basic premise is if I need to create an attribute that doesn't exist. I give it a name, right? I fill in some of the required fields that are marked with a star. Okay, I give it a value type. If it's, if I'm trying to, in this case, I'm generating something. If I'm not, I wouldn't fill in any of this information. Right. And then I would click on save. Okay. And that's the basic premise, right. But once again, all of these can be reused. Okay. So if I have a first name already, I don't need to make another first name. If I have sex already, I don't need to make another sex. So even though we're focusing on this TV program, if I were to go to make another program immunization, not communicable disease, whatever it is that I'm making. Okay. Anything that I've already created, or that already exists. Okay, I would not need to make again. And I noticed Brian pointed out in the chat, even that they're releasing a kind of metadata package that would give you these already configured. You could just install them on your system. Okay. And that might make it even easier for you. So you don't even need to make them initially from the start. Okay. So, but, but once they're made, you don't have to worry about recreating them. Okay. Because you really want to reuse, really want to emphasize that reuse metadata in the system. Okay. So I'm going to stop here again. Okay. And give you a chance to have a look at the track entity attribute management screen. Chances are many of you have done that already. But just to give everyone else a chance if they haven't. Okay. Give you about three, five minutes. It won't take very long to kind of get here. Right. But everyone should know where this page is, because you should be looking for track entity attributes that exist already. If they don't exist, then you should create them. Right. So if I were to create a more simple one, like first name. Without all this unique ID stuff, right, I'll just go through, fill in the information that I need. Okay, for this text. And then I could save it. Right. So just fill in those kind of fields that I need for that. And then I save it. Okay. So if I need to create something right and if you have a blank system, you might need to create something. If you're creating a new program, and there's attributes that are missing, then you might need to create something as well. Okay. So I'll stop here. And then if you go back to the learners guide, exercise three. Okay, it walks you through how to access the track entity attribute page and add them if necessary. Okay. So once again, if they're already there, you don't need to, but you should all know how to access this page. And if you do need to add some, it's pretty, pretty standard procedure in terms of adding metadata. Click on the plus sign, run through the fields, save your attribute. Okay. So we've created our option sets, we've created our track entity attributes, our track entity type. Okay. Now we can start to associate or create our data elements and associate any data elements that we need to. Okay, with the option sets that we've made. All right. So if we just check our sheet here, and we look at some of these data elements, for example, TV patient type has an option set of TV patient type. All right. So if we were to make that data element, the option set should already be there in place so we can associate our option set with our data element. Okay. So in order to do that, go over here to data elements in maintenance. Okay, so if you're at the front page in DHIs to you'd have to get into maintenance first. Okay, then from here we can go into data elements. Okay. And then similarly I can access from the left side, or just list them here. Right. Now that data element TV patient type. If I just type in TV, you'll see all the TV data elements. We have this prefix TV GC, which is TV treatment cards the name of the program. And we can see this data element is already created. Okay. And once again, when you're creating these data elements, you know I threw out this question yesterday about naming. You know we still want to follow those naming principles as much as possible. Okay, when we create these data elements. I often find, especially with these types you'll see here there's prefixes. So you'll see other data elements to MCMR, for example, there's data elements with prefixes. And you can see it's useful, especially in an admin context to filter out data elements that you need, because you can have hundreds of data elements, and it can become quite difficult to find. It's not really the most friendly for end users, to be honest, because they don't really care about the prefix necessarily right as long as you group things together in a nice way and make it easy for them to find. There should be other ways they can find it, but it does help administrators more in a sense. So we can add those prefixes and give them good data element names right so following these principles that we've discussed or hopefully you've had some, some exposure to in the past. All right, and let's just create the TV treatment type data element as a refresher. Okay, so I'm going to go ahead and click on the blue plus icon. Once again, these are already made right so you don't have to make them all for the purposes of this exercise right and this should be quite gets quite repetitive to create many, many data elements. So I'm just throwing in my initials again to keep it TV patient type. And then assign it a short name. We wouldn't normally have all these initials here this is just to kind of keep it unique. Okay. Color and icon. Once again, mostly for Android. There's a lot of fields here in data elements. I'm not going to go through them all. Okay, hopefully, we've had a chance to review creating data elements before right. I'm going to skip over these skip over quite a few, just to kind of get into the meat of this right. In this case, one thing I'm going to skip for name is a good one to add actually just to get rid of this stuff here at the beginning. Okay, domain type or always using tracker. Okay, in this case right if you're creating aggregate data elements and you're using aggregate data, the aggregate data element domain, but anytime you're dealing with events or tracker programs, you're creating tracker type data elements. Okay, so just keep that in mind whenever you're working with these tracker data elements that's the only really kind of key difference but if you've created an event program before, it's the same basic principle. Okay, you create tracker type data elements or the value type and the aggregation type this is actually an interesting one. Okay, what I'm going to do is I'm going to scroll down to the option set. Okay, and we're looking at the patient type so if I select the option set it'll actually automatically assign the data element of value type and an aggregation type, and I can't modify them. All right, this is because it inherits the properties of the option set. Right, so the option set is a text value and the aggregation type while you can't aggregate it in the same way anymore, because we're dealing with tracker data elements. We will talk about what to do with this later on right I saw some questions about things like program indicators, we will absolutely go over that in more detail later on okay. But when we're dealing with option sets. Okay, your data element will just inherit the characteristics of the option set that you've made. And you can see here at this category combination for those of you who deal with aggregate you can't modify it either right because you're dealing with the tracker domain. Okay. And then I'll just say, alright, that should be pretty straightforward, but that's why we create the option sets first. Okay, because when we go to make our data elements, we just select our option set it inherits the properties of the options that we've made, and we don't have to go back and forth between the options. Okay. So, right now we are at this place number six where we have created data elements with the domain type tracker. And next what we are going to do is to identify number of program stages in the program and identify if any of the program stages are repeated or not. We are going to identify potential scheduling of the program stages. So these three we will take together, and then followed by that we will actually go into creating tracker program. So, let me just try to recap our design. If you can recall the program design for the TV treatment card. We have this program which is the TV treatment card, and this program be identified that we have four program stages. So we have the first one which is initial diagnosis and face, followed by that we have continuation. I mean, in fact, two separate phases continuation one and two, and then the final program stage which is the end of treatment. So, like, now the question is like out of these four phases, which ones are repeatable, and I mean do we have any program stages which are repeatable, if not like why we don't configure it as repeated. So, the answer to this question. I mean to find the answer what we can actually do is to look at what are the data elements that we are creating that we are collecting in each of these program stages. So let me try to look at the different. Okay. So these are the different data elements that we collect in each of these program stages so you can see in the diagnosis and initial phase we are collecting data items such as the TV patient type that this is size. And the type of treatment sputans mere the result culture result, things like that. So interesting thing to note here is that now here in this TV program what actually happens is we are encountered with the patient who has been diagnosed as having TV. And then we capture the information, the data throughout his treatment period right so in the initial phase, as you can see here in the first program stage, we have a set of data items that we create that we collect, and somewhere between two to three months roughly around the day 60, we are going to see that patient again, and we are going to collect few few few more data items. So you can see the data items that we are collecting or is data elements that we are collecting on the first program stage, and the second one are kind of different. And when it comes to this continuation, which is around 150 days. Again, we are collecting few other data elements which are somewhat different to what we are collecting in the second stage which is around 60 days. Finally, when the patient has an outcome so it's probably patient is cured, but the time of course for the patient to get cured can be different so it totally depends on many many factors such as like if the patient is resistant to some of the drugs that we are giving to him. He may not ideally complete his his treatment period in like six months so they can I mean the duration can get can be longer. And you can also see that at the end of treatment, the final program stage, the data elements that we are collecting here are again different to what we see in the stage number two and three. So this is the reason why we have to have several program stages and because we are not collecting the same data data element in each of these program stages, we can make them repeatable. I just want to recall what should it was mentioning like one main reason for us to make repeatable program stages, for example, the initial example he mentioned around the about the antenatal care program. So we had this ANC visit in which during the antenatal care period, we are collecting same set of data. It's just that the time that we are seeing during the pregnancy changes but it's the same set of data that we are collecting. But in this example, it is not the same, and we are collecting different data items data elements in each of these visits. So this is one reason why we have to have multiple program stages and all these program stages are not going to be repeated. I hope that is clear. Right. So, now that we have identified. So now that we have identified the number of program stages in this TV program and the what are the data elements in each of these program program stage, whether they are repeatable or not, and also possible scheduling like I mean from the start date, how many days at which we are going to collect this data. So these these items now we are clear about that. So, the step number 10 is actually to create the tracker program. So if there are any questions related to what we have done so far, kindly ask them in the chat or probably or much better if you can ask them in the slack. So, my colleagues will answer them. Right. So, we are going to create the tracker program now so we are ready with all the metadata items such as the attributes, the data elements options that so we are ready with them and now we have a clear idea about how our program is organized. We know there's one TV program. And in that one we have four program stages, and these four program stages, all of them are not repeatable. And we know like the first program stage starts on day zero, and the second one is around two to three months, if you can recall the data that I should have demonstrated you before. So that means around the day 60 we are going to collect the data for the second program stage, and then around day 150 we have the third. And then we have the final program stage which is at the end of the program TV program. Okay, right. So let's try to create the tracker program so we are going to use the same program. The DHS to instance the customization DHS to instance, create this tracker program. Right, so hope you can see my screen. Oh, yeah. We are in this customization program customization DHS to instance. So in this instance you can see. So let me start over again. I'm going to select the maintenance. And then in the maintenance app. I'm going to select the program. So, if I click on this list icon, I can already see that we have this TV treatment card. TV treatment card is a pre configured program, but because of the user role, or kind of the permissions that we are having in this system. If I click on this TV treatment card. It will say that I don't have permissions to edit this object. That is because I mean we have configured it that way, so that the participants won't kind of alter the configuration. So what we are actually going to do now is to create our own TV program. I must also mention about one thing like now when we are when I'm going through the different options the features available in this DHS to maintenance app when configuring the program. Like, I will try to go over like the most the widely used features but there are like so many features and options available while you are configuring that that I'm not going to explain and go into detail. But what I'm going to do is I will share the link to the documentation with you so that let me copy and share it in the chat. So that if you have any questions like if you want more information about what each of these features in the maintenance app means, you can always check this document documentation and get more information about it. One reason I'm mentioning that it's very important for you to see what is there in the documentation is that like, so you might. What you will do is you will customize this tracker program today, but it's quite likely like if you are working in NGO or even in the ministry that you will not do your customization of the next tracker program for couple of months or even years. So it's quite likely that the configurations that you are seeing currently in this is to maintenance that might change in one year's time so it's no point trying to memorize what are the features that are there and what it but everything means so the best thing like what what we all of us we do is like we always try to refer the documentation so that we can get a better idea about what is available and and I kind of a and all the definitions right. So let's try to create the TV program. So first thing what I'm going to do is I'm already in this program tab, as you can see here, and I will click on this plus icon towards the right bottom of your screen. And once I do that, I will have a couple of options like it has with them going to create an event program or a tracker. So of course we are going to create a trackable. So I will create, I will click on tracker program. Once I do that, you will see that it's going to take us through series of steps, you can see like it starts from number one which is program details, and ends with the final step which is number six notifications. So we are going to follow each of these steps and in each of these steps we have to do some configurations in completing our tracker program design. Okay, so the first is to give our tracker program a name. So, because this program that you are going to create in this THS to instance is going to be a public program tracker program. It's always good to give it, I mean, have your initials to that particular program so that, I mean you are sure like which program you are. So I'm going to use Surajit's initials for now because some of these metadata was created with his initials. So I'm going to give it a name, TB, treatment card, and the short name also I'm going to use the same. Right. And there are some of these options which are there like which we are not frequently using and some of these things like colors and icons are kind of very useful if you're going to configure your tracker program to be used in mobile in the THS to mobile. And then there is this field called version. This is also mostly important if you're capturing data from mobile devices so whenever there is an offline data collection or whenever the capture application of the THS is fetching data or metadata from the THS to instance, it always checks the version number and tries to pull all the metadata from the THS to instance to the client device or the browser if there is any change in the right. And the next is I have to select the track entity type. So we have already created or configured the track entity type which is listed here which is person. So I'm going to select this track entity type person. Right. And then we have this option called display front page list. So what this mean if you can remember when you're collecting when we are collecting when we actually entering data in tracker capture application. We select the organization unit and we select the program and you if you might be able to recall that it displays a list of persons who are already registered in the system right that's the kind of default feature but for it to be default. How it works is we have to take on this icon here checkbox here display front page list. So when you do that the front page of the tracker capture application will list all the registered track entity instances. And then we have this option. First stage appears on registration page. So that means when we are collecting data using the tracker capture application. When we click on the register button, it will list out all the attributes. These are usually the demographic information and few more. These are the ones which appears in the registration page. But there may be instances where the first stage that we have in our tracker program will have some data elements which are kind of very related to the registration information that we are collecting. Right. So if that's the if that is the scenario that we are encountering what we can do is if we just take on this. It will include the first stage the first program stage also on the registration page. Right. But for this application, it is not relevant so I'm not going to select. The access level is something that we will we will cover in next week when we are discussing about the sharing settings. And then there are a few other options features available like for example completed events expiry date so that means like when an event is expired how many days forward. It allows you to enter data. We have these two features together one is the expiry period type and expiry date so that means like say for example, if we are in like 2021 October, and we configure the expiry period type as monthly, and we enter here the expiry dates as 10. So what it will do is it will let you edit the data from October all the way up to 10th of November. So if it is like the expiry period type is monthly it means after the expiry of the current month. So if you are in October so end of October it will calculate how many days forward from the end or the completion of the period. End of October means October 31st, and then we will count 10 days forward so that in November 10th it will be open to something like that you can play around with this features and see how they are behaving. And then here we have optioned minimum number of attributes required to search. So this again is a kind of a security feature so that we are requesting a minimum number of attributes so at least three attributes have to be entered in the search item. So if you mentioned three it is like at least three attributes are required to do a search and list all the track entity instances who are matching this criteria. And then we also have maximum number of track entity instance return in search so now I will just put a value like three now this again becomes a very handy feature because for example, when we are implementing COVID vaccination system so this is one practical issue we are having. So people try to list out so that I mean like because these are kind of like population registries that you have, there is a chance that somebody will try to list all the people all the patients available at the particular right. So that essentially gives gives them the ability to download a list of people from a kind of, I mean, if we have the access at district or sub district level, they can download entire population which again is a kind of a security risk as well as performance it is not good for the system so your system can crash. So to prevent that you can say like maximum number of track entity instances which are going to produce in the research so for example if you can fix it at 10. Even though like there may be so many people matching like it's only going to give you 10 of them. So what we are going to do next is now that we are kind of done with the stage one, we are going to do, we are going to move on to the second one enrollment details. So here, I assume you are kind of familiar with this concept of enrollment in our DHS to tracker data model. So we have the track entity instances, right, that we are going to enroll into a program, right. So here in this point, we are capturing information related to the enrollment. So again, like a lot of information features that we have here for configuration, but you can I have already pasted the link to the documentation you can read them and get a better understanding of what each of these means. For example, allow future enrollment dates means like we have to select the date of enrollment. So that the enrollment date with the we are allowing for a future date. I mean, that is what is meant here, but for this TV program, we are not going to do that. And then we have this future incident date. So again, like if you can recall like there were these two concepts enrollment date and incident date. So I'm sure like this must have been like you are you are you have some idea about these two concepts. So basically like what it means is the enrollment date, the definition of enrollment date is a date, a track entity instance. So in this in this scenario, a person, a person as in like TV patient gets enrolled into the TV program. Right. So that's the date that is defined as enrollment date. And the incident date is like kind of the date in which the reason for that particular person or track entity instance to get enrolled into this program occurs. So for example, let's look at a look at an example. So let's think of immunization program. Right. So if a childhood immunization program and we are going to kind of give vaccines to the children, less than one year. So for that fun, the date of enrollment is a date that the child is encountered with the health system. But again, like the date of incident or the incident date will be the kind of the birth date for that child was that I mean because of the birth only is getting this vaccinations. So it's kind of like depend on the program so you need to have a discussion with the program people also to determine like what would be the two. What would be the ideal dates you can select for each of these concepts. So for this, of course, the enrollment date is what is relevant. So we are kind of considering the date that we first register the person into our program. Right. But the incident date is kind of not relevant for this TV program but we have to like not relevant as it like what we can actually like if you are to define it. What would be the date that the person actually get symptoms so that because the patient has the symptoms. That is why the person is presented to the health system and he's followed up in this TV program. So in that sense, what we have to do here is we can give some labels, a description that will kind of replace the generic name of incident date when we are customizing the TV program so we will use the date of onset of symptoms. A description for the incident date and for the description of the enrollment date we will use date of initial visit. Right. And then we have also an option called only enroll once per track entity instance for lifetime so it's like if this is enabled that means a person cannot have multiple enrollments to a program so he will only be enrolled one time to this program but but in the context of TV it is not so because like you can have but you can get TV multiple times because a person who has kind of get enrolled in the TV program can get cured and he can get tuberculosis again so that is not relevant in this scenario. And then we also have a few other options some of you, for example the feature type and related program I'm not going into too much of detail. So what I will do is I will just so we have like steps from all the way from step one to six, but I will give you some time to practice this step number one and two by yourself. So I will stop here but before giving you the chance what I will do is very important to click on the save button. If you don't do that, the whatever the configurations we have done so far will not get saved. So simply click on the save button. Right. And once I do that you can see the program that I created a Cindy TV treatment card. Right with the configurations which I have done for the stage, the first step and the second. I need to configure the attributes but before doing that, I will stop here. And then what you can do is, if you can follow the exercises five, six, seven, eight and nine in the learner's guide. We can probably like I can give you around the 10 minutes to do those exercises, and we will resume in 10 minutes. So now we are in the final step in designing a tracker program. So the final one is to follow the stepwise approach to create the program. So in this we have multiple steps. The first is to enter the program details which we have already done, and the step two is filling the enrollment details so that is also now complete. And the step number three is adding attributes to the program. So that is what we are going to do next. As you can recall, we had the list of attributes that we use in this TV program, and this list. Okay now I think you can see the list so we have the registration number date of birth first name last name age, sex family address and phone number. And the attributes we have already configured. So there is no point in creating them again. Right. So attributes are already if in your instance, the teachers to instance that you are customizing if the same attributes are already present you can always reuse them. So let's move to the tracker program and try to include the attributes. So you can see the program that we have already created. And the program is this one, the TB treatment card, and I'm going to click and open the TB treatment card. Right. And then the step number one and two are already complete. And I'm going to click on the third step which is attribute. So here you can see the list of attributes which are available. Right. So what you can actually do is you can, like if you have a big list of attributes you can just select from that list and double, either double click, or you can click on one of them and click, click on this arrow icon to move it from this right. So whatever the attributes that we are going to include in this program are the attributes that will be in this box on the right hand side. So let me move these attributes in fact like the attributes that we have all the attributes that we are going to include in our program. So you can, in fact, move all of the attributes here from the left to right by clicking on assign all. But one thing that you have to be mindful is if you are not going to create a custom data into form, right, if you're just going to use the default form for collecting this registration data for the attributes, the attributes will be appearing in the form in this order. So you don't have to kind of alter this order if you want to do it. Say for example, age I would like to come here of the. So I would like to see the registration number then date of birth first name last name age, and then probably gender address and family and the phone number. Right. So, if you move down. You see here few options so all the attributes that we are using are listed here. Right, so probably we should be will not use this unique number that is not required. So we are seeing a couple of options here so display in this so if we select them these will be listed this will be displayed in the list of track entity attributes in the page so I will select registration number, maybe first name last name, age and sex. And here we have an option to make some of these attributes mandatory so that they will have to capture them during the registration process so for example, we don't want to let data entry people register people without any names first name and last name we can make them compulsory as well as the sex. So we have made them compulsory and we have option to allow future dates, and then we have an option to allow the attributes which are which which we can select them as searchable. Okay, so. Once I will just keep everything as it is, and once we have we are done with the attributes, we can either proceed to configuring the program stages but what I'm going to do is I will save this. The program configuration as of this point and give you the opportunity to do the exercise number 10, which is about configuring the attribute so I will click save button here. So probably you can take around five minutes to configure the attributes so we will start, we will come back in like five minutes time. So let me go back to the slide about the overview of arrangement of the program stages in our TV program. So if you can recall, we identified four different program stages in this TV program so we have diagnosis and continuation one to end of treatment. So, if you can also recall like the data elements that we are capturing in each of these program stages are different, and none of these program stages are repeatable. And when it comes to scheduling, we will start the first program stage on day zero, and then the second one we will schedule it around 60 days. And then the third around 150 days, and this end of treatment, we had actually scheduled a particular date because in this series of events, or once the patient is following this TV program longitudinally at any point of the time he can reach this end of treatment phase. So depending on the treatment, the different treatment protocol, the time in which the person will complete the program will vary. So that's why we are not able to schedule a particular date for the end of treatment, but you probably have now a good idea about how the different program stages are organized in this TV program. So if you don't mind, let us move back to the configuration of the program. So, I will open the TV treatment card program right now. Okay, and we are, we have completed the step number one the program details the enrollment details attributes, and now we are in this, the step number four which is the program stages. So here what we are going to do is we are going to create all of this program for program stages so to do that what we have to do is we have to click on this plus icon that you see here. Click on it, right. And I have to start entering data for the first stage so I have to give the name. So I will give the name diagnosis initial face. So, once I do that, there are a few, there are again few other options available, especially when you are these colors and the icons which are quite important when you are trying to visualize or collect data using the mobile devices, but we are not going to configure them now. And then we have to enter schedule dates days from start. So this diagnosis and initial face is in fact is the first is the stage that we are collecting data for the first time so for example if a patient is presented to our TV program we are going to register that person's information their attributes and then we will probably enter data for this first stage as well. So, because of that the schedule days from the start I will put as day zero, right. And I'm not going to check this repeatable icon so if I check this repeatable, then it will make this program stage repeatable. So you can have multiple events so like this program stage can be repeatedly collected over different days. But in this case, it doesn't make sense to have multiple stages for the registration. So for the diagnosis so I'm not going to check that. Right. And then we have this option display generate event box when completed. Right. So that means like if you if you have this check that means like once you complete this particular event so once you complete entering data for this diagnosis or the initial phase. And then you click I mean after you have entered all the data for this program stage and you click on the complete button at the bottom, we will again show how this works when we are entering data. So once you click on the complete button it will prompt us to generate another event so I'm not going to check this I will just say keep it unchecked. And then we have this option auto generate event. So when this option is checked auto generate event what it means is the moment we enter the registration information or else the attribute information and we click on save and continue. It will automatically open the first event or the event or it was like data entry for this initial diagnosis stage will be open for us. In fact, like that's kind of very easy for us if that I mean this event is generated because this is a kind of event event that everyone is going to have. So I'm going to have this checked auto generate event. And then I will also have open data entry form after enrollment check so that once the event is open we are presented with the data entry form to enter the data. Right. And then there are few other options that we can select like allow user assignments for events meaning like if you want a particular user who is registered in our system to be assigned. So that that particular user will be assigned to take care of this event, the particular stage right so that is why we have it so here I just keep it unchecked. And then you have another option they have block entry form after completed meaning like when you complete the event it will block the data entry fields so it will kind of great the all the data interviews will be created out so that nobody can change this. Nobody can enter the enter data so I will just keep it unchecked for the moment. And then there is option ask user to complete program when the program stage is complete. So if you have it checked that means like follow I mean after this program stage is completed, it will prompt the person to complete the program so we are still in the first program so we are not going to check that. And then ask user to create new event when the stage is complete so I will just check that. And then the events. The next option is to generate events based on the enrollment date. So, if you can remember, we defined the enrollment date, which is the date we register the person need the patient into this program right so that is the kind of day zero. So we want all these program stages to be generated based on that particular date. So because of that we are going to have this checked. And then we also have this feature called due date. So, all the program stages or else the events in DHS to have it. I mean like we can configure a due date this becomes very important for example in programs like vaccination where we always schedule the next date. So in this, I can I mean if I'm not using it I can actually hide the duty. And then there is there are two fields here down at the bottom description of report date and the due date so for the report date I'm defining here the label that should appear so I will put here the date of visit. So, once this is done, we are done with the stage details. The next would be assigning data elements so if you can remember, we had this four different program stages. So, what we have done here is to define the name and the details related to this first program stage. The next would be to assign what data elements are required to be captured in this first program stage. And here we'll have to select the program. I mean the data elements so we have many of them so I'm going to kind of filter. So I will start typing TV. So now I will see like these are the ones which are available for the TV. So I'm going to select all of them like this and then click on this button here so it will go to this side but I'm I also want the weight which is not displayed. I'm going to select this weight in kg and double click that right. So now I have all the required all the required data elements for this first program stage onto this right right side box, right. Okay. So, then I just moved down and here we can we have few few options. For example, we can make them compulsory and this allow provider elsewhere means like if we want to allow the data to be captured in a different org unit. Not the same org unit we are capturing this event. So that's why it is there. And then we have few other options, especially these options like render type is really helpful when we want to have different visualizations in the in the capture form in the mobile devices. So I will make a few of them compulsory, like the TV patient type, and then the disease site, I will make it compulsory, and then the type of treatment. Right. And also I will make few of them available in the reports so for example I will make the TV patient type and then the disease site and type of treatment, and then the sputum smear and culture result. Okay. Right. So, now we are done with the first, which is the stage details and then assigning data elements to this stage. Okay. So the next step is to create the data into form to collect the data. So I'm going to click on this number three, which is create data data in reform. So here we have a couple of options to create the data in reform. So we have the first option is basic. So here we will have all the data elements kind of selected which are listed in a in a plane design. Then the next is the section. So section is the one we usually prefer when we are designing most of the TV program so here what we do is we are able to put. We are able to arrange the data elements in different sections, which is kind of similar to what we have in the data entry, the forms the paper form so this is kind of a very nice way of making the data data collection forms look nice. We are in fact like today going to configure the mass section forms the custom is you will have to you will get you will have a separate. So let me click here. So you have this interface it's a specific editor where you can kind of even include HTML right and kind of create a very colorful vivid data collection form but one issue that you may have is if you configure custom data collection form it may not work that well in mobile mobile devices so if you so that's one reason why we always opt for that section forms because it works seamlessly on the mobile as well as well. So, hope you hope you can remember the different sections but let me share a slide again so that you can quickly recap how these sections are arranged. So these are the sections that you will see in the first first stage so we have the same we have a section for the type of patient, the disease site and type of treatment for initial phase, the speed, the speed of examination resource and the way. So what we are going to do is to configure these five sections and then add each of these data elements to the relevant section. So let's do that now. I'm going to click on this add section to form. Right. And I'm going to add the first section which is type of patient, right. And then I will keep the rendering type as the default, right, and I click on add. Next I think I will add all the sections first and then assign the different data elements or the next section I need is the disease site. Add. And then type of face. And then the next section is. Extermination. And we have another stage which is so we now have this for each of the five stages and now what we have to do is click on each of them. So once I click, you will see that when I click. There is this black color highlighted line that appears around this box right so when each of this section is clicked, you will see that it is getting highlighted like this. So what I'm going to do is I'm going to click on this first one, which is the type of patient. And then I have this list of data elements on to my right side. And I have to select the appropriate one and click on the plus button. So, here for the type of patient, what I'm going to do is I'm going to add this data element, the TV patient type. So to do that what I have to do is I have to click on this plus button, and you can see how this is grayed out and the patient type is selected and it's included in this section. Right. And then for the disease site I'm going to add two of them. So the first would be the TV disease site, and then the next would be the EPTP site. And for the type of treatment for initial phase, I'm going to select the type of treatment and then sputum examination results. So I'm going to select sputums mere result. And then culture result. And the gene expert result. These are selected. And then finally, the weight. So here I'm going to select the weight in kilograms. So now you can see that all the five sections have been configured and the relevant data elements have been added to each of these sections. Okay, so our section form is now ready. But what we again have to do is to click on this at stage button so that it can get saved. I'm going to click on at stage button right so we are done with the adding the first program stage but then for us to save it actually the entire configuration to the to the existing method of the program we have to click on this save button. Then only the program stage is actually getting saved inside this program configuration. So if I open it now, you'll be able to see when I go to the program stages, this first program stage is saved. Okay, right so let me quickly add the second program stage I'm also aware of the time so I'm what I'm going to do is I'm going to add the second program stage, and probably I will stop then give you the opportunity to practice, and then in the meantime we will try to add all this for four program stages during the exercise okay right so let me try to add the second program stage so for that what I'm going to do is click and I mean under the program stage details I'm going to put continuation one right. And then, if you can remember, like here we are going to see this patient around two to three months time so means like from the date of enrollment, this patient is going to be encountered in around 60 days right so I'm going to sign, put the value 60 in this box right and then we will put photo generate event, I will put, and then we will also put as user to create new event when the stage is complete and generate events based on the enrollment day. So these are the ones that we are going to put, I mean like, so I slightly changed the configuration that we put the previous form so that we can see how it is going to affect the final look and feel of the data collection for okay. So we also need to add the description, the description of the report date which we will put as examination date. And next we are going to assign the data elements. So let us quickly assign the data elements. We will add the type of treatment. And then sputans mere result, and then culture result, and of course the weight. So, once those are done, I will make all these three compulsory, right, and then we want to create data entry form. So here, again we have three sections the first would be the type of treatment for continuation phase and the sputum examination result and the weight so I'm quickly going to add the, the three sections if you if you don't remember we just kindly refer to the our design document where we have mentioned all the different sections. So I'm going to create this section here. The first is then weight. I'm going to add for each of these sections the relevant data data elements so for the type of treatment continuation phase I'm going to add type of treatment. I'm going to add the sputums mere and the culture result and for the weight going to add the weight in kilograms, right, and I'm going to click on at stage right so we have this continuation one also there. I'm going to click on save. Okay, so what I will do is I will just stop here and give you the chance to create the remaining two stages along with the first and second stage. So we have the instructions in the learners guide so probably we can take a break off around 10 minutes in that 10 minutes try to configure all the, I mean, as much as possible the program stages, and then after the break, we will start with the last section which is about the access control and sharing. So I'm going to stop here and give you the chance to do the exercises. So we are now, we have designed all the program stages so in fact I designed the program stage number three and four. So, only difference is like when you are configuring the stage number three we have to put the schedule days from the start as 150. It's just, it's quite similar to the second program stage. And then when it comes to the end of treatment. The only change I did was I'm asking user to complete the program. Once that stage is over. Right, so those are the two main changes, and you are configuring the stage three and four. So, the next stage is what we have I mean in that stage, stage number five is about access. So here we are kind of defining two levels of access. So the first is about which organization units in our DHS to system is going to have access to this program. You can remember the three main dimensions in the DHS to so organization unit is one main dimension. So here we are going to define like at what or unit level organic group. The data entry users will going to have access to this TV program. So what we can do is like for example if you are going to assign it to all the facilities we can select from the organization unit level facility and click on select button then it will select all the facilities or else if we just want to assign to one of the health facilities we can just pick on one of them like this. But what we will do is we will assign to all the facilities so when I click on select button here you will see that all the health facilities in the entire training land have this program assigned. So that is the first type of access that we are creating right. And then the next is about the roles and access so this is about a concept for sharing settings which we will discuss in detail in probably next week. I mean there we will talk about the access controls as well as sharing settings but what I'm going to do here is like I'm going to assign which users or user groups are going to have access to this program stages to wave data and enter it. So I can see here if I click on this send a TV card TV treatment card if I click here you will see right now the public access is there so if I click on this and I can. You will see the metadata has can edit and view access and the data has no access so what I'm going to do is I'm going to disable access to the metadata for public so I'm going to create the public no access and for data no access so that means right now. Nobody in the system can actually enter data or leave the metadata right. So what I'm going to do is I have to kind of define who is going to have access. So to do that, what I'm going to do is I am going to click here at users and user group. And here I can start typing the users or whatever the user group so we here we will define whether an individual user is going to have access or if we have created user groups in our DHS to system. So user roles user groups we will be discussing more about it on Friday. So that's why I'm not going into too much of detail but I will just assume like for the moment I will assign this this program to myself so that I can enter data. So what I'm going to do is I will select my user here, which is this one private test, right. And once I do that, I will, for this user. Metadata access is already there, and I'm going to give data access for capturing and view. So once that is done, I click on a play button, right. Okay. So the next thing is like, you will see some exclamation marks here right that it differs from the program so this, the changes I have done. So you can see here public public access and accessible to one user. So we have to make it apply for all the program stages. So here, all have been selected I'm just going to click on this button apply to selected stages. So now you will see the same sharing settings that is like no public access and access for one user has been assigned to all the stages, right. So once that is done, I can click on save button so that we are kind of almost done configuring the program. So the only section that we did not cover today is about notification, but even without notification we can actually start entering data. So I'm going to click on the save button so that all the basic configuration that is there for this program is kind of complete. Okay. So I think now it's the time to see our program in our data entry screen so what I can do is I can click on this app so I can hear and open, but and one more thing like it's always good practice like if there's any like, for example if you have been configuring the data, it's good practice to get rid of the browser cache to avoid unexpected, you know, like sometimes you may be expecting a particular metadata to be visible in the data entry form but if it is not that one main reason why it happens could be due to the browser cache. Just give me a minute to figure out my caching issue but till then, yeah, I will try to use incognito but but you can do till I get this sorted these two try completing the exercise number 12 and 13 in the learner's guide just give me two minutes I'm going to clear the I mean, close my browsers and then open and get back to entering data. Emma, maybe I can just show it. Yeah, please. Just so we can. Okay. Yeah, so this is the program that he made. Okay, I'm in the same system, same program. Okay, you can see that it's the same configuration that's there. It follows, you know, all the steps, basically that he's outlined in order to create this program. Okay, so after you go through all those steps and there are many steps and we lost about half the group. I'm somewhere along there we will review this in the morning, these last two steps that he went through regarding sharing or signing the organization units, and sharing the program. Okay, and we will review those I know I'm sorry we are a bit of a time but you can see there's a lot of steps we have to go through before we get to this final stage. Okay, and once that's done, you can see here here are the attributes that he's configured in the same order if you remember it's been a little while, but sometime ago he used those up and down arrows in order to configure these attributes in the order that we see here. An incident date we see here an enrollment date. I'll just make the incident date a couple days back and in this case we're not generating the registration number we're entering it in. We have a date of birth. I'll enter just enter in a sample individual these ones marked in red, these are the mandatory fields that he had selected. Okay. Save and continue. Okay, then when we go into the program, we'll see the stages and you see they're scheduled. Okay, and these are scheduled based on the periods that Pam would entered when he was creating the program. So we have this one here at 60 days this one here at five months, okay the equivalent of days from this first period, you can modify the days of course if you deliver that service on a different day, but the whole idea is to provide some idea of when these are supposed to happen. We don't see the end of treatment stage because this stage is not created automatically. Okay, and it's not scheduled. We can add it in. If we go to add in the stage you'll see it here and you can add it in. Okay, so if the person dies prematurely for example, lose them to follow up or for any other reason, that's part of the classification of the end of treatment, you could add in that stage. So in these stages you'll see the sections and you'll see the data elements that he's added to each of these sections. Okay, so you'll see here these are the ones that he's added in. See the options that's tied to those data elements that we discussed earlier. Okay, so after you've gone through everything, you can go to data entry, and you can look at the program that you've configured, and you can kind of get a sense, whether or not things have been made correctly. Sometimes you might not have to wait to the end. Okay, for example, if your program has several program stages, and you kind of want to see what it looks like, you know you've made one stage maybe, and you just want to kind of get a sense of what it looks like. You know you can go into tracker capture and view the configuration and kind of see does this reflect what you want, and then you know make some modifications based upon that. Alright, but eventually you'll have to go through this entire process in order to get here. It's kind of a longer process. And for bigger programs, like we didn't even create the option sets and you know those are all made for you can imagine if you have to kind of do that on your own, can take a bit more time. You know, there are tools and other types of ways, we can theoretically get this in quicker, you can import things for example, we have these metadata packages which are kind of preconfigured tools for you to use as well. So we'll just send discussion in that in chat earlier. Okay, so there are ways this can be done but we've just gone through the whole process to understand from start to finish, you know all the different components that are required to kind of get here. And this is just the kind of basic baseline right, we have our program configured, but there are a lot of other steps people have been asking about things like program rules. We've been talking about things like indicators right, there are other things we will add then to this configuration as we move on. But I'm just going to kind of pause here. Okay, because we've already kept you about half an hour over time. I do sincerely apologize for that. Okay, we're going to stop here. Okay, you can go through and finish the exercise if you would like. You can do it, you know, maybe tomorrow, even if you're a bit burnt out at this stage. Okay, we will review these last two components with the rest of the group, just to make sure everyone's kind of caught up. But once you're here, you know you just can kind of interact with the program, make sure everything is appearing exactly as you said it, you can see in this case you know everything is exact to panel specifications right you can see the stages the data elements, all the options that are always tied to those, everything's kind of functional. If it's not it's okay though. Okay, that's one thing I do want to emphasize. You know nothing's going to be busted if you just do it wrong the first time and then realize you have to fix it. There's no problem okay. People often you know I still make mistakes when making this configuration all the time. It's not a big deal right you just go through and change it it's not to not going to cause any major problems. If you if it's on a production system and there's other things happening then that can be a bit more problematic, but if you're making it for the first time just testing it. No problem right you can always go back and fix your mistake right it's not kind of mission critical to get it all right the first time. Okay. So, as Pam mentioned you can have a look at that exercise, you know, either today or tomorrow, depending on kind of where you feel you are right.