LIMS for Sample Testing

Use Labii as LIMS to manage the workflow associated with sample testing. With it, you can collect samples, conduct sample testing, document the results, and generate reports.

Overview

LIMS for Sample Testing is a Labii application for laboratories that process customer or project samples and need complete traceability from intake through final reporting. It combines sample lifecycle tracking, testing execution, inventory usage, ELN documentation, and report generation in one standardized workflow.

This application is designed for testing laboratories, core facilities, quality teams, and contract testing groups that need reliable audit trails, consistent data capture, and reproducible reporting.

Use this public application template to quickly deploy a production-ready structure with preconfigured tables, then adapt fields, steps, and permissions to match your SOPs and regulatory requirements. Learn more on the LIMS for Sample Testing product page.

Included Tables

The application installs the following tables:

• pj_project

• testing_plan

• testing_method

• sample

• testing_result

• core_receiving

• core_consumption

• core_container

• eln_protocol

• eln_experiment

• core_report

These tables support end-to-end sample testing workflows, including project planning, sample receiving, method execution, experiment documentation, inventory consumption, and final report issuance.

Use Cases

Contract Sample Testing

• Register customer testing requests and link them to projects.

• Track received samples, storage containers, and chain-of-custody records.

• Record method-specific test outputs and issue customer-ready reports.

Internal QA or QC Testing

• Execute standardized testing plans across repeated sample batches.

• Capture structured results for trending and quality review.

• Keep complete audit trails for compliance and inspections.

Core Facility Service Operations

• Coordinate intake, testing queues, and experiment execution.

• Track reagent and consumable usage for cost and traceability.

• Deliver consistent reports across multiple service types.

Getting Started

1

Install LIMS for Sample Testing from Settings -> Applications -> Add application -> Add from a template.

2

Confirm the application tables were created and visible to your team.

3

Set permissions for intake, testing, review, and report-release roles.

4

Configure your core references:

• testing plans

• testing methods

• report templates

• sample/container conventions

5

Optionally install companion applications such as CRM and ELN to support customer/account records and deeper protocol documentation.

Core Workflow: Intake and Sample Receiving

Objective: capture incoming testing requests and register samples with full traceability.

1

Create or confirm the related project/request record in pj_project.

2

Register incoming samples in sample with identifiers, source metadata, and requested tests.

3

Log receiving details in core_receiving, including condition checks and receipt timestamps.

4

Assign storage or handling containers in core_container.

5

Verify that each sample is linked to the correct project and testing plan.

Expected outcome: each sample is uniquely tracked from arrival, with complete receiving and storage context.

Core Workflow: Plan and Execute Testing

Objective: run standardized methods and capture reproducible testing records.

1

Define or select a testing plan in testing_plan.

2

Map applicable methods in testing_method to each sample or sample group.

3

Execute procedures and record lab notes in eln_protocol and eln_experiment as needed.

4

Log outputs and metrics in testing_result.

5

Track reagent and material use in core_consumption for cost and traceability.

Expected outcome: all methods, observations, and measured outputs are captured in structured and auditable records.

Core Workflow: Review and Reporting

Objective: validate results and publish final reports.

1

Review testing_result records for completeness and quality checks.

2

Resolve exceptions or repeat tests when criteria are not met.

3

Generate reports in core_report using approved report structure and language.

4

Release final reports to stakeholders and archive supporting records.

Expected outcome: stakeholders receive consistent, review-ready reports backed by traceable source data.

Advanced Features

Workflow Standardization with Plans and Methods

Use testing_plan and testing_method to enforce consistent execution across teams and reduce variation between runs.

This is especially useful for GLP/GMP-aligned operations where repeatability and documentation quality are critical.

ELN + LIMS Hybrid Documentation

Capture formal protocol context in eln_protocol and run-level notes in eln_experiment while still maintaining structured LIMS records.

This hybrid approach improves scientific context without sacrificing structured reporting.

Inventory and Cost Traceability

Use core_consumption and core_container to connect test outcomes with materials and storage records.

If consumption data is missing, cost analysis and full chain-of-custody investigations may be incomplete.

Troubleshooting

Issue: Samples are received but not visible in testing queues

Symptoms: sample records exist, but testing teams cannot find them in execution views.

1

Check that the sample is linked to the intended project and testing plan.

2

Verify role permissions for the testing team on relevant tables.

3

Confirm required fields for queue filters are populated.

Issue: Report output is missing required sections

Symptoms: generated reports omit expected result blocks or metadata.

1

Review required fields in testing_result and ensure they are completed.

2

Validate the report template configuration in core_report.

3

Re-run report generation after correcting missing data.

Issue: Consumption records do not match completed tests

Symptoms: completed experiments show no or partial material usage logs.

1

Check whether core_consumption entries are required by your workflow form.

2

Confirm operators have edit permission on consumption records.

3

Add validation rules to prevent test completion without required consumption entries.