 So just quickly, we're gonna do this next session as additional updates on going to talk about platform updates since the last year, covering versions 233 and 235 through 235. This will have a little bit more of a deep dive on some of the tracker things that Lars mentioned and then we'll turn time over to Mark to talk us through the Android changes. The first thing that I wanted to focus on though was to talk a little bit about growth. So tracker, as many of you know, is the newer part of DHS2. And it's been our intention and vision all along to be able to help push individual level data collection down as far as possible to better serve a lot of the health needs and decision making that we have. And we've had tremendous growth in just the last couple of years at trying to achieve this. So at this point, as far as we know, and again, we don't have clear analytics to everybody who downloads or uses DHS2, but we did a survey back in May, where we reached out to all of those that we knew of and were able to update our usage map to 77 countries that are using DHS2 tracker, presenting over 120,000 end users, meaning that we've had really quite significant growth. If you don't see your country represented on this map, please let us know because we would like to know a little bit more about where tracker is being used and how. I did want to highlight that this means that from 2019 to 2020, the time period that we're reporting on, we've had about 62% growth in terms of uptake and usage. The most common use cases that we're talking about or that we're seeing the most are disease surveillance, client level health records, which often feed into shared health records, particularly covering ANC, HIV, TB, malaria, immunization, public health event notifications, birth notifications, death notifications. A whole host of projects around malaria elimination, which if you remember from the previous conference, we showed a lot of functionality that was meant to support disease elimination in general and malaria elimination in specific and disease registers. This represents not only a lot of users but a lot of demands, a lot of interest, a lot of a lot of new functionality being requested all of the time. And about a year ago, we took the determination to try to slow down a little bit on functional requests. We had at that point a core suite of functionality that supported the majority of these use cases, and we wanted to let it grow a little bit more organically. We wanted to learn from existing projects what they needed, not potential projects. We also wanted to make sure that Tracker was well suited to support really large scale implementations, which is where we have seen this go in the last year or two years, that countries that are using Tracker end up using it a lot. You'll hear from at least one of those in the next session, where we talk about country use stories we'll hear from Ghana, who is using Tracker very extensively at the health service delivery level covering a whole number of projects. But what this meant for us is that our priorities during this timeframe really heavily focused on this top priorities, stability and performance, as well as privacy and security and usability. So knowing that we had a lot of users that were out there depending on this software and individual level data software is often transactional. It's something that needs to be updated immediately. It's a very different scenario when your system goes down and you have 5000 nurses around the country depending on that system versus when you have your aggregate system that goes down but reporting doesn't happen for another two weeks so you have time to figure it out. So we've really spent a lot of time and effort on stability and performance. We've always been interested in privacy and security and I've added quite a number of features related to that. And then again in terms of usability we want the features that are present in Tracker to make life easier for the people that are using it. In fact we have as a whole philosophy the intention not to do a lot of double data entry but rather to make this be a tool that is really able to use during their normal workflow and it can be something that can feed into aggregate and HMIS instances but doesn't have to be an additional burden on that. So I'm going to talk through a little bit of what we've done in support of these goals. The first one is not software it's actually a new tracker implementation guide. I've put the link here in this slide again these slides are all going to be available in the session that you see on schedule. This is right there on our docs.dhs2.org the implementation guide and this implementation guide is very much focused on all of the considerations about why and when to use Tracker. What are the appropriate kind of use cases, what kind of preconditions should be met, what's likely to lead to success, what are kind of the key challenges you need to be prepared for. It's not a software guide so much as it is it's a guide that is there for those of you that are managing programs that are setting up new projects that are determining what funding should be for an individual implementation. Have a better sense about what it takes how to succeed and what to be prepared for. It includes a number of write ups of example use cases from real countries. There will be more work going into this implementation guide that will focus on configuration of Tracker. But at the moment that's not what is in the tracker implementation guide this is very much for implementers and for those kinds of planning determinations that they need to make. We would love to get your feedback on this. It's very easy to make recommended changes to our documentation that's also open and crowdsourced and so we would be very happy to have people put more eyes on this and give us some more feedback to make a better tool for everybody in the community. So with the publication of the implementation guide we launched a new tracker implementation academy, a level two academy. The very first live version of this was in Accra in the spring. It was a six day academy covering all of the topics that were found in the implementation guide you can see listed in bullet points here at the bottom the different topics that we covered. There was participation there was something like 20 different countries represented there all tracker users already but we're coming to improve their own implementations and also to be able to learn more from each other and from those of us that are working on Tracker and Oslo. The implementation academy had to get cut short because that happened to be right at the moment when COVID really hit in Europe. And things started getting closed down so we had to end this two days early but the materials are all available I've linked to those as well as to the community and practice discussion that was around that academy. There's a lot of rich information there for for those of you that want to know better how to manage or handle or plan for an upcoming tracker implementation. I won't go into all of the details here about tracker performance a lot of this is kind of under the hood and you know not very easy to understand changes. But I wanted to make it clear that we had spent a lot of the developer time that we have focused on optimization on bugs on new kinds of architecture. Lars went through some of that in his presentation. A lot of what he talked about just generally as platform improvements also were driven kind of by this need within tracker for tracker to perform better to be quicker at syncing to produce search results more quickly to be able to handle the kinds of analytics that are being requested. Tracker implementation is rolled out in a country they can quickly triple quadruple when tuple their data size and what the number of users that they have. So there's a lot here that we really have done to try to make this better. One thing that Lars mentioned in his I wanted to hit it one more time just to say that based on a lot of the rewrites and changes that we've made at this point we think that trackers about three times faster and handles concurrency a lot better. So those of you that are still on 229 230 231 versions of tracker really it's worth considering an upgrade you you want to have the best when it comes to tracker performance and stability. And some of the changes that Lars has talked about, you know, should make it a little bit easier to set up your new tracker and to do these upgrades. We're running a very large implementation of tracker and you know have questions about how to do an upgrade please post those in the community of practice. Let us try to provide some guidance. I won't spend too much time on this Lars also mentioned this but I wanted to point out that one of the reasons that we were able to develop this application monitoring and we really sought as a priority was coming from our real experience supporting several key tracker implementations. The University of Oslo as you know we don't get involved with every implementation of software but we have identified some key implementations that were learning projects for us. We spent a lot of time working with Ghana with Rwanda with Botswana with others and trying to understand what the needs are for their systems and identifying what would be the kinds of tools that help them out. And as Lars said these we built these application monitoring tools on top of free open applications. These are the kinds of things that really when you're rolling out tracker you would want to have a team that is responsible for monitoring the uptime and how things are performing within your tracker implementation and be on top of changes as they happen or any problems that come up very quickly. We have a lot more information there in the sysadmin docs and so we'd really recommend taking a look at that. I'll go now through some of the specific features that we did add. Keep in mind for the last couple of releases again we tried to slow down functionality. What we wanted to do was was introduce tools that really were in high demand and that would either support directly the goals of security and performance or that would directly support usability. So one of those that is very important was the auditing. DHS2 was long hand auditing but this was a big rewrite of how we handled that putting all of the detail into a single audit table and being able to make it much more clear and easy to access so that you can have the kinds of logs that you need to be able to do real kind of in depth and granular kind of auditing performance on what is happening transactionally within your tracker implementation. This was one that came up from very specific use cases in terms of being able to support the kinds of programs that are going on at the clinic level. These Z scores from WHO that cover the wait for age, wait for height and height for age are complex calculations to do and often aren't being used to really monitor growth of a child. This is something that is an ideal kind of candidate to be just preconfigured into our program rules and so these were things that we added specifically to be able to improve nutrition and child monitoring programs and ensure that the DHS2 is providing analytics that are not just for programmatic decision making but also are useful for the clinical people that are making personal care decisions. In addition to this new information program rules evaluating for completed dates being able to make sure that those kinds of expressions can be written to show when a specific action has been completed. And as Lars started show some program rule expression validation. We know that for many of your implementations you at this point have have potentially hundreds of program rules. They're quite complex. We have always had the expression validation for other parts of DHS2 and it was one of the sticking points in tracker that it was not available for program rules. So now you will get this live validation as you're trying to form your program rule expressions and see if they are able to be calculated if they've been written correctly. So hopefully this will make it a lot easier to identify when there's a problem with a program rule that you're trying to put in place. Similarly in the data integrity app. We added in the ability to check for program indicators and program rules so that you can more easily identify those indicators and rules that are causing a problem within your implementation. We have seen especially when there's a lot of data in a tracker instance that a simple indicator expression or a program rule that is not configured correctly can really cause a lot of damage. We are doing our best to make that not the case but we also are wanting to give you the tools within your own implementations to be able to easily identify where the problem might be and then go to work on some fixes for that so that things could work much much better. In the privacy and security and data integrity kind of categories. It comes also down to deduplication. There's a lot of requests right now for automated deduplication tools within the HS to tracker. We haven't fully implemented a solution for automating this what we started with was the ability to be able to mark duplicates. So as you may be familiar with if you're running tracker you know that we have really extensive checks when you're searching for someone and trying to create a new user. So even if you don't intentionally perform a sort as search in the background as you try to register someone new tracker is running a search and is trying to see if you are truly creating a new individual a new track entity or whether this is somebody that is already previously registered in the system. What we've done is now link that kind of search to the ability to mark a possible duplicate giving you a spot in the data table now where you can see these flags and outside of the HS to do some kind of merging or cleaning. Some of the challenges associated with this are actually not technology as much as they are kind of processes and work decisions. Merging individual level data is potentially risky for quality of care. We want to be very confident that before any data ever gets kind of archived or removed from a data set that we are certain that is not data that is necessary for that person's care. So we are working a lot on this there'll be more design in the future. At the moment though your data set already can start to have duplicates flagged for those that the person at the point of care. The one who actually knows these patients the one who is providing the care as they see the names pop up they're likely to be able to provide a good determination that no actually these are the same person and to mark those duplicates with a flag. Another requirement for us again you may remember that we've done a complete overhaul of relationships in the last couple of years within the HS to tracker. One of the things that we've added now is to create bidirectional relationships. This lets you choose you can either have unidirectional or bidirectional but if it's something like a mother child. It's a great idea to have a bidirectional relationship. This means that whether you are searching and looking through the mother's records or you're looking through the child. You'd be able to follow that link back to the other. So that within the system there's a link going both ways. This is going to help us in the future as we develop more relationship analytical tools to be able to do a lot more interesting kind of analysis due to these bidirectional relationships. So looking at this lovely picture here you can see recently we had introduced a couple of releases ago the ability to add images images as tracked into the attributes or as data elements, but of course images are memory intensive. They're often not optimized or the same size between those that are being uploaded. And so we've added the tools within DHS to do some automatic sizing and downgrading so that these don't end up taking up your entire memory and your database, allowing for a much more kind of routine experience when it comes to images and the quality and the size that are being stored. So far as we went through some of this again the ability to assign events to users and then to be able to sort using those assignments. So this is taking us further down the path of having things like action lists or to do lists, so that events can be assigned to an individual user and then they can show up in that user's working list that they can follow. There are more kind of dynamic changes that we will end up making to the working list but this is already available in the existing tracker. This one is also the ability to search for relationship. The user interface, you're able to go and identify where there might be a relationship to one of the patients and predefined event views this is again this in the capture app here so let me pause a moment and capture app was introduced by year and a half two years ago as a starting point covering the event functionalities. So we previously had the event capture app that was for non longitudinal data. And the event capture app really needed to be rewritten anyway and what we have decided at that time is that the capture app one unified app for all data entries should really be the goal. Most of the end users that are entering data into DHS to don't really need to know themselves the difference between tracker event or even aggregate. What they know is that they have work processes that require them to enter data, enter data for different health programs enter data for different reporting periods. And so that work has been ongoing since then the capture app started covering all of the event functionality. We have now been working for the last year or so on getting the tracker functionality into it is not ready to be released yet as fully covering covering the tracker functionality. But that's coming up in the coming months and meanwhile, when we come across things like the working lists, we've done our best to move all of this new functionality into the capture app so I'll show a few of the things that are coming up in capture which will automatically be available for tracker once that is released. So, for example, the predefined event views here this is going to allow us to do the working list much more easily. It would allow you to save a specific view of events for example so if you are setting up the program for users at a certain level you can make a predefined chart here or working list that would be shared with everybody the same way that you had done in the last year. So that would be one of your favorite within the analytics apps. And we'll give you a lot more filters that you can use for this so that you could identify, for example, those that would be unavailable or that had missed their appointment through those that needed follow up visits. We've also heard the cries from people that the year selector is not so easy. It's just to try to make it a lot easier for people to not have to scroll back year by year or slide through so now we have a much more kind of functional year selector for dates. And then maybe I'll close on this one for the capture app. This is one that those of you that are old DHS to users should be smiling about at the moment. In the case that when you make changes to your metadata in DHS to that the first step is to clear your cash. And then every time in the future that somebody has some weird performance that we always tell them clear your clear your cash clear your cash. Within the new capture app. We have been able to implement the versioning here so that when the version numbers increased in the maintenance app when any changes are made in the configuration. The capture app itself will detect this and download all of the dependencies, meaning that we shouldn't need to be doing this browser cash cleaning so much. So this will, I think, greatly make the performance and experience for the user, much more friendly thing. We won't have to have these kinds of notices going out to the 5000 tracker users everybody tomorrow morning clear your cash. So this should make a big difference but again this is starting right now in the capture app and will be giving you updates in the future about when the capture app with tracker will be released. So I would take it to this to say we have a roadmap session that is later in the week on Friday, you'll get to hear much more about the actual roadmap for tracker in the future. You'll hear it also from Android and analytics and the platform in general so you'll probably want to join that roadmap session at 1pm Oslo time on Friday. And then I wanted to flag up two things before I opened up for maybe a couple of questions and then turn it over to Martha, but we have a couple of experts lounge sessions that have just been added to the schedule. So for tomorrow afternoon, there will be a program indicators session at 4pm. And on Wednesday, there will be a program rules session. And again these expert lounge sessions are there for you to be able to come and ask specific questions here from some of the experts behind Tracker to give you some guidance on managing your program indicators and your program rules. So with that, I think I will see if there's anything that we're able to address now just from a questions perspective for a couple minutes. We have to switch my switch right now and we do questions at the end if there's time. Yeah at the end or in the community or the expert launches. Otherwise, we will not make it to the next session. Great. Then we'll do that so I will stop sharing my screen. And we'll turn it over to Martha. And then meanwhile, I'll also be monitoring the community of practice. We have a couple of others as well. So if you have questions, please put them there as well. So you should be seeing my screen now. Can someone confirm that. Yes, we see it. Okay, thank you. So hello everyone. We're going to talk now about the data is to Android app and in this session we will explore the new features added in the last three versions combined with some demos of the key aspects but first we want to talk a bit about the use of the app. The scene here is the Android app adoption evolution as active devices and as you know the Android that was released in September 2018 is a relatively new yet strong component of the data is to platform. The app is the result of a strong effort made by the University of Oslo and donors to be able to reach the last mile for that the collection with a full open source and integrated solution. So as we see here the adoption, since its release has done nothing but to grow and we can see only a small decrease early this year. This is the impact we think of COVID in several projects that had to stop due to the dynamic changing of priorities to respond to the pandemic. The particular that we know of very, very big project in Bangladesh for maternal and child immunization that had to stop and we are happy to know now that is resuming its its activities soon. Even with such impact, the decrease is not as steep as it could due to the big number of new devices used also in the response to to copy. We will keep supporting and and helping adopt the the Android app in the field. So let's talk about the app for those new to eat a quick intro the DHS 200 capture app is a native Android application which works on Android still from version point for 4.4 is could change next year but for now it is and is compatible with all supported versions of the It works fully offline for the time tree and integrates the fee the three DHS today to models meaning data sets for aggregates event programs and track programs. The Android app was helps improving quality from the source because it runs your program and validation rules from the daytime three moment. Currently, the DHS 200 capture app is fully translated to seven languages, including Arabic, which requires right to left display. This is a community effort just as the DHS to web user interface is. So if you are missing any language or your language is not complete, please do not hesitate in joining the community asking for instructions on how to contribute. So yeah, let's start with the data sets when it comes to aggregate data in the DHS 200 capture app. The form is displayed in a table view. This was already implemented in the early versions of this year is not new, but the new feature is the support of the validation rules. Validation rules are useful as we said before for checking the integrity of data entered on will show instructions to the user on how to fix the potential errors or inconsistency. So let's make a quick demo of that. What we are seeing here is we are using a COVID demo instance. So what we are seeing here is three tracker programs and one data set. As you can see, we are trying this to be transparent to the user for the user. These are activities. So for aggregates, I'm going to open the COVID surveillance. This is a daily surveillance data set and I'm going to enter a new record. So let's enter the numbers for yesterday. So this is how the data entry looks like what you have here are the different sections that you can navigate with the tabs. And then when we are in one particular section, we can scroll the tab. This looks much better, of course, in tablet and in landscape mode. I'm showing it in the most difficult one. We can also adjust the columns just to decide the view that is more comfortable for the user. And then of course we can enter values. So let's enter a few and then let's save. Okay, so it's telling me that I have one error. This is actually one validation rule, which is telling me that there should not be more cases hospitalized than tested. All hospitalizations must be tested. And then the instructions to the users. This is coming from the validation rules configuration. So please check the number of cases in the tested and utilized table. Okay, so we go here. And it's telling us you have two tested six hospitalized. So let's say, okay, so I want to have 25. Okay, so now everything looks good. And yes, I want to complete the data set. So that's the demo for data sets entry and let's keep going. And go to the data entry for trucker and event programs. So in general, the data is 200 that does not require any additional configuration on your data is to server. It will download your metadata for the user logged in respecting the access and privacy restrictions on your server. It will replicate the data sets programs event and trucker programs configuration and then allow for mobile data entry collection just by logging in. The data entry flow, the logic for the data entry flow and the messages for decision support or feedback during data entry will be provided by the program rules just like in the DHS to server. So additionally, you can configure your programs for more user friendly and visual data entry. And to do that, we have different rendering styles that you can configure at program level. For instance, you can render your options in an option set as such selection images or icons, which is what we are seeing here in the screen. The assigned icons are selected from the DHS to icon library, which currently has more than 300 icons and it's going to it's been reviewed for for 235. Another mobile specific rendering type are the QR codes and barcodes so you can assign this rendering time to a specific this rendering type to a specific bill of type text, the value type has to be text, and then use them for searching just by scanning the code with your phone we will demo this in a minute. Yeah, the another one when it comes to option sets or Boolean values like Boolean value types like the just know or the just only. You can select the rendering as either radio buttons or checkboxes in horizontal or vertical display depending on how many options you have or how long your options are. And I think the last visual rendering we are presenting are the images. This will apply for fields with image value type. And the images can be displayed in the truck entertains dashboard in the list of instances and in the map cards that we will see later. The first image attribute that they have finds will be considered the profile pic, and then will be displayed as such, as we can see here. So data synchronization. As we said before, all the functionality works offline and data can be synced at different levels. So you can configure for periodic bulk synchronization either daily weekly or monthly, which will be triggered as soon as the app finds internet connection. The user can also sing a specific program or a specific register form registered from the from the programs from the user interface. So to do that, they just have to click in the icon in the gray icon next to the register or the program. It's also available the synchronization through SMS, which will be enabled when there is no internet connection and the server is configured to support it. There are also new, a new icon set so the, in the last version of the app, the sets for status icons and sync events status icons and synchronization status have been reviewed and we have reviewed them to make sure that they all have different shapes, and that their differentiation is not based on the on the color only as it was before. Yes, and I think we are going to make another little demo for their rendering types. So we are going to work now with the case based surveillance program. So this is our list of track entity instance. Thank you to the volunteers for the pictures. So we are going to search so I can search or I can filter we will talk about filters later. So we are going to search and we're going to search by scanning a COVID passport that, as a sample we have been able to, we have borrowed from his Uganda. Thank you. So we are going to scan a code for this patient. Okay, so here you are. You will know her is not Julianna. So we open her record. Okay, and then we see, okay, this patient has one clinical examination, which is open. You can see here the icon and then one lab request, which is also open. So this patient has been starting the examination and has been requested a test. So let's open this form. What you're we are seeing here are the sections. This is the different section that we configure in the data entry form. Here we can see how many fields are completed. And here we can see the completeness for the whole form. So let's process this request. And then I have another helper here. Let's scan our blood sample. Yay. Okay. So this is a bar code render type as the other one was a cure code. Here we have an option set just rendered as a drop down. And if it had more than 15 options, I think we will have a search box. So this is the type of specimen we are going to choose. Okay, we got the sample today we could change to calendar view. If that was more comfortable to the user. Okay, and we are sending this to the laboratory today. In the last section we can see this is a vertical checkbox rendering for a short option set. So, okay, we want that serology test. Save it. This is finished and complete. Okay, so this is what we meant with the icons. Now, now this one is complete. As you know, I think this is not new we have another tabs indicators, relationships and notes we will get back to this later. But for now, let's continue with our presentation. Okay. This is not new. As you know, you can filter your data in all screens of the app from the home screen to aggregate data sets or for program data. The filters are adjusted the possibility to filter is adjusted to each domain. And we have added two new filters in the last version. So currently, you can filter your data by organization unit by date either event date or enrollment date. By period we're working with data sets by synchronization status category combination when it applies events status enrollment status on if the event is assigned to the user. This is the new feature that Lars was introducing before in the device we can filter and see what is assigned to me we will see this a bit later. So I think it's completely new certain is a new functionality that has been added in the last version for tracker and event data to make it simple we have integrated it here in the same filter UI, just by adding one icon that the user can click. So you can sort ascending or descending as the user keeps clicking so you can start counting by event date and enrollment date, and also by organization unit by the status of the event, the status of the enrollment so these last ones will be ordered alphabetical user We have also new visualization this was added in the previous to last version for the events. So what you are seeing in the in the left is the traditional representation so we have a list of events, which is mixing all program stages they are ordered chronologically. So for very long programs when the enrollment lasts let's say five let's say five years and we have many different stages with repeatable events. It can be a bit difficult to navigate so by opening the menu in the three dots three vertical dots. In the top right corner, you can choose group events by stage. And then now we're going to have one line for each program stage and inside if we click on them now we have opened the third one. We will see the events that belong to this particular stage or their chronology and moving now to the last block, which are the maps. The map view is not new and is available for event and tracker data. The map view you can switch from list view, list of events, list of track entity instances to map view by using again the three vertical dots we will demo this in a minute. The maps can display a feature type so they can display polygons as you see in the left or coordinates in the other two. So when we are in the map view we can still search or filter. We will see this later as well by clicking in the top bar icons. Yeah, the maps can also be explored by swiping the cards as you see the cards are new. This is a new feature added from the in the last version so you can swipe the cards it will, it will keep navigating are your different in this case track entity instances. The cards can be open in case the user needs to see more details of the particular event or tracking. And the last year we are also showing some enrollment important information like in this case we are seeing that this patient has an overview event from the 14th of August, if that was critical. And there are also new map layers. We already had event layer track entity instance layer enrollment coordinates. But in the last version we have added to new the satellite view that you can display in any of the visualizations and the relationships layer. This is the most interesting one you can see it here on the left. Here, for instance, we are seeing one malaria case and the cases to which the kid or to whom the case is related and the focus that the case belongs to we will demo this in a minute as well. So let's go back. So for this for this demo we are going to use the contact registration and follow. I'm going to open the program. And we are going to see the map view at program level. So again, this is our list of and contacts. And then I'm going to come here. And I'm going to say, show and not. Okay, so these are my and I said before, we can search. And we can filter just as we were in the list. So let's for instance use you can see here the available features or dates we usually give some shortcuts today yesterday tomorrow. None of them and then the user can also custom dates. And then for the status we offer the options and the users have to click on them. I'm going to filter by assigned to me. So I'm a health worker I want to see what is assigned to me today. Okay, so we see this the head worker has two contacts assigned. We can also display the satellite view. In case it helps navigating and we can swipe up or cuts just to to keep opening and we are seeing the navigating sorry and we are seeing here that contact five has an appointment today so I could open it again directly. Okay, there is one appointment schedule for today scheduled for today and is assigned to me so I could open and work on it. We are not going to do that now because we have seen it already. But now let's see how can we use the maps. Okay, let's clean the filters from here. So now let's see how can we use the maps from the track entity instance. So for instance, we go back to the case based surveillance. Our previous user. No, sorry, we were in the contact tracing. I want to go to contact tracing. Here we have user. So, as we saw before, this patient has a lot of relationships. In this case, the relationships are contact so we can display this in the map. So what we are seeing here is that this patient has been in contact with all these other contacts of patients yet and belongs to this health area. We are seeing in the map and of course we can see the satellite. Another interesting use of it would be, for instance, if we go to the community health area program, and I say, okay, I'm going to work today in the southwest region. So because the patients or contacts are linked as relationships, we can see in the map. Okay, who is in my area today. And then we can open that contact for whatever work we want to do. Something I have no demo is that we can sync, as we said, either from inside the program or the register so I can sync from here. Or if I have many records to sync, I can sync from outside and the experience is very similar to this. The last thing I want to explain, and we are changing a bit domains now, is that during summer we release the web app and the role of the web app is called Android settings web app is to help manage implementations centrally from the server level. So currently this web app allows you to configure your synchronization settings like how often data is synced in the device devices data or metadata or the volume of data to download. When the users make the first sync. It also allows here in the user sync test, it allows you to make a simulation of the volume of data your user is going to download in the first call. So it can help you adjust your settings, your sync settings to whatever network you know your users have. And last but not least, with this web app, probably the most important thing you can encrypt the DHS to local database on the devices. So by selecting the encrypt option here, encrypt device databases in the web app, it will apply to all devices connected to your server. Yes. So I just want to leave here this since the screens, the slides will be shared. Here you have links to the website. And give advice on how to use the app. In the documentation, you find server documentation but also implementation documentation and MDM documentation. We are doing a strong effort just like making a strong effort just like backer on improving the support and documenting it. And then the Android SDK. I don't want to finish the presentation without mentioning that there is an Android SDK. Android is not only the app, but there is also an SDK which purpose is to post track your custom DHS to base Android apps. So there is one session for Android developers on Thursday in the track in the in the tech track on Thursday at 3pm. We have also tomorrow, the launch experts at 4pm so ready to announce it here but since we will not have questions. Time for questions now. I hope you join us in the wherever launch experts launch and that we will be it will be not only me, but part of the team being there available for your questions. And if not see you on Friday in the in the roadmap session as Mike introduced. I think, as I said, we don't have time for questions, but we see you in five minutes in the next session which is about tracker and Android country stories. So we want to hear about real stories from the field and share them with you. And that's all for me, I think. Thank you.