LMIS and Supply Chain Meetup: Deep Dive into CCE, EMS, and WHO PQS Plugin

[screaming] Okay. So, welcome to our community of practice LMIS meeting on coal chain equipment management. So, thanks a lot to Gaussim for setting up this uh this meeting and preparing it. Uh I'm joined by Breno Horst with the who is the LMIS lead at the H center university of Oslo and also has a merit of having developed both applications. So take the opportunity to ask any technical questions. He actually wrote the code uh which I don't understand. So I'm going to start by giving an introduction. So the and panel will then cover the um the details on the on the configuration and uh and the settings. Um so we have two topics the WHO PQS catalog plug-in and the EMS equipment monitoring system data import app that we will present today. And what I suggesting is that uh I will present the use case uh briefly present the tracker program that is uh linked uh to both applications. Um then briefly demonstrate what the applications actually do. U briefly present the analytics for the EMS. the PQS plug-in doesn't have analytics and then uh focus on um presentation by Breno of the configuration and how this is actually uh set up in DHS2 and I suggest if you have any questions just jump in and and ask them as we go so that um we we can clarify uh any issues. So I'll start with the WH PQS catalog plug-in. I can I hope you can see a slide. Um I will be quick but just as an introduc introduction. So PQS means performance, quality and safety. So this system of pre-qualifying cold chain equipment, refrigerators, freezers, but also any kind of injection devices, walking cold rooms. So anything that is cold boxes, anything that is related to cold chain equipment um has been um established by WH since uh more than 20 years. So who is has actually test protocols the test equipment and the pre-qualify equipment and any uh equipment that is pre-qualified is is in included in a WHO catalog. So I'm going to switch my screen. This is the website who WHO catalog of pre-qualified immunization devices and there's uh you can see they have revamped the they completely revamped their website last year and um so you can review you can download the the PDF catalog um but you can also go here and search for individual um devices directly on the website. So you see you have all these category categories. Um we are focusing only on the refrigerators and freezers but um if anybody has a need the same uh application the same the plug-in could be adapted to any other pieces of equipment. So for each refrigerator in this case for example you have the PQS number and you have the details and you can click on the on the on the application on the device and it will basically show you uh all the details of the refrigerator. So um the manufacturer since when it was pre-qualified what kind of refrigerator it is where it was manufactured. So there's an um extensive amount of technical details everything that you see here. So this uh catalog is also available and has been available as a PDF file for a very long time. But of course it's difficult if you wanted to use one of these devices in a tracker program. you would have to go down on this list and manually upload all these attributes and specifications into DHS2 which is quite cumbersome. So fortunately who I'm not sure exactly when I think last year improved the website um which includes a JSON file now for the download. So you have here all the data. You can download it as a PDF file but you can also download a JSON file. So if you click here just gives you a JSON file with with all the with all the data. This is available from from the who website and um the objective the whole objective of the of the tool that we're presenting is today is that if you enroll a new piece of equipment uh in a DHS2 tracker program then all of these attributes that you have seen in the PDF file and the JSON file will automatically be loaded into the into the tracker program. Um so as I mentioned for the time being we are only this is only working for refrigerators and and freezers. Um just to mention that we follow the WHO conventions. So we are not philosophical of what has included or not or the format the data formats of the the data fields. For example some of the the files of the data fields with the comments are very very long. But anyway, we have just we are just downloading the catalog as it is available on the on the WHO website. One thing that is important to realize is that not all devices have information on all the data fields. For example, if you if you download the specifications of a refrigerator, it will not have the the data fields of the freezer, for example, the freezer capacity. And you also have refrigerators with one compressor, others have two compressors. So the the data will vary. Uh what we have done in the plug-in or what Brena has configured, we have configured all the 72 attributes. So it's a very long list and we have done that intentionally because it basically covers everything that you could ever need. And of course, of course, you can reduce the attributes, you can hide some of them, you can remove it. It just depends on how you design your your tracker program. So this is uh you don't you're not obliged to use all of them. Um yeah so the basic function is that the plug-in will populate all the attributes uh during a DHIS2 enrollment. Uh this is important. So when you enroll a new piece of uh equipment a new device you register and enrollment is done in the same um in the same process. You can change it afterwards. So this is intentionally so that you would not inadvertently change all the specifications of your refrigerator. But if you enroll [clears throat] a piece of equipment and you see that you have uh selected the wrong uh device, you can always like discard the enrollment and start a new one. So I'm going to Yeah. So this is the last slide on this is just to show you that you basically you get the data from the WH PQS catalog and you put it into DHSQ tracker program with the PQS plugin and you can also do that with open FN. So I've shown the catalog. So I'm going to show the um um show our tracker program. So this is our sandbox that is also available publicly to you uh where you can test all these uh applications um and and VR configuration although we have not yet um activated the the plug-in and the EMS app. So we will try to do that uh today or tomorrow so that you can all use it use them. So I said I was going to show you briefly. This is a this is a a tracker programmer. Maybe I show you an existing device. So you see here you have all the tracked entity attributes that we are going to download now from the PQS catalog. I'm just showing you briefly what the tracker program does. Um you can use this in uh in any tracker program um that you may want to use. This case it's for a cold chain equipment uh life cycle management. So you see they have all these attributes that are downloaded and are tracked entity attributes for the tracked entity instance and we have the in this case um we have the cold chain equipment life cycle management. So just uh very briefly we had a a webinar on this previously. So you can um record and manage the corrective maintenance equipment transfer um the corrective maintenance the weekly preventive maintenance repair requests. um could also manually record uh temperature um and uh also record alarms and for our next um application um upload the equipment data from a refrigerator. So I'm going to show how this application actually works. So I'm here in in the capture app. I have here list of all my tracked entity instances. In this case, we have only recorded one. So, first I'm going to select the organization unit where I want to set up a new piece of equipment. So, imagine that um a new piece of new refrigerate is delivered. Uh you set it up and you want either the facility, the healthare worker, the storekeeper or the cold chain technician will enroll and will register and enroll a new appliance. So what you do is you go to create new code chain appliance and um in order for this to work uh Brena will show you have to have the PQS plug-in set up and configured. So this is the case um it is it is set up and it gives us this field. So here this is an option set where you can basically select any refrigerator from the PQS catalog that is available on the WH website. So I'm going to just take any of this like um this one is 3 110. So you have to know which you have to know the PQS number but that's the only thing that you need to know. And you see that if you select uh a PQS appliance, it's pure magic by Breo, you get um the category of the refrigerator. It even downloads the image and you get all these attributes like the PQS code, the model number. You can see it's pre-qualified. You can see when it was pre-qualified, you can see in this case it's a best frost refrigerator. This is the manufacturer reference 304A. It was manufactured in Denmark. And you get all these specifications. They are set in um they are grouped into categories. So you have the details. This follows again the JSON file, the product specifications like whether it has freeze protection or not or not, the d the dimensions, the energy source. Then you have product specific uh um additional um attributes like the refrigerator vaccine uh capacity and as I mentioned in this case it's a refrigerator therefore you don't have any freezer specifications but of course if you're using freezers and refrigerators in the countries you will be need to keep this. You have here some comments where the manufacturer can add any comments uh which are downloaded. You have information on the price and the shipping, quality standards, uh where it was verified, who carried out the testing and um you can see until when this refrigerate is pre-qualified. So you get a huge amount of of detail um all the details that are available directly from from the PGS catalog. So that's basically what the application does. I'll pause here briefly if you have any questions on the functionality before asking Bren to explain how this uh plug-in which uses native DHS2 functionality was actually configured. Yes, I see Mr. Baba you have erased your hand. Please go ahead. >> Okay. Thank you very much for the presentation. uh this is a wonderful uh tool that people are bringing on board there. Uh I hope you will enjoy it. Okay. So my question has to do with um the auto population of the information. So let's imagine maybe I have a refrigerator that is not sanctioned uh was a pre-qualified. So, do I have the option to still enter the information manually? >> Uh, yes. So, if you It's a good question. Uh, so by the way, I forgot to mention that what this application actually does it it connects directly to the WHO website and it pulls in the information directly from the website. So this information is not cached anywhere and that guarantees that whatever information is uh downloaded is is up to date. So in in this case if I don't want to answer your question I'm just going to discard this because I don't want to uh actually save this. So if you create new cold chain appliance you can also add add the information manually. So if you have a because probably in many countries you will have refrigerators that are not uh um not uh who press pre-qualified then you can just like um enter the data manually. Well, if you don't select any any uh refrigerator from the list, then you can just type it and you can save it like any other track entity instance. Yeah, thanks. That's that's a good question because of course you you don't want to limit yourself to only PQS pre-qualified equipment. Okay. Are there any other questions? Okay. Okay. Then I'll hand over I'll stop my sharing and I let Brennan explain how this uh wonderful application was actually uh configured. Okay. >> Okay. Thank you. George, can you see my screen? >> Yes, I can see code. Yes. >> Right. And I won't go through that now. I just want to quickly share that um this is developed as a standard DHIS2 web app and the plug-in is just a different way of connecting that to a DHIS2 instance. So the way that you I won't go into the details of the the configuration or development but um the key point is that you can download this uh repo and I'll share the GitHub link to it for now and you can deploy it using a tool called yarn which is a package manager that's used for DHS2 apps to facilitate deploying uh these types of apps. uh we do want to include that in the app hub in the future but for now I'll share a link and you can download this and this uh of course should be done by system administrator and once you have that uh you can use a yarn command to deploy and then you simply choose the instance to which you want to deploy the app and there I'm using our sandbox um URL and that can be done within um just a few seconds. You need to include the administrator uh user and password. And once that's done, you can enter then the configuration for that app to link it to your tracker program. So you download uh you clone the repo and then you deploy this to your instance and what you will then do is configure using the tracker plug-in configurator which is an application for this purpose to link that app to your um tracker program. We have a uh reference configuration for the cold chain appliance life cycle management. It's what George showed at the beginning and as he mentioned we have a previous webinar on this where we go through the different stages for capturing data for cold chain appliance. So now this is integrated for registering new pieces of cold chain equipment. So then you would then link this and choosing this tracker program and then once the plugin is chosen it will be available from a drop-own list. Here's the plugin and it's the field which you see uh in the registration form. As soon as George opened uh the form, you had this uh drop-own list and this is where the plug-in is functioning. What needs to be done again as a one-time um configuration is that each of the different fields. So for the image, the appliance identifier, title, PQS code, model, these need to be mapped to your tracker program. So the plug-in will have a reference to each one of these fields um 72 individual fields as he mentioned that are all included. So you can choose as many or as few as you want to map depending on your configuration and then you link that. Any one configuration will not be the same. We see that a lot of countries already have some form of equipment uh maintenance and follow-up um that they're using. So it will not necessarily match the exact reference that we have in our reference configuration. If you don't have that already in place, you can and we recommend using the reference configuration. But if not, you would then make that link. And once that's done, you will then have the option to then uh navigating to your program, choosing the organization or unit where you're operating. And this is where you have then the plug-in operating. It's linking to this one field. And all of these different uh options are available directly from the website after the app has been deployed using yarn deploy. And after mapping each one of the fields and that mapping will then ensure that appliance identifier will link to the correct reference within the catalog. Same for the image and same for all of the other fields which you may have again which may or may not match this reference implementation. Uh but that's more or less how it works. So quite straightforward um and quite easy to configure. If you have many again if you're using all 70 it will be a lot of fields to match but otherwise a relatively painfree deployment of the app. Back over to you George. Okay. Thanks a lot uh to PR for the explanation and for the configuration. It's uh I spent like three years trying to build a catalog in DHS2 and tried different tools like to extract uh data uh from a PDF file and upload it. I never really managed. So this is really a great improvement and also avoids uh mistaken entries. So you just download it and you make sure that you're not entering data into the wrong field and you're not uh entering wrong values into a field. So imagine if you have if you had several refrigerators and you had several hundred date entries uh the likelihood of making a mistake is quite high. So uh does anybody have any questions on the on the configuration? Any questions to Breno on the technicalities of how to set this up? >> Uh thank you George. Uh I see in the comments there is a question from Amad. Uh Amjad would you like to um unmute and read your comment or would you like the we can read it for I can read the comment. Okay. >> Yes. Yes. Thank you for the session. Thank you George for your great work. Uh yes my my question was about how this plug-in is syncing data between the DHIS2 and uh you know WH site as I understood this plug-in can retrieve data and configure data within the DHIS2 but is it real time you know when it comes to pitching data from WH site this was my question thank you >> yeah Um, this is actually real time. So what the plug-in does, it actually connects directly to the JSON file on the WHO website and pulls the data from that website in real time into DHS2. I maybe like just plain confirm. >> That's entirely correct. So it's pulled at the time of registration from the WHO website and then it's stored in DHIS2. So, it's not looking for that each time you're accessing the data, but it's the one time uh at the time of registration. >> But sorry, what if there was an update for certain equipment or let's say a refrigerator or something? Is it going to be reflected automatically on the DHIS2? >> Okay, that's an excellent question and the answer is no. Um so the thing is that um the the manufacturers the way the PQS pre-qualification works is they have to submit like a dosier which they can do electronically these days with all the details then the device is tested by who and then if the if the devices appliance is accepted it is included in the catalog. So, I'm not entirely sure, but my assumption is that um the the pre-qualification is accepted with the specifications that the supplier has submitted at the time of registering uh registering a new device. And if you take something like the voltage or the freezing capacity, that's not something that can change in an appliance unless you would have to build a new appliance. You do have a valid point. I assume it is possible that um doing the processing of the data and publishing cat the catalog that mistakes were made. So um um the supplier might submit uh the specifications and uh who might find that there is a mistake in the catalog or maybe the supplier made a mistake in the documentation that was submitted and then you would have a mismatch and it is true that we don't have we don't have the possibility of um of changing the data um but it's a very good point we will look into that whether we could extend the plug-in to also allow for like checking for updates. That's a good idea. >> Yeah. Yeah. Thank you, George. Yeah. My point here was because we have almost the same we went through the same experience when we developed a minifi which is an integrated imminization supply chain system for Iraq ministry of health. So we we do have we reached the same uh you know the same stage we were able to pitch data but not to make it live. But I think the solution is basically maybe who can offer an AI or something just to give it to partners or any interested uh you know development party to to use this API to pitch data real in real time uh from from DHI from WH side. So this will solve >> it's my understanding it's my understanding that this is actually an API. I mean uh like as Brena confirmed this is actually fetching live data from the WH website. >> Mhm. >> But it's only done at the time of registration. >> Okay. Okay. >> So we avoid the problem that initial idea my idea was let's download the data and then when you need to register you fetch the data but then you would have a problem that the data might not be updated and you have to have somebody who is regularly updating the data. So uh Renault came up with a better proposal that at the time of registering whatever data is available on the WHO website is pulled directly from the API and posted into the tracker program. So if WH made a change to the catalog yesterday or correction and you uh populate the data today you will get the data as of this morning from who I take the point that there could be change. I don't know. I don't have enough insight, but we'll try to find out from who whether they ever make changes to the catalog if that is possible and see if we can have a kind of um extended application where you would like check um the posted data against the data um if it was changed in the API and and and updated. >> Okay, >> thank you. >> Thanks for that idea. Um so if there are no other questions we are good in time. I'll move on to the second subject. Um yeah there's sorry there's still question from Baba Baba would you like to ask your question please? >> Yes um my um just about the testing of the plugin um think so if you are running um the DHIS2 instance on a local server uh is it the same procedure you used to deploy it or there's a different way. >> Yeah, that's entirely the same process. Um it's simply using uh the yarn package manager to deploy to that instance. Um if you're using it uh on localhost then um it would be the same. You can use yarn start actually and it would run on port 3000 or 3001 but the package manager will tell you where to access that. I assume you're running on localhost 8080 to access your main instance and then the app will be on a 3000 or 3001 port. So that's entirely um I mean nearly identical uh process. Okay, I think I'll move on um to the second application we want to present today which is the DHS2 EMS app. So the equipment monitoring system I'll give you a very short crash course for those who are not uh familiar. So the equipment monitoring system is a system established by who as a PQS standard. It is mandatory uh as of January 2026 for all new um appliances but also any appliance that was pre-qualified in the past they have to um comply with these new new standards. uh it is the facto global standard although there's of course no law on that globally but in practice all major donors like UNICEF kavis they all adhere to this uh to this standard and they will only purchase and uh distribute equipment that is EMS uh compliant so very briefly it's quite a complicated system with hundreds of pages of documentation which are publicly available so you have a level one refrigerator um that is a that has a built-in data logger that is logging the various data points every 15 minutes and um only has a USB port to read out the data but it is mandatory. Then you level two is a is the same data logger but you have an integrated display uh where you can read out the data also on the display and you have visual and audible alarms. And then there's a level three which is a remote temperature monitoring system which many commercial um suppliers offer but uh as a propriety system um they they work very well. They are highly developed but the problem is that you have to play you have to pay a license fee for accessing the data and for using the the data portals and as you know money is scarce these days and um it's um um quite expensive uh to pay a fee for for every refrigerator that is installed in the country. So um um thanks to who all of these level one to three they must all give free access to 73 data points through the USB port. So, even if somebody sets up a level three refrigerator with a proprietary um remote temperature monitoring system with a website and a SIM card and all of that, it is still mandatory to have access through the USB port, which means that any EMS refrigerator that is available already in the field and the the manufacturers have been starting to to ship this uh beginning of this year. So there's already thousands of them that are delivered to the field. All of them you have access to the data. So there's 73 data points um of which there are 32 standardized data points like refrigerator, like temperature, humidity, door opening and alarms which are measured every 15 minutes. Um there is a very detailed uh document I can uh briefly show you that you can find on the W website which is called data objects uh code chain data objects. Um and you can see these are all the data fields um that are available directly through the USB interface and that are mandatory. But in addition to those um that are mandatory, there's also manufacturer specific attributes. So we have so far mapped those u specific attributes from from two uh suppliers, two manufacturers and we are continue to collect others so that whatever data you would be extracting it would be available. So there's one year of data that is kept on the data logger with this 15minute interval. a huge amount of uh of data that is stored on the device um and is then after one year is overwritten but one year of data is still quite a lot is still a lot so you have temperature data but they have also performance data you have alerts whether you have a power supply every time the door is opened how long the door is opened so it's a huge amount of data and I guess everyone who is working cold chain management you're familiar with the tradition traditional way of uh placing a thermometer or a data logger in the refrigerator, taking out out twice a day. I have been doing that all my professional life uh in the morning and in the evening and recording the minimum maximum average temperature on a sheet of paper or in an Excel file. So here you can read out the data directly from your refrigerator. You can literally plug in a laptop um computer into the refrigerator through a USB port and um download and post the data directly into tracker program. And of course it will only it existing data will remain and it will add any data uh that has been locked since last time you posted your data. So basically what we are trying to do is to this is our ambition to put all the EMS refrigerators that are currently offline and where you have manual temperature and performance data recording or an Excel files and put it and make them available online. So keep in mind that whenever you post your EMS data from a refrigerator into DHS2 and you synchronize then that data will be available on the server and it will be available to anybody in the country you give access to. So not only to the storeke keepers in the health facility but even to the content technician or uh district medical officer or at the national level all this data is available as in DHIS2 is usual. So this is just uh briefly uh to show you the the different systems that are available. You can have a proprietary system as I mentioned level three with a SIM card or you have a Wi-Fi gateway. All of this you have to install and maintain and you have to pay for the SIM card. There's also the bar app that can do the same. So you can extract it the data but it posts the the data to a Gmail which um sends the data to a Gmail account where it sends the PDF file actually. Um you can also then stitch the data together with a prog app um to have like additional data and you can also do that um then link the data with DHS2 with open FN. But as you can see in the middle, the fast track is to use a USB cable, plug in the refrigerator to a laptop computer, open the DHS2 app that we're going to show, and then download the the data directly. So this is an example of the of the data that uh can be extracted. Um this is just a short um summary to show together the life cycle management that I briefly showed in the tracker program. So you can transfer equipment, you can document the installation, you can uh record your daily weekly inspections, the preventive maintenance that is done. Um you can document alarms, reasons for the alarms and whether they were resolved. You can make repair requests. Uh the cold chain technician, the engineer can document corrective maintenance and eventually can record the disposal of the equipment when it comes to the end of its life cycle. So this has been available for like five years and this is now comp complemented by performance management. So these are just the categories. So you have the compartment temperature and humidity. It records the power supply again every 15 minutes. You have also the ambient temperature and humidity. You have tech details on the compressor like the speed, whether it is running on the condenser temperature on the logger data uh itself on the battery and the errors. Um equipment monitoring device. So the again the battery and the errors. Uh door lid openings. So how often it was opened uh um and the duration and the fan speed. So before showing you the actual application, I will briefly show you what you can do with the data. So imagine that previously you had to record data and usually you probably have only the temperature data. You have to write it on a sheet or an Excel file and then maybe upload it to DHIS2. So this is the data that you will basically get free of charge as soon as you upload the the data with the app that I will show in a minute. So you have here the temperature. This is temperature from a refrigerator that uh we had donated actually by one of the manufacturers that we demonstrated to indoor conference that is now in Oslo. So you can see this is a this is actually actual data. So you have the the temperature for the time being we have only the the average temperature but we also uh working including the minimum the daily minimum maximum temperature. Um you have the the humidity um and the temperature data um the ambient temperature you so you can see it has a temperature sensor that is reading the external temperature. the room temperature of the appliance. You can see the power supply. So you can see the voltage that was supplied when it was plugged in, when it was unplugged. So this is very useful if you have a cold chain excursion. One of the things you can check immediately is whether the power supply was cut or not or whether there is a problem with the with the condenser or the compressor. For example, uh you can see here condenser performance. In this case, this manufacturer is not actually recording the the condenser temperature. So there are PQS um standards but not all of them are mandatory. So the suppliers basically choose what they want to dis display. But here you have the compressor performance. So you can see the speed of the compressor on the daily and uh yeah you have more information. we have um configured two um dashboards. So one would be like what would the dashboard of a facility actually look like and then we have uh what we call a library. So this is basically we have charts for all of the data that is collected uh charts and pivot tables. So any data that is collected um it's already configured in in the system. Um so you can see for example AC supply voltage availability uh how long it was available during the day and you can have all the data that is collected from the sensor. I'm just going to show the bottom um I think where you have a table with all the data. It's taking a bit time to load. Um so you can see you can have tables for all the data and basically this doesn't require any manual recording anymore. Yes. So I will not go through all the details. You can see have this on our uh in our sandbox. Okay. So I'm going to show you was just going to Yeah. Um so this is what I wanted to show you. So here I have a pivot table with day by day and this is all the data that is collected from on the data logger and that is available um in DHS2 and ideally if you have EMS refrigerators in all your health facilities and everyone uploads the data ideally daily but maybe once a week then um whoever needs to have access to data this data will have access uh to all of this. So now I'm going to show you briefly how the how this app actually what it actually does and then hand over to Brener to explain how he configured this prelimin tool. So if you go to um the apps and you select the EMS data import so as I said it's not yet available in our public sandbox but we'll try to do that as quickly as possible. It will open this app as it does for as it does any any other app. And I'm just going to show you how you would use this as a store keeper and Breno can then explain the settings. So all you need to do is to click on this file and select choose a file. And basically I'm not connected to this refrigerator because I'm sitting in Austria. But if you connect a USB cable to your laptop, then your refrigerator will appear like any other USB drive. So it it will look like a USB key that you plug into your computer and it will just say here um other device. And on the on the uh what looks like a drive you will be seeing files and you have here this is the ID of the best refrigerator and this is my most recent data file that I have available and all you need to to do is to select the date the file and you will see that that's all you need to do it instantly identifies. So this is a unique identifier the logger serial number and uh we have set up we have recorded this west refrigerator in DHIS2 and it is automatically linking it is finding this ID in the track entity attribute and um it this is the data that it finds. So it it uh found this data from the JSON file. it parse the data. You see all the details of the equipment are actually also available directly from from the refrigerator. So you also don't have to enter them manually. And here you can have the the latest data points. You can see like the AC current and uh logger battery remaining is available here. So all you need to do now is to select update data. So literally with two clicks um we already uploaded data. So there's only one data point that was uploaded uploaded. So all you need to do is to select the file, update the data and then when you go to the capture um that data will be available in the in the capture um application. Oh, sorry. Need to refresh to find my refrigerator. I'm a cog chin appliance. I'm going to select mouseot. Um yeah. Okay. I'll let I'll I'll I'm not in the right menu. Not sure why. And anyway, I I'll stop sharing my screen and let Brendo explain how this app actually works and how it was configured. Thank you. >> All right. So again, very um very briefly here um in the same way that you would clone the repository for the plug-in as a DHS2 web app, the same would be done for the EMS data import. and it's deployed using the same yarn package manager uh in the same way that I explained both to a to a server or to a local uh local instance. Once that's done, the app is available within the app menu. George showed how you navigate to it here. We haven't found a very uh fun logo or icon for that yet, but we will. Now, the configuration we wanted to make as easy as possible. So George showed you the data import, choosing a file, updating uh the records within uh DHIS2 for the settings. So this is what's done for the first time. You either configure for EMS or this can also be used for a fridge tag. If you have the sensite tech fridge tag, that can also be configured for the temperature data available there. But for the EMS, we go into the EMS category. You choose the program to which it should be linked. And here we have of course the cold chain life cycle management. And from there they're both attributes and data elements within program stages. And very similar to the plug-in configuration, we're simply linking the different data points either attributes or data elements within your program with the data that's available from the uh from the logger or from the uh uh the appliance that's providing this data. So there are a lot of different data points. Not all of them may be configured within your tracker program, but for those that are, you can choose them here. So for our program, we have an appliance manufacturer, and we simply choose it from the list, and we link it. And you also have a reference to the EMS um uh the EMS standards defined different codes for the different data points, and you can find those there as a reference. We've also included them here. So, as a one-time configuration, and this will apply to all of the different users that are linking to this program, so it doesn't have to be done per per facility. It's a one-time uh mapping that will link all of the different fields with our reference configuration. We have again extensive mapping including all every field. You simply make that link and once that's done both for the attributes and for the different program stages for the data that's being collected, we can save and that's immediately available once we're importing data. So here you see the same data. This is the same data file that George uploaded. So there won't be any new records, but that will immediately map and you can update So, we've tried to make it tried to make it as painfree as possible. One-time mapping directly through the app and that will then be available for all for all of the different users. Back over to you, George. >> Yeah, super. Thanks so much. Um, great uh great com contributions. I've been working in uh medical logistics for more than 30 years. I've been dreaming of this like for the last uh last 20 years. Um so dream come true. Uh what I want to show you briefly before is that in the capture we have a single stage with the equipment monitor storing system data. I just wanted to show you that it actually updates the data. So I had a fresh file from Preno from this morning. So this is the data from this from today and you can see that the data that is available from this refrigerator is automatically posted as a daily event to the to the capture app. So a few minutes left. Um we are not done yet. We have more ideas. So one thing is that the JSON file contains data every 15 minutes. Um but in order not to overload the tracker program um we are only posting daily data. So we're still working on aggregating the data the data. So you have the average temperature for example but we want to also add the minimum and maximum temperature. You have a record of all the door openings, but we basically we will be count how often the door was opened every day and the total duration of the of the door opening um rather than having the this 15 minutes data. So we are working on confirming compatibility with other appliances. By the way, uh the application that Breno just developed and just showed also works through the fridge tag. I guess many of you are aware of that. So works the same way. The fridge tag has a USB plug. Plug in the US plug in the fridge tag with the attached cable into your laptop and select fridge tag and update the data directly to the tracker program. So we have already added some of the manufacturer specific attributes which are indicated by set. But we will continue to select the those attributes from the other manufacturers. Um there's actually only a handful of them. I think eight that have PQS appliances pre-qualified so that whatever data you would be uploading from any refrigerator. It can be mapped in DHIS2. Um so the application that we have demonstrated works on a desktop computer or a laptop computer. Um and we are working on a solution for mobile device. So the the apps and the plugins uh don't work yet on uh the DHIS2 capture Android app but we are thinking we have already added a field in the tracker program where you can upload a file a data file and we are exploring the possibility that you could connect your mobile phone to the refrigerator and just select upload data. the file on the capture Android app and that file would then be posted to the server and then trying to see if it is possible for Brena to do some more magic to parse that file and post it to the tracker program. So this is kind of the idea that we are going to explore. Um my dream is to have a Bluetooth connection on the refrigerator. So this is only optional according to the PQS standards. It's not mandatory. But if any manufacturer would um develop an appliance that has a Bluetooth connection, we would try to extend the application that you have seen so that you don't have to even connect the USB cable. We are thinking of exploring the use of AI for identifying reasons for technical faults. So imagine you have a huge amount of data and of course an experienced cold chain technician could look at the data and probably identify common faults but we are thinking of like feeding the the data. So you have a full year of data 15 minute interval that's huge amount and um hoping that the AI could identify fault such as that there's a a leak of the gas so you would have to refill the gas in for your compressor or maybe the the the fan the cooling fan um needs cleaning or maybe it would identify that the gasket is broken or that the refrigerator is open too often and that the AI could do data analysis even for non-experts and guide on how to uh remedy those faults. Uh we are thinking that in principle what you have seen is it's a JSON file that is mapped to a tracker program. So you could envisage you could do that for any kind of laboratory equipment for an oxygen concentrator for ECG monitor for example provided that they generate JSON files you could probably parse the data in the same way. So if anyone has any ideas who would be really interested in a in a project uh you could also envisage to go beyond logistics and health like you could uh connect uh a laptop or mobile device to weather station that is not connected to the internet. you could um think of monitoring the water level in a in a in a well uh or in a water tank or in a fuel tank and extract the data. Um and there's a great possibility I think that there's actually been a concept on uh for that by Gavi that you could use the data from the appliances share it with the manufacturers of course if the MO agrees and that would be a huge uh treasure trove for them to see how their appliances actually operate in in [clears throat] actual settings and to try to improve. So they could like identify the frequencies of breakdowns of the compressor or the the the fan or uh the the gasket tearing and having to be replaced and could then selectively improve their equipment. So just to mention on our sandbox as I mentioned we are working on making those two tools available in the sandbox as soon as possible. And that basically concludes the presentation, but um uh looking forward to any questions you might have on the EMS app or on the on the functionality or on the configuration or if you have any suggestions on functionality is missing. Yes, Mr. Hassan, I can see all the hands raised, but please go ahead. Uh I think it's still muted if you're speaking. Okay, did we have any um questions in the chat? >> Um well, there are very important uh links that Brenno shared in the comment. Um people are also welcome to send a email. Your emails are there in the comments or post in the COP. Um you know I I could also you know close the recording just so to see if this is still anyone who'd like to ask before we >> Yeah, I see Mr. Alson has raised his hand so I don't know if he uh still had a question. Okay, he lowered his hand. So, I'm not sure if it's recording. >> Yeah. >> Yes, please. >> Okay. Thank you.