 In this session, I will go through some of the new features we have in the Captrap. As you know, the Captrap has been on continuous delivery since 238. It was one of the first apps to be released in this way. Many of the features I will show you today will be available all the way from 238 and up. So I will try to make sure whenever I'm showing a feature to tell you if this is not the case, if it requires version 239 or if it requires version 40, I will make a point of that as I go. You can update the Captrap in the app management app to get the latest version. I will go through many features that we call Captrap Parity, which really means that we have this functionality in the old Tracker Captrap, and we have now implemented and in most cases redesigned and reimagined the functionality in the Captrap. We have one completely new feature that I will go through on the very end. On the backend API side, we have made many technical enhancements and have also a few new features that I'm going to mention. But before I get into any of that, I will show you two new Tracker Analytics features. The first one is a new operator for program indicators in operator. We are all used to writing program indicators like this. We would maybe have a data element that might have several options. In this case, I'm using the data element for an ongoing or initiated ARV regimen and I want to count everyone that has either an ongoing or recently initiated ARV regimen. With only two options, this doesn't take too much space, but in some cases you might have ten or maybe a hundred options that you want to filter and your expression might become very long. We now have a new operator that will allow us to write it in a slightly different way and if I go to the next slide, you can see the small change in the expression there. We now can simply list the option data element and then individually list the options behind it so that we will get a much shorter and more readable expression. In addition to being easier to use, this is also faster on the database layer. As we know, program indicators are an area where we do need to optimize and be as efficient as possible. This is good to know that you should try to use this way of addressing multiple options for one data element. The underlying query and performance will be faster. The next feature I'll show you is the ownership analytics feature and this is a collaborative effort between many teams. It ended up on my plate to demo, but in reality this is an analytics backend feature as well as frontend. It's a maintenance app platform frontend feature and I'm representing it here today on behalf of all these other teams. On the user interface, it doesn't look too impressive or conspicuous. We have one new drop-down field in the program indicator screen called organization unit field. This field is there to allow analytics that specifically targets the owner of tracker data. As we know, a tracker, a HIV patient, for example, might be enrolled in one clinic, but throughout their treatment, they might move many times, their record might be moved many times between other clinics. This is better illustrated on this slide and we can see that we have the purple line there describing the point of which our patient moved from organit A to organit B. This is an enrollment that started in organit A. It was then moved to organit B later. To make efficient analytics on this, before we did not have the ability to analyze the data based on where the patient was currently owned, we only had the ability to analyze the data based on where the user actually started out. But with the ownership analytics feature and the new selection in the program indicators user interface, you will be able to count based on both methods. You can either count based on where people started out, where they were first enrolled, or you can do the count based on where patients or records currently are located. The use cases that requires this might include HIV and tuberculosis, but the list does not end there. I encourage you to look into the implementation guide as both the functionality and the explanation for the different use cases is much better covered there or is about to be much better covered there in the tracker design section.