ARuvosProduct

Run the whole sequencing workflowin one system.

WellGS covers the work a bioinformatics lab does between a sample arriving and a result going out: accessioning, plate maps, sample sheets, instrument runs, analysis, and reporting. You prep the run in WellGS, send the analysis to AWS HealthOmics, and the results land back on the sample record.

The Problem

One sequencing run gets tracked across Excel, Access, and a separate sample sheet for every instrument.

The path from sample to result is held together by hand: plates are laid out in Excel, extraction logs live in an Access database, and sample sheets are reformatted for each instrument. Analysis runs on a high-performance computing cluster, and the results come back somewhere other than the sample record.

Spreadsheet Plates

Plate maps are built by dragging rows in Excel, where the index moves with the row and nothing flags the break.

Scattered Logs

DNA extraction logs sit in an Access database, apart from the accession record they belong to.

Per-Instrument Rework

The same plate is reformatted by hand into a different sample sheet for every sequencer on the bench.

Disconnected Results

Analysis finishes where it runs and stops there, so someone re-keys the results, re-attaches the files, and re-checks the mapping by hand.

The Cost

The hard part should be the real science.

Each handoff is a chance to lose traceability or to silently break the mapping between a sample and its data. The work still gets done, but it costs the lab attention that should be going to the science.

How WellGS Works

Every run follows the same five steps.

You prep the run, sequence it, send the FASTQs for analysis, and get the results back on the same record you started from. Reporting goes out from there, so nobody has to leave WellGS to finish a run.

01

Prep

You accession the sample, build the plate map, and generate the sample sheet for the instrument.

02

Sequencing

The lab runs the sequencer, and the FASTQ files come back into WellGS from the instrument.

03

Analysis

WellGS stages the run and sends those FASTQs to AWS HealthOmics, where the pipeline runs on high-performance compute.

04

Results

The output comes back into WellGS, tied to the sample by accession.

05

Reporting

WellGS reshapes the result for ELR, PulseNet, or an NCBI submission and sends it on their schedule.

Compute

Analysis runs on AWS HealthOmics.

Lab-facing system of record

WellGS

Accessioning, sample tracking, plate maps, sample sheets, and LIMS integration all live here, which is where the lab actually works.

Optional

Easy Genomics and similar launchers

A launcher is a thin front end that turns a staged run into an AWS HealthOmics job. WellGS integrates with Easy Genomics, and runs just as well without a launcher at all.

Where analysis runs

AWS HealthOmics

This is where the analysis actually runs, on high-performance compute, whichever route a run takes to get there.

We build on AWS HealthOmics and integrate with its launcher, Easy Genomics. We can also tailor WellGS to the workflow a lab already wants, so no single external tool’s interface dictates how the lab works.
Plate Maps

Build the plate the way the run needs it.

Putting samples onto a 96-well plate is a decision someone makes by hand, usually in a spreadsheet. In a spreadsheet, dragging a row takes the index with it, and nothing tells you the mapping just broke.

  • Drag any sample to any well, and lay the plate out however the run needs it.
  • Multi-select to move a whole block at once rather than well by well.
  • Drop a sample onto an occupied well and the two swap, so nothing gets overwritten.
  • The index stays tied to the well rather than the sample, so rearranging does not break the mapping.
  • Export the CSV and the printable layout your lab already asks for.

You can rearrange a plate without silently ruining it.

Plate PLT-2024-0812 · 96 wells
QC passQC flagempty
Results

Results land back on the sample record.

A launcher shows you the status of a job, not the state of your lab. Analysis output comes back into WellGS instead, tied to the sample by accession and carrying a validation receipt, a file manifest, and presigned downloads, so your team never has to learn another tool to find it.

Your people stay next to the record they already trust. Each returned file has somewhere it belongs, and WellGS routes it there: receipts to the lab record or LIMS, operational logs to your cloud console, and scientific artifacts to the review tools built for them.

The result ends up on the same record the sample started on.

Sample FL-2024-008812Results returned
Date chain
Collection08-12
Lab receipt08-14
Mol. receipt08-15
Extraction08-19
Result08-24
Artifacts
  • FL-2024-008812_R1.fastq.gzsequence
  • multiqc_report.htmlQC
  • assembly.contigs.fastapipeline output
  • handoff-summary.jsonreceipt

run 20240824110543 · nf-core/bacass · presigned downloads

Where WellGS Came From

WellGS was built with a working public health molecular lab.

Accessioning sits in the data model itself, so it behaves like part of the record rather than an add-on. WellGS replaces the Access database that DNA extraction logs live in today.

It integrates with LabWare LIMS to meet the lab where its data already is, supports multiple instruments because that lab needed it to, and runs inside the lab’s own AWS account.

LIMS integration

Pull data straight from where the lab's data already lives.

Sequencers

NextSeq, MiSeq, and iSeq sample sheets from one plate map. More sequencer integrations coming soon.

Your cloud or ours

Runs in the lab's own AWS account, or hosted by us.

Walk us through one of your runs.

Bring a real workflow, from accessioning through the report you owe, and we will show you which handoffs WellGS removes.

Prefer email? hello@ruvos.com