THE AVENTURA STORY
Aventura was born in a hospital IT department that completed a desktop virtualization project, only to see nurses and doctors run the other way. Struggling to find the answer, the team realized they had two major problems. One was speed. When you log on fifty to a hundred times a day, the waiting isn’t an annoyance, it’s a back breaker. The second was that they were giving static desktops to people who were constantly in motion. This meant lots of extra keystrokes. They realized that if you’re trying to win the hearts and minds of clinicians, giving them lots of dunce work is not going to win you any prizes.
So the team that started the work that became Aventura realized that they had started at the wrong end of the problem. First, they needed to understand how nurses and doctors actually work. So they followed them around for months, carefully observing what they did, how they worked with each other, and with patients and computers. They noted the choreography when the work was really flowing. They noted the interruptions, the wasted motions, the waiting and the tension, when it wasn’t.
Once they understood how the whole system had to work for the people who delivered the care, they were ready to start building. And what they built was a universal architecture that reaches into all the layers–OS, virtual desktops, applications, policy, printers–so all these static components can act like they’re one step ahead of your doctors and nurses.
As far as we can tell, we’re the only people who have even come close to making this happen. We think a big part of it is where we started. While other companies are struggling to adapt products that weren’t designed for healthcare, we started in a hospital and we never got distracted. Where other companies have come up with one-off solutions to animate their own static software, our solution works with whatever you’ve got.
When you talk to us, it’s probably not a good idea to expect a normal conversation. Because you have to forget everything you know about desktops and clinicians, printing infrastructures, rules and policies and how they’re applied. We have an entirely new way to do this stuff that works now – and will keep working as you migrate your way to VDI.