 Okay, so can you see my screen? Yes, please. So as Madhu explained, MAI is a mobile application which facilitates the quality and real-time data collection and reporting of animal disease from the fields. So the workflow is still the same. We kept what is the basis for MAI, but we decided to modify slightly the functionalities to enhance the platform as well as the data collection and the flexibility of the tool. So MAI is integrated to a platform, which is called the MPresai. We have a public website, which is now where you can access all the official information which are collected from YEs or from EIOAs and all the official information on disease events, which is translated into three languages, but we also have a private interface which is directly connected to MAI, and from which the validation flow, the acceptance and validation of the event coming in from the field can be accessed, visualized, and also analyzed in five different languages. So from these websites, we can ensure that the data are confidential and can be disclosed to the public only when the data sharing agreement is signed from the country point of view. So until now, MAI have been deployed in 17 countries over Africa, and more than 2,800 users are already enrolled in the use of MAI. We collected more than 35,000 disease events with MAI, and the event had been accepted and validated through MPresai. We already did 29 training workshops, so we will already received a lot of feedback from the countries. But with the new MAI plus, we are moving to another way of using MAI. So we are already looking at what is outside of Africa and how to use it in other settings or the countries with different type of deployment, but also different environment. So what is new as a functionality in MAI? So we speak about all the interoperability aspects. So it's an ongoing process, but we will be interoperable with DHS2 and CLAB as well as other database which are under discussion. We already have a unique identifier which is prepared for cross interaction with other official and unofficial database. So we use a construction like UNFO, the country ISO code and a unique identifier for the events. We are having two types of platform, a training environment and an official platform from which the countries and users of MAI can differentiate the environment. We are more flexible and we have an extended set of role and permission from which users can access different aspects of the platform. Even if we have a unique URL and a unique mobile application based on the user role and permission, the user can be able to process different type of information. We are able to upload photo from gallery to be, I mean to attach to the form and report symptom and lesion with visual support. And we can also export the graphical representation on the summary on statistics directly from the mobile application and share it through social media. We have a customizable form. So in the past we had only one form used by any user and at country level, but now we also have some customization possible on the internal administrative unit for example for countries which were not well represented with the Gaul and subdivision we allow team work by segmentation of the environment. So we will use wording like workspace and segments to subdivide the grouping of the user at country level but also at regional level to propose some confidentiality on information shares. We also allow the distinction between emergency and routine reports. And we have an extending set of reports and analysis through dashboards. So this is the summary on the extension of MI and now I will go through some presentation and video to show you how it's possible. So MI is only made for Android so you can directly download through Google Play the mobile application and you can already switch the workspace and segment to access to specific events which are part of the teamwork that we propose. I will explain a bit later what is the meaning for workspace and segment. So the five different languages directly available within the application and based on the user role and permission you can access to different functionality within the mobile application to proceed to the acceptance validation also directly into the mobile application, but also to review what had been commented when you submitted for example on events. So comments are coming from the management team who could request for example additional information which were not present in the form or in the report that you submitted. So you can already see that there is also a different looking for the training mode. So it's a yellow version of the official MI plus. So here you can see some report and analysis available directly within the mobile application. All these graphical representation are also directly available into imprecise the platform from which you can accept and validate. You can share the information directly from the mobile application by sharing a link to the dashboard that you want to share or by exporting PDF or images of the dashboard that you created. So I was speaking about customizable form. So here for example you can see the page from which you can define if you decide to access to this customization. You will see that you have a switch button for emergency reports. They will be seen in a different way in the application as well as on the platform. You have the internal administrative subdivision that you can customize so you can create your own subdivision and you can select the item directly within the application. We are still taking the GPS coordinate from which we can also extract all the type of administrative unit and subdivision. The onset data and observation date are available as well as another type of date, which is the reporting date, the date from which the report has been shared with the hierarchy and the surveillance system. So based on this distinction, emergency or not, you will see that the overview of the report will be seen differently. And you will see as well this question mark on the top of the status of the event, as well as the red background directly on M-Presaille as well. So when an acceptor want to accept an event, he will see a red flag on the event. So from the complexity of the grouping of the user of M-I on the field, as well as in the acceptance and validation team, we will be able to aggregate the event reported as well as the type of disease reported and the number of animal affected based on this subdivision. So here an example from which you can see that the country has been subdivided into five team working at based on the regional subdivision and accepted and validated events reported from this subdivision, the administrative subdivision are grouped in a specific color code. So you will be able to know in a more specific way from where the disease has been reported and how many events have been reported to administrative units. We are also working on the idea of providing the access to the glues template of disease reports or disease events reported across various extent of areas, directly to countries. So you will have an access to the country border, the country extents with what has been developed by glues and based on the role and permission provided to users and the confidentiality of what they want to share. You will have the event filtered directly on the map. So in the past, the old fashioned of MAI were providing two types of setup. So you could deploy the DVO one flow or the DVO two flow. So based on this, you had three or four different type of user who could participate to the reporting process. So from this old fashioned way of doing, it was more linear and the information was shared only after validation of the event at a national level. So with a new flow of MAI, I mean you can still report the event in the same linear way. So following the surveillance system, but we have an extended set of user role and type of user. We propose up to three reporters from the fields. So following the DVO one and the DVO two ID, we have now up to three different people or group of people who can reports from the fields. We have up to two acceptance level as well as validation level. We propose as well a role of viewer and publisher to allow the user of other workspace and segment to share the information or view the information, for example, at a border level. So now it's important to understand what is a segment or a workspace. So actually it's two levels of grouping of the user that can allow a privacy and provide data sharing agreement amongst the user. So for example, if you are part of a district or a region, you want to know what is within your district or region, but you would also appreciate to know what is reported at the border of your administrative unit because you can also have access to some forming system or or or health that can cross the border and you want to know what is happening in the vicinity of your administrative unit. So you are not involved in the reporting process of the other administrative unit but but you are you are you can receive the the right of viewing the information after acceptance or validation. So so we propose this access at different level it can be from submission or from the acceptance or from the validation. So it's fully customizable. So it could be a segment based on the region or districts and a workspace, for example, based on the sector if you are working as a veterinary within the public sector or the private sector. You can deploy to separate workspace if you want to work on your own without sharing the information before acceptance for example, but you could also work all together in the same workspace. So this is something that we will need to discuss before to deploy the new system with countries. So this flexibility a little better control on the visibility the data sharing agreements and the surveillance across the sectors. So any request from from the country can be customized and and we already have five different scenario available. And more can be deployed or customized based on the country request. The role and permission are very important to know before to deploy the new new system, because it will be the core of the structure of what you can, you can see what you can access, and not only what you can report. So each segment can can have up to seven type of user from now. So user can report in a specific segment and be informed about what is happening in the surrounding areas, meaning that you can also have some surveillance system between wildlife and and and the public veterinary sectors with an easier way of deployment. So here an example of of Ghana and the surveillance system already deployed you can see that we can propose for example to have the three type of reporter from the community level to the regional level. We can for example propose to have to to acceptance level and to validation level to to remain flexible and follow the structure of the surveillance system. And we could also propose the viewer role after acceptance or validation based on the interest of the stakeholder, which also involved in the surveillance process. So I was explaining that we already have five different type of scenario already known and that we can propose in a in a very fast way, but more can be also discussed. We already deployed three type of scenario, but more or less all of the different scenario deployed or using the two different layers of workspace and segments. I will now start with more visual presentation about how and precise looks like and also how the workflow is working with with short video. So we have an administrative and administration section that we can also propose to deploy at country level. So for now, doing it ourselves from a quarter. So we propose the setup we define the workspace segment and we enter the user in the system. But we can also share the admin, the admin role with a master user at country level, who can also handle himself or by himself the user role and the and the permission attached to each of the user segment and workspace. Here for example, you can see that we have a country or from a quarter we manage many workspace and some workspace or segmented but on a regional subdivision. And we can also provide the user role to a specific user for his access to more than one segment. So we have two type of environment within the impress private platform so there is a training mode and the official modes. So based on this you can also manage the user the user and enrolled in the surveillance system. They're already enrolled in the in the reporting flow or if you are starting cascade training of MAI, you can manage the user and you can handle them from the same platform based on the their evolution using this training mode. When they are ready to start reporting they master the use of MAI and impress a they can be directly migrated to the official version. So we have here for example in red the emergency reports in white it was routine reports and you can also have this bubble on the right of the screenshots, which is the the color code for the segmentation that you applied in the workspace. So MAI is is shared by your notification so you are invited to to be enrolled in the in the use of MAI and impress I through a notification email from which you can access directly to impress I an MAI and you can download MAI and you can access to the URL of impress I to start using it. And now I want I would like to demonstrate you a use case. So we decided to to set up an environment from which we have three separate workspace applied in three different countries. So we have three other more segmented, but we provided the access to some of the user in some segments to the workspace of another country, because they would like to deploy a surveillance system or for example, for example, and there is a risk of importation of alien influenza in another country, bas on commercial activities, for example, or bas on the travel of my migratory birds. And so I have 10 short videos showing the the process of reporting an event in to go that will be shared with some users in in Ghana and and and Gambia. So here the video of a reporter reporting from the fields and sending an event. So you can directly access to to MAI, you can log in using your, your, your credential. Here it's a training mode because we are not reporting a real events, and we access to the site, the workspace of to go and the segment from which the event is reported. And the user will open a form and enter the information from an application which is customized so you have the emergency report and has done in the past you can just enter the information from the diagnosis source you can provide some comments. You can provide the locality name, the latitude and longitude will be modified to be reported from a location in in to go for the reporter provides the onset state and the observation dates as well as the relevant information on the suspected source of infection. And then the surveillance system that's reported events. So we are also here having another functionality which is the sets button. So when you enter the information. It's a bit fast but when you enter an information you can also set the default value to zero or in a based on the knowledge that you have from the field if it's a true zero or if you don't have the information you can now provide this distinction. The sample is taken on the chicken which is suspected of being infected of Newcastle by Newcastle disease and the event is sent as usual. So when the event is properly sent you receive a notification and you can access to the folder which is called sent events from which you can view the event overview of the events. The, sorry, starting again. So from the moment the event is is is sent. The user will receive a notification in directly in this in his email address with an action notification so here is a submission of an event. There is no direct comment other than the event is submitted and you will see that this email will be slightly modified across the validation process. So from the email at acceptance level and acceptor can provide comment to the hierarchy so directly another acceptor or a validator if the event is accepted, but you can also return an event to the reporter and request for additional information. So now we are on the process of reviewing of the events so it's the first level of acceptance remember that we we set the the environment with two level of acceptance. So one is the common acceptor and the other one is is from the laboratory units. So here the first acceptor access to the information directly on his mobile application but you can also do it directly from him preside. He review the event and when he's ready and and want to accept the information. He provide a comment and can also accept the event. So the two process are available you can accept the event or you can return the event to the reporter. So after acceptance, the reporter who reported the event and the acceptor who accepted the event as well as the laboratory unit will receive the notification saying that the event is accepted. It's pending for from the for the acceptance at the laboratory unit so the confirmation of the case with with the results from the laboratory. So here the user from the lab is is logged on and preside. And he has access to the event directly in the section in which the event is pending for for acceptance. He reviewed the information and he will he will provide the the results of the the test made at the laboratory level. So he can directly access to the laboratory form and provide the type of test so it's a false false even so the information is not correct but he provide the test type. The results and he can also provide a comment saying that the event is accepted for example. So at this step, the the validation level will be aware of the acceptance of this event with the lab the the confirmation from the the laboratory units with a notification. And the the validator can can this can then access to the to the platform and implement the validation process as well. So we can log into the platform access to the workspace in which the event has been reported. And he can go directly to the accepted section. So here are connected all the info are gathered all the information, the reports, which are pending for validation. Yeah, I think the video is just repeated so so the validate the validator is just accessing the information they can validate. And then the notification will be shared at national level with all the user of the application in enrolled in the segment and in the workspace if we are sharing the information at the broader scale. So you can access to the notification in your mailbox and you can review the comment and and and be aware about the event. So you can at any moment also access to the event near me functionality from which you will see what has been reported within your workspace segment but also in the location in which you have the access rights about a specific disease for example. So based on this, the dashboard available in MAI and then precise will grow and you will, you will receive the, the, the aggregation of the information for, for example, here the number of event per month in a specific workspace and segments, based on the status of the report if it's pending for acceptance if it's returned accepted or validated. You can also decide to visualize only validated even for example, you can also see the number of reports per disease. So the type of disease reported in a specific workspace and segments. You have an overview of the percentage of events based on the type of event if it's multi hosts, for example, or the which type of animal had been affected by the events. You can access to some maps on the density of reports in a specific location and you have the percentage of events which which are confirmed or suspected or denied in specific workspace and segment as well.