How QLIMS is Revolutionizing Your Laboratory: Interview with Jonathan from OnQ Software – PART 2
OnQ Software has a special interview with Jonathan Gannoulis that focuses on the journey to releasing the QLIMS platform. In part one, we got an inside look at the introduction, initial stages, and journey that led to the creation of QLIMS.
In part two, we will dive into how OnQ Software translated its principles into a product, resulting in a LIMS system that revolutionizes laboratory management.
Translating Principles Into a Product
Interviewer: I think we now understand why you are doing this. Now please tell us more about your product and the solution itself. How are you translating this into the new product?
Jonathan: We offer LIMS as a Platform, not just an app. Laboratories are moving towards a suite or platform of informatics, not just LIMS.
LIMS, data management and automation is the starting point. We base our entire application on our API technology. QLIMS is a containerized application that allows us to safely put things in little containers, pull apart and add elements or swap out and bring in other elements. The flexibility turns our application into a solution you can now lay over a platform to address complex scientific challenges as our customers’ needs evolve.
Interviewer: Just to clarify for our audience, an API is typically an application programming interface. Is your API what this is, and could you please explain what your API is?
Jonathan: It stands for an application programming interface. It is fundamentally a safe and secure toolkit that lets QLIMS talk to other applications. Our difference is that we built the whole application on this API, so there’s no real restriction to what you can do with QLIMS. Users can access it themselves and build web extensions, for example, mobile tools and integration. People are genuinely empowered to take the LIMS where they want it to be.
Importance of Independent Configuration
Interviewer: When scientists approach you with complex problems, they know they can solve them with your API-based architecture. They know they have a flexible toolbox to solve these problems. Whereas with other more rigid applications, it would be more challenging, right?
Jonathan: Yes. Even small changes are classified as customisation, so you need to change the code of the core application, which in turn creates more overheads. Not only does our solution have the API described, but we’ve also brought into our solution powerful configuration tools. This ability alone reduces the level of customization effort required close to zero depending on your specific needs. People working in the lab configure the system to suit what they want to do and then manage the system independently on an ongoing basis. Without hiring extra staff for LIMS admin. Without needing a coding degree.
We have the platform to empower every scientist. Less admin work and focus on the science, the important work.
Interviewer: I think I’m starting to see a better picture of the situation you are describing. It seems that the customization piece itself has also been part of why the industry has not evolved into offering more self-enabling systems. Suppose billable consultant hours are part of the business model. In that case, vendors have very little incentive to design a system that allows customers to customize independently.
Jonathan: Pretty much, we are a technology company, not a professional services company. This focus makes a difference to the end solution. We have the platform to empower every scientist. Less admin work and focus on the science, the important work.
Get in touch with us today to learn more about how QLIMS can help you achieve your goals.
