 The next section here is going to cover capture app parity. This is features that used to be in the tracker capture app and that now have been redesigned and reimagined in the capture app. And the first feature I'm going to show you in this category is called breaking the glass. It is a feature that is useful when your end users needs to have a means of accessing records that is outside their immediate capture organets. Without giving the full access to everyone to all organets, you can now with the protected program level, the access level protected, designate that users should have the possibility of breaking the glass and accessing records outside their capture scope. If they can find a person, they are able to break in, as we say, if they need to, as long as they provide a reason. I'm going to give a short demo of this now. And I'm in my search form in a version of the Sierra Leone database. I'm logged in with a user that has access to Nyan Dama only and I'm searching for a patient that I know is not in Nyan Dama. The program is slightly modified from the standard Sierra Leone database as the WHO RMSH tracker program has been set to access level protected. If I search in my own organets, I will not find any results. But if I go and search in all organets and programs, I will find a person called Ava Degriksson, which was my search terms. But trying to open her RMSH, WHO RMSH dashboard, I get this screen. And I do have to provide a reason to get access to the record. The reason I provide here is stored in the database in an audit table. And each implementation should have follow-up routines to make sure that any abuse is followed up and by the system admins. Clicking the check for enrollments button, there is one enrollment that is active and I'm directly taken into this screen and seeing Ava's record in the WHO RMSH tracker. The access will be retained for two hours. So I will be able to add to the record, work with her in the record for two hours before the glass would have to be broken again for this user. The original user, the original organet will retain access as well. So breaking into a record does not take it over. You just gain an extra temporary access to the record. Okay, the next feature I'm going to show you is a quite small one. It's also a parity feature. It is the program stage setting that is called ask user to create a new event when the stage is complete. You can see it to the left here. And I will give you a short demonstration of how this works. The use cases for this is two-fold. You can speed up back entry scenarios where a user would have to normally enter many events, one after the other. This is a more direct access to creating a new event with less clicks. The other use case it supports is a reminder in clinical settings or point of care settings where you would generally have a new visit scheduled when you finish the current one. This would, for example, cover ANC visits where you would normally schedule a new visit at the end of a current one. So I'm going to give a short demo. I'm going to open this already ongoing ANC visit here. And I'm going to complete the ongoing visits and save it. And when I do, I get this box. I can agree to creating a new event if that's what I want. And then I will be presented with the possible stages that can be added. In this case, I'm going with the ANC visit again. And the default screen here is for going directly to reporting a new visit. But what I want to do now is schedule a new visit later. So I'll go to schedule and click schedule. And as you can see, the schedule visit ended up here. The next feature I'm going to show you is a search form enhancement, creating a new tracked entity instance from search term. We now have a button for adding a new tracked entity instance if you don't find any or is not happy with your search results. This button will take you to the registration form but keep keep all the search terms that you had entered in your program. So I'm going to do a short demonstration and search by attributes. This is not a person that exists. And I can create new and the search terms are carried over to this form. The use cases that is strengthened by this is mainly allowing users to start by searching all of the time and this being a part of the user's workflow will potentially reduce duplicates in the end user and in the data in later rounds. The next feature I'm going to show you is a very short one. I'm not going to do a demo but mentioned that the high due date flag is now fully supported and when high due date is checked for a program stage, the due date will be hidden around the capture app and scheduling will be affected. This is useful to reduce complexity in the user interface and remove unnecessary data in the capture apps user interface. The next one is the attribute option combination selection for tracker. This is also a parity feature. We now allow selecting attribute option combinations in tracker programs. This is a screenshot but I'll give you a quick demo and switch to the child program up here. And as you can see, if I open an existing record and prepare there at the new events, I did not. Okay, I'm completely sure what happened there. I'll have to do something that happened to my metadata apparently so I'm going back to my screenshots instead of figuring out what's wrong. The implementing partner and projects was the demo category and as you can see here, the implementing partner projects category combo is presented now as one of the choices in adding the event to the enrollment. It's below the basic info and above the standard form when a category combination is used. So here you can see the implementing partner, which is one of the combinations being filled out and the project in the process of being filled out. To get this feature, you would actually have to upgrade your capture app after installing 240.0. The bundled version of the capture app in the 240.0 version is not containing this feature, but the latest capture app version in the app hub in the app management store will contain this feature. So just make sure you update your app if this is a useful feature for you. It would work from 238 and up as all of the other issues we have gone over so far.