> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/applications/laboratory-information-management-system.md). # Laboratory Information Management System Integrated LIMS applications for managing laboratory operations, sample workflows, and testing pipelines with structured, traceable records. ## Overview Laboratory Information Management System (LIMS) applications in Labii provide structured tools to manage laboratory data, operational workflows, and sample lifecycle records in one connected environment. This category supports teams that need reliable traceability from intake through processing, analysis, and reporting across research and service workflows. The included applications are designed for high data integrity, repeatability, and collaboration in both ELN and LIMS contexts. Whether your lab runs sequencing pipelines or customer-facing testing services, these applications help standardize execution and improve operational visibility. ## Applications * [LIMS for NGS](/applications/laboratory-information-management-system/lims-for-ngs.md) - Manage end-to-end NGS workflows from sample receipt to FASTQ outputs * [LIMS for Sample Testing](/applications/laboratory-information-management-system/lims-for-sample-testing.md) - Track customer testing services from order intake to final reporting --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.labii.com/applications/laboratory-information-management-system.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.