 OpenMRS is essentially, well stands for the Open Medical Record System, and it's a project that's designed to create a platform for different kinds of healthcare environments and resource poor settings to build meaningful record systems in support of improved healthcare delivery and improved health outcomes. Me and one of my colleagues, a guy named Burke Mamlin, were asked to go to an environment in western Kenya called AmPath. It was a partnership between the university that I'm a part of Indiana University and the university that is in Kenya called Moi University. And they were in the midst of building up a care and treatment program around HIV. So I was actually asked to go, based upon my background in medical informatics, go look at the information system that they had put in place for a couple of thousand patients and fix it. I worked in the clinic one of the days that I was there and I kind of took a step back and thought, well, you know, why am I trying to optimize a good health system in the US when there are all of these environments in places like Kenya and throughout Africa that have no information infrastructure and need really kind of simple systems to make huge kind of improvements and impact. So I decided that it was going to be more than a week consulting. It was going to be something I wanted to do for my career. I didn't know at the time, but I just remember being really excited about trying to serve the underserved. I thought everyone that was interested in open numbera, so the people that were working in these very environments, people that were kind of eating what they cook. So it's a relevance to them because they're trying to solve the problem. But what I didn't realize is that people are inherently philanthropic with their time. And just because they don't know about medical record systems doesn't mean they don't want to help. And so our whole model kind of evolved into trying to bring the people who need modifications and changes and improvements in the code to the people who are engineering. And so we've started to really create kind of this collaborative community process where software gets created that meets end-users' needs. I mean, there were a couple of points in time when I really understood that what we were doing is open source. And I went and just tried to become a student of it. You know, I'm one of the probably hundreds of organizations that looks at a project like Linux and says, well, but they've done it right. Look at the scale that they've been able to bring. And so I read a lot about the different kind of kernel engineers and how they manage software development. So yeah, we've learned a ton. We're like the tiny stepchild of Linux in some ways because you all certainly have influenced a lot of the work that we've done. So I think we've gained a lot from all of the good work that you all have done and more importantly, the way in which you've described how it's done. I mean, I think it's the historical remnant of how things evolved that are really important to little small fledgling projects like ours. We realize that when countries make national level decisions to work with a platform like OpenMRS, we have a responsibility to create structures that are going to protect it long-term so they can be sustainable. And so we've created a not-for-profit organization that is to support the continued growth of the community. And we're looking really carefully now at the kinds of things that that not-for-profit organization can do to stimulate this ecosystem that I talked about. Taking a lead from the Linux Foundation and organizations like Linux Foundation, we're trying to kind of play catch-up and create the milieu in which lots of implementations can happen because there's an anticipation that that's necessary and countries are already starting to move forward for that but there's not necessarily the supportive construct that's fully in place to allow it to happen at scale. So we're putting a lot of energy into that now.