 Don't be shy. Come in front. They still room in front. You can move around. You will not be stuck here for a week. Only until lunch, isn't it? So people come in. There is just one announcement I forgot to tell. An announcement. Every minute you're late is a minute less of lunch. Come on guys, let's go. So people, we are starting now. So all the tea chat and chatting is over. Coffee break is over. I will give an announcement. It has actually been. Remember when we had them, they're calling out for countries ministries to raise. Sorry. Sorry. It has started. Hello. It's an important announcement because what we were not aware, we were aware, but we forgot. It's a big fire in the city. Not dangerous. It's only a warehouse, but they have been fighting with the fire since yesterday. And that's the reason why many of us, of you guys were not here in the morning because they were stuck in the tram. So don't take the tram. It will have maybe be a couple of days without the tram. But the tube, the metro will work fine. So it's not a problem. I just wanted to say that remember we were asking for Ghana Health Service and Ministry of Health in Ghana and they were not here. They were stuck in the tram. So please Ghana Health Service raise. Welcome. Welcome. So now we all know that we are not going to the tram only the metro. So over to Austin. Thank you, Kristen. Welcome everybody. I think we're not wanted me to mention that if you can move a little bit in so that people that are coming in late don't have to climb over the top of you to get into their seats that would be that would be helpful. If you can move away from the inside edge at least that would be great. All right. So who wants to talk about DHS to anybody interested. Nice. I like the enthusiasm. We're going to talk about the latest features and releases in DHS to versions 39 and 40. The latest came out in November and May respectively. And there's a lot that we're going to have to go over so we're going to have to move pretty quickly. We're also going to try something a little bit different this time with some role play and theater so if we met. If we mess that up, please apologize. I apologize in advance. So for those of you who don't know me my name is Austin McGee. I'm the technical lead for DHS to relatively new position for me but excited to be here and share with you a bit about what we've been working on this past year. I'm not going to talk that much because I'm going to turn it over to many of my colleagues who are going to dive into the details and share more about what's what's new in DHS to in the last year. Okay, so first off, what, what have we done. What has happened since the annual conference in 2022. We've had two major releases as I mentioned version 39 and 40. All right. That's the kind of enthusiasm I like thank you. We're along with that we also had two releases of the Android capture application so that was version 27 and 28. And in addition to that we kind of highlight the new features that come out with the major releases of DHS to, but we've also been doing a lot of other work behind the scenes so probably many of you have seen the patch releases that are to all the supported versions of DHS to add a few minor features and mostly fixed bugs and issues and make sure that it's as stable and as as reliable as possible. We've also had a number of hot fixes to address critical issues in a very timely manner so we have hot fixes for supported releases about every two months. But if there's something that needs to come out quicker than that or needs to come out across all the versions at the same time, we release a hot fix so that might be a security issue it might be a critical performance issue something like that. So this is again trying to address and get out there as quickly as possible the most stable reliable version of DHS to that we can. I also wanted to talk a little bit about some of the things we've been doing behind the scenes so we'll we'll talk a little bit about, or a lot about the different features that are in DHS to, but there's a lot that's going on to to make DHS to better in more subtle ways. So this is an effort that we have ongoing for improving the design and usability of DHS to. So we have a new team that joined us at the beginning of last year in 2022, doing functional analysis and functional design and we're expanding the design team as well, and working with some partners to to really improve the usability of DHS to as a product, which in the end leads to better data and better use of data in programs that actually matter. So there's a lot of steps that go into design right so we've got talking to users we've got exploring how they actually interact with DHS to testing how they, how they use the software and how they understand it from a training perspective as well, and then using that to inform how we build DHS to software. So I started as I saw as you saw previously focused primarily on the Android capture application, which is typically the last mile user of DHS to, but this is going to spill over into all areas of the product so that includes the data entry on the web. It includes the way you manage and configure DHS to, as well as how you analyze data. And important thing that's going on kind of behind the scenes in the last year is the move to continuous release, and this is something that's been ongoing for a little while. But what it means is that the core releases so those two major releases we came out with in the last year are just a small piece of the puzzle, because those are now decoupled from each of the applications that we have. And it means that every application in DHS to can be independently released by the core core team at yo also can be custom applications built by anyone in the community that can be deployed through the app hub. And we can release those independently and also support multiple versions of DHS to core with a version of that. It avoids the risk of needing to upgrade your entire server just to address a small issue or a small improvement to the user interface, because you can update an application independently and very quickly roll that back without a lot of risk. It allows us to release features and bugs bug fixes more quickly. So we don't need to wait until the next major release to do some of those improvements and get those into the wild. And it allows for us to have also shorter interaction in a sort of iterations apologies and user feedback which feeds into that design process to better improve the software overall. So you can already find a lot of these applications that the team at yo develops and as well as those that are built by the community on the app hub and in the app management app on DHS to. So many of the features that we are going to talk about here today that are in 39 or 40 are also available for 38, or if they were introduced in 40 are already available into version 39, because they're just updates the application and that application happens to support 3839 and 40, for example, some things. So they have required for, but for any feature that doesn't have that requirement, we're able to quickly introduce that way that works across different board. This is the exciting step change and it's been a long time coming but we're getting to the point where the majority of our applications are actually on this new mechanism for delivery. So. Thank you. I'll buy you lunch later. Thanks, Ben. I did mention also that that is available for not only the applications that are released by the team but also for applications that are released from the community so we've had the ability to install and extend DHS to with web applications for quite some time. And, and all of the basically we're eating our own dog food as they say, which means that we are using the tools that we build for the community for our own releases. I also wanted to highlight one last thing about the version 40 release, and this is our beta testing program. So this is something that was introduced in 39 I believe, and but it really took off in the 40 release cycle. So we worked with seven, I think it was more than seven in the end, different organizations to do extensive testing of version 40 before it was even released. So more than 11,000 tests were performed by these organizations on realistic databases that they're actually using in production. So they were upgrading to version 40 and testing all of the functionality, one at a time. So it was a massive pass rate, and 96% is not 100%, but that means that the other issues so that 4% of issues that might have had something that wasn't exactly as it was expected to be were followed up, and the critical issues were fixed and those that weren't as critical or fixed in the future patch releases of those that version 40. So we're really excited to see this take off in version 40 and hopefully it will manifest in a very stable and smooth upgrade process for everyone. Once you upgrade to version 40, and we're hoping to continue and expand this in the future as well. To thank a few people who were involved with this, there were quite a quite a number of people. First of all, the QA team at UIO so the DHS2 QA team, and Phil in particular, has really been the champion of this so huge thank you to Phil for putting this all together. And the rest of the team as well for for really making that, making that possible fills right there so everybody can can can look at him. And then we also, of course, want to thank our beta testing partners who were involved in this and spent spent their time to make sure that we're testing each of the features and functionalities within DHS2 very rigorously with production databases and real use cases. And a special thanks to a couple contributors from his Sri Lanka, who, in addition to doing tests and being part of the beta testing process helped us to improve it and really had some good, good feedback and input on how we can improve that process and make sure that it's, it's fully covering all of the functionality in DHS2. So with that, that's all that's all the behind the scenes stuff now we get to the pretty pictures. And we're going to go through the different products streams within DHS2 one at a time. And we're going to introduce the product managers are each going to introduce the features that are in version 39 and version 40. We're not necessarily going to split them out and say this is in 39 and this is in 40 you can go to the release notes to figure that out, but you'll see what's new in the last year of DHS2 development, and I hope that you enjoy what you see. I'll finish with, as I said a little bit of that theater to show how these features kind of work together in a in a pseudo realistic situation, and to make a DHS2 system serve the needs of a real implementation or real real use case. So with that, I'll turn it over to Marta Vila, my colleague from the Android team to talk about the functionality that's in the Android capture app versions 27 and 28. Hello. Yes. Salute this one. Thank you as team. Hello everyone. Good morning. I'm Marta Vila, the Android or mobile product manager. I'm pleased and honored to present one year more the work that the Android team has been doing. So this, the difference with the demo means that we are going to go through our features without demo now. So we hope it's not very heavy. We have kept it light. And but if there are doubts or things that are not clear, please join us in the, in the, what's the name? Expert launches that we have tomorrow and Wednesday at 5pm. If you have questions about this is not only for doubts or anything. It's just to discuss the products. So let's start with Android. In this last two versions we have mainly focused in user experience and implementation support, but we have also done some functional parity. We have new Android web apps and we have an exciting use case data flow that I will explain later. The first one is the real time stock management module, which is for LMS. So for user experience, the data sets in the last two versions have had a real big change. So with the, I mean, the layout seems different, but the main functionality that we have been requested for so long is to resize the columns. So you can do that now easily by with a drag and drop. The tables also render the color that you select when you configure the data set. You can use legends and the scrolling when the table is big up and down and sidewise it has been improved as well. And the data entry. Yes, the data entry form keeps the context for the user this little field is near from to seven. So moving on to the sync process was also one of the, the processes or parts of the app that we got more requests. So we have improved the sync process, mainly the first one. Most of you using the app know that the first thing closer. Okay. So most of you that have used the app know that the first thing is the one when we download all the metadata and all the data so it's a bit slow sometimes. The time that it uses now is the same but we have tried to make it more dynamic by opening the home screen right after the app knows the metadata and then when the data is loading we are informing the user what's what's happening, which which program is actually being downloaded it's downloading the data. And the full sync will happen only the first time. So not every time you open the app that's a big improvement for for Brian's a community health worker. So here we have improved here and we are, we hope it really helps this is very new is that contextual sync error feedback which is this little dialogue here. So now we had already messages for errors that were adapted to the context but what is new now is that the user can navigate from whenever whatever screen in the app. And it is to the actual error in the form to fix it by only tapping on top of the, of the error when it's on the screen. So you can go from the home screen or the program screen down to the form and you have the field highlighted, like this is the field that is wrong. So we really hope this helps. So moving on. We have new renderings for tracker and data entry. First one, the digital signature you can now collect a signature for consent or however your configuration needs it. For mobile phone this is stored as an image so is the value type image and it has a specific rendering type. And then we have added a few actionable buttons for three value types so the email the phone number, and the URL value types will not will now be actionable if the user taps in the phone for example, it will go to the phone app in the device and let you call that patient for example same for the email and same for the if you have URLs. Thank you. Another rendering improvements is that we have extended the rendering types for the option sets. The option sets I don't know if this is widely used but you can decide the rendering of your option sets it can be radio button it can be a checkbox in horizontal or in vertical. You can also assign icons to your options. It can also be visual data entry and your icons will be rendered there. So this worked only for text before option sets with value type text, you can use them now for any value type that you are using on your options and so we hope this helps making data entry a bit more intuitive for the users. There are many other fixes that we have been doing we have increased the typable areas in the icons and in butons. We have added loading banners in the process that were reported that were taking some time so that the user doesn't feel that the app is frozen. We have improved the offline user experience by either removing the options or informing the user that this option doesn't work because you don't have internet. We have improved the display of long texts in some places of the app and then the navigation of the sections that now have this next button here because the accordion was not really intuitive. We are looking at this as part of the design project so hopefully we'll improve it even more but for now we hope this next button helps the user know what to do when they reach the last data element. So that's all about user experience moving on about moving now on about functional parity mainly with tracker. We have two main aspects that were we were a bit behind well one that we were behind which is the file value type the file value type was not supported in the app. It is supported now in the app for tracker and for data sets. Yeah, there is a maximum that you can configure for download, so we will make sure we don't download very heavy files from the server when you think you can set that up in the Android settings web app. And then the working list with data elements this were not we were not behind it's been released together in Android and and trackers or Mike will present this later. Just to say it will go together where the working list already where and the Android user, a community health worker or last mile user is not supposed to create the working list for now they will be configured on the server, and then the app will download them and offer them as a filter. So now about the web apps, there are two new web apps. And one of them is APK distribution I'm going to spend you this one right away. The other one is use case configuration I will explain that one at the end of the presentation and this is part of what Austin was presenting So you have to go to the app to the app hub and manage app management app and then up and find them and install them on your server. So the app APK distribution web app, we are very excited to see how this is adopted because this has been highly requested we are trying to offer functionalities that normally will be provided by an MDM software. We know that most or some implement most implementations don't have it. So what we are trying to do with this is is obviously part of the effort for supporting implementation from an admin perspective. So APK, so what this app is doing is to let the admin control the app, the update of versions of the apps in their own instance. So you choose which version you want your users to have, and they will have auto update, but from the version that you say here you decide you want to update an app version here and not Google play. So you, yeah. And, and thank you that was really spontaneous. So yeah, we are very excited to see how this takes into the field and and how can we expand this MDM mesh functionalities. For the implementation support we have removed the limit of offline accounts. We had a limit of three before. There is no limit now we are worried about memories in the devices but that's on you now. So we hope that helps. It was, it was really requested from the community. And then there was another request that is not fancy but it was apparently a bit painful which is that the under settings web app required and all authority. It's not the case anymore it has its own authority now. So those of you that requested it I hope you are happy. We think this is going to make a difference as well. And then moving on, because I'm taking a bit long. This is the second web app is the use case configuration web app. We are also very excited about this one. Let's see if I managed to explain it properly. This web app is letting you have a specific app module for your use case. A module is something that lets you configure your program and parameters to have a different data entry flow and user experience. So, for example, if you have configured your program let's say this is not a real example but if you have configured your logistics program to use the specific UI developed for it and I will show you a real example right now. When the user it's totally integrated in the app but when the user opens that program that you have set in the server this uses the this specific data entry flow and user experience it will open a different screen like this one here this is real. But you don't lose the rest of the functionality of the app for the other programs so if you have data sets if you have programs that use the regular user interface that we all know they are all here. It's integrated as well as the analytics. So we think this is contributing to the functional extensibility right now is really tied into the application. But we hope in the next versions because this can be more dynamic and more open to external use cases that are developed in the community. So this is the real example is the real time stock management module developed together with the LMIS team and his sound digital. And what it does is that it allows for real time stock management of health products at facility level it has. There's a lot of work in this module I have to say so so it has the barcode scanner up there so the functionalities that it uses from the highest or the same. But the way the data entry flow works and the and the and the UI is designed is totally different for the use case of stock control. So it allows for barcode scanner the actions are distribution discard and correction of workflow it has the offline capability because it's on top of the app so it uses the SDK and everything that was built in. And it allows for possible real time integration with with the LMIS. So this is not going to be demo today so I really invite you to join the LMIS session later today at 1pm in auditorium for is it correct. I hope yes is if not check the app. There will be also a stand in the bazaar later I'm sure if you visit them for that you will get very good cookies George. They're delicious and then there will be also in the expert launch both the days so please if you are thinking or if interested in logistics at the facility level join join those sessions for a proper demo and a proper explanation of the use case. And this is my last my last slide. Mike, over to you to present tracker. I think I'll try out this microphone is this one okay. Yeah. And based on all the chatter it sounded to me like Brenno and George you'll see a lot of participation from the logistics side so nice. So I might for us the product manager for we always say tracker but actually it's all the individual level data that this team works on whether it's the events or longitudinal data and tracker and and actually where most of this is functionality is now is within the capture app. So I'll talk to you a bit about that. Just to say that during this time period 39 and 40 we've had dramatically increased scale for the the implementations for individual data. This is showing a slide I think that we've shared before but this has become more and more than norm in a lot of countries so not only are there 75 plus government owned systems. We're hitting this very large national scale with millions and millions of people being registered 4050,000 users. And what we've had to focus on a lot is making sure that the the database can handle it and that the performance is something that will encourage use, and would not lead to all of the kind of offline or abhoc data collection. So just I know there's always more to go but we have been doing a lot to try to get the system to be able to handle this kind of load. There's been huge improvements to program indicators for example in terms of performance is particularly in 240. We continue to see more and more of these kind of performance improvements, which we hope is a good motivation for upgrading and for moving on to the more recent versions of the the capture app and end of DHS to. So, talking a little bit about this, those of you that have been around for a while know that the tracker capture app is quite old and has been something that's with us in our hearts for a long time. We have rebuilt it entirely in the capture app we have almost full parity between the two at this point and this will be the first time that I'm really urging you to move on. Let, let it go, let it go. So just to give you one sense of reason why the we've been able to redesign the capture app from the ground up meaning that we got to have a lot of time focusing on usability the way that we've been talking about before. I'm going to go into every detail of that but I wanted to show you just from the very simple enrollment screen here there's it on first glance they look similar but there's actually so many changes in this to improve for the user who is doesn't have to be a DHS to expert they're probably somebody very busy we know that they're entering a lot of data trying to make it as easy as possible. So adding in little tool tips that tell them the context of what they're doing they're saving a person in a child program in Gellarhoon, or putting a loading button to show that the system actually is doing something when they hit save person. So adding, removing all of that context on the left, and being able to put the full trail up on the top, adding more contextual information that gets pulled from your labels your configuration that would tell them. It's a person that's a new person in program child pulling from your attract entity type. So there's really quite a lot of effort that's going into usability trying to make it a much more intuitive product. Actually, many of you in this room contribute to that we have weekly meetings where we go through use cases we talk through user scenarios, we present back designs. These designs are being taken to the countries where we work often and being tested out. So a lot more effort going into this and we hope that that means that it will end up being something that you're really happy to switch to from the tracker capture giving you a sense of some of the things that are in there that aren't just feature parody but actually completely new, having something like an enrollment dashboard, where you could see the different stages all at a glance the previous events be able to interact with them individually but maintaining context over on the side that would give information about this person or this track density with the appropriate indicators their profile. So a lot kind of a landing page that gives a lot more of the context and overview, improving the enrollment widget giving the information not only of where they were enrolled but where the they started this program who currently owns the program when it was last updated. So a lot of information that can be contextually very useful improvements in scheduling and how that works we've had for quite some time request to make it again much more of a dedicated service to be able to go into schedule an event and not bury that in in some kind of menu. So we pulled that out it has its own specific landing page. So, I'll leave aside the usability stuff just to say we also invite you to continue to participate with us on usability there's many times that will ask if we can bring in test out new functionality with you with your users. If that's something that's of interest to your programs let us know because we're always looking for new scenarios. So then moving on to talk a little bit about working lists. The first thing I want to do is back up a little bit about what the working list is this is meant not as analytics this is a tool for the person using capture to have a list of what what things they want what how do they need to group these things based on what scenarios that matches their work processes. So this is a it's a commonly used term in in in various clinical management systems. They want to find the specific people or the specific items they need to follow up with, and being able to give them these kinds of tools is going to really improve their experience for the data capture data use. So just to show you some of the examples of these features, you can, for example, make a specific list and assign tasks, they can be assigned to yourself as a user, perhaps you're a manager and you want to see which tasks are assigned to which user. So being able to allow the the assignation of these tasks. Of course, it's flexible in terms of what you decide to include in list picking from the various columns which ones you actually want to show what information to provide. And then crucially in the latest release being able to add in data so having not just the attributes and that contextual information, but actually data from specific program stages and so you can see for example, a working list here where the the clinical user wanted to see all of the the children of low birth weight, because they're they have a specific action that they're trying to follow up with these groups, you can pull up the data element for low birth weight put in the range that is accepted for that and have generated from your data, the list of infants to be able to follow up with. And of course, can be saved as a specific view and that's what we are encouraging you as the program owner or configure to do set up some specific working lists for the tasks that that user is going to have saving it so that it's then available for them to easily click a button and get the the specific list of of tract entities or people that they need. So we'll move on from working with us ownership analytics is something that has been troubling us I think for a long time, especially those of us working on the HIV side of things. Very challenging I know there's a lot going on here don't worry too much this is really just to show you a single person of course can be enrolled at one clinic and receive services elsewhere, and that can happen as just a referral, where kind of the ownership of that person at the original or unit, but it can also be a transfer, and it can be that from then on they start to receive services at a new site a new clinic that's opened or that they've moved etc. And so what we've worked with is to be able to to include the ability and program indicators to capture this kind of dynamic change. Right so you make the choices based on the indicators you're trying to calculate what level of context you needed did you need to know where they were enrolled where they were registered. What currently is the owning or unit or what was the owning or unit back in the past in the time period that you are doing the analytics. So this is a big step forward for us we hope actually to do even a bit more with this when it comes to the analytics apps. But as of now you can be doing this in your program indicators directly and you'll have a very easy just drop down menu showing you how to choose the analytics context that you want. One more word about continuously released. I put this up here so that you could get a glance at what we mean when we say continuous release. This is the versions that have come out since June 1 of the capture, meaning that we in the app are able to constantly be adding in required features required changes updates fix. In the app of it would tell you, for example, update to latest version and will tell you which version that is it has very easily that you can uninstall the version that you have. And again crucially for us we know upgrade processes are very challenging they can be technically very difficult politically very difficult, and you don't need to update the back end to in order to upgrade this app. We've done everything we can to make the newest features compatible backwards to 238, which is when the capture app was was really coming out, meaning that right now if you're you're not able to get up to 240 in order to take advantage of it. Most of the new features you can get through the capture app through an update pressing that button is kind of instantaneous it's a very quick and easy painless process. That doesn't mean you don't ever upgrade again in fact there are a number of things that won't be able to work. If you're installing and hoping to get for example, the the program indicator changes for ownership analytics, you would need to upgrade the whole thing but but a lot of the kind of user experience usability features things that can change the look and feel of the app, those are available backwards compatible. So you can have the latest version of capture, even if you're on several versions back in in terms of the back end. The last thing I wanted to draw up here was a big thanks to our implementation team that's been working on the design guide for the the individual data for tracker. That's something we haven't had for years and years you've all been just making your own approaches to this which is great, but we finally have some very detailed information about what considerations there are when you're setting up your program and giving you recommendations about the best way to structure them. So, with that, I will finish up. Good morning everyone. I'll try to use this mic. My name is David Kennedy. I've just come on board as the new platform product manager. I'd like to introduce all of the features that have come on to platform for last year. I haven't been here for the whole year so if we go into a little bit more detail. So if you want a little bit more detail please come and find me and I'll point you to someone that can explain it a bit better. We're diving into a big one here. We have a brand new data entry app for aggregate data. This has been released now on a brand new technology stack. The old app was about 10 years old so it was time for an upgrade. We're currently running both the existing old data entry app and the new one at the moment. And what we'll do is we'll be adding more and more features to the new app and then slowly hopefully people will move across before we can retire the old app so don't panic. If you're very entrenched in the way that you're doing the aggregate data entry, the new the old one will be around for a while. And then we'll add new features into the new person as you can see similar to the new capture app that the top bar has the full context which will stay with you as you scroll down so that you can see which org unit which period which data set you're doing so you can maintain the context. This one's also been very well received. We've got an org unit data filter. If you're browsing the org units and the data set has not been assigned to that specific org unit it will show up with a little cross there so you can't select an org unit that doesn't have the data set attached to it. We've added some extra details to on the side to the minimax limits, the history and the audit log without having to change or go into a different screen so you can scroll through and see that extreme information as you as you go. This will be the validation also on the sidebar there without having to switch context. All right. There's also a lot of improvements to the offline data sync. This was something that we had a lot of requests for. There's a lot behind the scenes here that I will not try to explain how it works. If you do want a more more detailed explanation. I'll find someone that can explain it better. All right. A little bit of a shift. We've got now multiple org unit geometries. What this means is that for each org unit you can have not just the point location for the say where that facility is, but also the capture area so you can have an area and a point location or multiple capture areas for different different uses to be displayed in the maps. And then there's also a crosscut app which will allow you to generate those capture areas. So if you don't have the geojason files you can go and generate them with crosscut and upload them to the org unit. We also have a cool feature that is integrated with the Google Earth engine. Now this allows you to automatically load an org unit geography to the Google Earth engine. And bring in the population data. So if you don't have good population data already in the system, you can use this service to actually bring that in, use it as a denominator for indicators and analytics. So here's a little screenshot of how that works. You can select the org units, link it up and bring in that population data. Here's a preview. You can preview before you load it so you can sense check, make sure it looks correct before learning it in. This is one that we expect to be quite popular. There's a new multi-select for the text box in the data entry. So this is a very, very requested feature. Happy to say that it's available now. One screenshot here as you can see, rather than just one choice, you can have multiple colors. Red, blue, green, just red, just blue, you can clear a filter. There's lots and lots of ways that I'm sure that people will love to use this. Moving to a little bit more superficial, not so technical. New app icons. Everyone, everyone might be used to the old ones, but the new ones, there's references to the old ones. You'll be able to see some familiarity. But now there's some consistency. It looks a bit easier, hopefully aid the navigation flicking through all of the different apps. The apps haven't changed. So if you upgrade and you see that the icons have changed, don't stress that all the apps have changed, we're just changing the icons at this point. Here's another big one, the aggregate data exchange service and app. We'll have a look at it. This is really, really powerful new feature. This allows you to either transfer aggregate data from one instance to another or within the same instance. So this allows you to take tracker data and put it into an aggregate form or actually upload data to a different instance. So if you, for example, wanted to take tracker data for COVID vaccinations delivered for a certain age group and put that into one aggregate value to upload to an HMIS, you can do that through this service. It runs at the moment as a service and through the API. There is a web app that we are also will be in continuous improvement. So at the moment it's there, but we'll be adding a lot more features very soon. Here's a couple of screenshots of how that works in the web app. And this will the configuration will be improved a lot over the next coming years. We also have improved data integrity checks, lots of these. These are really powerful to help the data instance managers find out what the data quality issues might be within their instance. There's 25 at the moment, we are going to keep adding more and more. So this allows them to run really quick checks to see where there might be issues with the data and go and find them and fix them. So you can see here the interface lots of different choices. And again, the more and more choices will come to help people clean up the data moving along to job sequencing. So this is again a bit more back end, but it will allow people to bunch jobs into either parallel or sequential sections so that you can run a whole series of jobs if you need to run analytics before you do something else you can now sequence it. Set it all off and not have to run each job and wait for it to finish before starting the next one. This is a big exciting one for a lot of people. The API for dhs to has gotten very, very big, very, very extensive. And that means that it can be hard to find the right place in the API for the for what you're looking for. So now the open API three specifications are available, which means that you can download the entire API and use a browser like stoplight to go through and see what all the the functions are, be able to navigate certain sections. So if you want to just look at one part of the API not the whole thing you can look at focusing on that one section. So hopefully this allows developers to browse the API faster find out more information, make more extensible apps. This is another one that's quite technical but we very, very exciting for people that have been waiting for it. This is event hooks, which means that you can set something up to listen for a change in the system without having to go back and check frequently whether that that item has changed. At the moment it's available for the metadata and schedule scheduler features but this will be coming more and more would be moving this to meta users and and data itself. So this means you can set up an event hook to listen for for example when the analytics has finished running and then have an activity either in the console a console web hook Artemis or Kafka and there might be more targets coming soon as well. So this is a preview in 40 so that means it is fully featured but only for a couple of metadata elements and we'll be expanding that soon. This is another kind of more technical one that might be very exciting for people that have been waiting for it. So this route API means that you can now access external services that through the DHS to server where you store the credentials on the server and you don't have to have that external service exposed to the public internet anymore. So this allows you to be a little bit more secure allows you to access more external services without worrying about exposing internet and has a lot of expandability options. I think that's me done to pass over to Scott. Okay, best for last. I'm Scott I'm the analyst product manager I'll also respond to Mike or awesome or by Austin as well. Everybody gets us confused David shaved his beard off so I think that's probably clear who David is. Before I get into it I just want to say that I am not going to talk about maps, and the reason I'm not talking about maps is because there is a mountain of new incredible functionality in the maps app, and it deserves his own plan recession, which will be tomorrow morning. So tomorrow morning we're going to do all maps. And, and you're going to be able to see a lot of the incredible things that have come, but don't worry we have lots of other fantastic analytics apps and I'll go through those now. So just jumping straight into it. A very long requested functionality is now the ability to add custom calculations in the data visualizer application. So what does this mean this means that you're a district health officer, and your system admin never answers their emails or they don't listen to you and you need a new indicator. Right. So, instead of just doing it in Excel. Now you can just make it make it yourself in DHS to. And you can actually see that once you make the new calculation it's tied to the data dimension so that means it shows up just like other indicators of data elements, it can be applied to any different chart type that you have in the data visualizer application. And it will be saved to this particular chart, but even better. It can be saved and you can reuse it in other chart types so a few important things to remember here. It does not create a new indicator so for all of you sys admins out there who are kind of like oh crap now they're going to make a ton new indicators. It doesn't make a new indicator. So you still have control over that. But what it allows them to do is create what they we call a calculation that is saved in DHS to and also able to be pulled in to other charts other analytics that are made in the data visualizer application. So you still have your key population or key impact indicators. And those are run by sys admins, but you can as a user now make your own calculations that you can use in multiple charts maps, well not maps but multiple charts as well. It can be applied to any chart type so not just pivot tables but bar column pie whatever you want. And of course it will show up on your dashboard once you once you put it in. I'm very happy to announce that all of the analytics apps will nearly all of the analytics apps are on the app hub so just as the others have mentioned will be able to make continuous improvements and releases to these apps. So some bug fixes, some small new functionality. Of course if there's something that requires a back end change then we'll have to wait till the next release, but if it's a front end issue, we can hopefully continuously release that and make it available to you. We have also in the line listing app added legends. So, you're able to now apply a legend to your line list so it looks something like this. And one fun fact about this ticket is, or this functionality is this was actually the oldest ticket that are older functionality request that we had still in DHS to it was made back in 2016 by Lars. If you're familiar with our ticketing system. It was DHS dash 75 and for context, we are now at DHS 15,000 something. So, so the moral of the story is, don't give up. We will. Don't be discouraged. Of course, of course we had to build a whole new application to add this functionality to it but we did eventually get there. So keep hanging in. Okay, you're also able to add the schedule date to the line list app. So what does this mean this means that you can look at persons who were scheduled for appointments last week but didn't show up. You can look at persons who are scheduled for appointments next week or next month, and you can show those in the line listing app. And I'm also very happy to announce that the line listing is available now on dashboards in version 3839 and 40. Yeah. I know, I know a lot of folks were, were getting a little impatient, I appreciate your patience. And I'm happy to say that now you, you can have all of your line this on your dashboards. An additional functionality is the ability to add a legend and an icon to the single value chart types so you can see an example here. And, and you know, just like all the other products were going we're constantly going through a process of improving the user experience making the data come more alive, make it more available is more easily interpretable. And so we understand that adding these icons and then just changing the entire background color, hopefully makes it pretty obvious in terms of performance and exactly what the indicator is measuring. The icon of course is selected through the icon library in the maintenance app configuring the data element or the indicator. We have to talk a little bit about performance, we are continuously making performance improvements and investigating performance issues. And I want to sincerely thank all of those who come to us with performance issues, although we are doing much more rigorous than we all are using DHS to in many different ways that we can never test for in different context scenarios, scales, whatever. And, and there will be performance issues that you might run into that there's just no way for us to necessarily know about giving our test environments or our testing team. Over the last year you've been communicating these to us at least quite a few of you have been, and we've been trying to make continuous improvements to the analytics performance. So I'm also happy to say that analytics queries are about 25 to 40% faster over 2.35. And we're able to now generate our analytics tables about 40% faster, but continue to please communicate to us and number one rule is don't suffer in silence if you run into analytics problems do reach out. And I think that is it from me so now. Thank you Scott. All right now we get to do the fun part of the evening morning, whatever wherever we are. It all blends together these days and. Okay, so we've just heard a lot of very cool features can we have one more round of applause for all of everybody that went into everything that went into making those. That was also record time for how quickly we got through all of those features that were released in the last year I think we skipped quite a few as well so definitely look at the release notes and the webinars which go into a bit more detail about what what we have introduced in each of the releases. So this next section is going to be going to be a little bit interesting because we're actually going to have a little bit of role play. We have a few, make sure I'm here. We have a few actors in this, this little scenario for you. Brian, my colleague from the implementation support team at UIO is going to be playing an outreach nurse. We have Victoria who's going to be playing a district health officer, and I will be the omniscient narrator slash DHS to system administrator. I don't know if it's to stay in character but I might I might contextualize things a little bit for you as well. So, what we're going to do now is we're going to just weave together a few of the features that you saw here in introduced in DHS to version 39 and version 40. And we're going to show you how how those work together in a pseudo realistic situation or scenario. So in order to do that I got to switch the screen here. Can you believe I'm doing this correctly. Yes, it's a little bit blurry perhaps but you should be able to see my screen here now. So as your omniscient system administrator I am going to be doing a little bit of configuration to get us set up. I'm not actually going to be configuring the system but I'll do some some apps to install some applications to get the latest versions of the software. And then we'll go to our correspondent in the field, and who is the outreach nurse Brian, and that'll be in just a couple of minutes. But to start us off I'm going to go ahead and install a couple applications that have been continuously released in DHS to. So to do that, I'm going to go to the app management application. As you saw earlier this is where you can see a lot of different apps and the new versions that are available. So as soon as they're published or released. It shows up on my screen okay there we go. As soon as it as soon as a version of an application is released it'll show up here in the app management application you can update your applications independently. So we'll get back to core apps here in a minute and to do some updates there. But first, I'm going to start with what Scott just introduced, which is this line listing application. So you'll see I actually already have this installed but you can see the list here all of the versions that have been released of the line listing application. So you can go ahead and install it into your system to get that functionality. And, as Scott mentioned, this is available from 238 239 and 240. So this same version of the application with all the latest features, maybe some that are turned on and off based on this version of the server you're talking to are available there. So I've already got installed this one, I would click a button here to do that. I'm actually going to demo that so I just uninstalled it. Now you can see that I don't have a version installed here, and I'm going to click the install button to install the latest version. It takes just a couple seconds. And there we go. We have the line listing application installed into our DHS to instance. There's one more application that I'd like to install here as well. I actually already have this one installed as well. But you can see that this is the APK distribution application. So I'm going to do that one in just a moment. And the last thing is a very cool feature that Scott just mentioned, which is putting line lists on to the dashboard app. In order to have this functionality, we need to have the latest version of the dashboard app. So here in the core apps section of the app management app, you can see the the versions of the applications that are built into the app have updates available. So there's obviously a dashboard application already in this DHS to version 40 instance, but I can actually go here and we'll see that this one just was released on continuous release last week, June 6, which with this version after the 40.0.0 release. And there is a new version available that I can go ahead and install. So if I click install here, I'll get the latest version of the dashboard application, which allows me to include line listing application line lists on my dashboard. And with that, I think we're all set up. I did want to show here also quickly, we're not going to use this for the demo, but I could also update the version of the Android capture application. So you'll see that I already have a version installed here in my system. That is version 132.8. The version numbers are continually increasing and each each application has different version numbers. So usually you just want to go to the latest one. But you can go ahead and install that latest one if you wanted to, you can keep it on a slightly older version if you wanted to keep some of the if some something changed that you didn't like in the interface for that. For some reason, you can stay on an older version as well. So I wanted to show that in the capture app which is also on continuous release and has been for quite some time. Okay, so with that, I think I'm going to switch over to my colleague Brian who's actually not in the in the call here today. So I'm going to see if I can get him on the phone. See if we can call him in here. Let's see. Go ahead and give him a ring. Brian, are you there. Hi. Can you hear me now. It's Brian. I'm going to install my DHS to application. This is actually my not my first time putting it on, but I've just going to log in here really quickly. And while I'm logging in, it's going to be waiting for the authentication to happen. And yes, I actually do want to help improve this app. This is something that everyone should be doing. I'm going to send some notifications about it. Thinking configuration. And while I'm doing that, just thinking about what I have to do today. Some other things. This is a big part of being an outreach nurse is just waiting. But as a sync my configuration, I can also, I can also plan out my route for the day and where I'm going to be going. So I'm going to say, first, my configuration is ready. But I also see that I have a software update that's available to download right now. So I'm going to download the software update. And I'll say, yes, please. Please allow from this source. And then I will go back. We'll in the background of the application. It will be. Yes, I will. So I'm just going to open up the child program here. And then I'm going to see who I have to find today. So I'm going to open up my, my filter here. I'm going to go to my visits today. And I'm going to see here that I have Joel and Martin that I need to go visit. So when I go back to my, my list here, I can see that there's also a maps icon at the bottom. So I'm going to just quickly check out this map. And yes, I will allow location while using this app. And I can see as I zoom in here that actually they're both pretty close by to me. So who do I have here? I have Joel and I have Maria and Martin. So first I'm just going to select Martin here. And then I'm going to say, Oh, I want to go find how to find Martin. So I'm going to open up the maps application here. And while it finds Martin, it's also going to give me directions for how to find where this house is located. So I'm going to ask it to give me directions in Google Maps for how to get there. And turns out they're pretty close by because they're just in the auditorium over here. So we're just to walk over here. Usually have my bicycle for this part, but not today. Hey, was there a Martin here? You look like Martin. Okay. Well, I'm going to ask you some questions about your baby now I hope you don't mind with this live studio audience and everything. So I'm just going to click on Martin's name in the card here. And now we'll go through the baby postnatal visits. So I'll enter in the report date. How fat is your baby? 780 grams, like 780 785. Yeah, metric system is tough. I'm breastfeeding. No, no breastfeeding. Okay. Yeah, replacements. Okay. Measles. No, no, no measles, but you've received a dose for it right. Yes. Yes. Okay. Okay. No anti vaxxers here. We're good with that. I'm going to give you a dose. Also good. I'm going to give you a vitamin A supplement. Yep. Childhood ARVs. Nope, not for us right now. I'm actually really happy to tell you Martin that we have your HIV test results for your child. Yeah, that it comes from the PCR and they are negative. Hey. So I'm just going to ask you to add your signature right there if you could. Yeah. Beautiful. Right. You're an artist. So we're just going to save that up there. And now just save the event. And that's the last visit I had today so thank you Martin slash lad. Now, that's not the last thing that I had to do today. That was my last outreach visit, because now I'm going to plan my subsequent day and the next work that I have to do. So I'm going to swap over to the capture app. Whoops. Whoops. Can you see the screen here? Might take a while. Yep. So in the capture app, I'm actually going to already have this child program and my registration unit up here. And you can see the list of all of the different registered patients here and the child program that I have to follow up and see. So I have a custom working list here for just children who are low birth weight in a supplemental feeding program. So that could not be loaded for right now. So I will also maybe it's because there we are. It's always clear cash or not logged in. So I'm just going to go back to the capture app. And then again, child program. And click low birth weight. So now we can see that it's pre selected for me. The date of enrollment is in the last three months or last 90 days. The program stage was at birth and the weight was less than 2500 and it had a mixture replacement feeding in the child health program. So now I can see that these are individual children that I should be following up with tomorrow. But it's not the last job that I have to do. My work is not complete until it's all documented. So a part of my job as well is that I have to find my facility tally sheet for mortality and statistics. So I'm just going to enter into the data entry app here. Fortunately, these are all the children under five and say month that occurred. So at one case, a cute classic process. No rabies, cholera, some malaria, measles, meningitis, no plague, thankfully, and some no rabies, hyphis, et cetera, et cetera. So once I enter in all of these here, once I enter this, then I can run validation and see what the alerts are, that there's a high number of yellow fever and meningitis cases here. But then I will also mark it complete and that's my day for today. So hopefully someone will give me good feedback on the data that I have collected and we can improve our health programs from here. Thank you, nurse Brian. Now we're back at the system administration level so I'm pulling that up now hopefully we can get it on the screen. Okay, great. So we were we were just here. I forgot to demonstrate the actual uploading of the application to install the version so I am omniscient but I don't. I'm a bit impatient and skip some things sometimes so I will demonstrate just here quickly that you have a version of the Android capture application that you can upload in this APK distribution app. And so this will allow you to specify the versions of the Android application that the users in your system will get notified about, which is a very useful feature, I think we saw the update notification that Brian got when he was out in the field. So the last thing I'm going to demonstrate here as well is the data exchange application. So we just saw some data come in through a tracker program, which is individual level data. But sometimes you want to aggregate that and put it into the aggregate data model either within this DHS to instance itself so moving it from a program indicator or a program data in the program to a number in the aggregate data model, or potentially to send it to an external system, maybe you have a tracker system and you want to set to aggregate your tracker data and send it to the HMIS. So that's something that can now be done using the data exchange service and the data exchange application. So I actually have already configured one of these exchanges. And here I can see what data will be sent or will be aggregated. This is taking tracker data, and it's sending it to an aggregate data element. So I have the number of OQV three doses given in each of the chiefdoms in the, in Sierra Leone in this case. And so you can actually go through and review all of this data manually. And you can also schedule this so that I could schedule this so that it would run nightly, for example, or run after maybe maybe once a month I want to send my tracker data to HMIS or to another repository somewhere. And once I've reviewed this and made sure that it's okay. So I'm going to click submit. So it asks me to confirm what data I'm submitting. Again in this case we're doing an internal data exchange so we're actually aggregating the tracker data within this DHS2 system and putting it into the data elements in the aggregate model within the same system. So I'm going to go ahead and do that, and it's going to submit. And it will show that in this case this data was already created but I've updated all of those data values for the aggregation of the individual level data over the last 12 months and that's now in the aggregate data model and I can use all of my visualization tools. I can correlate that with other data in my HMIS without needing to query the individual level data directly using a program indicator, for example. Now we're going to go back to someone who's doing a little bit of analytics on this system. So with that I would like to introduce our district health officer Vito to come up on to her office and demonstrate a little bit how to use the data that we've collected in the field and how to use that at the district or the national level. Vito. Yeah, no, Brian. No, fantastic job. I heard you. What are you doing in surgery? What do you mean the loss to register? No, no, no, no, it's okay. It's okay. Just try to find it. Yeah, no, no. Is it it? No, don't pass it. No, Brian. Brian. Brian. No, don't pass him. Brian. No, no. Brian, Brian, you're fine. Hey, hey, hey. Hi, no, it's fantastic. Fantastic to hear from you. No, lovely. Yeah, no, every day I check. Yes. Yes, they enter weekly. Yes. I check every day to check that they don't enter more often, actually. Yes. Yes. Beautiful. Yeah, yeah, no, we're doing great, actually. Yeah. Yeah. Yeah, I'll keep you updated. Thank you. Thank you. Cheers. I have not entered or checked a time months probably. Sure. Okay. So, thankfully, I actually like follow a little bit when my admin dials me. But let's check a little bit. Yeah, that's actually, let's follow what admin says. Okay, so I have here my data that I had done a while ago. It's not fine. That's fantastic. Okay, so I had to check some, some immunization doubt, because that's supposed to be my job normally. I forgot my glasses, but it's okay. Actually, I forgot my glasses. Actually, my glasses are there because the demo is good. Okay. I have my OPV because we're doing great, apparently. So I have some deaths here, and I've heard that they were doing already some calculations. So I might add it there. But unfortunately, they told me that I don't have anything on coverage. So just, just very quickly. Oh, the pressure. How do you do it? I have OPV data. So that one. I know about weight. And of course, for coverage, you need a population under five. There you go. There you go. That's a good one. And then times a hundred. And then I call it. Let me check the formula because you know not all right. And then OPV three coverage. And I save it. And then I update it as well. So yeah, I should have everything there. So how do we even have high coverage that we have children? We need to find out. But doing great, doing great, not doing amazing. Yeah. Okay. Just, just let me quickly check what's going on here. So let me remove that. Let me remove that. And I think we should go down there. Let's do quarter since it's been a while. Okay. Let me check if I can do something like that because I've heard that I can actually, I can actually change it. Yeah, no, no, it doesn't work like that. There you go. There you go. And I heard that I can actually change and do it properly. All right. We're not doing amazing, but we can get there. We had the last year though, nonetheless. Okay, we might have a problem here. Okay, just let me save it a little second. Okay, let me go here. Got to love when they change all the icons. Okay, so we're doing great here. Okay, so actually something that I have to thank, I mean, again, remind me later, the line list, because I knew that something was dodgy here. Oh, there you go. There you go. And then the OPV3 coverage. Oh, do you want to me? There you go. I can't find it as usual. Oh, whatever. I'm going to type right into it. Okay, so I'm actually going to call Brian just a second because it looks like there's some work to do. Brian, so yeah, yeah, I already told you to get out of there. What do you mean they lost the surgeon now? No, no, get out. We need to like schedule some more visits. Just get out of there already. We need to talk. Thank you very much to Vito and Brian, our two actors today. Big round of applause. We had a volunteer from the audience as well who was a very proud father. I don't want to say thank you also to Marta Vida and Grant, who did a great job putting all of this together it was a little bit last minute but we're we're excited to try something try something a little bit different to weave the different features together so thank you to Marta and Grant. And with that, I think we are done for the morning and we are moving on to lunch. So is there an announcement before we move to lunch. Thank you everyone for your attention and for joining us on this journey through DHS to we're going across the across the courtyard here to lunch so follow follow some of your helpful UIO staff who I'm sure are going to be leading the way. And bring your badge, you don't get to eat unless you have a badge. So make sure you bring your badge. And there'll be instructions waiting for you on the other side. Thank you all very much.