Use our native integrations and modern, robust REST API to interface with other systems, create custom automations, and do more with your data.
Yes, and to answer your next question, there are no computer requirements other than a modern browser.
In the majority of typical use cases, there are CSV and PDF exports available. Less common formats (XML, JSON, Yaml) can be made available through a custom project scope.
Either the QBench API or the Microsoft Power BI interface allow you to do this with no additional customization. If you require engineering support, that can be made available as part of a custom scope.
For typical use cases, CSV is the most common. For labs that choose to use the API, JSON-based web requests are the norm. Less common formats and integrations can alway be discussed via custom project scope.
Yes. Via the inventory module.
QBench has the ability to store unstructured notes and responses with tests using a rich-text format. While this does not count as a full-fledged Electronic Lab Notebook, a number of our customers find this to be sufficient.
As long as customers maintain an active license, all platform data is stored indefinitely. If a customer terminates a license, the data is kept for six months as a courtesy. As part of the downgrade process, we work with customers who may wish to migrate the data for purposes of storage or re-use.
All user actions are tracked with date, time, and operation. Users are monitored at the order, sample, and test level. Every login is tracked as well.
Customer Portal Version II is a modernized, stand-alone tech stack, apart from the QBench platform. This allows for more rapid development and better design for customer facing operations. We have customers using both portals, but we are actively encouraging migration to Version II, where all future enhancements will be made.
Custom scope is always an option for mission critical functionality. For everything else (and even for mission critical functionality), we encourage labs to add issues and vote for their favorites via Canny, which is our customer feedback engine.
As a cloud platform with the attitude of continuous improvement, we’re able to move quick and be responsive to customer feedback.
QC data is typically managed with batch worksheets in conjunction with our Controls and Control Groups Modules, which can create a Levy-Jennings Chart and help filter data by equipment, inventory stock, and batches.
We would treat this as a custom scope of work and also a custom contract.
Yes, the no-code report templates are the best way to get your reports together in a quick, consistent, and self-service manner. We list one of the main limitations in the next question.
Unfortunately, charts and graphs are not supported in the user-friendly (no-code) editor. Support for charts and graphs is a fairly typical custom project scope.
Yes. Our API is available via RESTful, HL7, ASTM, RS-232, and TCP/IP interfaces.
We have a Postman collection that you can use against your sandbox instance. This will be distributed upon your subscription commencement.
The most up-to-date list is available here on our integrations page. It includes Microsoft Power BI for business intelligence, Hubspot for customer communication, Google for user management, and Quickbooks for accounting and finance.
This is a custom scope of work, due to the diverse market of lab equipment.
Much like lab equipment, there are many options in this market. We will keep an eye on Canny for obvious favorites from our customers. That may provide the launching point for an out-of-the-box integration.
QBench’s consistent and predictable approach to tests and data flows are an on ramp to compliance for a number of labs that have fewer checks and controls in place prior to adopting a LIMS like QBench.
For the purposes of ISO 9001, QBench comes ready with a Quality Management System to be used in accordance with the core LIMS platform.
Yes, we have white papers on how we help labs comply with 21 CFR Part 11 as well as 40 CFR Part 160. These can be made available upon request from your account representative.
No. Our AWS servers are located entirely in the US-EAST-1 region, which is primarily northern Virginia and some surrounding areas.
Yes. Specifically Google, Okta, and Azure (future options can be requested via Canny).
No (it can always be requested via Canny).
The same. Records can be read-only or editable depending on the determination of the lab team.
9-5 PST is the default window. A custom window can be made available upon request. All of our support channels allow for asynchronous communication, so the longest wait would be 16 hours during the week.
Our implementation managers will work directly with your team and train anyone within your lab that plans to train others. Additionally, we have a growing library of evergreen content that will allow you to learn more about the system at a pace that works for your organization.