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.
CSV and PDF exports are available out of the box. Less common formats (XML, JSON, Yaml) can be made available through a custom project scope.
The QBench API or our Microsoft Power BI interface allows you to connect to your environment with no additional customization. If you require engineering support, that can be made available as part of a custom scope.
CSV is the most common however less common formats and integrations can always be discussed via custom project scope. For labs that use our API connector, JSON-based web requests are the norm.
Yes at the order, sample, and test level.
Yes, via the Billing module.
Yes, via the Inventory module.
QBench has the ability to store unstructured notes and responses with tests using a rich-text format. We also support a default template for that area so that your lab can pre-fill the section with prompts based on your business needs. 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.
QBench has a robust history tracking system to show an audit trail for all actions taken on orders, samples, tests and more. It shows who, when, and what was changed from and to.
As a cloud platform with the attitude of continuous improvement, we try to move quickly and be responsive to customer feedback.
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.
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, our out of the box report templates editor is 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.
Yes! We can support many types of charts and graphs.
Yes. Our API is available via RESTful, HL7, ASTM, RS-232, and TCP/IP interfaces. Our documentation can currently be found here: API Developer Documentation.
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, Google for user management, and Quickbooks for accounting and finance.
The lab equipment market is mature, wide, and diverse with many technologies in play. We have facilitated many methods of connection for equipment with our customers. If your piece of equipment is capable of exporting a results file, then you can leverage our File Parser engine to map information to a QBench worksheet. If your lab equipment does not support file export then we work with our customer to develop a custom scope of work to create a connection.
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).
QBench supports multi-factor authentication for both LIMS users and logins by your customers through our Customer Portal.
No (it can always be requested via Canny).
Records can be read-only or editable depending on the role of the logged in user.
QBench support for standard inquiries is available from 8-5 PST. Extended Support availability can be discussed as part of a custom agreement.
Our implementation managers work directly with your project 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.
With this comprehensive overview of the six key factors every lab must consider, you’ll know which LIMS features you need to streamline and scale your operations.