This is a test version of Biostars. For the public version, visit https://www.biostars.org.
Forum: Building an open-source LIMS project to better understand lab and bioinformatics workflows

Hi everyone,

I’m a software engineer with experience building internal tools, APIs, Django/React applications, and bioinformatics-related web platforms. I’ve been working on a personal open-source project called OpenLIMS to better understand how lab software, sample tracking, and bioinformatics workflows can be modeled in a modern web application.

The project is still early and is not intended for regulated production use yet. My goal right now is mainly educational: to build a practical LIMS-style system that demonstrates common concepts such as sample management, inventory tracking, audit/event logs, configurable fields, file attachments, and Docker-based local deployment.

Current stack:

  • Django / Django REST Framework
  • React
  • PostgreSQL
  • Redis
  • Docker Compose
  • GitHub Actions CI

Current features include:

  • Sample management
  • Inventory locations and containers
  • Custom fields for different sample workflows
  • Event/audit logging
  • Sample file attachments
  • Basic reports and system status pages
  • Local setup with Docker Compose

I’m trying to learn more about what workflows are most important from a bioinformatics or lab informatics perspective.

For people who have worked with LIMS, sample tracking, sequencing workflows, clinical/research labs, or lab automation:

  • What LIMS concepts should a project like this model first?
  • What are common pain points when moving from spreadsheets to a LIMS?
  • What sample metadata is usually important to track?
  • Where do LIMS systems usually need to integrate with bioinformatics pipelines?
  • What would make a small open-source LIMS project useful as a learning tool?

I’m not trying to present this as a finished or validated system. I’m mainly interested in understanding the domain better and making the project useful for learning, demos, and possibly future contributors.

GitHub: https://github.com/Mokey2002/OpenLIMS

Thanks — I’d appreciate any advice from people who have worked around lab data, LIMS, sequencing, or bioinformatics workflows.

software python lims

Since you asked for general opinion about LIMS projects:

LIMS is a thing that everyone in a lab wants but they never seems to get right (unless they have a ton of money/resources/time available, which is a different story).

Fundamental reason is existing labs already have processes in place (unless one is starting a new lab) that they hate to change. Off the shelf LIMS solutions rarely fit existing processes. In order to model the processes in the LIMS software requires significant rewrites/changes, which a developer does not like or has time to support (especially if they are working on an open-source product). If a developer does want to make an effort, there is a lot of iterative back and forth that happens as people start using the system and start getting ideas about how the software can be changed to make their life easy. Unless requirements can be nailed down in advance that inevitably leads to "features creep".

Thank you, this is really helpful feedback. I agree that one of the hardest parts of building a useful LIMS is that every lab already has its own workflows, terminology, and processes in place.

That is a big reason why I’m trying to make OpenLIMS configurable and user-friendly rather than forcing every lab into one fixed workflow. Features like custom fields, configurable sample/project metadata, audit events, imports, and flexible statuses are meant to make it easier for labs to adapt the system around their existing process instead of completely changing how they work.

I’m also very open to working directly with labs that want to try it, helping them adapt OpenLIMS to their workflows, and learning from that feedback as the project grows.

1 answer

Why not have a look at other LIMS systems like

Log in to answer this question.