 Hello, everybody. Thank you, Alisson. Well, we're going to be talking today. This is not really a technical talk. We're actually kind of newcomers in the KDE event, but thanks to Alex Paul and the other friends who asked me to work on this framework. I decided to do the mobile application and desktop application on KDE and Kirigami. Let me start by saying what is GNU Health. GNU Health is first and foremost a social project with really, really cool technology, but our idea is to deliver social medicine, freedom and equity in healthcare all around the world. So that's our project. We started this project in 2008, so it's more than 12 years now that we're working with technology toward developing and delivering health no matter where you live, no matter how rich or poor you are. So just to give you an idea, GNU Health is an official GNU package. We relied everything on open technology and we pride ourselves to have a really nice friendly community for all these years. These are some of the environments where you will find new health and some of the tools and frameworks that we use. Operating System, PreBSD, GNU Linux, Databases, Postgres, SQL, mainly, both relational and document-oriented functionality. Programming language is not C++ in this case. We are actually using Python and we'll see later when we talk about the specific tool. Wikibooks for documentation, Triton for the ERP part, GNU BigG for encryption and Vue.js for the portal. There are way many more, but this is just a quick review of the most relevant tools. So GNU Health itself is an ecosystem. It basically tries to deal with this concept of public health and social medicine and collective health at the end of the day. So if we look at these four major areas and we start from the bottom, the very first part that we do in an implementation is work with those social determinants of health, all those things that will make you healthy or will make you sick. So we work with people before patients. We work before on demographics, on how you live, how you eat, where you live, etc. The second layer has to do more with the traditional doctor-patient relationship. That's the EHR, the Electronical Medical Record. That's where you do clinical history. That's where you make prescriptions, order lab tests, do hospitalizations, and so on. Now the third layer has to do with taking care of your health institution itself. That has to do with human resources, financial accounts, stock management, the lab itself, the lab information system, digital imaging, and all the things that have to do with dealing with your resources in your health institution itself. The very last one, to this point, had to do with making sense of all the data that has been collected through the three first layers that we just talked. The first three ones are more transactional type of components, and the very last one is more of an analytical statistics epidemiology and so on. So now we have these four big layers, and there is one more that had to do with the personal health record, and that's the thing that we will be talking today. That's where my Kinnu Health and Kittigami and all these really cool stuff will show up. Here you have the six main components of the ecosystem that makes Kinnu Health. The very first one is what we just talked, the health and hospital information system. But then we also have projects that deal with embedding Kinnu Health in, this is the CADAS, and we also have the Olimax here, and we have the Raspberry Pi images where we can actually embed Kinnu Health on these very small single board computers. They are very, very useful, not only in low resource settings, but you can actually do very good public health promotion campaigns by giving any of these computers to any household or any domiciliary units to be used with. My Kinnu Health, we will talk about it later. Then we have a LIMS, a Lab Information Management System. We also have a set of packages or modules that deal with bioinformatics, with genomics and clinical genetics, medical genetics. Finally, we have the concept of my Kinnu Health Federation. That's to be large or very large public health networks, distributed networks that we will also talk a little bit more about afterwards. This is just some snapshots where you can see different uses from histopathology to calendar system to some charts in growth charts for pediatrics, wristbands for new bones, digital imaging, population pyramid, really different. It's a set of functionalities, Kinnu Health is modular, so you can choose whatever packages you need to adapt to your health institution. This is just another example how we can also work with our Libre software projects like Orthanc for Pax and ICON, so we can actually import those studies into Kinnu Health in real time. But the reality is, and that was what took me or led me to write this ecosystem, this set of programs, because we live in a world of injustice. What do I mean by that is that as WHO said, nobody should get sick and die because they are poor or because they cannot access the health service they need. But reality is something completely different than what we wish. As we would see and as we see every single day, 20,000 children around the world die from social diseases. When I talk about social diseases, I talk about illnesses that can be prevented or those illnesses that strike the undernourished, the underprivileged, the poor. And we as a community have to make sure that we lower that number. We cannot have every single day a football stadium filled with dead children. So, some of those social diseases I have put them there are chagas disease, prostitution, human trafficking, domestic violence, HIV, AIDS, malaria. All of those are diseases that can be prevented and part of the Kinnu Health social medicine approach is work on this to minimize the impact of this type of burden. The other problem, of course, that we deal with every single day is the brutality and animal abuse that is not only extremely cruel, but it's also very bad, very bad for the environment and for your health. So, it would be great if we stop eating animals, just leave them alone and we will all be doing much better as a society. Now, going more into the technical things, one of the problems we deal today with our current health information system is that information resides in silos. So, I as a physician don't have the information in the Canary Islands from a patient that comes from Barcelona or from Madrid. Yes, we are from Spain, but each community has its own databases, their own set of software and so on. So, one of the things that we need to do is to break those silos. And that's where the federation comes in and the concept of collective freedom. Right, that's as we talk about social medicine as a collective health, we talk about libre software as collective freedom. We talk already about this. And yeah, we'll see this concept of collaboration based that we see pretty much every day in our libre software communities. So, this is what we need to do. So, if we want to break those silos, we'll set up this sort of federated distributed schema where you can be independent that all the epidemiology information can be seen in demographical information and clinical information at any time in any of those health institutions across your region, your country, or even if we talk about the European Union, right, that should be the way to go. And of course, and of course, use libre software makes no sense to have proprietary software in the public health system or actually in the public health administration in general. These are part of the things that are already doing new health. So, you can do real time observatory, for example, on the context of the COVID. Don't need to wait until Monday to collect all the data, you will have it, and that will prevent an outbreak to become an epidemic with the new health federation in place. And we also like to contextualize the information. So, we're not just talking about the molecular basis of the disease, but we are also taking in consideration all these socioeconomic determinants that will actually make a difference on your well-being and your health in general. Now, let's go to the part that you guys might be most interested in. That's the latest application, part of that ecosystem that we're seeing, that we should be able to release the beta on December. So, why do we do this? Well, we do this because we want the person to be in charge of that health. And that means empowering them to be part of the health system. That will make a huge difference. So, the main components are again for the development, Python. We are using PySci2, that's the queue for Python libraries, TinyDB to store the information, ADE and Kirigami to make it beautiful both on the desktop side, as in the pine phone, that's the mobile hardware we are using at this point to test. Yeah, here we have one. And matplotlib to do all the charting, UPG as in the main health and hospital information to encrypt and to sign documents or actions. These are some of the screenshots that are taken from the desktop itself. So, as you see, we have the bio-psycho-social components that might be always present in a person's well-being. And then if you click on the bio, it will take you to the, you know, in this case, we're dealing with things such as blood pressure or glucose level or your weight, anthropometrics, oxygen saturation. And then for each of these, you will have your history. And this is where matplotlib comes into. There are really cool libraries for charting in KDE. I just chose matplotlib because I knew it and I felt comfortable using it and it just plugged in very well, so it works, it was very well. And this is, this is not a screenshot, this is an actual picture of the pine phone running my GNU Health on KDE Neon. And again, it's the same, exactly the same environment that we use on the desktop. Hitigami makes it very, very easy to just port it to a hardware like the pine phone. So, when we were talking about the GNU Health Federation, and if we look on the left side, we will see that we have, in this case, it's made of notes, right? Always you will have notes and the note can be something very large like a hospital or can be something very personal as it would be the GNU Health, personal health record, right? The good thing about this, again, is it allows the person to be in contact, whether it's with your psychologist or your doctor or your nurse or your social services friends in real time, without the need to actually go to the health institution, especially in this context of the pandemics, it's really, really helpful. And of course, all that information can be actually sent to the Ministry of Health and the information will be there in real time. So, yeah, I mean, it's one of the reasons we use pine phone is partly because of privacy, we want to make sure that every single component of this personal health record it's private, it's secure, respect the privacy and it's Libre software and Libre hardware, right? We don't use Android, of course, you can compile it for Android, the same way that we don't use Microsoft Windows, but you can actually, it's Python at the end of the day, so you could compile the client for the GNU Health client. But I always work on Libre software and Libre hardware. I think that is also part of sending out the message of the importance of embracing both Libre software and Libre hardware in the public health care. I see Alison there, so I guess we are running out of time, Alison. But you have five minutes, but if you want to answer any Q&A, we can start doing that whenever you're ready. Oh, wonderful, so let me just, I will just, you will see the slides later, but these are some of the miscellaneous, so where is the development environment? Where can you download it? Where can you reach us? And things to do are like, you know, working on a good packaging, modeling, localization, of course, security and documentation. Very quickly, just show you some of the projects that we are around the world. These are from Clinique in the Rain forest to very large hospitals in India. We work with the organizations like WHO. We train them, we have trained them with the United Nations University. Countries like Jamaica has adopted the new health in the public health system, the Red Cross, Laos Ministry of Health too. We work with academia and research institutions on the new health alliance. And basically, that's all. So we have a couple of minutes now to talk about and to answer a couple of questions if you have. And then, of course, you can reach them. But don't forget that, you know, this is a, medicine is a social science and politics is nothing else but medicine on a large scale. So thank you very much. And I'm already for your questions if there is or there are any. Great. Okay. So we have two questions for you. The first one says, are there any plans or work on integrating medical devices and hardware to my GNU health? Anything from the MRI, CBCT, accusation or direct vital monitoring? In parentheses? Like, does the BP come directly from the cuff slash monitor? Right. That's that's one of the things we want to do with open hardware or or or Libre hardware. And actually, the guys that develop the pine phone are working now on the pine time, which is a smartwatch that is going to be integrated with new health and things like your heart rate and things like that. But we have to make sure that we deal with Libre hardware on the other side, but absolutely. I mean, that will reduce a lot of human error by typing. Yes, the answer is yes. All right. Next question. How does the GNU health ecosystem deal with GDPR slash hip hop regulations? Well, every country of every region has to do their own localization. Okay. So when it was installed in Argentina, they dealt with their own GDPR for for Argentina, or anything that has to do with the obvious data. HIPAA, it's for the United States. And that's something that whoever wants to use it in the United States in the public health, I mean, you can use it in your private consultation. That's no problem. But if you want to use it on your public health system, then you will have to go through the HIPAA certification. And if they want to pay for it and do it, I'll be very happy to. Okay. We have two more questions that maybe we can squeeze in. I'll start reading the next. Proprietary hardware is a highly embedded and unavoidable segment of the health ecosystem. Is an all Libre solution really a practical way or advancing the project's goals? Imperfect improvement being better than none at all? Yeah, I mean, we in a perfect world, we would love everything to be Libre. I am, I know that there are many pieces of hardware that are still non Libre. But as long as they can send information in a Libre protocol that new health can read it, then it's on our side to make sure that that information is kept safely and private. So we could actually interact and interface with them. Okay. Well, our last question is actually from a fellow Academy speaker who had his session yesterday. His name is Tess Shaw. And he is from Clear Dental. He asked, have you heard of Clear Dental, a project that we talked about yesterday? Yes, actually, I think that I saw those guys in the last Gino Health conference in Brussels, in Leish. But yes, I have heard about it. And I'm so happy that Clear Dental is actually using also this sort of similar development environment. And yeah, I mean, we should definitely join forces.