 So, I want to welcome everybody to this webinar on M supply DHS to integration and really looking at opportunities both from a functional side and a technical side for putting these systems together. I want to first introduce myself and then just introduce the other presenters. And we're very happy to have the M supply team join us for this webinar. But first, my name is Brandon Horst and I'm the technical lead at the his center at the University of Oslo. I've been working for the last couple of years developing this use case. Or LMS with DHS 2. And it's very much based on integration on bringing data together between DHS 2 and other systems. And then I'm very happy then to welcome the M supply team to present themselves who will be also having a good presentation on the system and taking part in a question and answer afterwards. So, welcome Craig, Richard, feel free to give a short introduction before I start the presentation, but over to you. Do you want to stop Craig? Good evening, everyone. I'm Craig Drowne. I'm the founder of M supply and been working with us for over 20 years now, originally a pharmacist these days. I just do a lot of emails and meetings, but I love it. Nice to meet you all. Hi, everyone. I'm Richard Moiseau. I'm a consultant for the M supply Foundation and have been working for the Foundation now for three years. Originally working in the supply chain management and mostly managing Frankfurt countries. All right. Will there be somebody else or will be the two of you presenting? I think you can see this also, Jonah and Adam. If they want to present yourself. Hi, thanks. Hi, I'm Adam, I'm the product manager for immunization and cold chain for our organization. I'm going to let Craig and Richard do the presenting today, but nice to meet you all. Hi, I'm Jonah Kismindo. I'm software developer and like development manager. I usually more work on the HIS integration, though just Richard and Craig will present today. Thank you. All right, great. Thank you so much to the M supply team. And of course, they'll have a big part in the presentation a bit later and we'll also have some time for question and answer with them. So what I'll start with actually is just a short presentation to set the stage and present a bit the approach that we're taking from a slightly different perspective, really looking at opportunity. So both implementation and technical opportunities. I've given a presentation now very many times on the DHS to LMS approach. So I'm not going to deviate for that. The approach is the same, but this might be just a slightly different way of presenting it also to say that I work very closely with George Maguire. Who's the LMS technical advisor who has extensive experience research experience as well within health supply chains who's really guided a lot of the technical decisions and that we've taken and how to use and optimize DHS to for LMS. Features and also to set a limit to where the software maybe reaches a point where it can't deliver anything any more benefit. And really, that's where we recommend using a dedicated tool, a professional tool such as M supply. And also pair Cron's lab who you see there who's been working more and more with us supporting some implementations and I'll touch a bit on those a bit later. So for the purpose of this meeting, it's to give an impression of what an LMS system is having an understanding of the different functionalities and what's possible within DHS to and what is not recommended understanding the end supply tool and what what it provides. I only have a single slide on that because of course they will they will elaborate in much more detail in their section of the webinar and then how some common projects can be developed together. Understanding how the his network and his groups can can work on that and a potential way forward and hopefully we can have some discussions and questions from from the participants. To give a very quick overview of current status and just a few countries and these are really just countries which we've worked with in the recent past that we can give as a reference for discussions on what is currently being being implemented. So in Molly, for example, you have a sage ERP implemented at a central medical store. And for some time there was no ELM is to working at a district level and providing support for distribution to facilities. So this was very much paper based in Excel. A lot of communication by email to actually work on that supply network portion of the supply chain to the facility. At the same time DHS to had been implemented for some time at facilities with computers and was collecting stock data as part of the regular. HM is and health reporting stock data was being collected for central medicines and for quite a few other programs for quite a few years from 2018 or so this had already been put in place or even a bit earlier. And the data was available through a central dashboard called OSP Santé but that operationalization of the facility level data was not in place. But recently we worked on an integration where that data was then connected to the Medexa CLM is through a more recent project. And that was a way of bringing in existing data into operational logistics management to be able to inform decisions and form resupply. In DRC Democratic Republic of Congo a complex setting with many different siloed let's say implementations of different ELM is is and really no central and holistic system for managing and DHS to also being used as a national HM is so opportunities to develop a similar type of approach as was implemented in Mali. In Rwanda one network is used as a national ELM is a very robust tool but also very costly DHS to implemented at a facility level but exploring on how that can be leveraged for even more better integration with this central tool and also seeing what the sustainability is of a very expensive this one network tool. And then in Sudan where we have a project now just finalizing with Global Fund where there was a robust ERP at the central medical store and at the state level. Ramco ERP and they had attempted multiple times to to digitize district and facility levels but had never achieved that in large part due to infrastructure and just general capacity to put in place a digital system. So what we've done is use the DHS to which was the the of course used as the HMIS and integrated stock data sets for aggregate reporting at facility level or localities as they refer to them in Sudan to again develop towards this digitization of the last mile and connecting it with a central tool. These are just a few countries in context just to give a reference to what is out there. I think they're generally representative of different countries with which we work with where there really isn't a holistic system managing supplies from central store down to facilities and not across all programs and this kind of fragmented landscape is actually a common one. It's something that we'll try to to identify ways that we can solve and improve both the supply management and health service delivery by digitizing facilities and integrating systems. Now quickly on the differences between the ELMIS and HMIS and I think this is really targeted now for the DHS to implementers that for HMIS it can be quite complex in terms of analytics and the data being used by the system and really having high data quality and right denominators and these are the common challenges that you have within an HMIS. These are the things that we work on a daily basis to improve when it comes to an ELMIS the challenges I mean it could be the same with data quality and so on but the general purpose of it is to manage products and then the distribution of products across a network. It's not simply reporting to a central database and pulling insights through the calculations but it's really tracking and managing flow of goods and identifying needs in order to supplement those to ensure that you don't have a stock out situation of over stock and that you have the medicines at the right place at the right time to treat the patients who need them. So there's a general difference in how these systems are built up and this is really leads to the reason why we have a very clear and defined use case for the DHS to system when it comes to LMIS. Now the challenge is why do we not have ELMIS or ERP systems fully implemented at all levels of the health structure across all programs in any of the countries and for example the countries that I mentioned previously. There's first a complexity of issues. These are often systems that are installed and run well during the project period but there's a question of sustainability how many of them are able to survive beyond the project period once the external consultants are no longer present and this is being handed over to the country. That's one of the challenges when it comes to an ERP which can be quite a robust tool going much beyond just supply management. There's a cost aspect the cost of maintaining of licensing of training and retraining of adapting to evolving needs and the cost really can become prohibitive especially within public health in lower middle income countries. To refer to another tool with open LMIS which has quite a few implementations but perhaps doesn't have the same sustainability and base in order to maintain these individual implementations and I think that's another challenge where you need to have an evolving core to be able to adapt to new requirements and evolving requirements. And the question as I mentioned the issues I mentioned previously of training and retraining staff is there's a high amount of staff turnover turnover particularly at the lowest level of the supply chain or of the health structures. And then having again the ability to pay for all of these the cost of maintaining and developing these systems. Now what can DHS to do and equally as important what can DHS to not do. I think as a starting point it has proven to be a stable system that's been implemented broadly and has lasted over time and I think those are very good aspects and good starting points. There's also of course the HISP network. The existing training guidance materials the academies that provide a very good basis for being able to implement and maintain the system independent of University of Oslo and his center and independently of any external consultants so countries have really succeeded in being able to use and implemented with all of the resources that are available. Of course being open source there's no licensing costs and really the cost of maintenance are those direct cost of having the infrastructure and maintaining and training and retraining staff. And I think those are key aspects when it comes to the technical or let's say functional requirements. As you see there if we start first from the right side at the health center level, you can both report on stock transactions on a monthly basis on the amount of stocks received the amount issued and so forth. There are also different features for doing calculations using indicators and predictors in order to facilitate some of that data entry and reduce the amount of manual data entry. And you can also have with the new version 40 DHS to manage stock transactions so issuing stocks from facility level. What we do not recommend what you should not do is using it for a central medical store a regional warehouse or even a district store. For that we really recommend using a dedicated tool, which is where M supply comes in and we would strongly recommend having this type of dedicated software to work on these different requirements. I won't go too far here because the M supply team will of course go into detail on the software, but they've also been around for some time. So they have proven the test of time to be able to implement and maintain the different implementations in different contexts. There's a stable stable core and a very expert and dedicated team. And I think those are also very strong aspects to to collaborating more closely with them supply. And they're also making a move towards open source and migrating their code and we'll ask them some questions about that and what their plans are for the future. They have solutions for all of the different levels of the supply chain and of course can be implemented at the health center and have great tools for that, including mobile tools. And I think the aspects that we can explore is how can the two systems be brought together and work at that that cut off point where we say, okay, we implement M supply to a certain level of the supply chain. But from this point down, it may be more useful to use the HS to and again, keeping in mind the capacity and resources that a health worker has at a health center and the advantage of having a single integrated tool for capturing both health data. And stock data, and then the need for having a dedicated tool for higher volume sites for potentially hospitals or sites with much more demands on the functional LMS. That maybe DHS to cannot answer to a very quick overview, of course, for a central medical store, a high quantity of items, high volume, many transactions, distributing for the entire country. That's definitely something you need a dedicated tool for the same goes for a regional and district store at a hospital level, depending on the number of items, the volume of transactions and also the amount of resources available. A decision can be made on exactly which system to use but it's clear that that's a higher volume site and then down to a health center, maybe 100 to 200 items with management of location and expiry manually. And oftentimes not having a dedicated person, whereas in the first three levels there you'll see some more dedicated staff to managing stocks for the health center. It may be a health worker having to both manage their regular activities and having the stock management as an additional requirement. So then the combined opportunity becomes identifying where having DHS to at this last mile, integrating the data into M supply to support the demand planning and forecasting and ensuring that stocks are at the correct level. Avoiding stockouts and overstock. I think that's really the key aspect here that we're looking to maximize is bringing the two systems together. In addition to that, there's the opportunity also for analytics to be able to look at health service data and also stock data and comparing how these match against each other depending on the amount of stocks that have been issued and the amount of patients treated. Different discrepancies can be can can be looked into and investigated to improve both health service and supply chain management. IT development never stops. Of course, and also the needs of the implementation don't stop they evolve over time. So this can be also something that can be implemented in a stepwise approach and looking at a maturity development approach where it started potentially in parallel at different levels at the central medical store with a dedicated tool and DHS to at a health center level and over time building towards an integration. We can also imagine it being implemented for a single program and being expanded across programs over time. But I think the intention and the standards which we refer to the target software standards for supply chain management from revised earlier this year really identifies having end to end visibility. Transaction or report based data and really looking to capture all of this within the digital landscape and together. These systems can work towards that, but it's not something that will necessarily happen overnight, but you can have a stepwise approach to reaching that objective. Now these are just my last two slides before I take a pause. I can take some quick questions before handing over to the supply team. But from a very his perspective, so both his center and looking at the his network. This provides an opportunity to work with ministries which you're already supporting you're already working on HMIS and other health related solutions, bringing digitizing data, bringing it to decision makers, but here also offering. Helping support within supply management as well offering multiple tools. Using the existing knowledge of the DHS to DHS to but also supporting within an additional field. And there's definitely support and backing from both UI O his center and M supply to develop this further and explore on a case by case basis to look into what may be appropriate for country a be yourself. And see what kind of model can we develop together and support what kind of development path can we see for for a specific case. And this can really reinforce the level and number of tools that are being offered to support a ministry and I think this is something that we can also explore further within this webinar. But then of course to be able to take advantage of these opportunities. Some time and effort and resources needs to be allocated to really understand what does this solution offer. What can it offer for the countries but what do we need to invest in terms of people. And to understand what the requirements may be the opportunities would be of course implementations and the ability to work on these projects together. But there is some time and effort that needs to be invested in order to explore these opportunities. All right, I wonder if there's any questions and also questions from the M supply team to what's been presented here as a starting point. We can quickly take those now. So I just opened the floor. Apologies. I hope you were able to see my screen or I think somebody would have stopped me. Yes, I'm so go ahead. Morning. And thanks for the good presentation. It is very clear what we need to do and how we can get profit of this opportunity. However, I would like to get some precision on to the cost of maybe involving people, the country people on trainings. The cost of working with them like doing this mapping. And also the, you know, if you are going on step to have like a daily report really also to put in mind the cost of internet for the tracker to be updated. So that is one, if we can have an estimation, of course, I guess that is what we can use when we are approaching countries to tell them how the solution is the best for them. That is one another, another, another is the effect that we can get also the same presentation for French countries so that we can help them also. And target some decision maker and why to convince them to go for this kind of solution. Thank you. Great. Thank you. Do you mind just giving a quick intro presenting who you are just so everybody is aware. Oh, sorry. My name is Hamza, working with his provider as a ditches to implement and system and that we are supporting currently country, most of the country are supporting the French speaking country, like Chad, Central Africa, Madagascar, Comoros, Congo brother. So we'd like to see how we can get this into French and try to see how we can target those decision makers at the level of Mr. Health, so that we can sell our approach and make them by if they are aware as especially about the court. Thanks. Great. Thank you, Hamza for the questions and for the presentation so quickly for French, we can definitely help with translating the the content I know for M supply as well. Richard is working on supporting the French countries. And so I think that would not be a problem. There's already of the DHS to LMS approach that's already been translated by your colleague actually Augustine so thank you to Augustine for that. When it comes to cost, I think that's a good question because really that's the first question we receive from countries when when we speak about these different solutions. With the initial investment, I think there's already good support to improve and increase the LMS competence within his group so we can look at existing funding both directly to his groups and to his his center. Again Augustine is a good example of that that we were able to recruit him and have him as a resource developing these cases with the 10 supported countries country supported by his brother. So I think that's a good example that there is good amount of backing and we can find that support to build even more competence. And then on the last point it's something that we can first hear from the M supply team on different on their really business model and costing model potential or their ongoing move to open source. But it's a work area that then his center and M supply can work on to come up with some costing for implementations to see. What does this mean if a country decides to implement it and what is really interesting is to look at also the potential cost benefit of having this solution versus having, as I mentioned earlier a very expensive ERP solution. What are you getting out of the investment being made into this so no clear final value I think it really needs to be on a case by case basis but something for us to explore together with the M supply team. Any other questions from the group. Craig, do you want to go ahead. Thanks, thanks Bruno. Just a quick comment on cost. When you're dealing with health supply chains. There's a much clearer link. A cost benefit equation because I mean just to use a rough approximation most of the countries we're working in are spending at least $10 per year on medicines. So you can work that out for the countries you're interested in and usually the cost of an alarmist system will be way below 1% of their annual medicine budget. And if they can't save more than 1% by implementing it then they shouldn't go ahead. So often you know wasted rates are running at high single digits. So that doesn't mean that implementing is a silver bullet. There's a whole lot of other things that you need to do to make a success as I'm sure you know that it is quite different from an HMIS where the link between the cost of the system and the benefits is harder to. To draw a straight line between so I think that's important just just to give you an idea of M supply is always charged ongoing support fees. Because we think it's valuable for countries to have support available on call that ranges for just a few facilities that might be like 25 to $30 a month per facility. If you scale up to thousands then that price can come down close to $3 a month. So once again $3 a month $36 a year. We can make the cost cheap enough that everybody can afford it. Thank you. All right, great. Thank you Craig for that. And this is great to hear your perspective because it's part of the thinking and general considerations that we don't normally deal with within HMIS. So thank you for that 1% of the value of medicines being the general cost for LMS. That's a that's a good reference point. All right, if no other questions I'll hand over to to Craig and Richard for the presentation from M supply. And we still have an hour to go so we have time to present and also take questions with them afterwards as well so I'll hand over to you guys. The floor is yours. Thank you, Bruno. Would you mind just enable the screen sharing. Sure, one moment. All right, do you want to try now. Sure. Yes, it's working. Great. Thank you. Good evening, everyone. I'm, I'll talk to the first few slides so we'll try and we'll try and go quickly over the background because we know that you really want to get to the nitty gritty parts about how this would actually work for you, but we hope that the background is helpful for understanding where we're coming from. So thank you very much for your time. Here we go. Okay, so we're got four major points about our organization. So we have transitioned all our work from being a company to being a not for profit trust. So you will only be dealing with the not for profit trust. And we're registered in New Zealand and means we have to publicly publish our accounts every year and we're subject to full audits, etc. And of course we don't pay dividends or any surplus goes back into writing more services. Secondly, we're transferring transitioning all our software over to being open source. We've actually had open source solutions for M supply mobile for a health facility level for almost 10 years now. But we're moving our main desktop application over to an open source as well. That process is about halfway through. If you were to maintain supply today for a country, there's still maybe around $10,000 of license fees is a one off, but that's very small and in relation to the cost of a whole implementation. So, along with moving to open source, we've been able to make two other major changes. Firstly, we've been able to maintain a single write a new single code base for that runs on on Android and Windows and Mac desktops and also on the web. So it means that when you add a feature that goes to all platforms and it reduces training costs because the software user interface is the same on all platforms. And lastly, we've been able to just take advantage of new technologies that have come along in the last 20 years. As you can imagine, there's been a lot. Thanks for a shot. So I think this slide will look quite different to DHAs too. Although 20 years ago, we only had an office in Nepal, all our work at the start was in the Pacific. And that was just kind of coincidence or good luck. And we're now at the point where every country in the Pacific use use them supply as their national system except to the two French territories. And I guess you could say how I if you count that. Yeah, Southeast Asia, several countries. And in Africa, we've been expanding fast and when we say expanding fast, that's just by trying to do a good job. We don't do a whole lot of the way of marketing and recently in Columbia and Latin America as well. And you can see we've got we've got our own staff in Nigeria and Cote d'Ivoire. And we have development offices in Nepal and New Zealand and a couple of other staff in New Guinea, Columbia and Fiji. Thank you. Hey, there's a lot going on in this slide. So I hope you will be sharing these with you later. We shadow you want me to do this side as well or were you going to take over at this time? I'm sorry. Yeah, I'm happy to do to do that part. So yes, like Craig said, I think there's a lot on that slide. The idea is that we are trying to summarize everything that M supply can do and all the applications are all the levels of the supply chain. And maybe because I think it's going to be clear from the demonstration afterwards. We can maybe just elaborate on the few things that we're not going to showcase for this webinar. But yeah, so on top of being an ELM is we also have developed a solution to manage the regulatory affairs called it's a product called conforma. It's been used now in Fiji and in Gola and basically in Angola it's being used to for the authorization to market for medicines. There's maybe Craig you have a better description of the project there. And the other thing that we have been developing as well is also a new tool called the health supply hub to manage to be able to manage tenders in M supply. So it's a separate tool where the countries can submit their tenders and receive offers from from external suppliers. And eventually so right now the link is not done between health supply hub and M supply but eventually we want to do that and be able to be able to place purchase order for instance directly in M supply using the the awarded contract in the health supply hub. And maybe the other thing I wanted to say as well is that we've been used in quite a few countries as a warehouse management system so WMS. And actually even sometimes in some country like Columbia or even it at the moment, we are only installed at the central warehouse level. And so it's mostly currently our proprietary system, so not the open source one that is used because that the solution that has the most features at the moment to manage large facilities like central warehouse. And then of course we have the MIS features and I think here we really try to have the basic covered with a system of report acquisitions, the ability to receive stock distribute stock, adjust stock by doing stock count or stock take and having a suite of built in reports as well to help with the operational side. And we have also this last mile solutions for the health facility level, including per patient dispensing vaccine administration. Yeah, so that the kind of activities that are more suitable for service that we point the lower level facilities. And on the right here you can see that we also have developed and culture nap. So that's an open source standalone app that you can, that you can use on the Android tablet, and you can pair this tablet with Bluetooth sensors that you can see here. Basically, it helps you to monitor the temperature in your cold storage to up to between six and eight senses at the same time so as you can see on the screen here. So you will see the real time in real time the temperature of your senses, and of you will receive alerts when something is happening, temperature excursions. The next bit is also online data visualization tool. So highly customizable dashboard to display the API so basically everything that is being captured in M supply can be displayed in a, in a web app that we call the M supply dashboard. So that's most of the time as a service that we offer to most countries, and that we adapt to their needs. And I can see at the lower part, you can see that we also showcase the fact that we are, we have integrations with other providers and I think one of the most important software we've been integrating with is DHS to I mean in most countries we've been working with there's always demand to make sure that our system can integrate with DHS to, but we also worked with other solutions, like open systems, which is another EMI solution, and also warehouse management systems such as Sage for instance. So the next part is really to go into the demo so so we start showing you how M supply looks like, but I just wanted to have this slide as well to just basically give some background on what kind of architecture we could do if we were to integrate, if we were to integrate with DHS to. So this would be a typical setup where the central warehouse and its direct customer so including the district stores would be used the M supply and receive the data, especially for the orders. So on the monthly, on the monthly basis, for instance, it would receive orders from the service every point, pulling data from the DHS to up. So, yeah, so that's something I will teach you because he actually going to help understand what we have been working on in terms of integration. So now I'm just, I'm going to move actually not to M supply right away but to a software that we are with. So that's the DHS to demo platform. And here, as you can see, I'm in the data entry tool. I've selected one specific to see organizational units, and I'm looking here at the real time stop monthly reports. And this period and just to show you that data have been captured here for this facility. And basically, now switching to M supply. So that would be just a very small introduction. So that's actually the interface of M supply this top. So M supply this top is our proper right. None of the source software. So I, I don't know if we're going to have the time to go into the details I really, really would like to show you the open source solution instead because that's the one that we are now planning to implement in most of most of the countries working with. But for tonight's webinar, the little integration that we've done is now only working in this version of the software. So, but yeah, so basically, this is the main and supply that you get to so you can manage everything about distributing stock to your customers in this section, the same here for your suppliers. You can see that we have the whole workflow from tenders to the actual receiving and including payments. And here for items that's everything links to inventory management, stock takes locations, pickfax replenishments, inventory adjustments, etc. So that's really advanced feature that most of the time used in large warehouse. And then we have also a whole suite of reports that that is available within the tool. So in this case, what I want to do now is that let's imagine that I am a district store and I'm, I want to receive the requisition from this organizational organizational units. So what I'm going to do is that I'm going to do good to go into that special menu on at the top. And here there's a special feature called gate they are chased to data. So what this is doing is that it's fetching all the organizational units. So the, there's an actual link between the supply software here and the DHS to server. And now in order to find the, the, the monthly report for this facility, I will actually choose it in the drop down list here. I have two options. I can either look up for all the monthly reports for the last 30 days, for instance, or if I know the period I'm looking for I can already select it from the drop down here. And then the only thing I need to do is to check the data. So it's looking to the DHS to server now. And hopefully we'll find something. In the bar in the list now you have one, one requisition one monthly reports for this period. And we can see that the complete date is actually the complete date where somebody clicked on that button here in DHS to. So we know that if this one has been validated. So now I can just open it and this is a requisition window or order window. And that's basically taking all the items that we can see here and taking all the data that we that has been entered, especially what has been distributed and the stock on hand. And then based on this data and supply would be able to generate an order. And that would be hit so customer acoustic quantity, basically on all the data that have been captured in DHS to. I think here we have chose the logic of saying that we would, we would set the target for reordering to three months of stock. So three months worth of distribution. And so the logic is basically so this target minus the stock on end would give you the customer acoustic quantity. And then, because the system is all integrated you can see that here at the district store we can see our stock on hand, so all the stock available. So now the only thing I have to do is basically choose what I want to supply to the facilities. Sorry, I actually realized I already worked on it. But yeah, so the idea is that you know I can give the amount I want to supply to that facility. And when I'm done, I can generate a customer invoice and allocate it. And then basically, when I'm going to finalize it, it's going to push all that stuff towards the health facility. And when we're talking about transactional system, what I'm just doing here is really is, as soon as I have finalized that customer invoice that outbound shipment if you if you want, then inventory records are automatically being updated on the once once it's finalized. Okay, the other bit I wanted to show you as well is that. So that's one way we are pulling the data from DHS to. But what we can do as well is that we can also show to the facilities that the consignment has been made available. So, again, I'm not sure you're mostly familiar with the DHS to capture tool. So here I'm going into the consignment receipt acknowledgement. And if I go into the same store. I should comment. Then you can see that we do have the confirmation that consignment has been completed. That's it for this integration but that's just really to show you that we are able to basically at the district store level using M supply to retrieve the data from the health facility using DHS to to basically generate an order and to process them at the district store level. And now I want to switch to our open source solution. So, as Greg said it. This solution is now our new open source software. And it's available on different platforms. So here tonight I'm using the web application. As you can see, but once again it's been. It's also available on three tablets and the stock app. Without further ado, that's connected to open M supply. So as you can see, and that's, I think what we meant when we said that we are going to monitor that modernize our interface. It's a way more modern interface. So when the user logged in open M supply. The first thing you're going to see is this dashboard, where it's going to be a lot of different metrics to basically have an idea of what's going on in in its warehouse or in its store. So you can see, for instance, here, in terms of inventory management, we have the extra in stock. So we know immediately that we have three expired stock. But most importantly, we would know if we have anything that is going to expire within the months. Stock level, what is in stock outs. The items who has enough stock and the item who has too much stock, for instance, so here 11 item with more than six months of stock. Then to navigate within the system. We opened that menu here, and we have all the different activities that you need to perform in a, in a district store, for instance. So just to kind of show you how, for instance, we can do a shipment. So basically, this is the main step. I mean, I'm going to create a new shipment. I'm going to select one of the customers within the list. And basically just add items that are for which that I want to send to that other facility. So I can either drop down here, but there's a possibility to search the code that you want to add. And here and the system will basically tell you how many, how many units are available. So you can basically just decide to say, okay, I want to give them 100. And the system will automatically allocate those, those 100 units through the multiple batch that may be available at your facility based on the first to expire first out logic. But if you're not happy with the system suggestion, you can always modify it and decide which batch you can send. So, but we expect most of the users to just use this button and to allocate this way. And then if I want to add another one, I just have to click on, okay, next, and I can immediately add another item to that list. So that's it. I got my cut on one must have not confirmed the other one. So once it's done, I can actually go to hold the process so confirm that it's been allocated. Confirm that it's been picked, and then obviously shipped. And as you can see, there's also two additional status at the end. And that's when the other facilities going to receive the shipment and when he's going to acknowledge the delivery, then actually me as a district stores I would be able to see that yes the shipment has been delivered and verified by the by the customer. So let's do this. And once again, because it's a transactional system, as soon as I'm finalizing this transaction, the stock is immediately being updated. And talking about stock, that's also one of the pain. Obviously, the most important thing in any nice is the ability to have a visibility on your available stock very quickly. So here's the list of all the stock available in this facility. And again, it's easy to just look up for one specific item and to look at all the batch that are available here with ability to export everything in an Excel as well for reporting purpose. Yep. So, here, for instance, so as I said, here we are logged in as the Waikato district store. And I may want to move to another store like, for instance, the health center. And because I wanted to show you as well, for instance, how it would look like to place an order going to move to the other one sorry. So, yeah, basically, this is actually let's create a new one. I think it's going to be better. So let's place an order to the original warehouse. So we have this very useful tool that's called a master list. So, instead of adding all the items one by one can just use a master list to add multiple items at once. So all the master list are customizable so you can choose the list that you want to create for whatever purpose you need them for. And as you can see, because I chose that list then immediately all the items have been populated into my into my order. And now what I wanted to show you as well is that the kind of thing that you can see when you are placing an order. So unfortunately here I'm not choosing the right one. Sorry, it's a it's a demo server. So sometimes it doesn't have very updated data. But there's like obviously some visual aids to help the district store manager to know what kind of quantity needs and what has been the consumption in the past and this kind of useful tricks that can really help when it comes to orderings. So yeah, that's one of the thing. Oh yeah, actually this one is also important so you can place basically just internal orders the way you want. But most of the countries we've been working with they are they also want to have some kind of a periodic system. So they want an order to be placed every month or every three months for like the TV program for instance. So in that case it would be the API for the vaccines. And so we you can actually set that up in a supply to make sure that the every facilities will be ordering on the on the schedule basically. So you can either place monthly or urgent and there's no available period sorry but then you would choose the period you want to place the order for and, and basically it would generate automatically an internal orders for that for that program. So that's what we have been implementing in Djibouti for instance. Maybe a little word that was well about our dispensary menu. So here in open and supply, you can manage your database of the patients of that health facility. Obviously you can create a new patients if you want to do. You need to create a prescription for new patients so obviously there's already a lot of Richard here because I've been using that demo quite a lot. So that's also the system telling you that there's been duplicates. And then when it's ready can go create a new prescription or Richard and other item as well, very similar to the way we do outbound shipment. So, let's give amoxicillin, you can give direction here if you want. And then select the quantity that you want to give to that customer. Oops, must be something wrong. This one is expired. Okay. Here we go. And the same way we can confirm once it's been given to the patient we can confirm it that's verified and then that will also update the consumption. We're talking about the purpose and dispensing features, which are going to be really useful in facilities that have the capacity to basically end all these kind of activities. And the last thing, the last thing I wanted to show is also something that we've been working on recently is our cold chain module. So there's actually two components here. That's basically showing you so you can actually use the culture nap that I was, I was talking about earlier, or you can also, we also recently developed an integration with the bellinger bridge tags. So you can upload the bridge tag that are directly to your into M supply and then have basically monitor the temperature in open M supply. Here you're going to have the bridge logs. So basically you're going to be able to see all the other temperature bridge that have been recorded in your facility for all the sensors and all your cold storage and basically your temperature log for all your sensors and storage location. And at the moment we're also working on the culture and equipment inventory module that would be used to basically manage your culture and equipment in terms of functional status and and maintenance. And the last bit I wanted to show is also another tool that we have developed for PNG, where on top of being able to dispense medicines to patients, we also have the ability to create what we call encounters for specific programs or in this case, PNG, and basically on top of dispensing medicine to the patient, we would be able as well to capture clinical and epidemic, epidemic, digital data, sorry. So, a physical exam, for instance, the heights, you can add symptoms. Yeah, so all these forms are entirely customizable as well. Yeah, depending on the needs of the country. Yes, I don't know, Craig, if you want to add something about the live demo, do you think that's something was showing? Thank you, Richard. No, that's fantastic. I think the main thing to say at this point is that we've developed. Open M supply firstly to run at sort of a district store level and at a health facility level so we'll be adding the warehousing functions and the procurement functions and forecasting etc to open M supply over the next year. We already have a grant to enable us to do that. Thank you. Thank you, Craig. Please make sure to to note all your questions we will try to make the time at the end of this presentation to to receive all your questions if you have any, and I'll keep the demo active so if we can always go back to it if needed. So, yes, what's the M supply secrets. It's, we think that one of the main main factor of success of M supply is its offline first architecture. So basically, the ability to work in M supply without internet. So basically here is this little diagram when internet is on everything is working well. You can do your daily operation with data. So like we said, you can do your stock takes you can dispense stock to your customers and patients. Same at the other facility, and that I can synchronize between the two facilities, thanks to the internet. However, when there's no longer internet, you can still use M supply at both facilities for your daily operation the data. However, you would need a connection or the data to be shared across the facilities so technically it's actually synchronized with the central server. And that would be necessary for instance if you want to send an order to another facility so you would need internet at least once to allow the system to synchronize the data and then that would be good. So you need internet and continue keep on working on your PC or tablet. So now, so you've seen already the integration that we've done so this is actually another kind of integration we can do as well and that we have been working on in in some countries. So it's actually what we call like the monthly push to DHS to. So in this case, instead of putting data from DHS to generate orders and to pull replenishment data. In this case, we are only taking like a few metrics from M supply, like stock on hand, the months of stock, the expiring stock, this kind of thing. And we are pushing them into the DHS to server to automatically update for instance on a monthly basis the DHS to dashboard that is being installed in in many many countries. So what we've done for instance in Timor that's what we work on in Djibouti as well so basically for a list of facilities and for a list of the selected products, we would share on the monthly basis this metrics coming directly from M supply. Yeah, like I said, so it's been used now in Laos Timor. It's been almost finalized in Djibouti, South Sudan, and also in South America. Yeah, and we can, we can say that the gray lab is very good. And it's a very, very easy setup. It's just too much organizational units and data elements. This one, I think I'm not going to go into the details but that's basically the side that present the integration we've been showing you tonight, sorry, tonight for me but this morning for you to say that. There's more advanced integration like we like we like the one we showed you so where we are actually pulling data from DHS to generate orders at the M supply level. So most of the time that would be in district warehouse running M supply. So I think there's a lot of potential for that kind of integration and hopefully soon this will be implemented. So as you can see we already have a proof of concept working so it's only now I hope a matter of time before we can actually implement it in the countries we are both working on in health design options. So that's also something that we did to share. I think, I think Brenno has been very clear when he said that. I, you know, the ideal setup the DHS to would be used at the service every point level and M supply tools like M supply like other including other EMA solution would be more suitable at the central level regional and district level. And both system can work together at we just demonstrated using an interface between the two. Yeah, we try to have a basically just to start the discussions to see if we could make like a decision tree to see which kind of facility should use and supply and which one should use DHS to. So, I think here we said that the type of facility would probably be the first question. So, like we said, warehouses so what you see on the right here with most likely use a software like M supply to be able to manage more advanced transactions. But then that's obviously a bit different for the other facilities. So if we take for instance if we start for service every points. It's important to really understand where the service every point is at in terms of maturity for managing the supply chain so most of the time in service every points the staff is already very busy overwhelmed. And so it's not necessarily a good thing to install a software like M supply that requires to be used on a daily basis to update the stock and to make sure everything is in order. So that's why we kind of say, for instance, if health facilities is using the existing system in the health facility is the paper based system that potentially it's better to go with the DHS to EMA solution. And whether it is the monthly monthly real time stock or whether it is the daily one. And then, like we said, it's always possible to to push that data towards M supply at the district level if need to. And then, for instance, maybe just the case of hospitals so obviously hospitals can have a large range of sizes, but it happens sometimes and we've seen it in the in countries that hospitals will have a dedicated pharmacy to place orders and manage the logistics basically the hospitals. And so this kind of service where they have a ticket that are dedicated to basically the logistics operations, then in that case, it might be worth considering using M supply, but really depending on the on the staff capacity and and the kind of needs they they have one of the main thing would be, for instance, the batch level stock management. So if there's a real need to go at the batch level so have the visibility on the different batch and expiry dates available, then in that case maybe open and supply would be a better option. So, yeah, that's also quite an important topic as well. So we are, we have taken the journey to try and be TSS compliance compliance, sorry, by the end of 2024. I don't know if you're aware, but the TSS they are the target, target software standards, I think, or I don't know if I'm saying this the wrong way that have been published by the, you may know better, the international supply chain group, I think, without actually taking the feedback from large organizations such as Gaby the Global Phone. And yes, so our goal is to make sure that open and supply would be TSS compliant by the end of 2024. And so, yeah, that's an important part first so we are really trying to, to stick to that roadmap and to, to try and achieve as many as as many TSS as possible. Do you want to add anything on this topic, Frank? No, that's pretty good. I guess this friend's going to want to have been in this world with the supply chain to get software standards. Happy to talk more contact us later if you want to know more about them. Thanks. Oh, do you want to carry on with this one? Oh, sorry. Sorry. We, so how, how could spotlesses work with us and with your existing work with the HA's too? So, firstly, we are very open to experimenting and working with different countries to find where your strengths are and how we can come work together in a way that's good for the country. So we're open to all sorts of models. Obviously, you have a lot of local knowledge, cultural competency in your countries and we would like to use that wherever possible. And then we bring specialist skills of the tools that we work with. And yeah, so, and obviously you have a lot of DHS to knowledge, which is extremely valuable as well. So, if we have long term support arrangements with the country, we would be very happy to upscale you to the point where you provide first line support. And then we would revenue share regular support fees with you to ensure that you were compensated for the time you spent in maintaining that support service. Obviously, when there's new deployments, there's, there's work for business analyst kind of work, trying to design an implementation that will meet the country's needs. And then there's a degree of stakeholder engagement and training and then of course deployment work actually working with facilities. We find that bringing people in for a central training and then just sending them back to their facility doesn't work well. Partly because there's quite a bit of work just to get a facility going, they need to do a stock take and they need to get and obviously every facility, especially the larger ones have very unique needs that they don't tell you about when they come to a training. They specific, you know, edge cases and it's much better if you're on site for a week and can help them work through those issues for the first time. So is anybody got any questions about this one? This might be very good to get down to the nitty gritty. So how are we going for time, 20 minutes for any questions. Thank you very much, Brennan team for organizing and thank you all for listening. All right, great. Big thank you to you Craig and Richard for presenting. That was a really great overview and then also a detailed demo. So I think that was really great for us to see in action. Also good to see the move from the existing system to the open source and how you're making that move. I'll open up immediately for questions I see. Dojo, do you want to go ahead with the first question. Yeah, thank you for the presentation. I just have a question. My first question is about the way that you are going to make a decision to open source. I don't know. Do we have a roadmap about it, a timeline? If it's already, we have already an available open source sample, how can we get it? This is my first question. And my second question is about dispensing products for the like HEV. We have this use case where we need, when we have our FACA on HS2 to be able to pull dispensing to the warehouse and then from there we could make, we could order the enough products we need. So I want to know if this system is possible from the FACA HS2, upload like a patient list and they are dispensing products and push it on the M supplier and this is the HS2. Thank you. Hey, I'll try. We'll reshatter you A.K. for the first question and I'll do the second one if you'd like. Yeah, for the first one I think, so I think I heard about the, yes, so yes, so the second part of the demonstration, so where I showed this software, it's indeed an open source software and yet we can definitely make it available to you if you needed to test it and or even to show it to your partners, that's absolutely no problem. And in terms of roadmap, so like I said, we, I think we are really trying to get these target software standards. And we are publishing our progress on our documentation website. So that's also something that we can make available to you. And this documentation website also includes our current roadmap for developing new features. So we'll make sure to send that to you as well. Thank you very much. And then for the second question, Craig, you wanted to say something but I think I can answer, right? I'm quite sure that as soon as we capture dispensing quantity in the trackers and since the HS2 has an API, I'm very sure maybe actually Bruno can say something about this but I'm very sure that there would should be no problem to pull that data to basically aggregate the consumption at the district or, yeah, regional level. Okay. Sorry. Yeah. All right, thank you for the question. Dojo just to mention to the group that you're working then with the his Western Central Africa team based in Togo supporting very many countries in Western Central Africa and many of the French speaking countries as well. I think that's a very good question as well on dispensing that can be a another area that we can develop the use case on the integration. We've really focused on the supply chain management distribution of stocks and demand network. That's been the focus so far. I think this question of dispensing is coming up again and again, and I think you're referring to the patients registered in tracker and looking at quantities, but I know if Mohammed is still on the line. There's also a use case wanting to bring in the amounts that are paid by patients for non free items that that needs to be first paid before it's being distributed by the pharmacist. Maybe a use case that we can explore in a bit more detail how to bring those together. Mohammed just feel free to to speak up if you want to ask anything related to dispensing. One question that I actually had related to the integration. And I don't know if Craig Richard you want to comment or Jonah on the level of effort to build this demo integration which Richard presented, because I think it's partly interesting from the purely technical aspect. This is a point to point integration and you're making use of the, the open API but really M supply is doing all of the heavy lifting all of the work in pulling and pushing data. If you can maybe just comment on that how much effort and and how that's done. And then secondly, I think it's to understand. Yeah, the potential for working and building additional workflows like the dispensing or others if you have any comments or opinions on that. Thanks, Bruno, on the amount of effort. We've, we've done a moderate amount of the work already that's in our main code basin is reusable by other countries. And there's always because the two systems have their own item lists. We, we record the the IDs from DHS to an M supply and there's a little bit of work to set that up. And John has actually coded it very nicely where it finds new items and DHS to it will add them to M supply automatically. So you didn't need to allow some budget for a new country to get the integration working but not huge amounts you know you're talking five, five to 10 days to for configuration and maybe the same for a little bit of custom development. And those are one offs obviously once it's all set up if they don't change anything, then nothing will break. Thank you. All right, great. Thank you for that. Again come with your questions for those of you that are connected and interesting and learning more about M supply. I actually have an additional question which has come up other times and it was something I think Richard mentioned in the beginning. There's often the request to integrate the M supply with DHS to and I'm just curious what is the use case what is the need that you're presented with when it comes to integrating to DHS to is it from the LMS and supply chain teams or is it coming from the HMS side for the point of analytics what is the use case that you're presented with for integrating. Thanks to date the integrations that we've done have been about a desire to get supply chain data visible for stakeholders whose main source of health information is DHS to. So obviously if if you're working in supply chain then you've got access to the customized in supply dashboards and you don't need to go somewhere else but people for example, you know high level planners in the ministry people, you know making human resource decisions across multiple departments these kinds of things and people who obviously are reporting on health data that they want to include things like medicine availability then it's much easier to buy pushes that the DHS to. So the new work we've been doing with Bruno and his team we've got some countries interested in that and that would be a new a new direction for integration and we're we're keen to explore that as well. Usually a country would maybe want a combination of both in the future so interesting to see how things go. Thank you. I should I should clarify that the two integrations are not mutually exclusive it would be possible to have. If in supplies in the warehouses knowing your stock availability at your central warehouses critical to your functioning of your health system so it's still be pushing that data to the HHS to even if the HHS to was being used as a stock management tool at the low level facilities. Thank you. Thank you for that Craig. And I think we have similar requirements and I think it's interesting to understand I'm going to put up a slide just to show the HHS landscape and just a second to show the complexity of the different. Data and needs and also the requirements so I think it's important to know yeah that we can fill multiple roles and multiple use cases there. We're presenting a different aspects and touching on a few different potential challenges but if I can be direct Craig we've discussed quite a bit around potential solutions but I wonder what can you comment on the challenges what for M supply have been existing challenges in implementing your system so far and you have as I mentioned very extensive experience, nearly 20 years of implementing. What are the main challenges that you've faced and what do you see as challenges, but also opportunities going forward with this kind of, you know, collaboration, but also in a general sense both, you know, organizational structural technical. What can you comment on that. Sorry, sorry about that my connection just dropped out and back. I did get the question about challenges thank you. I think that if you were to sum up the main challenges that all all about people not not about technology. So, once you have a system that can work offline. Did we lose Craig again, or is it just me. Sorry about that I don't know what's happening. It's a, it's the second time it's dropped out. So we people challenges are firstly about management buy in. So, if it's very hard for workers to be enthusiastic if their management aren't enthusiastic themselves so and a good management team was often in a motivated workforce. So, you can teach people skills. It's very hard to teach the motivation so that's the first thing. Secondly, you need a moderate level of HR functioning as well. For example, if you keep swapping out swapping people out to different facilities. It's very hard to get to train to train enough workers who you can do the job well. So just some basics around those sorts of things. And then I think the other thing is to implement slow go a bit slower than you'd expect that you'd maybe want to go but do a great job it's much better to make incremental gains that you hang on to then to go fast and then have the system fail and then nobody wants to go back and to redo work in a failed in a failed system. So, I think those are the main things and then the last thing is to listen well to the people in country and hear their concerns and just work through them carefully and respectfully with them so that they feel that they're being listened to and that often they have a lot of good ideas and local knowledge that we often get great ideas from people in new countries so work with them. Thank you. Okay, that's great. I think first that speaks to the complexity of the context we're working in both in the specific countries and the challenges face but also the complexity of the requirements and I'm just sharing here a world bank snapshot from a world bank report, just showing the complexity of the landscape and how these different pieces fit together. Of course, a lot of these are kind of not as neatly defined as you see it within the image but I think it adds to the complexity when you're going from HM is to LMS pharmacy management dispensing accounting and finance, and other requirements I think we would definitely agree that a lot of the challenges also come from having the management and organizational buy-in and support and not necessarily simply the technology. So, thank you for that question. I think Abdul Rahman had the question. Go ahead please. Okay, perhaps not. I thought there was a question earlier or a hand up earlier. Maybe one quick question again, Craig and team. If I missed it on the question of sustainability. What happens after the implementation period. You mentioned having this support cost by facility. But is the management of the system generally handed over to to ministry and how was that. How was that done and how has that been this model for sustainability after the implementation period. Thanks, Bruno. Firstly supports entirely optional so no country is is obligated to take support they can write they can run the system on their own without recourse to us. Usually, when you're getting into a national medical supply system. Very high income Western countries would never dream of trying to do that without recourse to expert help. So, we think most countries would agree that having some expertise available is really valuable and usually our ideal is to train super users in country. And the ministry develops their own first level support team and we're in the background helped them with issues that they can't address in country. We often say that we're a little bit like paying for a fire fire on ambulance service that you have to pay a little bit even if you don't use them that when you do use them you're very glad that you were paying regularly. Thanks. Okay, that's great. I think that's a very similar approach also with the HS to but having the his network being a present in country they provide. Definitely the first line before having to engage with his center university of Oslo, but that's good to hear it also provides some potential for developing a collaboration with them supply. I'm another question from you. Thanks Bruno. I have a question about like backup. Is there a way of country having their own backup, like country can set their own server where you can be sending sending a daily backup so they can keep kind of some records. That is one. Secondly, how do you manage the changes. So in case like they want to add any product or they want to delete a product. How do you do you let that part being done by the country themselves or you do it on their on their on their part. Thanks. Sure the for the backup options. We have multi level backup. So that firstly backs up to the machine that they're using. And then we offer countries and encrypted cloud backup but it's up to them if they don't want the data to leave their country they can have to provide another machine and country. We have a fantastic record of not losing data for 20 years so we we've even had hold whole facilities burned down and they lost all their records except for their supply data which was backed up overnight for for the facility bird down so Yeah we try very hard and that those backups can be restored on to you onto a local machine at a his if they give you permission so that you can help with troubleshooting and that kind of thing as well. And then you asked about, for example, adding an item. So that kind of master data management is done on what we call our central server and then it synchronizes out to every facility so even though the facilities are offline as soon as they synchronize they get any changes. Almost always that's done by the country. They don't need to. They don't need to come to us for doing some tasks like that. And there's a very detailed permission system allowing people to, you know, to decide exactly who's able to do these tasks. Thank you. Thank you Craig and now we have a question from Roger as we are just up on time but go ahead Roger. Yeah, thank you. I have one question in terms of deployment. Do you allow country to wire setting up them supply to install in their own data center or it must be on the supply. So, just the second question that I have. The last two demo that you presented to us for someone who interested in me, like playing with the demo, how can someone get the potential for those two demo, especially in the web so that we can get familiar with them supply. Thank you. Yeah, for the first question so. So basically to, I think the question was about hosting and supply whether on the cloud server or maybe in a local in country data center right. So, yeah, the answer is it's basically up to the country. So some countries have chosen to host it in the cloud because that make it easier for support team to access it, even though it's not impossible for our support team to access a local server, but then some countries they have some regulations that actually prevent them from storing this kind of data in the cloud so we're happy to to use an existing data center. Like for instance, I know for Djibouti we've been using the cloud so far but soon will be transferring the DM supply central server to their to their data center local. So it's really up to the to the countries and then yes, obviously, like I said it's it's totally okay to have access to our demo. The only thing maybe just send an email to our team and we will make sure to organize that maybe I think we'd like maybe to give you a even more detailed demonstration of the tool. Let you play with it. Like you as you want. All right. Thank you. All right, great. Thank you everyone. We're just a few minutes over time, but I want to say a big thank you to the M supply team for taking the time, both beforehand to prepare and work on and develop these discussions. And then for presenting today. Thank you to all the participants for taking the time for the good questions and engagement. I guess we can share, I will share with all of the participants and all the the invitees the contacts to the different teams so you can follow up if you can reach out to M supply about accessing their demo instance. We're quite happy in developing this relationship. We see that there's a lot of common principles that we're working on. I mean, we're looking to build sustainable systems that can support support health systems. In the different countries we operate in. So I think that's a really great common objective that we have. And then also from the DHS to his center aspect, we're looking to work on existing gaps within implementations and listening to information coming in through the his teams from the ministries that we're supporting. So I think that's really key to have this understanding of where the gaps are what solutions are you looking to to solve and then in this way collaborating with M supply more closely we can provide a holistic solution and not simply going from very limited specific feature from one to the next and building over the organic system but really looking what is the architecture that we're looking to to build towards and what is the holistic approach that we're looking to to reach here. So again, thank you everybody contributions participation and I'll share both the recording and contact information and some different resources after the webinar. Craig and team if you want to say any final words or share any information please go ahead. No, first of all, really thank you for this opportunity to to engage with the his groups. I think we really see this as a as a as a really good opportunity to work together first. And I'm sure there's a lot of countries and and the donors would be very interested in having a combined solution between our two solutions so yeah the only thing I want to say is that please if you want more information if you are interested. If you want to use our demo, please just reach out to us we'd be very happy to answer all your questions and and requests so yeah but again thank you for listening and hope to hear from you soon. Thank you everybody and thank you Bruno and team. Yeah, that's fantastic. Look forward to hearing from you. Again everybody and have a good rest of the day. We will all be in touch. Goodbye for now.