 Yes, Brenu, you can see my screen. This meeting is being recorded. Yeah, we see it perfectly well. Or Alice, can you confirm that you can see the Android tablet screen? Yes. OK, thank you. So just to remind you, Brenu showed the access to the sandbox on Monday morning. So what I'm showing is our sandbox that is publicly available on the web portal. But also you can download the native THS to capture app and then connect to this URL to explore all the features that we're demonstrating this week. I'm cheating a bit because I'm using the sandbox development so that we can do some configuration. But it's basically the sandbox that you have access to is basically a copy of what you are showing today. So I'm going to show what we call the Biomedical Equipment Lifecycle Management Tool. And then I will show briefly the analytics. And finally, we have a short under the hood session on the tracker program in case you have any questions how this is configured. So we call it Lifecycle Management. We realize that there's a lot of need for cold chain equipment management, so refrigerators and freezers. That's often the burning issue and probably the most widely used at the facility level. But Biomedical Equipment is a huge field and there's a very wide range of equipment that needs to be managed. And there's also academic studies. So it is known that there is a lot of very high percentage of equipment that is available in health care facilities, but which is not used because it is not functional. It's not maintained. And it's very difficult to manage all this equipment without sharing the information on the functional status with the technicians and the biomedical engineers. So that's basically the idea that you are replacing a paper record if you have an asset register or you have a kind of system with cards for each of the pieces of equipment on paper that are maintained for recording all the repairs and the maintenance. But this cannot be easily shared with the technician and therefore the use is limited. So again, what we're doing is quite simple. It's quite basic, but sharing the information from the facility level throughout the entire country to all those people who should have access is of course a huge improvement in terms of management. So it's Biomedical Equipment Lifecycle Management for those experts of DHS2. You can see that there's a due date and I have not synchronized my data, which I'll do later. So the first screen that you see is already kind of the first application. So there's actually two tools in one. And the first one is what you see here. This is like an asset register. Yeah, it's scrolling on. So you can see this is a clinic and you can see a list of all the equipment. So you have a pulse. This is actually not a clinic, but you have a pulse excimate. You have a refrigerator, a cold box, different cold boxes actually here. But you also have a patient monitor and suction machine, so any kind of equipment. The specifications for refrigerators and freezers will be of course specific to cold chain equipment, but in principle, the tool can be customized for any kind of biomedical equipment. Even in principle, you could use it for other kind of equipment. You wanted to use it for generator sets or water pumps or other equipment you could in principle modify it. So this is basically the asset register that is then also accessible to anybody else who has access to the tool, either on the mobile device or on the web portal. So you have here a list of attributes that can be freely configured. Of course, this is adjusted actually it's generic. So you can, but again, this is just an attribute. So you can easily change these attributes. You can add, you can remove, you can change the order very easily. So you have here where it is installed. You can see the manufacturer, the brand name. You see the details. You can record the serial number who has provided it. You could record the warranty expiry date if that is available. And you see this is very nice. You have also picture. And that is extremely useful because chances are that you have different pulse oximeters in larger facilities, different refrigerators. And sometimes you have similar models. So it might not be obvious what is what. So you can enlarge and you can see then the picture of the equipment. So this is already kind of the first use case having a centralized digital asset register that can be managed. You can control the user access. So you can define who has the user rights to add equipment to remove equipment or to remove the specifications of equipment. So again, DHS2 natively has a very sophisticated user management tool which allows to give view and edit access to the different functions. So I already mentioned that you might have several different pieces of equipment. So typically refrigerators. You might have one or two, but you might have also several. And of course, if you are going to record any information on inspection or on maintenance, you want to make sure that you are recording that information for the right piece of equipment. And some of the inspections you might do it every day or every week. And this might be a frequent job. So you might could easily inadvertently be clicking the wrong item. So what you can do is you can furnish each piece of equipment with its own bar code or it could be a QR code or even a GS1 data matrix code. But the easiest is to use a linear bar code that within code is a unique identifier. So this is one of the attributes that are indicated here. You have here the unique identification. So I'm going to do that just for demonstration purposes. So I have what you're seeing is my tablet PC. So let's say I want to record an inspection or a weekly preventive maintenance from a refrigerator. And I want to be sure that I'm selecting the right one. Then I will attach a label to that refrigerator. And you can see here the unique identifier. You see here this is actually a symbol for a QR code. But it stands for any kind of bar code. So I'm going to select it. And on my screen, on my PowerPoint, I have opened the bar code on the side. I'm not going to switch my screen just to show you that. You can imagine it's just a bar code that is attached to your refrigerator. And then just put it down again. And then I'm going to click on the Search button. And you see that it is going to bring up this refrigerator. So now I'm sure that I'm entering the data in the right refrigerator. But I have prepared a little scenario. So I'm going to use another piece of equipment for the demonstration purposes. So if you have any questions or comments, just jump in. Preparing something? OK. So what I have done is I have basically to demonstrate how you would use this on a day-to-day basis, I have selected the pulse oximeter. And I'm going to open this. I don't have such a fancy pulse oximeter. But anyway, I have a little one. So to show you, this is basically just to keep it practical. So you see I have a pulse. And you can see a pulse oximeter. So let's imagine that I'm a nurse in outpatient department or in an emergency room. And one of the tasks you have is that when you take over your shift, you're supposed to check your equipment. So you make sure that everything is working if it is needed. And so why we call it life-cycle management is basically reflect the entire life of the piece of equipment from, I will explain the translator, from the installation. Then inspection is basically the daily, weekly monthly checks. Then the preventive maintenance like cleaning, checking the gasket, whatever is required for the equipment. Then for colching equipment, also other equipment, there's a WTO requirement that you should record and document all the alarms, the reasons how it was resolved to have a complete record. Then if the equipment needs repair, then you can make a repair request. Then if the next step is then for technician and engineer, biomedical engineer, to carry out the corrective maintenance, also called repairs. And if the repair is successful, you continue the cycle. If the repair is not possible, then you dispose of the equipment. So you get a complete record of every piece of equipment that is then also digitally archived. So I'm going to start with installation, and I'm going to spare you the agony to watch me type on a little screen. So what I have done is I've basically entered the scenario already. Let me just see how I can show this best way, and maybe like this. So let's say the equipment is installed for the first time, so delivered to the facility. So you can write a short report. You will normally test the equipment. You will check where the alarms are working. You will brief the staff, and you will hand over the user documentation. So that's what you would typically do to document the installation so that you know who has installed it, when was it installed. And just to mention that for everything that I'm showing today, you will see one or two windows only. That is because we have no standard document on what should be reported. But this is also fully customizable. And you can add these questions that needs to be filled in as required. So I'm planning myself. We are not a biomedical engineer. So we rely on a subject matter expert in the respective country or project to advise on what is required. Then for the inspection, very simple. Let's say you're just checking whether your pulse oxygenator is working, whether the refrigerator is working temperatures, and you have different ways you would just enter this shortly. And then maybe for those who are not so familiar with the tracker programs yet, so how this would work, let's say I have, you can see these entries are from June. And let's say I'm going to do the functional check today. I don't want to, no, no, sorry. Inspection, I should click on the plus here. And I'm going to add a new inspection. And that's going to open the window and it will say to this by default show today state. I'm in Mahasot Clinic, I click on next. And then it says inspection report and then you will write whatever you need to write. Obviously on the tablet, you don't want to have too long text, but basically the fact that you have confirmed, I delete it again. That you have done the inspection is kind of sufficient and you will also have the record of the name and the date and the timestamp, so you know that that equipment was checked. And then you save it and that's basically all you need to do. So, oops, that was too fast. Maybe I should stick with using only the tablet or the screen, but you can see that you have, I have successfully entered for today the inspection report. So that's basically how it works, very simple. Again, we don't want to burden the health workers with a lot of work, it should be simple, easy to use. Then the preventive maintenance, let's say I would have recorded teen servicing according to the service manual, checked alarms, calibrated sensor, so whatever is required, cleaned equipment. Then you have a record with the date and the time. And then let's say I have an alarm, so my oxygen content, sorry, the post-oxymator is prompting an alarm. And I think the screen is cut off at the bottom, I don't know if I can change that, but you can see that. Alarm, you can see audible alarm, so maybe I should show that because it's important, you don't have to type everything, you can also use various dropdown menus. I don't know if you can see the whole screen, it's cut on my screen, so I'll go to next. And you see here, if I click on alarm type, you have different dropdowns, so I could say this was an audible or visual alarm. And here you have free text entries, and then if the weathered alarm was resolved, then you can just select from the dropdown menu. And if the alarm was resolved, you're not informing your supervisor. So that is obviously much easier on a mobile device to just select from a menu. And again, these menus are fully customizable, so instead of having guests, no, you can have any kind of text, you can have many, several of the options, whatever is required. So it's a native tracker program, very versatile, I'm not going to save this now. And just go back. So the repair request is straightforward. Actually, I'm going to show that in the next scenario. Okay, you have any questions or comments so far? I have two more short scenarios. Anything Brenner wants to add, otherwise I'll move on. Okay, so I showed basically the happy path, you check, you install the equipment, you check it, alarms are resolved, everything is working, so no need for any intervention. Now we have again equipment that was installed, preventive maintenance was done, and now I have an alarm. So alarm type audible alarm, replace battery, and the issue was resolved. And no need to escalate to the supervisor. But then, yeah, so then I have another, I have a repair request, let's imagine, I have a pulse oximeter that is not working like this one. You can see that I'm not able to switch it on. So it says the LCD displays flickering, and you can enter the urgency of the repair request. It's unusable, but it's needed. And this is kind of a huge improvement because you have a digital record as soon as it's synchronized in mobile device, the technician using a mobile device or behind the desktop computer can also see that the repair request has been launched. Find it on our maps, so no need basically to send urgent SMS to call, you could have it basically a digital record. And then the next step would be for the biomedical engineer to intervene. So here you have assessment of the technical fault. So if identified that there was just a loose contact, sold with the loose contact, the technical fault was resolved and the equipment restored to service and everything is fine again, the equipment is working again. And again, you have a complete record from the inspection, the alarm, the fault found by the health worker, the request and the corrective maintenance. So the very last short scenario that I'm going to show is if that is not successful, so I will not go through everything again, but just to demonstrate kind of the practicality of how this would work in real life. So again, you have pulse oximeter. So this morning was not, pulse oximeter was not switching on, changed the battery that didn't help. So that's good to provide some information. So the technician is not going to the clinic for something that is trivial. Purchase is medium as there's a backup equipment. So you have two pieces, so one is working, so it's okay, but still needed, still essential. Then you have the corrective maintenance. So that's the repair of the biomedical engineer. So basically you can have a short repair report, assessment report of what was checked. And the conclusion is that the equipment cannot be repaired and has to therefore be decommissioned. So it was not restored back to service and the technical fault was not resolved. So by the way, this yes, no questions or falls correct are not only easy to fill in, but they are also really useful when you have a line listing report that we'll show in a minute because you can just filter, show me all the equipment where the technical fault was not resolved. And then the final step in this case because the equipment could not be restored, you're going to decommission it and write a short report what was done with it. Maybe you can use the replacement parts where you have to destroy it and then you should remove it from your equipment inventory, so from this list so that it's no longer appears on your list and you have again an updated list of the equipment that is actually in use at your facility. Okay, are there any questions or comments? Hi George, there was a question and I don't know if it's possible to demo that now but the enrollment of devices and assets first, are they first previously done in a separate tracker program or is it all done within the same Biomedical Equipment Lifecycle Management Program? Good question, so it's done in the same tracker program on the web portal that I'll show in a minute. Okay, if there's no other questions on the mobile application, I'll switch my screen and show the line listing. Yeah, I just wanted to mention, I'm just taking my notes. So the functions, the option that you have for entering are text numbers, dates. Also you can record the geolocation if you need to do that and one important feature that I've not shown is that you can also take pictures. So in the repair request, take a picture of the fault and attach it to DHIS2 and this is visible to the technician anywhere in the country. I'm just cautioning because of course that takes a lot of storage space, you have to synchronize your device so it should be used with caution but in principle that that is possible. Okay, then I'm going to stop sharing my screen and go to the DHIS2 web portal. See, share that, share my right window. I think it's this one and I'll have, I don't know if this works. Renu, can you see a line listing report? There's nothing on screen yet, no. There's no screen. Nothing on screen. Okay, I think it worked. Okay, try again. I'm a screen window, try again. It says I'm sharing my screen. We now see it, George. Now it's good. Okay, Renu, do you want me to show the enrollment? How that works? Registration? Maybe we can do that at the end, just do a few. Okay, we can do another general question as well. We can take up later. Yeah, so the first feature I want to show is the transfer. So transfer of equipment that was a use case that was requested. So we don't have a native functionality for this yet but we are requesting, this is a use case for the bulk transfer but we have a workaround. So you can see that this pulse oximeter here was transferred, was sent from Mahasot Clinic and it was transferred to Meetup Hop Clinic. So you can have the date and all the other details. I'm just showing like the essentials. And then when that piece of equipment arrives at Meetup Hop Clinic, you can also say received from Mahasot Clinic and received at. So it's a workaround, it's not perfect but you do have a record. If you move a refrigerator and the other piece of equipment from one clinic to another, you have a digital record of who transferred it, the date and time and you could also have if you wanted to transfer report why you did that. So that's already quite good compared to a paper solution. I will not go through this in detail. You can imagine that for each of the stages that you have seen, you can have a report. So if the technician or the manager of the clinic or a health worker wanted to see a cut of all the inspection reports or you wanted to check whether that inspection is done, you can have a dashboard here. So for those who are not familiar yet, line listing is really a wonderful addition to DHS too. Very powerful and really very beautifully designed. So use it. And I will briefly show you have then the maintenance report preventive maintenance report. So as a technician, if I had a technical fault, I could go through all the maintenance reports of a specific piece of equipment for a clinic and view them. Of course here, I don't have time to show all the details of what you can do here, you can have a filter. So you can filter only for one piece of equipment. Then you have a report on the corrective maintenance. So you would have a complete record of all the equipment maintenance done in a district or even a country by the technician, biomedical engineer called Jane Technician on one digital record. And again, of course you can sort or filter for different organization units facilities. You can sort or filter by the department, by date, by equipment, anything that you can imagine. Very powerful also to have all these filters for each of the headers. And then you have the, did I duplicate? Sorry, that was already corrective maintenance report. And then the disposal report and again the report on the disposal. And as I mentioned, you can have, if you have yes, no questions, then you can easily filter for them or sort them and have, if you just want to look at all the equipment that was not received, removed or that was not answered. Okay, I think we can take some question that completes the demo on the analytics. We can take some question maybe before very briefly discussing about this under the hood. George, I think Alex Watila, oh, I see Alex, you have your hand up if you want to ask the question you had in the chat. That's perfect for now. Go ahead, Alex. Good morning. Good morning. So one use case that comes, especially with donated equipment is that the donor requires some kind of audit or verification. So like was the equipment delivered to the facility? Is it still in the facility? Was it entered into the government asset register? Can this functionality assist with that? So I think you could, if you had a list of the equipment, you could filter by it if it is identifiable with equipment model, maybe a unique identifier. And you could have a list at the national level. We are all of this equipment currently is in place and it's a very good idea. So the donor could even see whether that equipment, regular preventive maintenance is carried out and the equipment is inspection is done and so on. So it would be interesting if you could share with us the exact use case and we studied the details, but I would think that partially it would be extremely helpful. Again, anybody can have access to this record so no need to send any paper records or paper reports from all the facilities. In principle, anybody who has access to the ChS2 server is authorized and is giving credentials could view this kind of information. Okay, do we have any other questions? I think that was a great answer, George, because I had answered it in writing in Slack and I think it was the same as you just said. So I think that was great coordination by us. I think the other questions were a comment from Nora saying that the ChS2 report is great as it holds the history of the device. And then I have a question now from Robert Modi. The reports are great. One data item that would be great to add to the biomedical equipment lifecycle reports if not already in is the warranty validity? Yeah, great point. So the warranty is, I called it the warranty expiry date. It's part of the attributes. And yeah, I mean the, we have included it, but again, we call it warranty expiry date, right? So you could have, you could of course rename that. That is a possibility, definitely. I think it's a good idea. You could also add as an attribute the contact company person who holds the warranty and who can be contacted. One other thing that you could do again with caution is that you can attach PDF files to like upload a file. That can be quite heavy then of course on the synchronization but then principally if you had any kind of user instructions or warranty documentations or any other documentation that is relevant, you could also add it directly to the tracker program. Any other questions? I think that was it, unless there are any hands. No, I think that's it. There was the point on the input. I don't know if we're gonna go back to that. Yeah, so you can see registration screen, Brenel. Yeah, we see that. Okay, so basically you can go on the web portal and you can register a new piece of equipment. So you see my house or the clinic, you have the enrollment date. So let's say if you have a new refrigerator delivered, let's say probably to the central warehouse that is then going to inspect it and deliver it, enter unique, so just basically enter all the attributes and click on safe and it is added to your asset register. So very simple to do and maybe related to that, I can also, okay, I will go back also to mention that of course you can edit this asset register. So let's say I registered a piece of equipment but I found that I make mistake and you can again go on the tracker or on the event, on the capture app and you can, all these fields are now editable and you can change it. Let's say I forgot to enter the product number and I'm going to now type that product number to complete the registration. So very flexible to do. Of course, you should make sure that the editing rights are limited so that only authorized people are editing this record. Okay, I think that concludes the presentation. Let's ask questions. So we do a quick under the hood. For those who are familiar who want to know how this is configured again, quite simple. I think we can continue George and more questions for now. Yeah, okay, I'm opening the maintenance. I'm going to go on the program. Again, I'm not a specialist so you might detect something that can be done better but again, for that we have the expertise of the HIST group who do that configuration for living. So I have here the biomedical equipment, life cycle management. It is a tracker program, right? So you have tracker and event programs. This is a tracker program because you have repeatable events and as I mentioned, you want to keep a complete record of the equipment maybe over many years. So you just give it a name. I think there's not much here to configure also if not on here. So attributes, this is important. So here you have basically the attributes that you have seen on the, let's say the asset list screen that you can configure. So you have the unique identifier so that it's on the top of the screen and when you are scanning for the barcode, you don't have to look in the list. It's always, it's going to be all the way on the top and this is fully customizable so you can create, you can see, you can just, I will not save it but it's very easy to remove or to add. I'd say if I wanted to have add the image of the equipment to my list, I could just put product image added to the right and that would add it to the list. And then if I wanted to move, we talked about warranty, you move this up or down, you can also do that. So you have complete control of the order of the items. You can also then decide whether all of them are searchable or not. Maybe you don't want to have a long list for the search but just have the unique identifier and type of equipment. And just if you have a, for the unique identifier, if you're using a barcode, QR code, TS1, just make sure to configure this as a QR code so that you have the icon and then DHS2 can read it as a barcode. The registration form basically comes up, is kind of the same order, but again, you can customize it. So that's all there is actually on that. Then the program stages, as you have seen again, fully customizable, you can also move them up and down if you want to change the order. You can add, you can remove some, there's quite a few so that might be already too complicated and maybe good for hospital, maybe too extensive for a small clinic if you just want to manage one or two refrigerators. And within the program stages, let's say if I go to alarms, it's repeatable, right? So except the disposal is only done once, the installation might be done in several places so that's why it's also repeatable. And then the important part is to assign data elements so basically have attributes, those are appearing on the home screen and then for the individual questions that you want to appear on the questionnaire, you have to create a data element for each of those. Very simple, you go on the data element tab, you create new, just make sure that you create it for tracker, not aggregate, otherwise it won't appear. And then it will appear on this list and you can just add and remove them very easily. And again, you can have text, yes, no, you can also in the data element, you can use an option set for having several options in a drop-down menu. Maybe I will show that briefly afterwards. So again, you can add, remove, you can, I think they also always appear in alphabetical order but you can change the order actually. And then you have the data entry format to display the order in which those items are appearing in the screen, I'm not going to save any of that. I think that's basically it, that's a program stages and then you have the access, that's basically just giving access for which organization units it applies and the notifications if we are working on that. Maybe actually to mention that we are also thinking of expanding the functionality to have a maintenance report with notifications. So we hope to use this for the, have this available with the bulk load. So you could already create an event separately for maintenance, for example, if the technician had an instruction to replace the part to carry out any specific maintenance, but that will be cumbersome if you have many pieces of equipment. So we think that with a bulk load that will be an option to just upload weekly, monthly maintenance. And the great thing about that is that the respective person, the technician or the healthcare worker then will receive a notification in THRs to please carry out weekly or monthly maintenance. So that's one of the future use cases I'm going to check. I think I might have an option set that I can show for drop down options. Yeah, yes, audio, audio visible alarm. So if you have demonstrated that briefly, right? So we just have a yes no question. So I should check the alarm type. Sorry for clicking so much. So what you can do here is you have a data element which is called alarm type which is appearing in the stage. And now I want the user so to prevent them or avoid that they have to retype every time. I'm going to create this kind of drop down menu where they just selected was an audible or visual alarm or this is in future for the coaching app that they received a notification through DHRs to and you can easily modify, edit or add options to this list. So even if you're not a DHRs to expert, this is very easy to customize. But again, the details of a tracker program are quite intricate. So we do recommend using his group. Okay, I'm just going to check my notes if I covered everything. Otherwise, do we have any other questions or comments? Okay, last thing that we're actually currently working on in the functional design and working group. So you might be asking if I have, I'm going to go back to my, if I might be wondering, so you have a list of equipment and have inspection arms, preventive corrective maintenance which will be quite different between a refrigerator and an XM machine or Osoximeter. And you would like to be able to differentiate the tracker program for each of those equipment. So you see like a pulse Osoximeter suction machine are quite different. So we are working on the hoping to provide in future next year, sometimes the option that you could customize the questionnaires depending on the piece of equipment. So DHRs would automatically when you register and open a pulse Osoximeter, you would have a customized list of, for the inspection and preventive maintenance. While if you open as for a refrigerator, you would have another. If you're refrigerator, you would have another list of inspections and preventive maintenance. So that would be quite an improvement because now you have basically one checklist that applies to each and every piece of equipment. So you could also, you could already do that today with program rules, but it's a bit fiddly because you would have to hide certain stages or data elements and that's kind of, just takes a lot of program rules although technically it is possible. Okay, I check my notes. So I think I have covered everything I wanted to cover. I don't know, Brenny do you want to mention the work we have been doing with UNICEF on this? And his Malawi actually. Sure, of course. And we had in the annual conference this year, we had Malawi also presenting this type of configuration for managing cold chain equipment. And that's the similar dialogue that we're currently in with UNICEF to develop this kind of configuration, meeting certain requirements, similar to what Alex's question was related to the auditor, to the audit questions from specific donors that they have specific requirements. So this would be specific to cold chain equipment inventory management. With the COVID-19 pandemic, there was a wave of equipment and ultra cold chain equipment that was sent to countries and there was a influx of equipment that now needs to be managed, repurposed and maintained. So that's one of the driving factors among others to have a tool that is able to then capture and follow all of these different operational stages from starts to end of life for cold chain equipment inventory. So this is something that we hope to have finalized soon that we have something that's in line with the UNICEF requirements that's in line with existing standards and practice. Some of that too, George, I'm not sure if you may be touched on it, but the ability to connect this to the PQS, so having this data being populated once equipment is enrolled and ensuring that this data is available there as well. And not all of that happens within DHS too. There's also some dependencies on other systems and other data sources like the PQS catalog is not something that we would host by any means. That's a separate discussion or separate data source, but the point being that we would then develop a tool that can be implemented across countries and immediately meeting certain standards. It's the principle behind the disease packages, like you may have seen it for HIV, TB, malaria for disease surveillance and case management. Now, this is a similar approach. It's not, it wouldn't necessarily be the same implementation, but it's simply having a configuration that meets some donor requirements and some industry standards for management reporting and so on of this equipment. So that is very specific to cold chain equipment, but it's the same, similar functions as you see here, similar reporting and similar kind of data. I think that's what we can say. I can also maybe mention, and as I think I put this in the chat, I'll elaborate a bit more on the Friday morning session that we've presented this to a lot of the donors. I think all of the major donors are aware of this. So all the ones that are working with DHS2, which is most of the major ones, just about every major one of the global donors. And we've presented this as a tool that can support cold chain equipment inventory and Gavi specifically has already included this as part of their funding for country level assistance, so technical assistance. So to actually conduct an assessment and consider the implementation of this kind of tool, it may not cover a full national scale implementation, but it would definitely be able to launch, conduct an assessment and have a project startup coordinate with stakeholders and then make sure there's a proper requirement gathering and developing a proper implementation plan. So for a pre-project that should be sufficient to cover the consideration for this kind of implementation. And then I'll go through a bit more details on Friday because that has to be done through contacts with country contacts and so on and different considerations on budgeting. That's again beyond our scope and engagement, but it's something that's already been communicated, accepted, supported and now in a sense budgeted for through the Gavi TCA contracts. So yes, that is I think what I can say about that. You have the configuration. I just have a, yeah, just for a comment because I understood the question correctly from Jose that was a request. So just to mention that we have mentioned several times, Breno, that we have the sandbox, you have access, but we also have this configuration guide needs a bit of updating, but this is quite up to date that you can find on the DHS website and download, this is a PDF document. You will need some DHS to expertise, but it gives a short overview of the use case and it does give a configuration. So if you had even an empty database and you wanted to configure the aggregate data entry form, you could basically follow here. It tells you these are the category options, create them, create this category and so on data elements, dataset. So it's a very short summary, but it is comprehensive and it does list hopefully all of the settings that are needed and you also have that for the tracker programs. All right, I don't see that we have any more immediate questions. You have there, thank you from Kulsi, but yeah, so you have the demo site, the sandbox. You have the configuration guide available on the website. We have this work with different donors and partners to align the requirements. So it can be used for biomedical equipment or cold chain equipment. A lot of this can be configured and it can be adapted to specific needs. I think this is again similar to Alex's question on the requirements for the donor audit. So at the time of implementation, a lot of these different things can be changed. New question from Abdel, if there's a French translation, I don't think we have a French translation yet, but it may be something we work on again with this UNICEF work and maybe that they require the French translation. What I believe we have actually is a Portuguese translation because it may have been already done by the team, the HISP Mozambique team. So I think we have it in Portuguese but French would be something that needs to be worked on. So the standard DHIS-II components are translated but not the specific biomedical equipment. Yeah, my thinking is that if you are working in a Francophone country, probably you only need the French version. So I could suggest that you then configure the tracker program in French. And of course, DHIS-II, as Parano said, comes natively in dozens of languages. Yeah, so only the specific equipment contents or the stages that would need to be translated but not the other additional DHIS-II native. Exactly. And just an idea for Alex on the reporting, great idea on the donor reporting, you could even consider having, let's say a dedicated report that the donor can just open, view access only and customize it to their needs so that you don't have to create manual reports. So I think Brenner is a world champion in being on time. So maybe we'll just go for the break. Yeah, I think it's good to respect people's time and that we stick to that. But if we've covered all of the different points, if there are no more questions, if there's no more anything more you want to know about this, I think it's there. Use it, share it with your teams, share it with others, either through the written guide. Again, the recording will be available later in the day on the YouTube channel and just share and promote this. And then if you have any feedback as well we already got some for how this could be improved, how it can be changed, let us know, we're always happy to hear from you. But I think good recommendation, George, if we take the break now, so my local time here is 11.17, we can come back at 11.45, all right? So quarter two, we can come back and continue with the temperature monitoring tool and some of the work we've done there, all right? And then we'll finalize and then we'll finalize with question and answer and how this may be applicable also for your cases. So I think we'll start there, quick comments. Sorry, Phillip, before I hand over to you that I did post in the questions channel on Slack, I posted a summary of the different points from this morning's mentee. I know some of the questions were somewhat ambiguous it may have been difficult to answer the right answer. So then I just made a summary of the points we wanted to communicate and get across to everybody. If something's still unclear, comment there and we can have a discussion and we can make it so it's perfectly clear for everybody, all right? So now I'll hand over to Phillip, welcome again and he'll present and then we can continue with some of the development path for this tool but over to you, Phillip. Thank you so much for the introduction. I'll just use my screen now. Yes, we see that. Yeah. So hi, everybody. My name is Phillip Larsson. I'm a former master's student and I'm gonna present my thesis which is the cold chain monitoring app. It's a same sensor-based cold chain monitoring system using the DJI's to tracker capture app. So I was so fortunate to pilot this project. The thesis was given to me by George and Breno and Johan and we started working on the concept and made a minimal viable product which we tested in Sambesa, in a province in Mozambique with some objectives of implementing the application at four health facilities, providing the facility workers with tablets so they could use the application and training the health workers in using it and the goal was to digitize a manual temperature reading process which is today paper-based. So on the right side, you see a picture of us and the facility workers conducting a polar campaign in Sambesa and in the cooler box, you see the sensor we were using and they were using the application to see the temperature during the campaign and to verify that the vaccines that were given to the children were at the right temperature. So what is the problem with the insufficient cold chain monitoring? The most obvious is that people are vaccinated with vaccines that may be unsafe due to insufficient temperature during storage and handling. So giving vaccines to or bad vaccines to children and patients. And as immunization program grows, the complexity increase and the need to strengthen components like cold chain and logistic management is critical to make the immunization programs scalable. And the unit costs of this is an example of some other consequences. Unit cost of vaccines has increased from one US dollar per child in 2001 to about 28 in 2014. And I guess after COVID and other stuff, it's increased furthermore. So therefore poor vaccine handling can have significant financial consequences as well. So yeah, the goal was to improve temperature control with the cold chain monitoring application we had built. So on the first picture, you see the current cold chain monitoring system in Sambessa, which is a paper form representing one year and the health facility workers captured the temperature of the freezer in the morning or the fridge in the morning and in the evening. And their work processes, they take out all the vaccines to a vaccination station. So actually the cold chain monitoring of the vaccines are yeah, not so good. So and on the right side picture, you see the application where some digitus implementer explains how to use it. And we wanted to digitize the paper-based solution by using the Bluetooth sensors to monitor temperature. And this provides for a more advanced work process where you can bring the temperature sensors out to campaign works and to rural vaccinations and having and verifying that the temperature is at the correct temperature. And using the application, it also prompts real-time alerts and provide historical data for analysis in DJI's too as collecting the data from the paper was often not digitized. So the technical solution of this application, it's using a Blue Maestro B Elite temperature sensor which has at the picture on the right side with a battery lifetime of two years and it's low cost, estimated at 35 US dollar per device and it's open access. So when you purchase it, you can use it, it's no subscription cost and additional costs afterwards. And it's possible to buy a fully waterproof sensor or you can buy a silicone wrapper to make it fully waterproof. And over to the software, my contribution to this work, it's a custom Android application using the Android SDK and actually the bare bone of the application is the Scalot map provided by DJI's to Android team. It sends data to the tracker capture application and it has a local database which so you don't lose any readings. It provides local alerts in form of a notification on the Android device if the temperature are above or below a given threshold. It functions offline, giving you the possibility to capture temperatures and then upload it to the DJI's to instance when you have internet connectivity. And you can also export a CSV file from the local database. If you want to distribute the data or provide the data to other programs or non-DJI's to related programs. So this is briefly the system architecture of the solution. On the left side, you see the Bluetooth sensors and they advertise temperature data using Bluetooth low energy. And in the middle there's the custom Android application which is integrated to the tracker app and you can capture data from the Bluetooth sensors. And then when you have internet connectivity you can upload it to a DJI's to instance and then decision makers can visualize and act on the data collected. So now I'm going to give a quick demo of the application. It's to give you a brief. This is a minimal viable product. So you sign into a DJI's to instance and grant access to location and Bluetooth. And then you're synchronizing metadata and data from DJI's to and then the Bluetooth sensors appears. You select one and you can see the different temperatures like current, mean and max and average temperature and you can upload a temperature to the application. And then it gets stored in the local database. And you can see that you can see the battery time of the sensor and stuff like that. And when you keep uploading, the graph view will update. And it automatically listens to changes in temperature. So it gives you the option to... Yeah, and you can see the database, the local database. You can set a minimum and maximum threshold for the notification. So if it's above or below, the notification will come on the Android device or we show. Yeah, and you can export the entire local database to a CSV file, which I mentioned. So you can distribute the temperature readings. And yeah, you can display the database and clear it if you want to start with a clean sheet. So after using the application for some time, you can press upload data and then all the data will go into a tracked entity instance in the DJI's to ecosystem. And you can see the temperatures and aggregate on the data you have collected. So that was the demo. Let's see. So the goal of using such application is to reduce the number of spoiled vaccines through improving temperature control during storage and handling. And that will, again, make it more safer to give... You know that you give the right vaccines to the right people, so you don't vaccinate people with the spoiled vaccines. And it can also help reducing complexity by introducing support for cold chain monitoring integrated with the DJI's to platform ecosystem so that you have one vendor and the data goes directly into the DJI's to instance. And it can also increase the global health and immunization by reducing the number of spoiled vaccines with a cost efficient cold chain monitoring application. And furthermore, there's a dedicated Android developer is being recruited to work with this. And it's the second priority for the Hispelminus team in Oslo. And I think it was approximately April 2023. There will come some further development on this subject. And Mozambique is interested in expansion of the pilot and the application will apply for a WIO performance quality safety pre-qualification. And yeah, that was my presentation. And thank you so much. I want to thank George and Breno making this possible and believing in me. And big thanks to Saadijutus and the implementers. And thank you for your attention. All right, thank you for that, Philip. So this was a presentation then on this custom app that was built to connect to the remote temperature monitor. So the blue maestro sensor to collect temperature data. So again, the functional use cases are really to collect alarms so that there's immediate corrective action being taken once temperatures are outside of threshold. And that would be coming through the capture, the mobile capture app, and then also to capture data and have it for the purpose of analytics identifying where you have underperforming equipment, which maybe needs some action to correct to replace that equipment. So it's for the alarm purposes and also for the analytics and reporting purposes. All right, and this of all the features that we present, and I had this already in day one when I presented the set of features that we've developed for facility level management. This is the one that requires the most amount of development. It's the one where we've implemented or ran this pilot and we had this MVP, thanks to Philip who developed and gave us a very good starting point for continuing the work. So now it's one of the two top priorities we have left together with a transactional based app to be able to have a functioning integrated solution within the DHS2 environment. So that's the objective now. He mentioned also the April, 2023 release. It's the same for the real-time stock tool. So we hope to have also a functioning version by that time that we can already use, but there's already been quite a lot of work that's been done. I don't know if there's already some questions. I actually did not check there, but. Yes, if I can just one very good question. Whether there is any limit on the number of blue master temperature sensors that can be connected to the Android device. I have studied the blue master documentation carefully, also the native app. I'm not aware that there's constraints, but Philip on the technical side, do you think that there will be limitations? That's a hard question because my application just connects to one. And I think there's no limitation from the blue master side, but then we're talking performance of the application. If you connect to several blue master sensors at the time, will data collide when you capture and how slow will the application be? I think that's a bigger concern. Did it answer your question? Okay, I think we leave it like that. Thanks a lot for the question, Sean, that you're here. I realized that we need to consider the user requirements. If you can, I would be interested what's how many sensors you would think would be a typical use case for you. Do you think two, three would be enough or should we consider five? But yeah, I think... That's a question to the user, Philip, not to you. Exactly. Yeah, sorry, that's a question to Jean de Dier because we are establishing the user requirements. So I had not thought of it as an excellent question and we need to kind of specify that for the development, but happy to have input from the field. George, I actually have a question slightly related to Philip that maybe, Philip, I wonder if you can just elaborate on the work for you connecting to Bluetooth low energy. So it's something that took you a little bit of time to understand how that worked. Is there anything particular about that? And maybe, again, you may not have the exact answer, but is that different with the number of devices that you would eventually connect to if you could say something about this? Yeah, so there's different protocols to do this and there's a GET protocol and it's very specific and I only managed to connect to one, but yeah, but I haven't looked at it because when I got the one connection, I was happy with that. So, but when you learn about the Bluetooth low energy protocols, I think it's possible too. And there was a partly a leading question because what I was thinking is what we discussed that there's no connection being established. It's not similar to pairing to a wireless speaker, for example, like we have at home, but rather you have the sensor broadcasting data and then the app needs to be able to filter a poll for the data that they're asking for, that it's being requested, also using this hexadecimal. So it was partly a leading question, but if you want to say anything about that. Maybe I didn't explain it in depth, but the idea is the sensor is always advertising data. So the job of the application is to go to a sensor and capture the advertised data. So if you have five different sensors, as long as you walk past them and they always advertise, I guess it's possible to capture from each one as you walk by them. Yeah, but then we get into more technical and demanding, I think, programming requirements there. And I think that's what you mentioned that you didn't get into that level. You made a connection to one device and that's the kind of thing that we'll have to explore now when we're developing this further with our development team is how to build in some of these different than technical programming workflows that will facilitate a person in a health facility to be able to capture that data, receive alarms in a way that's also efficient from their functional requirements so that the technical programming and equipment requirements facilitate the workflow for the person at the facility. Did we have another question here, George? Is it a DHS to Android app? Yeah, go ahead. Is it a DHS to Android app or have you developed a separate app to link with DHS to API? Yeah, so it's part DHS to the starting point was the Android scale it up. You can, which is set up with the SDK and it's linked to the tracker capture app. So that part is simply DHS to but the second part is the Bluetooth communication and that's what I mentioned, the gut service and the BLE packages are separate. So now for the further development it's also another discussion that we're having and it's probably much more of a technical than a functional question. Should this be part of the native DHS to capture app? So the app that you've all downloaded onto your Android devices, should this be a native function there or should this be a separate app? And there's still some ongoing discussion, the likely and I think what we, at least from the functional perspective, we see it as being more useful, being integrated to not have additional apps but there's still some talks about what would be the best solution. So we'll see how that actually plays out but I think the integrated idea is much, from our perspective and not from the developer perspective would be to have it integrated. Yeah, lots of interest and this from Gerald Thomas. So thanks for that Gerald question from Nora. The expected lifetime of the sensors is two years running 24 seven. Yeah, so battery life and partly related to the number of readings that are being made. I don't know if George or Philip, you guys have an answer to that. Yes, I'm just copy pasting the answer into the window. Yeah, so according to the specifications, public documentation, it's a one year continuous data transmission or two years intimated data transmission. So that gives you an idea, but then the temperature data log is programmable and how often the data is collected. So that would also have an influence but it's approximately in that range and this is why we're also keen on selecting a device which allows you to change the battery, which is by the way, the drawback if you have a waterproof sensor, that's great, but I think you will not be able to change the battery. So that's the trade off and it's a standard battery that you can find anywhere in one of the CR flat batteries. It's very easy. It doesn't require ordering from the manufacturer or something. Yeah, and we have a question about differentiating which sensors are being reported on the app. And I think if I remember the MAC address was visible, but that should be something that could be relatively easily managed with identifying devices. But Philip, if you want to elaborate. Yeah, so my solution was it's a minimal viable product. So time was of essence. So I just used the MAC address, but you can give it a unique ID and you can change the name of the sensor. So it's fully possible to identify it. Right, that's great. We actually had a question in the beginning and George, I don't know if you'll take this up with the alarms and then an escalation alarm, but Nisreen asks if this connects remotely to responsible people far from the facility, sending alarms for any problem. So the alarms are for the temperature excursion, but there's this issue of alarms and escalation. I don't know if you would take that up, George. Yeah, reading my mind. It's on my first slide. Absolutely. Okay, so we'll let you take it during when you present here now. Abdel asks if it's available for download and you want to buy the hardware and do simulations. Okay, Abdel. So Philip had a link to the GitHub for the code and the sensors are called blue maestro sensors. So it's still something that we're working on, but in principle it is available and everything that we produce, of course, and once there's a final version that we're publishing integrated, it will be freely available. But the sensors are called blue maestro sensors. Just a keynote. If you download the application from my GitHub repo, you have to change the DJI's to instance. So you have to have your own instance and configure a tracker capture program. And then you need to change the credentials for the instance. And then the access to each of the sensors is also hard-coded with the MAC address. Is that right, Philip? That's correct. Yeah. Don't need to reconnect those to their own sensors. Yeah. You have the MAC address. Just go ahead. Yeah, on the back side of the sensor, there's a sticker with the MAC address and you can just add it in the code. All right. I think that's it for the questions now. Again, this is something that we're developing and working on. It's definitely the tool that will record the most future further development, but it's something that, again, we're communicating with partners and donors. We're aligning with standard requirements for remote temperature monitoring. We're connecting with different platforms and different partners offering similar solutions and seeing how is this useful, how is this beneficial? And this is, I think, part of what George then will present now is a bit of the development path and what we're working towards when it comes to remote temperature monitoring and this temperature management tool. Do you want to present a bit the... Okay. Thank you. You're welcome. Yeah. Thanks a lot, Philip. Great work. If every master's thesis would be so relevant, you know, the world would be a different place, so that's absolutely amazing and really looking forward to taking that forward. I'm going to share my screen just to mention that the selection of the BlueMastro temperature sensor, temperature data logger, was actually a kind of precondition for the project because it is open source. And also to mention that there is many WSU pre-qualified temperature monitoring devices, but there's actually only two who use Bluetooth, which use Bluetooth. There's one that was pre-qualified recently or this year, but according to the catalogue, the pre-qualification is no longer valid and that device doesn't provide open source or it doesn't provide access to the source code, so you cannot connect to that device other than with the proprietary application. So that's basically the only choice and that's the reason why we made the choice. It was not for any other reason, it was just Reynolds and my preference. Brenner, you're seeing my screen and I'm going to go into presentation mode. Yeah, that's perfect, George. Okay, so thanks for the Tunisian, you hit the nail on the head. It's all about real-time alerts and immediate action. We do see of course the temperature requirements on recording temperatures and having a record, twice daily record at least, but of course as a practitioner your immediate concern is what happens if my refrigerator fails during the night or on the weekend, a day off and I don't want to come Monday morning and see that all my vaccine is either spoiled because the power went off and it took action or because it was frozen. So our focus is really on this how to manage alerts, which is a challenge, but of course in addition, the temperature recording requirements are also important. So I have only two slides. So what we are looking for to have prompt immediate alarms on a mobile device in case of temperature excursions, so that's the idea. Somebody leaves the refrigerator open or you have a power outage, the temperature rises or the refrigerator is defect and the temperature drops and the vaccine is in danger freezing that basically as soon as the temperature excursion is noted, so keep in mind it will take 10 minutes if you're logging every 10 minutes, that immediately with the next measurement you would have an alert on your mobile phone and we hope to develop that natively in the DHIS2 app. And of course it's critical to take immediate corrective action by the storekeeper when she or he is at the store, that's the objective of the alarms alone are not alone, are not enough. And then if nobody is at the store, then you want somebody who is able to take corrective action so who has the keys and can start the backup generator set or move the vaccine to another refrigerator to immediately go to the facility and take corrective action. Refrigerator should have 24 hours hold over time but so within that time span take corrective action and the hold over time will protect the vaccine against increased temperature but of course if your vaccine is in danger freezing then vaccines can be damaged by freezing within minutes. And I'm just mentioning the WHO document that we are using also because this is kind of normative reference how to monitor temperatures in the vaccine supply chain. To my knowledge updated 2015 which gives exact instructions how to measure what to measure the temperature how to document it but actually to note fascinating document that at the facility level the possibility of continuous temperature monitoring is not even mentioned this best practice which is not even a consideration yet. But we hope that will change. Now if you want to have an alarm on your mobile phone then basically the application that Philip demonstrated is that that mobile phone is connecting synchronizing data directly with the blue master temperature sensor but that requires then the temperature sensor to be within the range of or rather the mobile device being within the range of the blue master temperature data logger and that is a few meters so depending on the size of the facility that could be in the entire clinic or in the vaccination site but if this is in a hospital in a large pharmacy that might not be the case. So our thinking is that of course the critical point is if let's say if you're in the hospital or in the clinic and the power goes off obviously you're going to check for your refrigerators but if you are not in the facility it's even more critical because you might not notice that the power went off. So then of course the blue master temperature data logger is using Bluetooth low energy so it has only a few meters of range and you will need so the thinking is to have a second device that is basically kept in the cold store in the range of the temperature data logger of all of them so usually the refrigerators are kept together and anyway we are thinking that hopefully you will be using mobile devices I showed yesterday for your monthly reporting of your stock on hand and your stock distributed or even for the real-time stock management then anyway it is advised to have a mobile device ideally a backup device at the facility because it's not really good practice for staff to have to use their private mobile devices and if you have a tablet let's say you put it in the cold store within range of the sensors and you make sure that it is charged when you leave the store and it doesn't run out of power on the weekend then we are trying to build an application that will basically take the record alarm on the device in the cold store and then transmit it to any number of mobile devices through an SMS an email or a DHS2 notification of course that does require that the cold store where this dedicated mobile device is left is connected to the internet so briefly this we have been we have written an extensive document I think it has 85 pages currently on the user requirements so to basically write out in detail was Philip has presented and to add some final touches so the idea is the same you have the blue master a temperature data logger that locks the temperature starting point is every 10 minutes it can be less than that if you want but of course then you have more data and as Nora said you have less battery, short battery lifetime and you have seen the screenshot for the application in the DHS2 but we hope that the application that you have shown will then be integrated into DHS2 so it will appear as one of the icons that you have already seen in the sandbox it will just be another icon with a temperature management then you can access it everything else will be running in the in the background so the android app you use it for configuring sensors synchronizing the data we're thinking of maybe storing the 20,000 data points that is something to confirm and again the important part is the alerts and the mobile device then will synchronize with the web portal as I mentioned in order to manage the notifications but also in order to provide the analytics the dashboards that you can see some examples of you can have a pivot table with a recording but also can have a chart with a minimum maximum and we're also thinking we also will count the number of alerts so the number of excursions and ideally the duration and calculate the minimum the average maybe the mean kinetic temperature okay and up strong screen yeah so this is kind of a very crude mock-up just on an excel the way we think we could maybe have a visualization on the mobile device because what is important for me as a storekeeper is I want to see the excursion so you could have basically in green you have the average you can see that it was in range the first few days and it went out of range then you can see the when and it froze and how long it froze hopefully this will not happen because you will have the real-time alerts but still it will give you a complete record and on the bottom if you can if it's not too small you can see the number of upper and lower limit excursions that were recorded that's kind of the first mock-up but analytics is still to be seen on the mobile device on the web portal exactly what data that we want to present in on what way I don't know Brenda you want to take some questions before I move on I don't think there's any immediately Nasserine just comments that it's better to react in one hour and yeah but I think you can continue George so exciting new development that I at least only learned recently is that WHO has issued in January so it should be PQS of course not PWS sorry that's too embarrassing sorry for that back to the slideshow on it's called the equipment monitoring system and it's an M2M so it's a machine-to-machine interface and the idea of the PQS standard is that it will eliminate the need for separate temperature data logger like Brenda said we are not we don't we want to basically be able to connect to any Bluetooth sensor that is on the market of course it is WHO pre-qualified and the the pre-master is kind of the pilot but eventually we would like to extend that but the dream is of course that you don't need a temperature data logger but rather that temperature data logger is integrated into the device already and that I mean some devices to have thermometers like small LEDs on the screen but this would be like a full-fledged temperature data logger that is not only showing the current temperature but actually logging the temperature so the manufacturer integrates a sensor in the equipment and locks so you have an equipment identification that's quite amazing so if you were to connect in future your refrigerator freezer to a DHS2 DHS2 mobile application then automatically every piece of culture and equipment would automatically identify itself like an aircraft does with a transponder so there's no need anymore to attach great unique identifiers attach them to the device that would also already be built in and you might notice that these four pieces of information is exactly the WHO PQS standard and global asset management which I will briefly mention tomorrow so all those information that in future will be required to be included in the barcode or GS1 data matrix code on the equipment will also be available through digital authentication compressed information until the runtime this can be probably really useful for the cold chain technician you have the minimal maximum average temperature it's calculating the alarm limits the time of the excursions you also can record the voltage availability even a door lid opening sensor is mandatory so the number of times that the refrigerator is open the cumulative time that the refrigerator was open humidity contents and fan data so a requirement is to log that every 15 minutes minimum and to have at least one year of data stored on the device so quite amazing almost reminds me of rockets with telemetric functionality where you basically have all this information available digitally now one caveat is that the data transmission there is clear standards is that the PQS requirement is only to have a usb interface so you have to be the storekeeper has to be able to connect laptop computer or a mobile device with a usb cable and basically read out the data but obviously if you're reading out the date on Monday morning and you saw you see that all your vaccine froze on Friday in the night it's good to know like Philippe say we will prevent vaccinating a child with a vaccine that is not effective but you still lose your vaccine and might not be able to to vaccinate other children but there's an optional feature which allows sharing the data through wi-fi or bluetooth and this is basically what's going on we hope that today's is optional we hope that many manufacturers will voluntarily include this option I'm sure it will only cost them a dollar or maybe less to do that and we want to be prepared so the requirement is that for all the new pqs pre-qualifications from I think 2024 this will be mandatory of course it's going to take many years until all the equipment in the field is exchanged but we think this is a really exciting development and will greatly facilitate the temperature monitoring so no need for paper and no need to manage external devices and the hope is that in future you can basically walk into any cold store that has this system installed switch on your dhs2 mobile app and just connect to the refrigerators and read out and store the data in the dhs2 database without having any configuration and a dream coming through this is actually a screenshot from the WHO pqs requirement it's my last screenshot so you can see you have the appliance identified you have the you can see upper alarm limit so the temperature was above eight degrees for 10 hours below 0.5 for one hour you have a complete read out of the temperature the total alarm time the power how long the refrigerator had to have the power the compressor running time and also apparently automatically locked faults so that's really an amazing development it's not coming tomorrow but hopefully in a few years this will be the standard and we definitely want to be prepared for that estimate so yeah should we take questions or any comments from anybody just a let's see Robert has a comment I think it would be great to configure automated real-time email or SMS alerts in the LMIS for the temperature alarms to facilitate quick response so this is definitely what we exactly what we are planning so you can see here the alerts that we envisage so as I mentioned you would have the alerts coming directly from the mobile device directly on the mobile device but DHS2 natively has functionality that if you synchronize your mobile device with the with the database then the then the database the DHS2 database can prompt alerts to the sorry to the mobile device through the notifications but of course we are also thinking of SMS alerts or email alerts definitely and then maybe just a quick comment from Colsi or a quick question about not using Wi-Fi so these sensors they only support Bluetooth and so then there's no Wi-Fi option to connect in that way however there are definitely other sensors however the long-term development path is through this EMS requirement and that we go that route rather than developing individual connections to each sensor based on what their current capacity is but back over to you George yeah just quickly I mean as I mentioned we have carefully studied the PQS pre-qualifications and it's my understanding that currently this is ProMaster is the single device that currently still holds WH or PQS pre-qualification so it doesn't look like many manufacturers are going down that path of course maybe others might be developing I'm not sure I understand the question on the Wi-Fi but it's my understanding that if you want to use a Wi-Fi connection then that would require using a gateway I don't know I have not seen any PQS pre-qualified sensor temperature data logger that can connect directly to a wireless network yeah that was the connection that was the question if a connection could be made from the sensor to a Wi-Fi network and then connecting to the device actually I saw Alex has his hand up here so Alex if you want to ask your question good afternoon I was trying to figure out how do you match the vaccine batch with the the refrigerator because now you would want to know if the vaccine batch got spoiled or not I was trying to figure out how do you now match the two now basically the supply change side and then now the temperature monitoring okay excellent question here I step ahead we are dreaming of this it is on our roadmap so we do in this itch but again this is like iteration three or four we do in visage that if you were to use a real-time system stock management system that when you put away your vaccine and when you pick it from the refrigerator refrigerator freezer that you will every time identify the refrigerator freezer through a gs1 data may be called or maybe automatically so that you can link the batch with the refrigerator so we're definitely looking into the possibility of doing that the problem will be that in order to clearly identify the batch that will only work with a gs1 data matrix called because otherwise if you just receive measles vaccine and you would have to like type in the batch number expiry date that you're entering your refrigerator that would probably be to come or some but indeed the gs1 data may just call at the secondary packaging level is already a requirement by UNICEF and GAVI officially since I think January last year and that is possible and we are looking into that I don't know if it mentioned basically I have demoed straight to the real-time stock management mode that you have seen yesterday the next step will be to include batch numbers and expiry dates if you're integrated with an upstream system and then the next version next iteration that we are thinking of looking into is to use gs1 data matrix codes for the stock management and once that if that were to be available then you could link it with a refrigerator and definitely we're thinking of that even going a bit further that if you were to integrate DHS2 with an upstream national ELMIS like you have seen Medex is M supply or this afternoon be later then you could even envisage that if upstream the same recording is done that at any time you could have a complete temperature record of the vaccine as it travels from store to store across its entire lifetime ideally also on the truck or in the cold box to transportation so thanks for that George yeah to a comment and a question and I can give a quick reaction and also if you want to fill in so first from Nora she writes we're seeing some very good examples of how digital technology can help and support healthcare services we also need to help ensure low resource settings also get enough support to also be part of these developments and I think this is entirely in line Nora with what we've proposed here last mile solutions that can be implemented in low resource sites and also at scale considering all of the aspects both the technical the human aspect the workflow and how that matches their requirements also the sustainability both from a technical but also from a financial perspective so very much in line with what we're looking at here and then secondly from COSI about the connection between the sensor and the app how do you handle the sensor broadcast to ensure you're getting a transmission from the expected sensor for instance if there are other sensors nearby so COSI this is a similar to how if you have multiple speakers or wireless speakers you're connecting to so the app will be able to identify by the MAC address so the MAC address is a specific address identifying the network or the transmitter through a network so it's sort of like a serial number for the internet connection or for the wireless connection that identifies that specific sensor and it's partly what Philip also said that we could provide a name and connect that MAC address to a name so we identify which sensor is which for which device I don't know if you have comments to those two points George if not we can continue we have eight minutes left in the session yeah just a brief comment on what Nora said definitely I mean I suppose you're all aware but just to be safe I mean the the details are given the PQS catalog so I will not give numbers but the great majority of the available temperature monitoring devices that are specified in the PQS catalog they require annual fees myself I have worked in on a project in one of the leading suppliers basically you buy a device you have a one-off cost that can range anything between 50 and $3,000 for cold room that can be depending on the sophistication but in addition most of those business models foresee that for each and every sensor that you install in a clinic you pay an annual fee and you can imagine that even if that fee is only a few dollars per year per device if you add that up to hundreds of thousands of clinics that's a huge cost so that's why we think that using THS2 is free and open source application would be a big contribution because basically you don't need you eliminate this recurring cost and one of the features apart from the transmission is that these business models provide you then also access to a web portal where you can study the analytics but this is basically baked into THS2 so no need to pay to have your data hosted on a database and shown on the dashboard provided that you're already hosting a THS2 server great I'm just trying to capture some of this and writing as well George so we can I hope to be able to make a Q&A or an FAQ actually from this questions channel so that we have this published also on our website there's been a lot of great feedback in comments but I think that's it for now George if you want to continue yeah that was all I had just a comment what I'm reading on the on the question and answer so indeed we are thinking coming back to this question of like recording the refrigerator freezer where goods are stored unfortunately it's I think it's quite tricky because you have to identify the products and commonly drug products only have a bar code with a product number which is just a seven or eight digit number but it doesn't identify the batch so if you want to record exactly which batch was stored and which refrigerator freezer you will have to have a GS1 data matrix code on every secondary packaging which is a given for vaccines but also keep in mind something we will need to study carefully is that it sounds very enticing exciting but it will also require that if you receive a cold box or even a small refrigerator truck and you have hundreds of packages of vaccine then you will have to scan each and every GS1 data matrix code because every secondary package has its own serialized number or the alternative to avoid that is that you're integrated with an upstream system and as I mentioned if the upstream system is able to load all your serialized number into a future DHIS2 version then that would also take care of the stock received but it is quite intricate and then we'll have to see the practicality in the field because you will have to then really thoughtlessly record every secondary packaging one by one if you miss it then you will not have a record All right George I think we if we've wrapped up I don't see any more do we have any new questions I have a comment for Robert yeah so linking vaccine to refrigerator but that's a comment to he made to Alex actually I'll let you all read that I think we're okay again this is something that we're developing trying to fill a need fill a gap very much in line with what you commented Nora about making it available to low resource settings and making sure that it's sustainable in multiple ways both from a technology, financial and different ways that it suits the the sites and the locations which where it will be implemented I think this is all great any more feedback any more requirements both for the biomedical equipment management coaching equipment inventory management the previous session and this one on temperature any feedback any questions any inputs we're very welcome to receive that so feel free to share either through Slack through email or any other channel to understand the requirements and understand what kind of use cases you have and how we can we can help meet those a lot of what we've shown is still you know configurable adaptable it doesn't have to be implemented out of the box as we show but it can be customized for the different contexts in more of a general sense so if you have very specific needs also reach out to us and we'd be happy to hear and if it's something that's useful we can also include it as part of the regular guidance for the configuration so we have two minutes but again no need to to go on if we have all of the questions answered all of this content is there I'll share again the links to the presentations but you have quite a few documents and resources already that you can access for this so let me know if there's any other points but if not we can stop here it will take a 15 minute break actually 16 minute break and we'll be back at 1 p.m. austral time so in 60 and we want we want to welcome Suganya from the Belida team who will present their ELMIS solution I think Suganya correct me from wrong you'll also be joined by Danushka but you can confirm that so we've had some talks with them and we will then yeah hand over to you you can take the time that you need we have 45 minutes but if you go a bit longer a bit shorter that's fine because we'll be following up by question and answer you can also check the Slack channel throughout because there may come some questions in the questions channel there and if there's anything just to speak up when we can we can support but we've had a very active three days already lots of questions lots of engagement so we're looking forward to hear what you have to present and the floor is yours thank you thank you for that Renault we have uh Danushka Hi Suganya and hi Renault great so let me start by sharing my screen can you see my screen and am I audible yeah yeah that's okay great okay great so hi everyone it's a good morning good afternoon and good evening based on wherever you are located around the world and thank you very much for the interest and connecting to our presentation today so we're really excited and we really appreciate your participation about myself Danushka Kavindo product manager for Intuition Vesta product vertical Beleta Private Limited I've been with the company for the past six years and have worked with ELMIS product from the scratch and I have been in the ground for all of our implementation in Asia and Africa I think most of you would have joined previous to ELMIS presentations as well and I believe most of you're having a good understanding of the capabilities of ELMIS solutions so during my presentation I will give you introduction to Beleta and will explain about the problems and challenges we saw when we were developing the system and I will explain a little bit about the functionalities of the system and highlight some key features and implementation approaches and the support mechanism also at the end of the presentation I'm really happy to answer any questions that you all have yeah I hope you're good to start great so about Beleta Private Limited started back in 2020 close in 2010 so as a enterprise scale solutions providing company and we are 100 plus at the moment our specializations are with web mobile technologies and we have software solutions for supply chain management and other healthcare applications so we are focusing on digital finance procurement smart manufacturing and also we have decision support systems with AI capabilities so all of these solutions are built on a single platform called intuition so it allows to integrate with all our solutions and with that we have been able to build a good interoperable layer where we can integrate with other solutions so this is our intuition platform with four main products we have a fully fledged ERP mainly implemented in South Asia covering industries such as manufacturing retail health hospitality and services and then we have our intuition Vesta ELMI solution which is the focus product for today's presentation and also we have standard treatment guideline application for health workers implemented in SWAT in then COVID-19 CVLN's platform implemented in Sri Lanka so all these several technologies have won many awards and and I thought it would be worth highlighting the Commonwealth digital conference award back in 2017 and also we were recently run us up in Asia Pacific IT awards last year so this is just a quick snapshot of the solutions we have around the world for ELMIS and this is kind of a research conducted by global fund and Gavi back in 2019 so these are the vendors and these are the functionalities they provide so the thing is so we also a solution which has all the the compliancy and a very fully compliant ELMI solution which are taking all the boxes and all the requirements which are highlighted by the donors not only that there are many recognitions this is just extract from Accenture report back in 2019 highlighting the importance of our decision support system in health management logistic space yeah so that is about Belita and where we come from and now let's focus on the ELMI solutions so this is what we think when we talk about health supply chain when we talk about the warehouse management but this is the reality in the one middle-income countries so I'm coming from a place where we have different conditions we've seen very tough conditions and we wanted to build a solution to match these reality and to deal with different conditions so that's why we built Intuition Vesta electronic logistic management solution so these were the the main things you need to make sure the six logistic rights so you have to make sure you have right products right in right quantity in right condition at right places at the right time at the right cost so we were focusing on this and then we were checking what are the challenges we were researching and we were going to different locations around the world to see what are the challenges the health ministries and service delivery points are facing when it comes to logistic management so these were the key things that we saw when we were developing the solution and and there are new things getting added up and we're building solution to create those needs so we were checking whether we have whether those locations are having forecasting mechanism can they project their pipeline do they know what are the the requirements for next three months six months for a given time period and do you have a proper distribution mechanism so when you receive commodities do you know where you should push these commodities do you know the demand in different locations and can you cater for different programs such as maybe family planning maybe maternal child health maybe TB, HIV likewise so can you have a solution which can cater for all the programs in the country then we were looking at the data so can health facilities have a real-time visibility to their stocks can higher levels get a quick snapshot about the locations in real-time and can you track and craze batch numbers lot numbers VVM stages expires and are you getting advanced notifications to take better decisions so if products are getting expired today you need to get those communicated in advance are you getting those communications so we were thinking through these things then the stock management can you manage stocks in your warehouse do you know your receipts versus the consumption in your service delivery point and do you have a proper mechanisms for cold chain management expires management and also there are other interesting things like when we go to countries there are a lot of systems implemented and how can you fit in your solution within the existing systems which are already in place for example if you go to a country you may have DHIS-2 implemented you may have other ERP systems implemented so how are you going to integrate with those solutions and provide the solutions and software solutions only for the requirements the countries are having so we were thinking about those and also we saw a lot of infrastructure constraints so there were not there were locations which are not having good internet some locations they are not having interrupted electricity so how we can provide a solution to counter all of these challenges so that was our main objective when developing the solution so that's why we came up with Intuition Vesta ELMI solution so counter all of those challenges we saw we developed online web-based ELMI solution and also we developed offline desktop application which can work online and offline it can work without internet as well and whenever you have internet it will start synchronizing data and then we created two mobile apps one is transaction-based mobile application you can do transactions in service delivery points or else we have another mobile application which is having data entry module if you are not ready with the warehouse to go and implement a fully-fledged ELMI solution you can start with data entry application and all of these data we capture are connected with our decision support system which we have built around Power BI and with our reports and with our notification mechanism so this gives kind of a 360 view of your logistic management in your organization and it can cater for all the levels across the supply chain so these are the main features we have in the solution so we have pipeline forecasting procurement management distribution and transportation management inventory management warehouse management dispensing systems where we where you dispense commodities to the patients then we have an asset management module and also we have a good interoperable layer to connect with other health systems and like I explained earlier all of those information can be visualized using dashboards and reports which I explain later so this is a basic use case when it comes to logistic management which I will explain the functionalities through this and how beneficial ELMI system could be in this scenario for an example so before you procure anything from the suppliers you need to know the the forecast for the next six months three months for a given time period so you can use the forecasting tool built in the system and identify the future demand then based on that you can go and procure commodities using the system so once you create the purchase orders and conduct the procurement then you can inbound your commodities to your national store even this can happen at regional levels provincial levels as well the system can be configurable based on your requirements so when you procure from the national store basically you need to deliver those commodities to different levels like regional provincial if you have local government levels for those levels and to the service delivery points so if you have a ELMI system you can conduct all of those activities in a single system and then the full information will be available in a single system which will allow you to understand real time which will allow you to see real time snapshot of all the activities happening across the supply chain not only that so during the COVID-19 pandemic we have expanded our solution to vaccine management so one thing we saw was there were lack of systems to conduct a vaccination session so we built different solutions around our platform to cater these needs so we created a multi-channel citizen registration system and so using that citizens can get registered of our vaccination sessions then from the admin panel administrators they can set up different eligibility verification criteria and prioritization criteria based on that appointments will get scheduled and those will get communicated to the citizens so with these appointment scheduling using those data a pipeline can be done and based on that the procurement can be you can conduct your procurement then once you procure communities those can be distributed to your central levels and then to different other levels up to service delivery points then we created a mechanism to manage the dosages of the vaccines and also we created a mobile application to administer the vaccines and also we created a mechanism to report the adverse events which are occurring due to the vaccines and also vaccine certificates can be generated using the system so these are a few additions which we did like add-ons to existing Yileman solution also I thought it's would be worth highlighting asset management capability of the solution so if you have let's say assets like different machineries different devices and if you want to maintain assets of the warehouses in the system so we have asset management module built into the system so using that you can record the breakdowns you can create preventive maintenance schedules even you can transfer the assets from one location to another then you can generate reports on assets and also we have enabled the capabilities to integrate with our team devices where we capture temperature readings and also if you don't have the capabilities to integrate with our team devices we have given like manual forms where health workers can enter temperature recordings into the system also we support GS1 bar holding so we have a three layer barcode generation and label printing mechanism built into the system and the compliant with GS1 we are connecting with GLN and Chetan platforms with GS1 India and we have a barcode application built by our company which I will show you a quick demo so this is the barcode application we have built yeah so basically if you have the purchase order you can scan the barcodes for the in common commodities you can scan them when you are receiving the commodities then you can so system will automatically capture the batch numbers expires so you just have to verify the quantity same applies to the outbound shipment as well so you will have the sales order then you will have the invoice same when we are doing the outbound shipment from the system by using the barcode scanner you can scan the batch numbers then verify the the quantities and you can dispatch the commodity so this will allow you to accurately capture the batches using the system then if you move on to the AI capabilities of the solution and the forecasting that we provide with AI capabilities so this is the machine learning model that we are using in the system so basically we gather all data from ELMI systems and also we are connecting other data sources such as supply data sources such as data sources from to capture different other factors so then we conduct data analysis and the data sequencing and then we are doing the future engineering to highlight specific features to identify these features then we do feature scaling and data preparation and then we train the models and then we identify the most accurate models so once we identify the best model then we take all the factors and we put those factors into the model and then we create predictions so right now in our forecasting tool we are using a live GBM model and these are the factors that we are using to generate the forecast so basically we are using factors related to country, province, district and we take the growth rates in the regions then we count for campaigns and other programs then we count for legs in consumption then we rank location product categories then we are taking the impact like COVID impact or else we are actually having different pandemics those impacts into the model then we are taking information from YLMAs where we capture order field rates monthly stock outs likewise and then lead time for distribution so by using that we have seen accuracy levels around 80 percent with this model but we are trying to take it to the 90 percent mark and that's the research our team is doing right now to make it more accurate and try to bring it to a level where we can have 90, 95 percent of accuracy also using the system you can generate different reports like transaction reports, analytic reports transaction reports are like the direct reports that you can generate from the system like purchase order reports commodity receive issue reports the reports about your stock adjustments physical inventory bounds likewise but if you take analytical reports it could be related to the plan forecasting your stock outs your stock out trends then reporting trends then summarize data so all of these information you can visualize as PDFs or else you can download those as Excel tables or as raw data Excel so this is a small demonstration about the reporting tool so basically we have a report pool with a lot of reports which can be configured based on your requirement then once you provide the permission for the reports users will have this dashboard front of them they can select the report which they want to visualize if you hover over you can see the description about the report then you can apply the filters the filters can be customized based on your requirements in this one you have like product filters you can run it for single product or multiple products and you can run the report by product group then by warehouse and by organization level whether you are running it to the province entire country or specific district likewise then you can run it for the financial period you require after that you can preview the report as a PDF or else like I mentioned earlier you can download it for Excel or Excel raw data Excel tables so if you preview the report it will show you a report like this in PDF format so we have made it very simple for the users they can quickly read the description about the report then they can apply the required filters and they can download the report in PDF or in Excel formats and if you they want to further analyze the report they can download that report in Excel raw data format and then they can do their third analysis so these are the dashboard and KPI as we have in the system so we have shown the information in different types of visualizations could be budgets GIS maps tables crops workshops so basically these reports these dashboards and KPI country specific based on country's needs we can customize these dashboards and provide the information based on country's requirement so let me share my screen and try to show you that so this is basically a power BI dashboard which we have done by connecting the data sources from the ELMIS so we have basically categorized those based on the health programs of the country so for the first tab you have data relating to the performance of the system itself then you have different dashboards for different programs and the KPIs so if you check the performance of the system you can see the stock out by the periods and what are the stock out properties you have then the system shows the reporting status of the country so this will give you a better indication whether you are seeing 100% data of the country or whether you are seeing just 50-60% of the data in the country because like I explained earlier we have different systems in place so if you have all the facilities using the web-based solution you will have 100% reporting but if you are using offline solutions sometimes it may take time to synchronize based on the internet availability so the system shows the reporting levels based on that so these dashboards are very interactive you can build down those two different levels and you can see the dashboards getting filtered for those different levels and you can analyze information like that so likewise we show different visualizations for commodity reliefs, issues generated and these are very specific for countries needs so we can do specific needs by customizing these dashboards so if you go to a program so you have their consumption for that program and then on top stock on hand in the expires and the loss rates you should select consumption you can select a specific product and you can see how's the consumption around the province then you can build down to different levels to see what are the consumptions in district levels local level government levels then at their sleepies then we have month of stock on hand that's kind of a very good indication to show for how many months you have stocks in your country so you can again select the product and then you can see where you have stock outs for the specific product and where you have satisfactory stocks where you have over stocks, under stocks and dead stocks in the country and if you go to expires similarly we show the expires by percentage so you can see the products which are getting expired so we show the expires in one month, three months and six months intervals and the best thing is also the system we have a notification mechanism where you will get notified about the expires the loss rate, the similar concept applies and if I go to KPIs so we show KPIs like order field rate expiry and with expiry and loss rate then we show the lead times where you have lead times then local versus foreign procurements and procurement by funding source so this list of KPIs can be different based on the country's requirements so that's why I said we're creating very custom dashboards based on country specific needs yeah so let me move into the presentation again so then I think it's worth highlighting the interoperable capability of the solution system can be integrated with the solutions which are already in place or else the solutions that we are planning to implement so that's why we have created a very good interoperable layer with the best press APIs and we have done these sort of integrations with our team devices we have done with ERP systems we have done integrations with EMR systems and also you can integrate with DHIS too which I will highlight in the next slide and then you don't have to implement the full solution full ELMI solution but what you can do is you can implement the missing components let's say if you need the procurement module to be implemented so you can implement the procurement module from Vesta ELMI system and if you're already having let's say ERP system which is handling inventory and all of those activities you can use your system by integrating with intuition Vesta or else let's say if you need inventory and warehouse capabilities but already you are having the procurement systems in place again you can there's no need to switch for our full system you can use your existing system but you can integrate with our system to get inventory and warehousing capabilities so likewise with our interoperable layer that's what we're enabling for an example if you take our implementation in Zimbabwe so they are already having Microsoft Dynamics ERP system in their central warehouses so what we did was we implemented the solution for the other levels which they have after their central warehouses so all the procurement and central warehouse related activities are happening in Microsoft Dynamics but from then onwards up to service delivery points we are managing the commodities using our ELMI system so likewise we can create integrations based on your requirements so these are the solutions and this is how you can implement the solution so you basically have your central level provincial district levels local level government levels and service delivery points and these are the solutions at each level you can implement so if you take the lowest level the service delivery point if you have proper internet if you are fine with your internet connectivity then you can go and implement our online application but let's say you are having on and off internet connectivity the connection is interrupted you can go ahead and implement our offline application which is a windows based desktop application it has the same capabilities to perform all the activities for inventory for warehousing for procurement likewise then if you are again having intro internet but if you would have proper infrastructure place like laptops, printers then you can go ahead with the mobile application which is again a transaction based mobile application and also if you have specific vaccination needs service delivery points you can use our vaccine information management system so you can use our vaccine information management system to provide vaccine for the patients however if you don't have capability to implement transaction based system then you can implement our data entry application or else you can implement DHS2 data entry application for an example if you're already with DHS2 and already if you have placed systems with DHS2 is no need you go with our data entry application or else any of the applications which are capturing data so you can directly go with DHS2 and then from there onwards we can take data to other levels and you can implement full scale ELMIS in other levels and whatever the information you are recording from service delivery points will get integrated to the the fully fledged ELMI system and those information can be used to generate your forecast and those information can be in your reports dashboards likewise so and also with at each level we are providing our decision support system which is coming with notifications which is throwing emails which is throwing which is having dashboards reports for you to get alerted and then for your local level governments so you can implement online offline mobile and vaccine management information system but we don't recommend having a data entry system in those locations because we expect the crown section volumes are really high and if you do have a transaction based system that's where you can get lot of accurate data and real time data and at the district level you can implement our online offline applications but at that level we don't recommend having mobile based transaction system because the levels could the transaction volume would be very high and if you go up in the order for provincial and central levels we're mainly recommending online application which is a based application where you need to have proper internet to have an up and running system so we always propose online application because we always expect the crown section volumes to be really high and these levels stock levels and the stock levels and the the crown sections they perform need to be monitored in real time this is our project deployment approach so when we go to a country when we gather requirements based on our RFP or as we conduct requirement gathering sessions then we visit sites and we see how's the readiness of the sites because then based on that we decide whether we are going with offline mobile data entry or else with the the web based application so those decisions will happen based on site readiness and then what we do is we conduct software customizations configurations and bonds the system is customized based on the the local context then we go ahead with user acceptance testing and we allow users to test the system and provide their feedback so based on the feedback if anything needs to be changed so we are really happy to do that so we have our dedicated interviewing teams in place to provide to incorporate those feedbacks and I think operating those UAT feedbacks and further customizing the solution then we go to the training of trainers so we train government trainers to go and implement the solution then we conduct user training then then we go for the implementation and we are making the software live and once the software is live everything is we are providing level one support level two and level three support so level one is mainly where you will have a support center in place for users to directly get contacted at any time and if they are having any concerns if they are having issues if they need any clarification we can get those quick clarification from the level one support center then we have level two support in place in provincial level where you have provincial officers who can go and visit the locations and provide direct support then you have level three support this is where we have our development teams in place in our headquarters when you have new requirements when you have software bugs you can communicate those to our level three support team and then they will do the required modifications to the system to address the needs of the users so these are some some of the pictures from our implementation in Nepal Zimbabwe and also this is these are some pictures from our recent implementation which is ongoing in Philippines so these are like I mentioned these are the three implementations in Nepal, Zimbabwe and Philippines so we have partnered with USAID Global Fund in these projects they're supported by UNDP Chemonics and MSH also I thought it's worth highlighting about our support structure which I explained earlier because in this type of a machine critical solution you need you definitely need support and you need that support maybe very often and and the lead time shouldn't be high so that's why we have this sort of a support mechanism in place so you have on-site teams and off-site teams on-site teams is in the country where we implement the solution so that's where you have users level 1 help desk support team and level 2 provincial ELMR officers so users can basically contact through emails they can raise a ticket in our ticketing system or else they can have phone calls, text messages to deal to communicate with level 1 support team so they will direct these support queries to level 2 support team they decide they want to go and visit these users and provide direct support or else that's a change request to develop a new feature or else it's a software bug so that is getting communicated to our offshore team which is based in Colombo, Sri Lanka in our headquarters and our support team we work on those and provide them and address those requirements to do that we have a dedicated support team in place so that's where we add a lot of value so we have support manager software architect software development team lead business analysts software developers quality assurance engineers then business intelligence analyst and distance intelligent developers in place with this team who are specifically looking at software bugs then looking at new requirements and that's why we've been able to address any concerns or the new features requirements within a shorter lead time yeah so so about inclusion investor ELMI solution so this is a solution we have implemented in three countries so it's a proven and tested solution and also it's not program specific you can implement the solution for any program like maternal child health like family planning for TV malaria so using a single system you can address multiple programs and also we have features for pharmaceutical drug management then laboratory and EPI management so Nushka I don't mean I don't mean to interrupt but we have 10 minutes left and there's a few questions that have come in on Slack so I think Suganya you can also reply directly in Slack or if you want to take these just so you know that to manage your time if you want to take these in plenary but back over to you sure thank you so I mean the last slide so I can take on the questions so we have a 24 seven dedicated supporting like I explained earlier and also I wanted to highlight the solution can be hosted on promise based on country specific policies which in place or else you can host in Ashura or AWS the best thing is we have a very experience globally experienced team with us who can go and identify the requirements and implement the solution in the countries so yeah so so we have come to the end of the presentation and also I thought it's worth highlighting about our the newer solution which is the control tower which captures data from ELMS systems and different other systems and which can provide functionalities relating to demand forecast procurement transportation management order tracking and for services yeah so these were the things we wanted to highlight in today's demonstration within the shorter time period we have yeah so I would like to take any questions you have thank you so much for that that's really impressive all of the features that your system provides that was really great to hear if you could share the presentation I can make it available to all of the participants we have a shared folder where they can have access to that and then they can reach out to you directly there are a few questions that have come in maybe I can well there are two of them of course DHS2 is an open source platform and the first one question is is if this is open source and if it's available on github from another one it would be quite a comprehensive system but if you can say something about the licensing that would be great yes actually we're not open source and we're a hot solution and the thing is but when we implement the solution we are sharing the source code for the country for the sustainability and also we train the teams within the health industry to take up the source code at any time they require or else like I mentioned you earlier we have a dedicated team who are specifically supporting any new requirements any software bugs so you do have to wait for a longer time to get things resolved so that's why we have placed dedicated teams as level three support yeah we are a hot solution right now okay that's great and we work the HS2 works with also private platforms and we have integrations with Oracle ERP and others so this is not some kind of requirement but it's definitely a question we get being an open source software it's one of the first things that is asked there's another question also in the chat asking about the support is it all from Sri Lanka from your your headquarters or do you also what's the level of building the local capacity and local support within the countries where you implement is that a requirement and any of these three implementations you've had so far definitely because sustainability different definitely depends on the local capacity building so that's something we really value that's why we always build a level one level two support with local capacity so when it comes to level one support the support center will always be placed in with in that the country that we implement in the solution there you will have dedicated support team with support managers support analysts who can directly engage with the local users then we train level two support officers we call them ELMI officers who can go and visit the sites based on the level one support center's requirements so they can directly engage with users and they can provide any when you configure configuration level changes and also they can train the users and have a look on the issues they have and there's anything that they can't resolve and if it's relating to new future development or any software bug related activity then it comes to level three support in Sri Lanka but like I explained earlier if the country wants to have the source code and if they want to build things around the source code yes that's something that we allow and then we can build the capacity of the local resources to provide even when source code modifications and provide healthy support all right that's great now I have a comment and three questions from Robert Moldy he's been actually very active throughout the week very good questions Robert so first the lead intuition Vesta is definitely a comprehensive ELMIS with great UI and analytics use of AI machine learning is leading edge that's his comment and then yes three questions so first question from any past experience where it has been deployed as an ELMIS how easy or how long does it take for users to get up to speed with effective use second question if a country took up intuition Vesta for national LMS and installed on premise rather than cloud with the system what would be the system requirements and then third are the level one and level two supporting locally recruited and developed are these posted or are these posted by Belita yeah great questions about past experience implementing a solution so we have implemented the solution in Nepal we have implemented the solution in Zimbabwe and we have implemented the solution in Philippines which is ongoing right now so how easy and how long it takes to implement a solution depends with countries requirements for an example if you take the implementation in Nepal so it was our first implementation it took actually six months to implement the pilot locations then if you go to Zimbabwe took less months and the requirements were not very complicated like Nepal for an example in Nepal we had to develop the application with the local language we have to have features because they're having a different calendar as well they are in 2079 I think right now so we had to develop different calendars to manage their financial years likewise there were a lot of very complicated requirements in the country that's why it took six months but if you take Zimbabwe the requirements they had were not very complicated so it took like three to four months for the implementation then if you take Philippines again bit of a complicated requirement so it took like six months to have the pilot so likewise it depends with the the requirement but the basic requirements you can implement within three months timeline after customizing the solution and for the local context the best thing is most of the things we have in the solution you don't need to do code level modifications you can basically start configuring the organization hierarchy and then we have a specific admin panel for the users to upload master data admin to upload master data and users to upload their opening balances likewise so we have built a lot of configurations around the system which allows to up and run the system within a very short time period about on-promise and system requirements yes we provide the on-promise capability to take all three of our implementations we have right now all are on-promise so in Nepal they have a the system in a local data center in Zimbabwe they have a solution in ministry of health and even in the Philippines they have it in the department of health the requirements again it depends with the number of users you have so you don't have need to have only the thing you need to have is you need to have the internet connection if you are using our web-based application or else we can provide you kind of a VPN connectivity depends with the infrastructure you have right now in the country or else if you're using our offline applications you need to go to a specific location just to synchronize data on a weekly monthly basis otherwise you can start using the the solution and start start creating the transactions when you want to synchronize and the report the data we'll need internet connection about we can just stop you one second Anushka because we're at time at 14 so I just want to say thank you to the participants who have to leave for a follow-up meeting I want to just respect the time so the word of the day for the attendance is red rock and we will meet back then tomorrow online at 10 a.m. also time to continue with day four okay so thank you to everybody who has to leave now but we can go back to you now Donushka just to continue and hear the answer to the third point on the local or remote support and we also have a couple more questions that we can we can come with if you still have the time to stay with us so back to you Donushka definitely so regarding level one and level two support mostly what we do is we always encourage the health ministry to provide their resources to build capacity around them for level one and level two support or else if they don't have enough resources we encourage them to go and partner with a local company in the country and then we build capacity in local resources so always in order for implementations level one and level two support we have done with local resources we have trained them starting from the beginning of the implementation so what we do is we when we normally go to a country first we are trying to establish these level one and level two support teams and they will get trained start from the beginning and they will be engaged in the project start from the beginning so when we go to the implementation stage then they are up to the level where they can provide level one and level two support so we conduct specific trainings targeting level one and level two and also they will be part of a UAT as well as they will part of our TOT's and user training sessions so then once we go to the the implementation stage they are already connected with the users and they are already moving the system to provide data support all right thank you for that I wrote a summary in writing in the slack in the channel just so that's captured there's a lot of information I have another question from then George Maguire asking in what countries is the mobile app used at the facility level for stock management yeah right now the mobile application is used in Nepal and so there is when we go to the second stage in Zimbabwe they also they are going to have the mobile application for transaction based mobile application right now it's in a post because of the pandemic but I think hopefully things will start 2023 and Philippines they are going to use our LMIS data capturing mobile application until they make all sites fully live that means until they make until all sites start using our web based transaction application okay thank you for that and then I have a final question from Abdu Kader Hassan Abdi who asks if you have any plans to implement your LMIS in Somalia a very specific question yeah definitely that's something we would like I really like to discuss and see what other requirements they have and we're really open for that so we can definitely conduct a demonstration session of them and discuss with their health ministries ministries to see their specific needs and and then we can take it forward from there that's something we would really like to have we have a hand from Robert go ahead Robert thank you Brayno and thank you to present there's just one question which I which I raised there was that backward scanner which was in the radio that he demoed is it running as some kind of app that is developed by the company or it is that's not the case because I saw the user interface we were looking familiar yeah I think I just wanted to seek that clarification yeah good question actually we are providing the software so that's software built by our company but the device we recommend certain devices which are compatible with our solution and and you can install the software basically it's an android application you can install the software in the device and then you can get the features relating to backward scanning etc so we mainly provide the software solution but you can procure the devices and we recommend the devices all right I think that more or less covers all of the questions that we had coming in I think that was a very impressive presentation a lot of good and complete features that you have in your system unless there's any more comments I don't see any more hands I don't see any more hands here but yeah Danushka if you have any final comments to the group we would otherwise like to thank you for your time and for presenting and we'll definitely continue to be in touch but over to you again thanks very much we're really thankful for DHS2 Academy and for you for providing this opportunity for us to present our solution and we also really looking forward to engage with DHS2 and like I have seen you have a very good application mobile application which can capture data at service degree points so if you are already if any of the countries are already having the infrastructure in place for DHS2 definitely you can start using that solution and then they can they want fully fledged capabilities in ELMIS then you can switch to any of the other vendors to get the full functionalities and we're really happy to work with DHS2 and also we would like to thank everyone who in this session today and there were a lot of good questions and interest and we are really looking forward to work with you all thank you very much for the opportunity all right thank you again Danushka thank you Suganya who we've also been in touch with and yeah feel free to reach out to the VELIDA team if you can share the presentation I'll make it available to all the participants and we definitely look forward to being in touch we'll touch a bit more on the aspects of assessment and seeing what's the the best solution and what's the best option for the country on the Friday morning session again and then again it comes into what are you trying to achieve where are you trying to to bring your system and with our approach being making use of existing infrastructure where it's available and again depending on a dedicated ELMIS to manage your supply chain from a central level down to where you can connect to this DHS2 data where it's available but again thank you and we'll be we'll be in touch for the participants we'll connect tomorrow again at 10 a.m. and continue then on day four of the LMS Academy thanks everybody who stayed over time and we'll see you all tomorrow