 Hello everyone. Good afternoon and good afternoon and a good evening for those who are, the time is a little bit late. I hope you can all see my screen and also hear me quite well. Yeah, so I'd like to start by welcoming you to this second day of our TrackerUse level one webinar where we are going to look about DHIS to attract, you know, a little bit of an overview and features updates and what we have updated in the new versions, but as well as we'll touch upon a little bit about the features which we are looking about to kind of incorporate within this particular application. This session will be for the next one and a half hour to two hours, but we'll split it up as I just said halfway where we'll stop. Here what you have your reaction from the presentation and we encourage you to kind of post all your questions in the Slack and when the times comes when we kind of break a bit, you could actually have the time to actually pose that question and our facilitators, a team of facilitators here will be responding to these questions. So, by the way, so basically our objective for our particular webinar today is about to describe what is DHIS to Tracker. We hope that you had before attending this TrackerUse level one academy, you had time to go and attend some of the online Tracker Academy which we have. So you have the basics of the DHIS too. So here we will try to be more specific on describing what is DHIS to Tracker, understand how DHIS to Tracker can be modified customized to fit your particular context needs, and give a little bit of examples of how DHIS to Tracker is used. And I think for our first webinar which we conducted yesterday, you had time to actually see different use cases of how this DHIS to Tracker has been used and this is only specific for Tanzania, Uganda, Rwanda, Malawi and Kenya, but and those were just one example from each country but there are so many use cases where DHIS to Tracker has been used. And then of course we'll describe along the way, some of the features of DHIS to Tracker, which we have available. So DHIS to Tracker overview. So DHIS to Tracker allows you to collect and analyze identifiable individual longitude data. So DHIS to I think we all know stands for district health information software to start with collecting aggregates data, however, as it involves it started also to correct individual level data, where you can collect these individual information and analyze it using a set of range of tools available within the DHIS to. However, you know, as you track this information you could actually decide that this information I want to track them through longitudinal events where this particular case or patient is living through. So for example, if you have a child being immunized, you would want to try, you know, being vaccinated you want to track that particular child through different stages when the child is born, the set of doses, the set of immunization which will go through the second visit, the third visit, etc. So we'll be tracking that particular child across different stages and set of information which will be tracking which could be similar or different from one visit to another. So there is how DHIS to Tracker kind of comes into allow for collection of visa individual identified individual longitude, you know, data. That means of course you can create a unique set of, you know, unique and shared records that can relate as I said several services to that unique record you attract particular tracking and as I can give you as I give you the example for that particular child being immunized into different visits. Now, this is just a summary of the tracker features which are DHS to track features to be exact, which offers. So for example, the tracker DHS to track feature track allows you to schedule visit for various services and sending automated reminders based on these schedules. So for example, I shared the example for a child being immunized through different visit. So you could actually schedule for this visit and luckily enough you know exactly these visits are scheduled within different weeks. So you can schedule that the next visit should be X number of weeks. So the client could receive these automated reminders to either SMS or email. Then the DHS to tracker could also help you to track miss or end upcoming case so they can. For example, healthcare workers they could actually know the children going on with a similar example again, can know exactly how many children who the child who has missed a particular visit and also know exactly that how many children are expected in the coming day are based on the schedule visit you have. So those DHS to tracker can help you also create reports displaying both individual identifiable information which we have captured, as well as aggregate data. So this is kind of one of the powerful functionality of a DHS to track and DHS to in where you can capture your information at the individual level, but you can analyze information both there at the point of service of the individual, you know, monitor the clients who you are servicing, but as well at the programmatic level where you can aggregate this information and and inform some of your. Indicators monitoring. Since somebody's. Can we all have our mics muted. Thank you. And then DHS to trucker can support also data quality functionalities, as well as decision support during data collection, that is, if you have any logical pro logics through your data collection skip logics, then DHS to can accommodate those skip logics to allow you a more robust process of data entry and you know, limit errors that are that are that entry errors. Of course, that means your information becomes more of a high quality, and of course, you know, supporting the information use processes. And as I said before, you can also use DHS to trucker to send notification a lot based on the data within each individual event so for example, if you have collected a particular information. Right now we have a huge case I think yesterday we had a use case where we are talking about cove in 19 certification vaccination. When you you are vaccinated you are fully vaccinated. The information is entered into the system then you know, there, there could be notification or a lot schedule, generated to inform a particular individual particular client that you know either your certificates already you can access them, you know, at a certain position certain location, etc. So these are notification a lot based on the data which has been entered into a specific event within DHS to trucker. So that's, that's on the data entry that a collection but also you could, it supports also the analysis part and this, this is where it gets more fun. That is you don't only use this DHS to trucker to collect information but rather also to analyze the information which you have collected. So you have collected your information at the individual level, but these information can be automatically aggregated based on the pre defined parameters through your either program indicators, or through these DHS to analytical tools. This is something which is very powerful in terms of you know within the DHS to trucker where you can have these information as quickly as possible, you know from the individual level to the aggregate level. And then of course you can, you can both have these individual aggregator the doctor can be viewed in these are different DHS to analytical tools, you know, such as dashboards tables charts and mark the variety of analytic analytics tools which are there. It's you, and you are you know system of administrator system of our users who can configure these things, make sure that you can view this information. You know how to fly. And also, you can also the DHS to trucker can also support exploitation of these data to any analytical platform of your choice, you can download these data through common format for example, you know CSV files but you can also see how you can explore this information through a different mechanism. So when we talk about, as I said, DHS to truck, you know helps you to collect your individual level data. So when we go to an individual level data, the aspect of privacy is is is a concern. DHS to allows you or contains these granular sharing settings that allow your system administrator to define which organization levels, which user, which groups, which individual users or which user groups can, you know, can ask access specific kinds of data stored within the tracker program. Later on in our presentation and we'll kind of display or show you a little bit of that aspect where one can either view a particular record but not you know into this information. The other one could not even register this information within the track. So these are kind of a set of I would say sharing setting or access level, which DHS to can be customized to allow that only individuals who are supposed to view a certain individual level information can view them only individuals who are supposed to create or register this information they can, they can be able to register this particular information so that's that's something which it's quite important when you are dealing with individual level information. Also, hosting of DHS to instance is handled by own organization who define the own parameters of data storage, you know, depending on local laws and privacy concerns or if your organization for example your Ministry of Health is comfortable to host DHS to instance within the organizational data center then it's fine if it's they're hosting it within the national data center that is fine but also if it's hosted on the cloud that that is something which the own organization needs to make a decision on where do we want to host our DHS which will host an individual data and even if you host it in the cloud national data center or within your own offices access access to this particular database and the data that itself within will be limited to who you provide access to. So, this is something which is very important to kind of underlying this that the own of the database is you, the person or the organization or the institution which is, you know, hosting this database and running this database. Now that means that you might need to make sure that you have a clear SOP to make sure that you know who access what and when and etc. So those are very key aspects. Then of course, you know when you decide to host this DHS to trucker. The configuration of that is, is others could say pretty much straightforward but other to be could also have a different opinion. However, the DHS to team or the his team has kind of come up with approach where you can have a number of standard digital packages, you know configurable digital packages, which can be as a starting point of starting, you know, collecting certain particular information so for example, the his community has been working with these are global international organizations such as to ensure to establish these standard packages for example for malaria for immunization malaria TB HIV, and also for immunization, where you can you can have a set of, you know, predefined metadata ready to be imported or inserted within the your DHS to instance, to start running those start collecting those information, but following the standard international standard which has been set there. Of course, if your country or your organization has deviated a bit from the standard data collection processes, which have been set there, then there might need to be a father customization of these particular packages. So some of the international partners which the his network has collaborated to customize these standard digital packaging for the show as I said, CDC, UNICEF, Gavi, etc. So that's, that's, that's one way, but of course, if you have a use case which is quite intriguing and you think that this is, you know, oh at least you know there's something which is you want to use a use case which you want to use DHS to trucker then feel free to reach to the network and, you know, explain your use case, believe some of the people within the network might help to advise you how you can configure that. So, where we have come from and where we are so far. I said before DHS to started as an aggregate system collecting aggregate data, but I did both to collect individual level data and currently we have over 75 countries, including and Indian states, which are using DHS to track and as the graph there shows, there's been in recent years, I think five to six years ago there's been a huge kind of push to to collect these individual data and as you can see from 2015 2014 2015, then the kind of the graph kind of started to rise up as more countries started to you know explore the possibilities of collecting individual data individual level data using DHS to trucker. Even if your country is have deployed DHS to aggregate, then there's a huge potential for you to also scale it down to the lower level where you can also collect individual, you know, individual level data. There's additional software platform to engage with of course it might need to, you know, a little bit of customization to fit to that particular use case which you want. Of course, some capacity building and support, but as I said before, if you're using aggregate system right now, feel free to reach to the community where, where you can be advised on how best you can scale. This presentation from the aggregate to the individual level and as we see there's a huge number of use cases there are a huge number of users who are operating that DHS to trucker. So, in summer there are several co apps features related to DHS to trucker on the aspect of data collection. The presentation will be covering, you know, some of the tools, for example, capture up tracker capture and also these are two apps caption track capture these on the web. But also, we have also a mobile and capture up which mostly allow us to capture information. Then of course for the output analysis and we have also, you know, different DHS to abs features for example charge tables. Maps dashboard where it integrates different analytics tools to allow you to view this information in one particular place, not that you know every release of DHS to involve updates of these particular tools. And so what we're presenting here is, you know, the features which you can see in the very latest DHS to version. Yeah, so you might see something here which is not maybe, you know, accommodated in a DHS to trucker of a previous version. So that's something which you should know then of course as I said before, later we'll also discuss some of the features which we want also to incorporate in the future in the future DHS to trucker. So, I'll jump straight to the start with the data collection processes will start with the capture up. I hope you are familiar with this capture up this capture up has evolved through a number of iterative processes. Right now, this particular capture up is able or facilitates can can allow you to register new tracked entity instances and enroll, enroll them into program. So I think this is quite a revolution where you have one this capture up where you can, you can include, you know, you can register a new truck into the instance. So for example, if I give you an example of a child child organization program, where you want to modern monitor these children through different visit. So you attract entity instance will be those, you know, children will be monitoring them through specific visits. So this capture up allows you to do that previously, it was, you know, registering only invent base data, but right now it come registers also a new track entity instances. This app can allow you to search for track entity instances, and of course, list and filter track entity instances in track program so this is kind of a putting your track entity instances or your individual level information into one up where it's possible for users to capture this information, regardless of a program or type of program which we have it's that program. It's, you know, tracking clients longitudinal, or if that particular program is only based on particular one event. So, this is a one feature which we the latest features which we want to discuss is this integration of events and tracker data capture like I said before the capture up previously was only capturing the events. For example, if you have a program monitoring, you know, mortality, you know, for example, death. For example, this year we have in patient will be doing mortality, you only registering that particular patient or client once. So once they come to a service point of sevens, you record okay. This particular person has come. He has either if there's it's about mortality, then you say that okay. Time of death, you know, cause of death and etc. All this information, and of course the personal information of that particular person. So you don't expect to record additional information, you know, or you have another visit of that particular person if that person is, has faced some mortality issues. So that's a more or less event is more or less kind of collecting individual level data, but you're collecting it at that particular event. However, you know, previously, like I said, capture up was capturing this information, but now it has shifted to also include or integrate to capture also the tracker, the tracker or the longitudinal data which you want to monitor and the example which I gave you was for example child program where you want to, you know, monitor this particular child coming to a particular facility, and you want to monitor that particular child through different visit, you know, getting different immunization or vaccination. For example, BCG, you know, OPV, little measles and etc. So now within the DHS to capture up, you can both have a program which is an event based and also program which is a tracker or tracking and information longitudinal through different visits. Then of course, the capture app is now accommodating pattern based ID generation, this is something which data has been requested for a long time where you can have a pattern based ID generation where when you are registering a person you can customize your app so that you can, you know, generate a unique ID for that particular patient or client, but this particular unique ID can should follow a specific pattern so based on certain criteria or parameters which you have kind of identified. So this is something which you can configure within the DHS to capture up here as you can see in this particular example where you enter or you are starting to register, you know, your tracking instance or your patient, your client, and then the unique ID, you know, generates here based on the parameters which you have specified. Then of course you can, the capture app can also help you with a duplicate detection during the data entry during the registration. This is quite important because you know you can, you can actually enter information of the patient, a client and then that particular client is already registered within the system. So the DHS to capture can, you know, when you're registering, it can check based on the information which is existing within the database and then I give you a notification. For a possible duplicate and of course ask you if you want to proceed or of course if you want to, first of all if you want to view to confirm the duplication and of course if you want to proceed if you think the duplication, there is no duplication in the information which you have registered. Okay, so that was the DHS to capture app. Then of course, we'll talk a little bit more about DHS to track capture app as well. So as you can see here on my left here there's a track instance dashboard and track entity dashboard which kind of displays basic information of this particular person So once you register, you register or enroll, when you enroll the particular person to a particular program at a particular health facility, then this dashboard, the individual, the track entity dashboard becomes available where you can see some of the basic information of that particular person, but also you can also continue with managing or monitoring some of the indicators, which this particular person has, but also you can manage the data entry processes and also view some of other features which I'll talk about a little bit. Yeah, so this is this is the track entity dashboard as you can see different information for example here, it shows the enrollment information which I said so it tells you, you know where this particular client or patient is enrolled, when was the enrolled you know if there's any other programs for example here. You can see that this particular program is also enrolled in another program so here at the top you'll see of course the name of the current program the COVID-19 for this case the COVID-19 case based surveillance. But of course you'll see that this particular person is also enrolled in another program as you can see it here of course here on the right there's a profile where you can see basic information of that particular track entity. For instance, but you can if you want to view the full list you can actually toggle here, click the edit and then I can see the full list. You can also view and manage relationship of this particular attractor entity so relationship is linking between one track to the instance to another based on a certain relationship could be you know mother to child. It could be for this case of COVID-19 it could be you know a suspect to a contact tracing and etc. So the relationship all of these are customizable you can customize and then you can actually start to add this relationship here so you can manage the relationship of the track entity instance here through the attract entity. And of course as I said here you can see the indicators configured indicators for this particular attractor entity instance for this example we have the patient agr for two and years plus one day. And of course if you add additional indicators they'll be listed here and whenever you enter your information, these indicators will be updated here. And of course, as I said you could also continue with your data entry through different stages, where you have access to. Okay, so one of the feature which has been accommodated is to allow you to compare repeatable events during that entry. The DHS2 tracker allows you to track your information across different visits, and there was a need to actually you know when a health worker or at the service point of entry there when you're entering data for existing visit, you should be able to view a previous visit and, you know, try to compare or triangulate some of the information which you're entering now this is what was entered or what was shared in the previous visit. So, the tracker capture now allows you to, you know, enter your information, the current data entry, then of course you can view or you can compare this with the information which was entered into the previous visit so for this particular example, we have here an antenatal program where it monitors pregnant women, you know, through different antenatal visits, the first one, the second one, the third one, the fourth one, until that pregnant women delivers and then of course could be shifted to another program. So for here we have, for example, here we are just showing you the data entry for the antenatal second visit where you're entering these information but you can actually see the information which has been entered at the antenatal first visit, and then of course, you know, you can compare what information you are entering now vis-a-vis what was entered, you know, previous visit and, you know, make some informed decision through that particular process. Yes. Then of course, our track DHS2 tracker capture allows you to share metadata and data, share metadata and data and this is quite a broad concept in terms of access of information within the DHS2 tracker app. Now, for example, and this is quite important because we are dealing with individual level data so it's important to actually have a robust system which allows you to have controls who can see what, when and etc. So for example, the DHS2 tracker capture allows you to control who can register information. So you can have a user, a group of user within your organization who you have entrusted them to, you know, register into information, individual level information for your particular program and plan. So that particular, those particular user group you can, you know, customize well within the DHS2 to say that, you know, for these particular, particular user group or users, they are able to register within other users who do not belong in that particular user group or are not assigned to that privilege, then they will not be able to create or register patient or clients within that particular program and this could be based by program and program. So, you can have immunization officers, you know, at the facility level, being given access to register clients, you know, their clients in the child health program, but you also have malaria. For example, maybe you have a disease surveillance officers who are working with the, for example, another program COVID-19 surveillance, then they are only monitoring or they are only able to register suspects or clients in a different program from that child health, child health program. So that's one aspect where you can look at it. Then you can actually control access to specific program stages within a specific program. So I could give you an example of COVID-19 surveillance program where you, you know, once you have a suspect you need to register that particular suspect. And then of course to, you know, confirm that particular suspect, you need to take a sample, send it to the lab. The lab needs to test that particular sample and then of course I give you the result. If it's a positive then that suspect turns to be a case and then of course you need to, you know, place him into case management where there's a different team working, you know, with that particular case. And of course different team working with the counter tracing of that particular case, COVID-19 case. So you have different teams working together in a particular one program. So, so in that case you could have a team working with, you know, at, for example, part of entry or their facility where they can gather these information they can identify the suspect and register them so you can actually create a user group and assign them control access to inter or to register this information and also populate this information in the stages where they are supposed to, for example, you know, collecting the basic information, but you could also customize your system to allow that the lab team can only view a stage where they can see the request for the lab, as well as inter information for, you know, the result of the test as well. So that is something which you can create within your system, where people can only access the specific stage and of course the same can be done for contact tracing, the same can be done for case management in that particular example, that only the team, the user, the team are assigned to specific roles or specific stages within the bigger program where they only able to inter information based on what they can, they can access. And then of course you can control who can access the data in the analysis app. This is of course something very important that you know it's not only at the data collection point but also at the, you know, use that you need also to make sure that you can control who is able to view what particular set of data. If you have multiple program within your national, you know, instance, national database, then you can actually decide that you know analytically. The information is entered at the facility level, where you have, you know, a small number team where they introduce all this information from different programs for example HIV malaria, maternal childhood and cetera but at the national level, you want, you know, the national HIV program. The national AIDS control program to actually view only their set of indicators and data that is something which you can also configure within your analysis analytics apps. So, this is an example of what I was, I was explaining that there are users who you can configure and then they are able to enter this information, individual level information directly directly into the data entry section, but some other people will not be able to view this information. As you can see here, this person is able to view but is not able to enter this information, even though this particular visit is open, but this particular person has, does not have the access to enter this information. Then DHS2 tracker capture allows you to persist the top bar while entering your information. So the top bar is this, you know, the, the, this gray bar here where it have these attributes information of that track that the instance the information which you have, you know, registered when you are enrolling that particular person so sometimes, when you have registered enrolled that particular person you might come and you know continue to enter data for this particular instance and you might need to kind of project or to see, to know which, I mean, am I entering information at the, you know, right profile right client, so you can configure your app where this top bar can be persisted and you can continue to enter your data while this top bar, you know, hovers within your particular app even though you scroll down so this is something which is quite relevant, especially on the data, data entry part. Then of course, another function which is quite, quite innovative, but I'm not so sure if a lot of people are using it. You know this breaking the glass so you know to ensure confidentiality to ensure that you know the right person can access, you know, can view only the information which they are supposed to, you know, there's a there's a need to kind of set some barrier controls in the way that, you know, one one person can search can view can access other information and also importantly to put audit, you know, trails where you can know who has been searching for what and why, I think these are these are very key information so for example, I could give you an example that for health worker in a particular facility is trying to either find an information of a client which is not based on that particular facility or in a different, you know, registered in a different facility. So DHS to allows you to search for that particular person, but you can actually put in place some controls where you can monitor who searches what and for what particular, you know, for a particular reason so for example, this customization you can, you know, set this customization to be either open, audited, predicted or close if you say this is, you know, this is closed, then of course that particular person or the health worker cannot of course search for these records in those other facilities, but if you can say open then that particular worker can search and access, you know, this particular information, but once you, you know, put it here audited or protected, then when the health worker searches for that particular, you know, record, then they'll be, you know, prompted with this particular dialogue here that, you know, distract entity instance belongs to another organization unit, you know, placefully in the reason for accessing your action is being, you know, monitored. So that first of all tells the health workers that, you know, the system is quite comprehensive and monitors most of the action which are happening within the system, but also the health worker could also, you know, enter this information and allow for a record to be shared or to be accessed across different facilities. And I think this is something which is quite innovative in its own way. Then of course, the DHS2 tracker capture app allows you to, you know, trace to find these audit history of who did what, when and those kind of things, you know, and this is quite important when you're running, for example, organizational database or national database, where you have so many users, so many things happening. So having a proper audit history where you can track all these information is quite useful. So for example here you could actually track audit history for, you know, tracking instance attributes. So, and of course, data element. So for the attributes attributes are these values, which we capture when we are registering a tracker entity instance, you know, for example, first name, last name, you know, date of birth, gender and etc. So you could actually track who has changed, you know, have they created, have they updated, you know, they deleted those kind of things and you know, it puts of course here the date, the date and time of these particular changes. Then of course, we have the data element, these are the values which we capture in the follow up visits. And, and you could also, you know, capture these information as well. So whenever they are created or updated, you know, and who has updated that as I said, and, and of course, the, guys, the mics, please let's mute our mics. Okay. Then of course you, the DHS2 tracker capture can allow you to, you know, a shift between several data entry modes depending on the program requirement to user preferences. So some users likes to enter the information in the timeline base where they can view or they can see. They can be able to, you know, toggle between, you know, previous visit and the current visit easily as you can see here, where you have different boxes showing you the timeline, where you have the ANC registration, the ANC visit, for example, first one, second one and continuous. And then you can, you know, these boxes have different colors showing you different stages of that particular program. Then of course you can enter your information here as you can, you can see and then you can toggle between these particular visit as easy as that. So that, that could be one, sorry, that could be one way of looking at it. But, you know, sometimes you could actually have other who wants to have, you know, enter the information row by row as you can see here, where you can enter your information instead of like, you know, the previous screen which I showed you, you can have it here as, as, as a row by row where you can enter this information for the first registration, ANC registration, the follow up visit, and then of course you can complete them as it is. These are more or less user, user preferences, how they want to change their particular view, and etc. Of course, here you, this is, you know, similar to what I've said. Of course you can decide to have a more tabular data entry and this is important if you have, you know, different stages and number of stages which you want to kind of monitor throughout then you can, you know, can have this tabular data entry view where you can have all your images here as you can see, and then you enter your information so that's that could be also another mechanism of, of entering your data these are all different data entry modes, which you can configure within your system to make sure that your user is getting user friendly interface to enter these information. Then of course we have user assignments of events and custom working list management so talked a little bit about this that you can assign users to a particular events within your particular stage or within your program, and then of course that particular user could be assigned to this and work in that. However, you could also, you know, assign or customize a working list for those particular users so that they can view a certain, you know, they can view a list based on what they want to do so for a good, for example, you can have a user group or users who you want to customize or you want to create a custom working list that you want only to view the current information or you want to view a certain uncompleted information so that you can, you can view tracking instance which are either complete or which are not complete or which are current registered within the system. So this list will be kind of, you know, here top of the interface when this particular user comes to the DHSU tracker capture app, then they can see this particular, you know, they can see the list based on this custom working list which you have designed for them. So this gives them a little bit of a powerful way of either, you know, viewing a tracking instance which have been registered which are of their particular need for that particular time. Then of course I mentioned this a little bit when we're going through the tracked instance dashboard that you can create relationship between one tracked entity instance to another and this relationship, you know, can be a mother to child. I could be, you know, a suspect or a case COVID-19 case to, you know, the contacts which he has been in contact with in the recent days. So, you know, the examples of the use cases will be varying from depending on a program and a program. So this relationship can be added as easily and of course one thing when you are in the tracked entity instance dashboard, you can see this relationship but also you can see the contacts which you have linked with. So for example, this year you see this person as a contact with Sarah and James and how you can do this, you can, you know, add, it's quite straightforward, you can, you know, add and then you can present it with a dialogue box where you can search for another entity instance within the database or you can register a new profile or page and that particular person will be linked to your entity instance. Then of course I mentioned this a little bit. There's somebody with a microphone please mute your mic. So, then we have this enroll entities in multiple programs that is a person can be in one program. But you can, you can allow for that particular person to register into a different, a different program and this is can be done directly in the in that particular track entity instance dashboard. Then of course there is a show live indicators program that are values this also a hinted when I was going through the track instance dashboard that you can have these live indicators display some information which you want to track as you enter information for that particular client or a profile then these information are dated and you can, you know, monitor these indicators. And of course they're, for example, if there's any feedback then you can monitor them as well here. Then of course the DHSU tracker capture can you know allow you to schedule visit and track these visits and their status as well. So, you can schedule for a visit for example if a person, if a child is vaccinated, you know, in the first ones they are, you know, born then they are certain kind of doses which they are given there within two to three days but you know they are scheduled to receive another vaccination in the, you know, in the next visit. So you can reschedule this particular visit there but as well as you can also track this particular visit and see the status that if they missed, or they have attended, or if they delayed attending visits, you know, and etc. So those are kind of things which you can track. But as well, not only tracking but you can also send reminders to this schedule visits, to the, you know, clients, patient but also send notification based on the occurrence within an event. So for example, here, there's a message here from the lab. For example, this is a message from the lab which says the lab result of, you know, unique identification already at CHWM, so please log into DHSU in order to view the final lab results. So this is a way of, you know, notifying a person through AIDA. This is an email but you can also send this notification through an SMS as well. AIDA by when a certain occurrence is happening in a stage. For example, here the values has been entered into that particular lab stage or based on the scheduled visits. For example, two days or three days before a visit, you can notify the client that okay in the next two days you're supposed to come to visit to a particular clinic. Please, you know, come with certain AIDA identification and other materials which you are required to come with to the clinic. So these are things which you can configure into the system and send them to the client. Then of course, speaking of data quality, improving data quality, adding a little bit of decision support within the system. The DHSU Tracker app can allow you to do this. Basically, yes. So here you can see this example where you have different vaccine and the different vaccine have a different approaches. These are different COVID-19 vaccine and the different vaccine have different manufacturers, information, different batch, lot number, you know, different vaccine expiration date, but as well as the schedule for the next dose. There are some vaccinations which, you know, have one, you can only have one dose as a J&J, but the other vaccination are required to have more than one dose. But their schedule is quite different. So DHSU, DHSU Tracker capture can allow you to configure these key projects and understand that whenever you have selected the vaccine to be given, for example, in this case AstraZeneca, then it will, you know, identify that, okay, the next dose will be, you know, which date, but when you have selected a specific manufacturer, then it will understand, okay, the batch lot number is this one and the expiration date is this one. These are information which you have kind of pre-populated within your particular system based on certain program rules which you have identified. So this helps, of course, to improve the quality of information captured within the system, but also elevate some of the workload at the point of entry. Yes. And of course, if there is any information which is of a concern, then the DHSU tracker capture can, you know, give you feedback in terms of either warning or error of the particular value which you have entered. And this is quite important because sometimes you might, you know, the health workers can enter some information, but, you know, once you have these data quality checks, then it will kind of improve the quality of information which is entered. So for this example, you know, there is a feedback here saying that this client has received their last dose, please consider completing the stage and program. This is based on, you know, once you have checked here that, okay, here this is the last dose, this particular client has received based on that particular type of vaccination. Okay, so before jumping to DHSU Android, let me stop here and welcome some of the questions which participants might have. There is participants who have a banning question. Maybe you can raise up your hand. I'm trying to look here to the our question to see if there is any question, a question channel in the Slack to see if there is any question. So I see here there's some question but does the pattern base ID generation work for event program and currently 2.35 version I'm wondering if that is possible in that particular version, but our facilitators have also responded. Thank you for the benefit of all. Let me just read the response. Thanks for this question the pattern and its uniqueness is based on attribute which are only available in the tracker, not event programs you can however use program rules to create the pattern by assigning to that element, but won't achieve uniqueness in an event. So that's partly some of the questions which I've seen. I have not seen a hand so far. If we have any participants who would like to react or ask a question directly we welcome but we need you to raise your hand first. I was having a challenge about the Slack channel I hope we have shared the Slack channel I think now you can be able to go to our Slack channel and go to the question and respond there. Okay. So we have a few questions here. One says my Amiko, Menda Menda says okay. Thank you for this self presentation on the capture app. What properties are being looked for during the duplication detection. Is it only the first and last name or all the user details. And to allow this to, to make it more interactive, let me welcome some of my colleagues here to respond to you to this particular question, so that you can also hear their names, hear their voices as well. I hope you're not tired with hearing my voice. Any response from the facilitators. Yes Wilfred, I would like to respond to the questions that have been asked on the Slack channel. One is asking if at all we're going to learn on how to use these features that have just been presented. The response is yes, starting from Monday, we'll be looking on these different tracker features how to use them. And of course even the analytical part of it. And there's also another question asking when do we use tracker capture or capture itself. So I think at some point Wilfred had mentioned that trucker capture is sort of phasing out where previously trucker capture was specifically for trucker related data, meaning that you're tracking data that it sort of has a continuation it's not just a one occurrence data. And the capture itself was used to capture event related data meaning that it's one time data. It doesn't have a sequence or follow up. But moving moving forward, the trucker capture is phasing out. And the idea is to have a single capture app that will be able to incorporate both tracker data as well as event data. So I would welcome other facilitators if at all we have more additional points. Yeah, thank you. This is prosper. He's Buganda. Yeah, just to take on the question about duplication, and I just to go back on the question and be able to understand what you're asking and I think here you are either asking in relationship to in relation to data entry. You want to capture duplicates as you enter your data you want to see if the record has every has been entered before or not by just based on the uniqueness that you have defined in your system. If that's the question. The answer would be no it's not respected to the first and last name. Still there it could have you could have multiple attributes because they were looking at attributes that will be able to help you to specify your uniqueness of your records so you could have multiple records you could have probably a unique identifier which is pattern driven as Wilfred has shown you. And once you enter into the system then you will be able to see that. I mean, once you enter a second report then it will be able to compare with what has been entered before. And this setting again we shall be able to see them in the training next week that you can say that it's unique within the entire system and that means from facility to facility or unique within your facility. And once that is done then the uniqueness will be based on the attributes that you have selected, not necessarily the first name and the last name that is to the understanding that I reflected the question that you have asked. Thank you over. Thank you, Alija, and crossbar for those were a liberative response. Yes, my, my Amiko has responded and said yes that was indeed the question which was asked. Just to involve other facilitators as well I will read two more questions and then we'll continue with our presentation. The first question is, when do we choose trucker capture or capture and why this is from John power, and then the second question is for the different that entry interface, is this something that has to be defined during configuration and cannot be changed afterwards, or is this something that could be changed during that entry as the encoder pre files. This is to one bit. So I think the first question was already responded to in terms of the, the, the capture, the tracker capture and the, and the capture. And for the views, those can be switched at entry in terms of whether you want that other standard view or the other tabular view. So one can switch. And I think I also see in here there's a question on the building reports indicators in the in the trucker assume that talks about having configuration of program indicators for analysis. Is that correct. So if it's it's that. I did a session within the academy, I think that talks about indicators so I think that would be visited then but in short, there's a maintenance section within the DHS to platform. And under maintenance, there's a component codes indicators and they can access program indicators where you can do the configuration of the specific indicators mapping them to the data elements for which you are collecting data. Yeah, so nothing that's what I can say in short. Thank you to one again I would just like to build up on what you want to say it as being of program indicators configuration, there's a separate academy for that, but for this academy will be focusing more on how to use whatever that has already been configured into the system So there will be a session on how to use program indicators, but more details on configuration that will be covered into trucker configuration indicator. Thank you for responding to participants question. I was thinking of, you know, we could have a live question from a participant but I think if you have any question. Before, please write it down on the slot but we'll try as much as possible to have a chance where you can ask your question at the end of this particular particular session webinar. Let's continue with our presentation on the DHS to trucker features and overview and you know some of the features key features which are available there. I'm hoping that you can still see my screen. Yeah, so we have covered more on the web, the HS to capture up the HS to trucker capture how you can, you know, and different features where you can capture this information. You can maintain the quality of information which you are capturing, but as also you can, you know, send some notifications some reminders to your clients and etc. Now we are shifting gears to the mobile mobile application where we have a DHS to Android base where it's it has also gone through different maturity stages. And now allowing you to work, you know, with aggregate event and trucker data on your mobile phone and the survey of course you can both have it while you have the connectivity, but also even storing these information within the computer. So within your mobile memory so meaning that it works also offline. And for the mobile base, you can actually, you know, configure user interface based on, you know, some of the icons, some of the, I would say way which you want your user to see your information. Remember, you have a mobile is a small interface and it's not like what you have in the computer. So you can actually tailor the interface specific for this mobile data collection, but as well you can also the app. The DHS 100 app is also evolved now to work with an offline analytics within the track entity dashboard in terms of, you know, showing you some of these analytics data which you have collected. Yes. So, as I said, the interface is different. So you in the DHS 200 app, you can assign different or different colors, different icon to your particular program. Remember that at the facility level at the web, the web based system of configure different kind of programs are there but you know, once these programs are accessed through the DHS 200 app, you can configure them to have a specific, you know, colors in terms of program, but as well how in terms of color in terms of where how you enter the information, you can also work on that. So that's, that's, that's one way. Then of course, you can also use a simplified icon sets to capture events or trackers we have seen in this particular second, second, second interface. So that's one way of looking at it. Then of course the important part is that you know the DHS 200 app is compatible with the already configured programs within the DHS to web, you know, however, there are some a little bit of some considerations which you need to kind of put in place. So when you are configuring your data collection mechanism through this Android app so the beauty about this is all the configuration you can do it in the DHS to web, and then of course, these configuration can be pooled. Through the Android DHS 200 app and as I said, you know, it works with the aggregates data but as well as the event and trucker. So this is a kind of an example of, you know, a program vaccination in a particular facility, where you can see different sections, you know, data entry through different sections. And, you know, within this particular app, it can actually give you a notification of, you know, how many fields you have already entered, you know, if there's any notification to be informed, it also kind of highlights. So it's kind of very intuitive in a way that it helps the data plug at the, you know, service point of service to actually enter this information if they see that there's missing value they can actually go directly to that particular session but also, they will know that they have already entered, you know, all set of information which is currently required in this particular stage. So another key feature is about, you know, collecting track data offline I think this is quite important especially developing countries where the connectivity. There is a fluctuation of connectivity, but on top of that there are some places where the connection is not available. So you can actually, you know, load, configure your system and then start your application load all this information within the DHS 200 app. And then, of course, you can go to the outreach places where there's no connection you can, you know, proceed to enter your information within this DHS 200 app. All these information will be stored within the device memory. Whenever you have the connection then of course these information will be synchronized with the DHS to there. And of course you can also even schedule this kind of synchronization so whenever at a particular point of time then the app will actually see how they can synchronize this information. Of course, important part is that you will always see this notification that you know there's some kind of, I'm not sure if you can see this but there's this icon here, this great icon will kind of show you that there's data stored in your device only, and it needs to be synchronized with the saver. Once you sync it synchronized then this icon here we have now changes to green. So whenever you see this down you know that your information or your record is synchronized with the server. And that is the important part because you want all this information within these local devices to be synchronized with the server so that all this information are put into one place. And the national program people they can work on this information, or at the organization level, you can work with all this information from different sites, which you're collecting. And then of course, the DHS 200 app is also integrated with the search and duplicate detection that is what we have given you an example or some kind of, you know, how the, how the DHS to handles duplicates record. So it's something which, which DHS to also Android app can also do that when you're registering into a search and of course, find any duplicate based on the set of criteria which you have checked, and as a prosper said, based on the attributes. And then of course we have full support for the tracker entity dashboard. As we saw in the web where you can have the profile information where you can have you know the indicators the relationship where you can add some data then of course even the DHS 200 app this is something which you can also see so for example this is the tracker entity, you know dashboard where you can see the basic information of this particular tracker entity instance, the profile you can view more details, you can go to the indicators and check the indicators which have been created. You can go to the relationship to see the relationship which available there the notes, but also you can, you know, either view the events which have already be our card entered, but also schedule new one and add another one of course, make a referral if you want to make a referral. So these are, you know, information or I would say kind of tracker entity dashboard on the level for DHS to Android app. Because you can actually have a map view where you can review your entities with coordinates on the map instead of a list. So the previous slide I showed you where you have kind of a list of your entities but here you could actually also review these entities through a map, see how these and where these entities are and also the distance I would say to the outside service provider so you could actually see where they are and also of course it allows you to capture location and in the location base you can capture, you know, these are through the device GPS, but you can also capture, you know, as a point, exactly where you can either this particular client stays or where that particular event occurs, but also you can track, you know, you can capture polygons of that particular area. So that's, that's kind of way where DHS 200 works, but also you can take pictures and read QR and back codes for registration and searching. This is quite useful if you are dealing with logistics where some of these information are, you know, stored in these QR barcodes instead of, you know, starting to enter all these information from scratch, you can scan, take a picture, read these QR barcodes and then all these information or some of these information will be populated within your your, your, your, your Android DHS 200 app. So this is kind of an innovative way of fast tracking some of the data collection processes. Then of course, there is a way of how you display your option sets. So basically, we can render these options within the app, you know, vertically but there was a need also to do this horizontally and as you can see there. You can use these radio buttons and checkbox you can actually render them either horizontally or vertically depending on the choice. Depending of course on the value type which you have, you have choose but depending on other criterias which are there. The second part is that when you're rendering this horizontal just be careful about the number of options, which you have because if there are too many then they start to cluster, and it is much more neat, if they're going here, I would say, vertically I think this is a part partly about you know the choices of, of a design and see how the interface will look like at the, at the, at the data collection points. Of course we cover this about custom working list. Also the DHS 200 app allows you to, you know, customize this, this working list, and the, and the, and the health workers, for example, will be viewing the list based on what you have customized so either you can custom, you can create a list based on the events which happened today, or based on events which they assigned to that particular worker, so that they can monitor, you know, these profiles, I would say, or factory instance, and, and, and continue with the data and so this is something which also at the 100 base 100 level can be achieved. Then of course, the local line analytics in that content instance dashboard. This is something which I hinted that you can actually have this particular analysis and these analysis can be either you know about charts you know it can be a line chart, but also you can have a more advanced level analysis for example these are child growth chart, where you can track the growth of a child from you know different stages, and if of course that particular child health is you know, optimum or not. There's a huge, there's a different level or different ways of visualizing these information, they are at the DHS 200 up and of course, through the track tent instance dashboard. So this is quite an important part because, you know, once you collect this information, you'd want to actually be informed on some of the parameters which you'd want to to see so for example. And a very important use case was this of seeing the progress of child health, you know, through these weight weight featuring age charts, where you can, you can chart and then also find the Z score and etc. And then, apart from the data collection DHS to truck up offers a number of visualization tools to help you analyze your information because the process you know the information processes you understand what you want to collect you collected information you analyze this information make a decision and then continue with that particular cycle so there's a number of visualization tools which DHS to offers to analyze to visualize your information and help you analyze so I can range from tables. I could go to numbers I could go to different chart like pie chart, you know bar chart but it could also be maps as well so there's a different level of analysis where you can do. You can do that in DHS to once you have collected your data. Through the different mechanism, either through the DHS to capture up DHS to track up, or the DHS to trade up. So the important parts to realize is that these information once you are collected the individual level they can be aggregated and provide a summary of your tracks track data, and this is kind of an example of, you know, an information where you have I mean as, for example, cover first dose, and the second dose and then you can you can see here, the list of facilities which are providing the services, but now these information is disaggregated, you know by the number of those but also by the gender and female and of course you can get the, the total so this is something which you can get straight away once you have into your information within the DHS to track but of course you can also create a detailed line by line report where you can, you know, see exactly the information which you have entered. And then you know monitor this information by specific record. So this is something which you can you can you can do in DHS to through the DHS to apps, but also you can, you know, aggregate this information through the program indicators, and then of course post them through the different through other visualization apps, for example, dashboard where you can have now at the programmatic level at the, you know, higher level name you can monitor these information that you know across different time across different parameters. So here is where the importance of data collection becomes where you can, you know, seamlessly visualize your aggregate information and inform your managers of what is happening in the ground. Then of course, based on how you have configured your information system you can always sorry, based on how you have configured your system you can always get the reports based on certain parameters or option set I would say so for example here you have configured your system to capture different COVID-19 vaccines, Modena, AstraZeneca and etc. So as you know data collection process continues, you can have these information, you know, have these analysis based on, you know, the option sets which you have, you have kind of customized so for example here you have AstraZeneca saying that yeah, 400825 and then of course other other vaccination as well. Then of course you can decide to create indicators which use both tracker and aggregate data and I think this is kind of a pathway of analyzing information because some of information could be coming from the tracker, some of information could be coming from the aggregate part and you can use this combination to inform you better or to create an indicators which combine this information and then give you a certain kind of very unique information so you can triangulate or review these tracker data and aggregate. So for example, I can give you an example that during the COVID-19 pandemic, built individual level system but we also had a COVID-19 daily aggregates data collection tool. So while I had a connection problem, I hope you can hear me now. So I was kind of going through this creating an indicators using both a tracker and aggregate data where first you have your aggregate data here at the, you know, for example, your data set population data set, but also you have these, you're collecting this information, for example, for people receiving the first dose of a certain vaccination and this particular person was age 41. So once you aggregate these individual data, you might combine these information into one, you know, your one analytical favorite or one analytical report where you can see the people receiving the first dose, you know, in age 35 to 54, you know, and we are assuming that this particular person here with the national ID, MRR005 will be, you know, part of this particular values here. And then you have population here, which is coming from the aggregate, and then of course you can create or you can calculate the COVID dose one coverage for people age 35 to 54. And this particular indicator will be combining the tracker data, which you have collected through this data tracker capture or DHS200 app or DHS200 app. And then of course, this aggregate data which you have here as your particular denominator. And of course, you can apply different disaggregation as you can see here you have different disaggregation for the lab results, either for a particular way which you want to display your information for example here you have a different age groups, from age 30 to 405 to 14, etc. But he also you have a different age group 05, 6 to 11, etc. So you could actually decide to use a different way of desegregation your raw data, so that you are, you know, handling or addressing some of the different needs from different stakeholders. You can decide to review your data tracker across multiple program stage. This is just an example where we have different stages, stage one critical examination diagnosis, stage three lab results, stage four health outcomes and as you can see in one particular Pivot table, you can combine this information from different program stages, and of course review this information so that's one way a pathway of accessing or analyzing your information, but not only that but you can also map your tracker database on the location of data capture where the information has been captured then you can track or you can analyze this information, but not only that, but you can also, you know, map your tracker data based on the individual location when you are entering data you could actually decide that I want to capture the location of this profile of this tracker instance. So you could also do an analysis based on that individual location of those people so that becomes more important or more relevant in terms of analysis. But apart from that analysis, we also the DHS to have a robust web API which allows different users, administrators to develop custom apps and access these tracker tracker data which you have entered a good example is during this COVID there was a need to have you know these COVID-19 vaccination certificates and there have been a lot of different custom apps which have been developed to actually access this information based on certain configuration and allow these certificates to be, you know, available to the public, as well as those who have access within the DHS to. There's an example here from Ministry of Health Republic of Vanuatu there's also here. There's another example so these are just an example but for example in East Africa, most of his groups have developed these custom apps to generate similar COVID-19 vaccination certificates. Not only that but we have an opportunity to also have different use his groups to develop some apps which are helping or giving some other detailed analysis which are the core DHS to my not offer at that particular time and a good example is I work from his Lanka where they've created a relationship analysis app, what kind of tracks, for example, one case or one suspect, how many contacts have that particular suspect had, you know, how many in that particular contact, how many, for example, for that particular case, how many contact has been indexed as confirmed, how many are suspects, you know, and etc. So you can actually do a lot of analysis based on your particular particular particular particular apps and this is just an example where you can have or you can see one case, for example, you know, being linked or having different relationships with different suspects or even different cases and etc. So this is quite a powerful way of analyzing information and make sure that you are your data which you're collecting stays relevant. Now, performance. There's a lot of work which has been done in terms of performance optimization of the new tracker data importer to make sure that you don't, it doesn't take a lot of time importing your data. This is more under the hood in terms of helping the user to import as much data as possible within a very short time. Also, the trucker search engine has been improved in terms of, you know, code efficient, removing of bottlenecks which have been, you know, hampering or making the search engine a little bit heavy, improving the database query optimization database indexing, but also the database locks contention improvement. So those are some of the improvement which have been done at the trucker search engine and we've been getting a lot of feedback that now the trucker search engine is quite more robust quite faster when you're searching the records there. Of course, the efficient API usage in the new track up for example saving entire event, not individual data values previously we've been saving each field one at a time but now that it's not, it's been seen as not efficient so now you're saving the entire record and also helping with the client side catching. So this is kind of an example of the improvement which has been done from version 2.34.3, this is the version 2.34.4, and as you can see there's an average response time in second has increased tremendously across different ranges from the Android synchronization to the search of unique attributes, you know, to posting enrollments to posting events and etc. So we actually encourage you, if you are embarking on deploying implementation of a trucker use case then it's better if you, you know, deploy the latest one because you'll be having all these features, very cool features but as well as the performance side as well. Yes, and then of course, usually DHS to has to to cycle release first one is in April and then the second one is October each year. We have a planning cycles prior to release of the the next phase so for example, for the release in October we have a planning meeting in March, where the team sits around and and and come up with all these categorization and for the release the first release after release for next year, then the team sits in September. So it's really important to understand this and also to see how you can advocate either the his group which is near you, or through the DHS to community that are some of the features which would want them to be integrated or incorporated within the next release. So also, so, and then of course, the following slides I'll be just presenting some of the upcoming features, which are still in development and of course will be incorporated in the next release, but some of them are not yet finalized so a good example is a new event report up, which will be taking a more modern use experience and take stock. And of course this particular new event report will be following a similar look and feel as the visualization up. I'm hoping you are all familiar with the new visualization up where we have put Diego and different visual visualizations into one up to accommodate that. So that's, that's one of the coming soon feature, but also the track entity analytics, where you can do a cross program analytics and I think this is something that the community has been asking for it for quite a long time. This will be kind of a look and feel for the coming event report overview, where you can, you know, select your input dimensions here but also you be able to drag and drop your dimension here as what it is now with the DHS to create that visualization up. Then of course the new trucker web UI user interface this is something also which it's been worked on so this trucker support for the existing capture up so all as a teacher itself, all new tracker features will be available in the capture and that's the trend where we are going where we are putting everything into one place, so that the user don't shift much from one application to another, and some of the main themes you know as you can see here, including record, improved duplicate, record handling, line listing, organization filtering performance and of course modern user experience. These are some of the things which will be worked on of course this is just an example of the type of trucker web app where you have the person dashboard with enrollment of a view so this will be quite different from what I've showed you previously but this is where we are going now where we have this information are populated here as the personal dashboard, where you can see the profile you can also see the enrollment information, but you can also continue with your data entry. So this will be kind of a little bit of a different view. So, and also you also have an enrollment dashboard with the stages and events, as you can see it here. You are entering your stage as you can see but also getting these errors and warning feedback, kind of notification whenever you are entering your information so this is kind of a sidebar, having all this information so the point is to make the data entry experience or the, you know, the personal the truck entity instance dashboard as neatly as possible but as informative as possible. Then of course the process of duplicate handling I think this is quite an important part where it will be also being researched and also kind of being implemented. There's a lot of work being done here in terms of making sure that the system can you know automatically flag if there's a possible duplicate and then ask for the administrators to handle those particular, those particular duplicates. Then of course our line listing that entry this is a partly something which is being handled within the enrollment dashboard to allow the users to do this line listing that entry in the in in there. So, just finalizing my presentation, our statistics from the field. Just a bit of examples. It doesn't mean that these are the old examples but this is just an example of how the DHS to truck is being used. For example, for Bangladesh, you know there's a mizan Rubella munition campaign where you have more than 400. More than 35 million vaccinations so the system can accommodate a huge number of events within that and also for Sri Lanka we have, you know, a COVID vaccination program where you have more than 60,000 entries per day with a 16 million people trapped. This is how robust the DHS to truck is is in terms of, you know, being able to track as many possible as possible. But also another example is from Rwanda where they've been handling our COVID case surveillance but also COVID vaccination where they have around 100,000 plus people per day being vaccinated tracked through the DHS to COVID vaccination system. You know, through around and they have around three million targets by end of 2021. And of course they have a target of 7 million by the end of July 2022. So that's just an example of how the DHS to truck is being used across different countries, but different use cases. And just to end with my slide, my presentation, you know, so when you're dealing with individual level that is always about making sure you have a high quality of information. So the team is always improving identification of duplicate records and making sure that you have a very robust search and matching a mechanism, matching between different combination of attributes so that it's much more easier to identify these duplication data. And all these for me checking should be done on the background job for finding duplicates. And of course the other parts once you have identified the duplicates, it's about majoring this duplicate so you know suggesting candidate for automatic majoring and also make it easy for the user to merge these duplicates records within your particular system. Now, it's around the top of our. We have gone a little bit. It's now 402 East African time. I know we started a little bit late around 410 or 411 so I will welcome some questions from the participants. If you are around the participants feel free to raise your hand and then we can unmute you. Just raise your hand unmute you, we can unmute you and then of course you can, you can post your question here, while we are reading some of the questions which you might have posted. In the in the Slack. Maybe a DJ can you take over with questions. Sure, thank you will Fred. I think we have a couple of questions in the chat box, but as well as on the Slack channel. So I would start with the one studying the chat box. One is when the Android is offline would it be still able to use the feature of real time historical data comparison during data encoding, for instance, looking at a and see fast visit, while doing a and see second visit. Any facility that respond to that. Yes, what's up. On the online, when you're offline a lot of the features, especially the features that depend on the on the database and this is only using only one, let's say one, using the tool on only one site, you can search it's own. So if you could get close to Mike, please. But who are you from far. Okay, so probably is adjusting his mic. We have another question, which is asking regarding the line listing, can we import back load data from Excel. Facilitators are you there. Okay, so we got it. The HS to support uploading of data only that you just have to abide to the HS to format. And it's not exactly as excellent but rather a CSV format, but it also supports the JSON format as well. So all you only have to do is make sure you follow the format or template of trucker data. Yeah, so I think, just to add on to that, I think on the app store they also some apps that assist with data import. I think like there's the data is up. So those are also a bit more user friendly in terms of like allowing you to map some, some fields to do a program. So I think they're quite assistive in trying to import data into the data to trucker. Thanks to one game. And it's can Android up hold on data for a relative long time if this ever got hacked or if it cannot be reached due to different reasons. Yeah. Okay, I can go ahead. Yeah, sorry. I have a background noise which comes on and also sorry if it comes on. Yeah, I'm just to answer that and also look at the NC first, we stand second. So the Android, as Wilfred explained, it's actually almost offline most of the time, but you can set it to trigger that every now and then at the given intervals it goes and features data from the metadata and data values from the server to the device. So what happens in terms of storage that will heavily depend on your storage for the Android phone. So the storage on your phone will limit how much that you can be able to store on your phone. So if you have, you know, small memory on the phone then you will not be able to store quite a little bit better. But also when you talk about hacking, that would also depend on what you've done on the other server. So if you have, if there was a hack and you change the, the whole server and pointed it to different instance, then you may not have issues in synchronizing the data. Otherwise, every time you are online, what the Android does is synchronizes both ways, upwards and downwards for you to be able to keep the data. For the facilities you assign to the data and also keep the facilities where you are allowed to be able to search in the entire organization. So that's what actually happens with the Android. So you can keep data as long as your memory is not full, but it's always at whether to keep synchronizing that upwards and downwards. And when it comes to the question which was asking about the on Android offline and enjoying the off the online real time data. So this, what actually happens with the Android for the track entities that you have access to, that is the track entities where you, where, where you assign capture data. Every time you were going offline or you go online and synchronize, it pulls all the data for an individual. Say this man, being tracked from first week, second week, the registration and so, so all that will be synchronized to your Android phone, you will have a complete record of that particular track, track entity or client during offline session so you'll be able to see a first the entries in the different stages over time. And also you'll also be able to enjoy some of the program indicators and the visuals that you will be have synchronized and configured into your system. Thank you very much prosper. I think we have another last question, but from prosperous response I think it has already been covered. The question was asking on if at all the Android app is offline. So from prosperous explanation, I think the answer is clear that it. Yes, it is offline as well. I think at the time I think should end this session if there are more questions you can just drop them the Slack channel. And be looking forward to meeting you all on starting from Monday, the actual sessions now the trucker use Academy was I'll be sending out the Academy agenda. There are more details about the sessions starting from Monday. Otherwise, thank you all for joining us today and looking forward to meeting you all on Monday. Thank you too. Thank you.