 Many countries have some fairly good systems. Some countries have excellent systems. And I'm not here to say that how donors and multilaterals have been spending their money as a waste of time. But what I am trying to say is that from our perspective, as the DHIs to platform developers and managers, we see a large hodgepodge of different systems being used, very little global coordination or standardization, and a very wide range of sophistication. And I think that is a good foundation to appreciate what do we actually want to do with DHIs too. Martin, you can go ahead and start recording now. Looks like you are. Great. OK. So what do we want to do with DHIs too? Well, we want DHIs too to be the single platform. And the platform, our DHIs to platform is not just one thing. It's many different apps, right? You all use DHIs too. Hopefully you know that it's made up of different applications, kind of just like on your smartphone. There's multiple applications. DHIs too is the same kind of platform. But we want that platform to have all of the apps and tools that are necessary for facility level and community health worker level logistics reporting. We want to make sure that you can use DHIs too in the apps that are within that ecosystem to be able to report all of your supply chain at the lowest levels. Again, that's one of the biggest issues that we've seen. You don't have to take my word for it. That's something that Global Fund and WHO and Gavi have all published is that there is a lack of resources and tools at the lowest levels for logistics reporting. And we want DHIs too to be able to be that tool. Many countries are already using DHIs too at the lowest levels for disease reporting, surveillance reporting, service delivery reporting. And so we want that to be able to be extended into supply chain as well. We also want to develop standards for supply chain indicators and reporting in partnership with the WHO, with the CDC, with Gavi, Global Fund, and others. And we've actually established these lines of communication. We have already developed some of these standards in partnership with the WHO and we'll be presenting those throughout the week starting tomorrow actually. But we want to continue to develop on this. We want everyone to kind of appreciate some harmony here and make sure that DHIs too is able to support that those standards. Also very importantly, we want DHIs too to have as easy interoperability with other supply chain and logistics software out there. We know that many of you, and I've previously said this are using other systems. Maybe you're using Medexis, OpenLMIS, M-Supply or maybe you've developed something locally. But we want to make sure that if those platforms, those other supply chain software that you're using and maybe that you like them a lot we're not saying that you should change necessarily but if you do like that you do want to use it then at least on the DHIs too side it should be able to speak to those systems. Now the question always becomes is can those systems speak to DHIs too, right? It's a two way street. You know, the interoperability can't only be on the DHIs too side it has to be on their side as well. And that's usually where things start to break down is we maintain what we call API that's application programming interface. That's the backend interface of DHIs too. We maintain interoperability standards there. And I think on Thursday more than our lead interoperability engineer is going to take us through some of those. And we're going to hear from John Lewis who's practically used them to make interoperability with some supply chain software out there. But we want to make sure that we maintain these standards so that if another system wants to be able to talk DHIs to it's as easy as possible for them to do that. That requires a lot of work on our end to maintain these standards developer time and time that we're not developing new features and shiny buttons and new fancy apps this is all work on the backend that basically no one ever sees unless you are trying to connect two systems together but it's necessary and we make sure that we have the resources required to be able to do that. We want to be able to calculate or produce all key logistics indicators and analytics. So any and all supply chain indicators that you deem as necessary or that the donors and multilaterals or say are standard or required we want to make sure that that value can be calculated in DHIs too. That DHIs too has the functionality the ability to be able to produce that value and produce it accurately to produce it that value whenever you need it. That number is always available to you and it's available to you on any type of analytics that you need that you want to see. So whether it's a scatterplot, a bar chart, a map, a pivot table, a dashboard, a standard report however you want to actually see that indicator we want to make sure that that indicator can be seen in that way the way that's the most appropriate to you. Second to last point here is that we want to also provide the guidance to countries and users how to get LMIS data into DHIs too. And this academy is the very first step to providing this larger global guidance. Again, this is the first time we've ever even done this academy. And so you're all a little bit of a guinea pig right now we're all you're the first cohort of folks that we're kind of testing this academy on. We certainly appreciate your patience and we do very much appreciate your feedback but this is the first step for us as a platform, as DHIs to owners and for you yourself as the DHIs to user community that is interested in supply chain to start to build out this kind of guidance that can be handed into countries. And again, I talked about wanting to build a community of practice after this. I think that's one of the major goals of the academy is that this doesn't end on next Tuesday that we are actually all kind of moving together as a global community, sharing ideas, learnings, lessons best practices resources collectively to actually just move us all forward together. This is something, this is not a zero sum game. This is something that everyone in the world can benefit from. And we wanna make sure we have those connections in place to be able to allow that. And then the last bullet point and this is the most important bullet point probably the most important point of the entire presentation today. So I might repeat it several times it's also going to be one of the quiz questions at the end of today. We do not want to develop DHIs to to be a warehouse information system or to be a complete ERP. That's electronic report and electronic requisition and reporting system. That's like the kind of systems that you see at grocery stores or supermarkets but check out counters. DHIs to will not ever be those systems. And the reason is, is because those systems require a fundamentally different database architecture than what DHIs to has. So you will never probably see DHIs to core applications that are developed out of University of Oslo functioning in a warehouse. You may see other software that are working with DHIs to that are operating in a warehouse. And I think that we're actually getting we're working towards that goal. But DHIs to will probably not be the warehouse solution for you. But that takes me back to the the second bullet or sorry, the third bullet point here which is that we want to make sure that we have as good interoperability as possible with these systems so that these systems are talking to each other. And I think that that brings me to this point here. This is a model of what our good friends over at I Plus Solutions who developed the Medexus platform are trying to produce in Burundi and potentially some other countries as well but currently ongoing work in Burundi. And Burundi is using DHIs to as their health information system as many of you are but and they capture data at facility level in DHIs to. So what are we trying to do? On the left side, you see the supply chain information systems. And then on the right side, you see DHIs to serving as the health information system. In the middle, you have the various levels of the Burundi health hierarchy. So it starts at smaller health facilities then you have larger hospitals then you have district level, regional level and central or national level. So what are we trying to do? I think that this actually serves as a great example of what we are trying to build DHIs to to be able to support. First of all, you have DHIs to at the lowest levels at the lowest health facility levels community health worker level. And that means that we don't want to give them we don't wanna give them a lot of different tools. We want the people working at those levels to have one tool that they can use to report all of their data. We don't want them to have to use multiple apps or different devices or go between lots of different registries. We just want it all to be in one place simple, easy, clean as possible. And we are configuring DHIs to to be that tool at the lowest levels health facilities and community health worker level DHIs to is capturing all of the supply chain data. Then that data is then pushed into Medexus. And Medexus is serving at larger hospitals, district level and regional level and also national level to perform the higher functions of a supply chain information system. Those are warehouse management, routing and fleet management, developing pick lists and commodity catalogs. These things that DHIs to is not so good at. And that's exactly fine. I mean, DHIs to is not not always the best tool for every job. So Medexus is there and we are developers are working with the Medexus developers to try to form very close connections and interoperability between these two platforms. And actually, I think it is Thursday where we will have the team from Medexus actually present on what they're doing in Burundi. And I think they're gonna actually be able to demonstrate this to you. So you don't have to take my word for it. It's something that we'll be able to see. So, but of course, data is not just pushing from DHIs to into Medexus. Medexus is also pushing data back and forth with DHIs to. So if you're looking at DHIs to, you're able to see the supply chain data. You're able to see the supplies at health facility level. Then you're able to see the supplies at health facility level and you're able to see your patient data in DHIs to and you're able to have these two and you're able to put all of that data into one dashboard into composite indicators. And that's how you're able to do your root cause analysis or bottleneck analysis. Of course, above Medexus looking at the highest level in the top left corner of this diagram, you have some ERP. So you have like things like Oracle or Sage. Some countries have this, other countries don't. It's not, I don't think it's actually from my experience necessary that you do have a fully functional ERP to have a very functional supply chain. Maybe some other folks may disagree, but at least in the Burundi case, they're trying to push this to another higher level ERP. So I think this is a good model and I think Medexus, they may actually present this model again, but to me, this is one of the clearest pictures of what we're actually trying to get DHIs to, to be able to do. Again, capture data at the lowest levels, produce those analytics and indicators around supply chain all the way up through all levels and then have these more specialized functions that are required for a well-functioning supply chain like warehouse management in a product, a platform like Medexus that is specifically developed for it and have the data moving back and forth between the two. In the future, could it be that Medexus is presented in DHIs to ecosystem? Could Medexus just be maybe another application within DHIs to, possibly? And it's something that we're going to be exploring over the next several months with them as well as our other partners. But as it stands right now, Medexus is a separate platform and we're working with their engineers or working with ours to make sure that those systems are able to speak to each other. Okay, so this is kind of what we want to be able to do. How are we going to get there? So we commonly say that now we have four legs to our LMIS approach here at the University of Oslo as well as with our partners in this. The first leg is that we have new DHIs to functionality. The second one is that we have new content. Of course, this Academy being one of those. We have the third leg being interoperability integration. Again, I've talked about this a little bit, but we'll go into a bit more detail. And the fourth leg being some technical expertise. So people who actually know both the DHIs too, who know supply chain and are able to actually develop solutions in partnership and collaboration. So let me just go into each one of these in a little bit more detail quickly. So functionality. Over the last three or four years, we've been developing a lot of new features in DHIs too, to facilitate both the data capture as well as the calculation of indicators and the presentation of those indicators in DHIs too. For example, in the capture app, that's the Android capture app, what you use on your mobile device, you are now able to do QR code scanning and barcode scanning of commodities as they come in. And George McGuire, I think on later in the week, will actually be presenting on how the international right cross is currently doing this in filled hospitals in Yemen, which is gonna be really exciting to see very cutting edge use of DHIs too. But we know that scanning barcode, especially for immunizations is extremely important. You wanna get that batch number, you wanna get the commodity details. You wanna get it in the same place that you have your patient data, because if there's an adverse event or reaction to any of the immunizations or drugs that are being given out, you wanna know who received that drug, who got that shot from that vial, from that batch number, and you want that to be all able to be easily put in through barcode scanning. And so now we have that, we have that in DHIs too. And you can use that two day, if you're using DHIs too. And the mobile app, the mobile capture app. We also have been developing resources, technology resources like the API that I mentioned earlier, as well as many others to be able to support local innovations within DHIs too, to be able to capture supply chain data. And we're gonna have a few of these present. So in Mali and Burkina Faso, his West Africa, that's Adam Kosi's team, again, he's gonna be presenting tomorrow on this. They developed an app for the capture of supply chain data. And that's the picture at the top, the first picture at the top, you see that is the application that they've made. And it provides, it does a lot of calculations automatically, it provides a really good, clean user interface for the lowest levels to be able to enter in their supply chain data. And so Adam is gonna be able to present that tomorrow. We also in Bangladesh, a group of developers has made up a kind of a fork of DHIs too, called D2 log. And this is basically, like I said, a fork of DHIs too, specifically for supply chain. So that's another innovation within the DHIs to ecosystem and community. And then the last one, which is the bottom picture here, that is from Uganda. Uganda has also developed a supply chain application for the capture of supply chain data at lowest levels. And so that's what you can see there as well. And we want to support these local innovations. We wanna make sure that DHIs too is a platform that people can build apps into. And those applications can be, say, unique for Malawi, or sorry, for Mali or Burkina Faso or Uganda, but you can still feed data into the same data warehouse or backend and produce indicators and analytics using the common applications like maps and charts and pivot tables and scorecards. The third point to make on the functionality is that we want to be able to integrate aggregate and tracker mobile data together. And so if you're entering aggregated data and you're entering tracker data, if you're not sure what tracker is, tracker is the modality of data capture that we have in DHIs to track individual, what we call tracked entities, which could be a patient. It also could be a drug or maybe a stock out. It doesn't necessarily have to be something tangible. It can be the lack of something like a stock out. And we want to make sure that those different types of data can be captured in one tool as well. And so again, with the new Android application, the new Android capture app, you're actually able to capture both aggregate data and tracker data in one app. There's not moving back and forth between multiple apps. There's just one app. All the data can be put in in that one place. You only have to provide one training to the health staff to be able to enter that data, right? So that's a new innovation and that's largely built on the development of the Seastock system, which I'll talk about in a little bit in just a few minutes in Kenya. Some additional functionality. Now, if you're a DHIs to techie, you're going to appreciate this a lot. If you're not so technical in DHIs to, maybe this might go a little bit over your head, but I'll just try to make it as simple as I possibly can. And I think later in the week, we will come back to going into this in more detail. But starting in DHIs 2.29, 29, all the way up into DHIs 2.34, which is we're currently at DHIs 2.35, DHIs 2.35. But from 29 to 34, we built in something called predictors. And predictors are a special way in which you are able to calculate indicators in DHIs to your calculate values in DHIs 2, referencing previously reported data. So this is very important. Being able to reference previously reported data gives us the ability to say, like, calculate consumption averages, right? Consumption averages can be used to calculate things like stock status and resupply values. And these really key supply chain indicators. So predictors have been there actually now so for about two and a half, three years. And those can today be used to calculate some very complex supply chain indicators. We also have built in some advanced indicator logic. So little known fact, if you're a DHIs 2.techie, you're probably not aware that on the bottom picture here, so if you look at the bottom picture, you can actually see that I'm building you can build indicators now in DHIs 2 that have some aggregation of logic in them. For example, if statements. So you can see here's an indicator that's saying, like, if this, then do this. If not, then do this. If not, then do this. If not, then actually it's the if and or statement. So if this, or this, or this, or this, or this, do count one. If you didn't follow me, that's okay. But it's just basically to say that you can build out fairly complex logic in standard indicators now. That can become very important. For example, I want to count the number of health facilities that are stocked out of all malaria commodities. So I can say, if this stock equals zero for ACT6s, if the stock is zero for ACT12s, if the stock is zero for ACT18s, and the stock is zero for ACT24s, then count one. And that would tell me that would actually put a value for all of the health facilities that are stocked out of all anti-malarial drugs. And then you'd be able to build maps and charts and dashboards and stuff with that number to show, hey, now get a total count of the number of health facilities that are stocked out of all malaria drugs, for example. Again, we're gonna go over this in a lot more detail later in the week. So if I'm losing you now, it's okay. But just to let you know that these kind of functionalities are available. And of course, the last bullet point is we have something called program rules, which we are now able to connect an individual dosage of a commodity to a specific patient. So you're actually now able to say that this patient got a shot from this vial. So in the case of adverse events or something like that, we're able to make those relationships and produce some analytics around them. So what are some of the indicators just to give you a snapshot? And again, we're gonna go over this in a lot more detail later in the week. We're able to do things like resupply values based upon average consumption as well as seasonal trends. Again, yeah, average consumption, maybe average consumption is looking at, and you can define your average consumption. Maybe you wanna look at the last three months. Maybe you wanna look at the last six months. Maybe because you're looking at some kind of seasonal consumption, like with malaria or rotavirus or something like that, you have a kind of a more seasonal frequency of these kinds of diseases. Then you once say, I don't wanna look at the average consumption in the last three months. I wanna look at the average consumption over for this month over the last three years. If you're going into the Epicurve, you don't wanna look at the last three months because that would be misleading because that has a lower consumption. You wanna look at maybe the consumption over the last three years at the same point in time. So you can do that as well. So this is all very definable by you. You can also do stuff like stock status. So I wanna say the facilities that are understocked, adequate stocked or overstocked, and you wanna count these or you wanna have a percentage of each order fill rates. So how much did they ask for versus how much did they actually receive? The number of stock out days, lead time, which is the amount of time between when a facility needs a drug to when they actually receive the drug. And we are also able to do, depending upon how you configure DHIs to, line listing of something like current stock outs or the total number of stock outs over time. So we say, where are those facilities today that have a stock out of some drug? We can do that kind of analytics and calculation in DHIs to now. If you don't believe me, you can take Malawi's word for it. Mungini from His Malawi will be presenting this later. Just a quick look, this is some of the work that they've been doing in building out some supply chain indicators and analytics. And it's really incredible what they've managed to achieve over the last year and a half where they're actually able to seed now in Malawi, where do they have stock outs of various drugs? And what is the stock status for each one of, at each facility for each one of the key commodities that they track? They've really done a lot of work to kind of, in the guesswork, they know where, oftentimes where the stock problems are now in Malawi through connecting open LMIS with DHIs too, to be able to produce these kinds of analytics. And so this is actually a picture directly from the Malawi HMIS. And so we'll go over a little bit this in more detail. I think Mungini will have an excellent presentation on how they managed to do these kinds of analytics and these kinds of indicators in DHIs too. Again, more types of analytics. On the left, you see a custom dashboard app that HIST West Africa built for, I believe it is Mali. And in this application, they're able to monitor the stock status at facilities and give key indicators and analytics to monitor the current stock availabilities as well. Again, on the right side here, we have some analytics from Malawi. And again, this is also like demo data as well. So you don't have to, if you're trying to study this in detail, you're not actually seeing the current status in Malawi. Of course, this is all demo data and it's quite old now as well. But you can see that Malawi is actually able to build in some really incredible ratios. So like stock on hand to case load ratio or consumption to issuance ratio. These kinds of ratios where they actually put the supply chain data in the same indicator as the service delivery or case data, right? They have it in one place now. So they can build these kinds of indicators and these indicators are very useful for forecasting, for planning, for policy development, for looking at how disease trends and patterns are affecting supply data or commodity availability data. They're able, because they have the data in one place, they're actually able to build these indicators. And it's a very powerful, very useful analytics to have. Okay, so that's on the technology innovations. Let's talk about the content that we're working on. And again, we're gonna go over this quite a lot of detail starting tomorrow and then George is gonna take us through some of the indicators later in the week. But just to suffice this little bit of an overview right now, over the last, I think about four years, the University of Oslo as a WHO contributing partner has been working with them to develop what we call standard metadata packages. These are packages of preconfigured DHIs to reporting forms, data elements, indicators, dashboards, sorry for the Slack notification. And they are there available for you on our website as well as the WHO website to download. They come with guidance materials, PowerPoint presentations for you to install. So for example, if you are a country that's brand new starting and you wanna start an HIV program which most every country already has an HIV surveillance program. But just to say that you were starting from scratch or you wanted to update your existing one to follow the new global guidelines, we have already configured the data elements and the indicators and the dashboards following the WHO standards for you. So you can grab that standard metadata package and you can just simply install it into your DHIs too, in instance. And you may will probably have to do some configuration, a little bit of customization based upon your clinical workflows, how your country is structured. But for the most part, it's done there. It's something that you can start to utilize much more quickly than say if you had to develop it from scratch yourself. So these exist for many different WHO programmatic areas. So you have HIV immunization, malaria, tuberculosis, I know that they're working on integrated disease surveillance, they have maternal and child health, they have immunization, yeah, sorry, I already mentioned immunization. They're currently working on non-communicable diseases as well. There also is one for COVID-19 if you were interested in that. And we are additionally now building on top of these supply chain indicators and components. So we are building out a standard metadata package just like we have for these various diseases, one for supply chain data. So no longer is it just disease specific data, it's also the supply chain data that goes with these specific diseases. So, and you can see an example of that on the second picture on the right. So looking at some stock indicators. Again, George is gonna go over this in detail. I'll talk about it a little bit more tomorrow as well. But this is really exciting that we have some pre-developed content available. Second, the third leg to our stool here is around interoperability and integration. We are expanding our conversations and communication with other supply chain systems like OpenLMIS and supply and specifically a lot with Medexus as well. And we want to make sure that we are able to be able to speak to these systems. You know, and if you're asking like, well, can you talk to my system that was developed in my country? That's a question that I can't really answer because I don't know anything about your system. But these are three platforms, excuse me, these are three platforms that are some of the more commonly used ones in that, you know, there's a handful of countries, you know, probably a little bit less than 10 using each one of these systems. And so because of that, we want to make sure that we are having, starting to establish some bilateral relationships with these various platforms to be able to have as good interoperability as possible. Next year, we've started those conversations now, next year they're gonna really take off because next year we're gonna have additional resources on our end, developer resources, hopefully to be able to more seamlessly connect these to these platforms. And the last point that I want to make is that we have now some additional expertise. We will have a LMIS starting next year here at the University of Oslo. We will have an LMIS portfolio lead, that's actually Brenno, he's on this. I've seen him post some questions to the Logistics Slack channel. So hopefully this time next year, Brenno will be giving this presentation. We're really excited to have Brenno, he's coming to us from the Norwegian Red Cross a tremendous amount of experience, practical field experience on implementing supply chain information systems. And so he's gonna be kind of steering the ship to some degree starting next year here at the University of Oslo, which is the first time that we've ever had anyone solely devoted to sitting here at the University, solely devoted to LMIS. So that's a huge addition. We also have George McGuire here, you're gonna hear a lot of presentations from working as a DHIS to technical advisor. George is again, one of the world's experts on supply chain, at least amongst all the folks that I've met, certainly a fantastic addition to the team. And the big news is, you're some of the first folks to hear this in the whole world, is that we have a new partnership with the University of Basel, the Swiss Tropical Health Institute and ourselves, the University of Oslo to develop a partnership, an actual organization, it's called the Stella Organization based in the University of Basel, they're gonna present next Tuesday. And this partnership, this organization comes with additional resources, both human resources, implementation advisors, technical experts, but also technology partners as well. So trying to plug in, not just with the three software, other platforms that I mentioned, but with a lot of other much more advanced technologies. We're talking about like machine learning, there's some talk around blockchain and these really cutting, a lot of cutting edge technologies that we could start building around and collaborating with. It's also being very practical. This organization, the Stella Partnership, will focus on preventing global guidelines and global guidance and hopefully producing some standardization, of course, in partnership with WHO and Global Fund, et cetera, but starting to be kind of a resource hub that anyone in the world can start to utilize. So we're really excited about this partnership, the addition of these two people on our team, which again, you'll be introduced to George this week and Brenna will hopefully be someone that you're working with in the future, as well as the collaboration on the Stella Partnership with the University of Basel and the Swiss TPH means that there's about to be a lot of resources and expertise in the DHIS2 community on supply chain. And so something that I hope all of you feel that you are able to take advantage of, to tap into, they're gonna be here to help you. Okay, so I think that is all that we will be presenting for today. Martin, can you help me with any questions that are coming through on the Slack channel? So again, if you have any questions, please post those to the Slack channel. We have a few minutes now, we can answer any questions that you have. So we're taking your questions through Slack. Martin, are there any questions out there? Thank you, Scott. Yeah, first I would like to remind everyone that the word of the day is welcome if you haven't already got it. Some of you may have come in late and didn't get it before. So remember, it is welcome. Right, we do have at least two questions from the Askable Logistics. First one is from Brino. Scott, can you see the question? It's pretty long, so I don't sure I wanna... Yeah, I do see the question. So Brino's question is coming about software development, understanding the ability to share information among various platforms from a technical architecture perspective. Will we touch on this? And will we be able to talk about a little bit about interoperability? Yes, we will, I'm forgetting the day. We have a day specifically on interoperability where Morton, who is our lead interoperability engineer here at the university, will take us through some of the fundamentals of interoperability. And then we have John Lewis, who again is leading HISP Vietnam. Talk about how they managed to form interoperability specifically with M-Supply there in Southeast Asia. We will not be going into a lot of very technical detail on interoperability. This is not a super technical academy. There is a developers academy that is for if you're a DHIS2 developer and you're listening to this right now, I think that it's important that you appreciate that there is a specific academy on how to develop applications and make connections between multiple systems, make applications within DHIS2 and make connections between multiple platforms and DHIS2. That's the developers academy. They offer it several times a year. So I think that that would be the format which they go into a lot of technical detail. But we will be giving you an overview, at least give you a list of key things to consider and show you some examples of it. All right, so the questions are coming in a little bit quicker now. Pascal says in the indicator calculations, internal validation rules to be built in between levels of health facility, hospitals, ministry of health levels. There's often confusion errors around data standards stores, specifically that stores are greater than secondary box packages or containers, cartons, pharmacies have more containers and blisters and dispensary levels have more single tablets. So yes, Pascal, that's a really great question. Actually, two weeks ago, we had a specific academy on how to build validation rules and data quality checks into DHIS2. All of these different scenarios that you just described about inconsistencies and stock levels across multiple places or sites can be checked with standard data quality checks already existing in DHIS2. Again, we have a whole academy on that. That was actually just two weeks ago that we did that academy. I believe that the materials are also still available online for that. So if you just wanna know how to build validation rules, data quality checks, use the various data quality tools in DHIS2, you can do that. Now the question then becomes, do we have these specifically for supply chain? And the answer to that one is no. We have not developed kind of standard validation rules or data quality checks for some of the supply chain indicators and data elements reporting forms that we have been developing with WHO. That needs to come next. We need to actually start working on that. It's one thing to have the standard indicators and data elements together that countries can use. It's very helpful, but it's a whole nother level of usefulness for them to also have guidance on how to analyze the data as well as to make sure the data is clean, accurate and validated. And we need to build those kinds of guidance into the standard metadata packages as well. We don't have it yet. This is all still very new. Hopefully the next steps that the LMIS team will be working on. I think also, sorry, George does actually have a lot of guidance and I think George hopefully will be able to go over this in his presentation later in the week on how some of these indicators can be used and maybe George you can also speak to some of the common data quality mistakes or issues that you might see among them. Sophie asks, is there a general perspective about common, about consumption definition between service delivery points versus medical stores? I think that's a great question that would be good for George or one of the supply chain, more technical supply chain experts to go over in the coming days. So I think that maybe we'll put a pin in that question there, Sophie. Martin is reposting a question from Tentally and asking, do we need administrative privileges in order to customize DHIS2 LMIS app? Well, there's a couple of things here to be said. The first one is that there is not a specific LMIS application within DHIS2. We are customizing or really just configuring the existing applications to be able to capture supply chain data as well as visualize or analyze that supply chain data. So there is no custom app. There is no specific supply chain application currently in DHIS2 that we develop as here at the University of Oslo. Now what you will see throughout the course of this week and a little bit next week are some of the apps that have been developed amongst the community. So people in West Africa or in Vietnam developing applications that are specifically for supply chain data capture or analytics. And so those apps are fairly customized. They may come with different privilege settings, but if you're using core DHIS2 to capture, I mean, not a custom app, if you're just using a core DHIS2 generic application to capture supply chain data or visualize supply chain data, you will have to have administrative privileges to edit and configure those applications. So it's not something that you can do if you're not a DHIS2 administrator very likely. All right, some more questions coming in. So we still have a bit of time here. So please do ask your questions. So he, Sophie asked, sorry, is there someone speaking? Yes, it was me, sorry. I thought you, yeah, not just to remind the Mentimeter. All right. Okay, so let me just answer one or two more questions here and then we will go over to the Mentimeter. Yeah, we're not done for the day, so please don't leave. What are your recommendations for LMIS in country? Okay, that's a bit of a loaded question. That one will take a little bit of a longer answer. I would say I referenced, I guess the slide on what that we got from the DEXIS on Beroondi, I think that's my general recommendation. Okay, so Alice, thank you so much for the reminder. I'm sorry to just keep on rambling here. I will hand it back over to you. I'll stop presenting my screen. Yes. And you can take us through the Mentimeter for the day. So over to you. Okay, cool, just a minute. So I would invite everyone, do you all see my screen? Yes. Yes, Alice. Yes, okay, cool. So I would invite each of you to go on menti.com and then enter the following code, 72 58 176. So I will give you one minute to do so. And then we will get started. So it's very simple. I will ask you some questions. You will have a few seconds to reply. And then Scott will let you know the correct answer and maybe a few explanations if needed. Is that okay, Scott? Yep, sounds great. We will start very soon, 10 seconds. Okay, let's start then. Or maybe, Martin, can you double check in the chat whether anyone has any problem joining us on Mentimeter? Yeah, on Mentimeter. Just to make sure, do we need to use the phone or can we use it directly from the browser? Oh, you can use it from the browser too, no problem. Yeah, because the link takes us to an instruction to use the phone. You basically type www.menti.com. Okay, let's start with the first question. Okay, sorry, I'm having some trouble moving to the next question actually. Here it is. Yes, now it works, great. Yes, so first question. Question should be posted on Zoom, Slack, or I don't know. People keep voting, that's good. Okay, so let's show the correct answer. Oh no, sorry. It's okay, hopefully everyone knows that the correct answer is Slack. We are using Slack. Sorry about that. We're able to see Alice from your screen sharing what the majority was voting, and that was the correct answer. Yeah, exactly, that's cool. Then second question. It is critically important to have supply chain data in the HMIS. True, false, that's good. Yeah, I think on this one I'd be very interested to hear the opinion of the 16 people that said false, certainly not part of the general global guidance and understanding, but certainly, I mean, there are now 17 people. I mean, there are many different opinions on this. Like I said, there's really very little standardization out there, but I think in our experience, we really can't do the bottleneck analysis, the root cause analysis. We can't actually start to appreciate why are we having issues in our clinical service delivery unless we get the supply chain data in with the HMIS, something that many countries are struggling with. So if we see that our service delivery, our coverage rates are going down, our immunization coverage rates are going down, a lot of times that's an issue with the supply chain. Maybe we've run out of supply chain stocks. Maybe we've had a lot of expire, and if we don't have that data in one place, we can't really actually start to figure out what the issue is, and so that's why ourselves in partnership with the WHO and many other multilateral are trying to stress that we try to get all this data into one place, the HMIS, which is often DHIS too. But again, the 70 people that said no, certainly, I would like to appreciate your opinion as well on the subject. Correct answer was. Well, the correct answer is true in our opinion. In our opinion. Then next question. Select all that apply. We want the HMIS too to be able to capture all of the HMIS data at facility level, able to calculate all of the HMIS indicators, able to visualize all of the HMIS data, serve as a warehouse information system. On this one, we do actually have a little bit more of a clear specific answer in that we as DHIS too platform developers are not trying to develop DHIS too to work as a warehouse information system. Again, a warehouse information system has a fundamentally different database architecture than what DHIS too is. Some people do use DHIS too to manage warehouses, but it is definitely not something that we would recommend. So for those 37 folks who said to serve as a warehouse information system, please out now 38, someone even had another one, please talk to us and maybe reconsider using DHIS too to manage your warehouse. It's not the best tool for that job. And it's very important for us as University of Oslo to have you appreciate what DHIS too can do, but even more important that you understand what DHIS too cannot do. We certainly know the limitations of DHIS too better than anyone. And I would just make it highly a strong recommendation that DHIS too not serve as your warehouse information system. Okay, and the other three are correct. Yeah, we of course do want DHIS to be able to capture all supply chain data at facility level. We do want it to be able to calculate all LMIS indicators and we do absolutely want it to be able to visualize all LMIS data. But just the function of like the day to day operations of managing a warehouse, it's not really the best tool for that job. Thank you Scott. It was the last question. Great, so then we need to point folks to the feedback forms as well as the participant. Sorry. Alice, what do you mind sharing your screening going through quickly the Slack channels again and functionality? I think we have a few who missed that part. Yes, just give me seconds so that I can go and Slack. And Alice, can we also take a look at the feedback form and the participant survey as well? Yes, just let me go first through, let me share my screen, which functionality is exactly, Martin? Everything? Show the channels what you want to use for which type of questions. Yes, no problem. So we will be for any announcement that we would like to make if you want to inform you guys about anything, we will use the channel announcements that you can, no, sorry, it's not the correct, I'm sorry. It's not the correct Slack channel. I have multiple ones open, obviously. But it will be the same idea. Just give me a second. No, it's not this one. Okay, here it is. We're also getting some feedback that our feedback and survey link are not working either. So we will be handling those issues as soon as possible. Let me just, okay, so if I do that, then it will be, okay, so now normally you see, you're all seeing the LMIS level to academies Slack channel, correct? Martin, if you can confirm, yeah? Yeah, that is the right. Okay, thanks. So we have, you will see, we have the different channels here. So for any, as I was saying, for any information that we would like to send you, we will use this channel announcements. So I would advise that you keep an eye on these channels, if you want to be informed about any major updates, then we have the channel ask about logistics. If you have any questions regarding, or if you want any tips regarding logistics at large, if I can say, do not hesitate to use this channel and we'll make sure that one of our facilitator or one of the training member, training team member will try to make sure that you get a reply as soon as possible. Then the two following channels are also quite interesting because tomorrow from 1.15 to 2.15, and also Thursday from 1.15 to 2.15, we will be hosting the experts lounges. So the experts lounges are basically an hour session where an expert in this case for Africa, especially West Africa, our partner from East West Central Africa will be facilitating this channel discussion. So for one hour tomorrow from 1.15 to 2.15, if you are based in Africa, if you have any questions related to logistics in your local context, don't hesitate to participate in this conversation that will be held once again tomorrow from 1.15 to 2.15, or through time. Then the same will happen again on Thursday, we will be hosting another experts lounges this time for Asia Pacific region. So if you are based in Asia and would like to ask some questions about logistics, still same time Thursday from 1.15 to 2.15, we will have our partner from his Vietnam will be dedicating one hour just to reply to your questions, giving you some specific tips on logistics in Asia region. Then the other channel really interesting is introduce yourself because we want to know where you come from, why you base what you're doing for which organization you are working. So do not hesitate to drop a few words on this channel so that we get to know you a little bit more. And then finally, we'll find the last channel if you have any technical issues like difficulties to access one of the platform or the videos or the forms, you can drop us an email message here and we will try to make sure that we sort this out. We see that some participants have some problem with the attendance link. We will sort this out as soon as possible. I'm sure my colleagues, Simona and Martin are currently working on that. So give us two minutes and we'll make sure it is sorted. And once it is sorted, we'll post a message to let you know here in technical support channel and announcements channel as well. Final thing for those who arrive a little bit late but you probably received the information by email. I sent an email, I believe last week. So we will be, besides Slack, we will be using the LMIS repository folder. It's a Google Drive folder that I shared with you. So in this folder, you will be finding the attendance and feedback form. Very important to us because we would like to know what you think about our sessions or we can definitely improve them, at least improve the next ones so that we are sure we meet your needs and requirements. So don't hesitate to fill in the feedback form. It literally takes one minute. So we'll be more than happy to hear from you. This session today is recorded and it will be the case for all the sessions during the academy. And we will make our best to make sure that the session, that today's session is available in the LMIS repository folder within one or two hour maximum. So if you missed anything, you will have the opportunity to go to the folder, to the LMIS repository folder and have a look at today's session. Same, once the recordings are available, we'll drop your message on Slack. And same for presentation, I'm sure Scott will probably upload today's presentations in few minutes. And I believe that's amazing, already uploaded. Sorry, but while sharing the screen, could you also show them how to add channels because I don't think everyone has all the channels are in all the channels yet. And normally on, okay. Sorry. So if you go back to your Slack for a second, please. Let me go back here. So I would believe like here, you have this arrow. If you click on it, you will be able to see normally all the channels included on Slack. Sorry, you have to click on the plus icon next to the channels to find the rest of them. Oh, and you have to be, yeah, and browse channels. Yeah, that's good. You will be able to find another question and answer there, for instance, if you click on that. Yeah. That's it, yeah. Is there any other questions related to? I don't think so. All right. I've been told that the link should be working now. Please check the links for your survey feedback again for today. Right, so we have two forms there. We have the feedback form, as Alice correctly pointed out, we take very seriously. We do review your feedback every day. And then we have a participant survey. We just want to know a little bit more information about where you are with your country supply chain logistics information system and tell us what things are important to you. We will be looking at the participant survey to maybe potentially revise some of the content over the next few days to be more specific to what you guys are telling us is important to you. So we take these very, very seriously. Please fill out the feedback and the participant survey. Both of them should take no more than five minutes. Okay, so I know that we're a little over time. Today, Alice, Martin, anything else that we need to mention on the logistically? Nothing from my end, Scott. Okay, all right. Well, then I just want to say, okay, thanks, Alice. And then I just want to also thank all of you all for joining today. I do apologize for going a little bit over time, but thanks for hanging with us. We will get started again right back here tomorrow at 11 o'clock Oslo time. In the meantime, I hope you have a wonderful afternoon. Rest of your day. Good morning, tomorrow. And we will see you again soon. So bye for now. Thank you, bye-bye.