 Live from Boston, Massachusetts, it's theCUBE, covering Red Hat Summit 2017, brought to you by Red Hat. Welcome back to theCUBE's coverage of the Red Hat Summit here in Boston, Massachusetts. I'm your host, Rebecca Knight. We are joined by Andre Baumgart and Dorothy Rheinstraub of Swiss-based Easier AG. Easier AG is a Swiss-based emergency room management company. Dorothy, tell us about the idea where it started. I'm an MD and working in emergency rooms for several years now, and I thought it's annoying how people have to wait if they wanna be seen by a physician. And I thought if I'm able to make an appointment for a hairdresser or just reserve a seat in a movie, it should be able to make an appointment for a physician, even in an emergency. And that's why I came up with the idea. It's like checking in in a hotel. It's so easily done on your phone. And I shared my ideas with my partners, Andrea and Kai, and they thought it's something worthwhile to pursue. That's how it came along. So your physicians, and you saw a problem from the doctor side, from the provider side? Actually, I saw the problem from the patient side cause I'm trying to think for a patient. And I'm more relaxed if I have a problem myself. I'm more relaxed if I can sit at home and wait for an appointment, or if I know that one of the physician will see me today instead of trying to get there and just be sitting around an emergency room and waiting area. And what about the provider side, though? What is that like for you too, as a physician trying to make sure you're seeing the all the patients that need you? I think one of the good thing about this app is as well I can schedule my day. I can tell my employees what they will be expecting, what kind of patients I can trigger or schedule the workload as well. And you can keep in touch with your patients, and I think that's a very important thing to be in touch with your patients and your employees. That's one thing too. So that was the problem you were trying to solve. So tell me, after she shared this idea with you, so then where did you go next? What was the next process and the next step of the process? After we discussed what to do with it and we sell it internally to the hospital's management, but unfortunately due to budgets and due to other projects strategically, they decided not to do it. And then we said, hey, it's such a great idea to have a booking.com-like emergency room scheduling system that we should follow this and should do it. And then we said, okay, let's start our own thing. And we discussed with whom you could do it. And we found Keir as a perfect partner and we said, okay, let's do it together. And so the company started, essentially. And that was the foundation of EZRAT then, yeah. And then, and as you said, you couldn't find necessarily the money, the backing at first. So then you said, where do we go? Where do we really now take this to the next level? And how did you get involved with Red Hat? I know Red Hat for quite some time through the open source community. I myself did development in the Chabos community. So I know Red Hat quite well for several years. And I know that the stack and the technologies they used evolved over time. And now with the announcement of these self-service open shift platforms, this was actually, or is a revolution for the technology side. And then I saw last year the Innovation Lab announcement. And I... The light bulb went off. Right, and then I said, actually we tried for several months to find a partner that could support us in a very structured and modern way. And then I said, okay, let's try this. I mean, they are a big company. Maybe we are too small for them. But I emailed the Innovation Lab people and I got feedback. And we met for a discovery session. And the people were so nice, so engaging, so challenging also that in the end we came up with the plan for this Innovation Lab. So share with us a little bit about those early days. As you said, they were challenging you. What kind of questions were they asking? Because that is the whole point is that they are trying to figure out what your minimum viable product could look like. So what kind of questions were they asking you? How were they pushing you forward? I think you have to answer that. Well, the discovery session is there to really validate that the solution is sound, that it has a market potential and that you have a potential to solve this within a short time in form of a minimal viable product. In order to show that this prototype really solves the problem. And Rathat has the technology then to scale this up to really market solution. And that was the struggle to really validate is this MVP able to do within this short time, eh? And then they challenge us as people, you know, are these guys really, can they do that? And can they market it in the end? Because I mean, doing it for fun might be nice for some time, but it's not really our goal. And that was the first challenges they made. Then we did conceptualize the user journey from a medic perspective and also from a user perspective, patient perspective. And then we found out, okay, this might make sense to do it in an innovation lab matter, okay? And this was really a very sound approach. We had half a day of a workshop and it was actually perfect to map our ideas, to map the criteria that you have for this approach and then we found together. So after the discovery process and persuading I guess the Rathat people that you are the right people, that you are in fact the right team to bring this product to fruition, how did it work? What were you actually doing at your time at the lab? We went to Waterford, Ireland for three days. Normally the innovation labs are I think three or four weeks so that was really a special for us. We went there, Andre, me, we had three developers of our own at the site and I think about 12 people from Rathat. I think the best ones that really could get us and we started early in the mornings. The whole day was scheduled. We built our case we wanted to do and you have to help me with the right words. Yeah, we did essentially what is called an event storming. Event storming is what happens. What is really the app doing step by step in terms of a user experience from the patient and the hospital or the doctor side. And then this event storming leads to a big board of what is happening as a process and you do that iteratively four or five times during one or two days in order to really engage all of the different levels of people from the developer to the business owner and as well as from the Rathat side as from our side of developers. So everybody's engaged in this process and this is I think the innovative idea that you do not have a waterfall like. Some people sit together and do it and then you hand it over to the developers. You bring them together and you discuss it and make the case their own thing. And then they are fully engaged in realizing the product and that was really the innovative part. When you told me that we are going to be at the innovation lab I thought why me? What shall I be doing there? They're all tech guys. I don't understand the word you're saying that's nothing really for me. And but I really saw it through quite fast cause it really makes sense that business partners or the person who has the idea in head is there cause you can really interfere very well and very fast and to get to the point what it's needed. And it was really it made sense to be there the whole time. It is very important that because you could see that sometimes the ideas were flowing apart from the original business idea and that we were all people in the room together. You could ultimately control in every direction where this is heading. And so we had a really intensive two days in order to figure out how this event and system really should work as part of the innovation lab and then as a product for the MVP. Well that is so much of what we're talking about here at Red Hat. It's not just the tech. It's also how do people get into a room and get work done together and solve the problem that they're setting out to solve. And I think that you were talking about how you were in the room thinking why am I here? But in fact you are representing the user from both the patient perspective understanding what it's like to be in an emergency room and also the doctor perspective. So how would you sort of bring it back and say hey, remember what we're doing here. Remember the problem which we set out to solve. Most of the time I listened. But then when I thought no, that's not going in the direction I want it to be or we want it to be, I just stood there and my hands up and said no, we have to do it other way. Or I think that's not going to work or that's not the MVP. And they really, they understood us very fast and at the beginning it was fascinating to see the Red Hat people and our own developers. Everybody wanted to do it their style because they really are both very good. And it didn't take much time to combine them and they really worked as a team and everybody got one up step and it was nice to see and I think it wasn't a problem to tell them what we think we should be needed. And at the end, I think we even got more than we discussed as an MVP after the three days. Okay, so three days you have the MVP, where do we stand now with the easier AG? We have an MVP after three days in Waterford. We figured out what to implement in sprints and then after four or six weeks we came out with the MVP. That is essentially an app on a smart device for the doctor as well as the patient. And this is now working as we presented yesterday in the keynote. And this is really a valid product as it is and this can be applied now to healthcare trust or institution. So if somebody wants to really use that, they can do it because it's really working on an open shift, red hat, innovative platform, right? And you can ultimately push the button and roll it out. I mean, this is really working. So and of course what we have to do is use of validation. So in terms of is the use experience really perceivable independently for the users? This is something user testing we are doing right now in order to make it really perfectly user friendly. And also for the nurse side and the doctor side that they can really use it easily. That's one of the most important things. And do you have, are you, it's using it at a hospital in Switzerland. Countries around the world have different approaches to healthcare, different approaches to the emergency room. How are you talking to other places about implementing this in other countries and other parts of the world? We all have the same problems in healthcare. It doesn't matter where you live or where you work. I think it's all the same, the same problems. And when you need emergency care, you need care. You want to be taken care of and you want to be there really fast and you don't want to repeat every time the same sentences and the same problems to four or five people. And so yeah, we're talking to health institutions at the moment in Switzerland and Germany, but we hope to get there out soon in other countries as well. And I think this summit has opened many doors and windows and we're looking forward to the future. Yeah, the process itself, that's the good thing, is totally independent of the context of our country. It is the problem in any country or every country of the world. So we have a common approach to that and the only thing that needs to be changed is maybe, is the hospital willing to accept that a certain automation takes place or not and it can be fully automated or it could be done manually, right? And this is the decision of the healthcare institution or the trust who wants to implement that. So we are flexible in that because of the technology of Reddit because they provided a container that is really flexible in implementation, right? And that's so great. Andre Dorothe, thank you so much for your time. This has been really a lot of fun learning about your company's journey. Thank you very much. Thank you so much for having us. I'm Rebecca Knight. Stay tuned for more from the Red Hat Summit.