Skip to content
LAB ACCREDITEDISO 17025 Compliant Bio-testing & Metagenomic Workflows — Preclinical Phase Queues Open Q2Review Protocol Standards →

Research update

Planning a metagenomic submission

What to agree before transfer: read depth, controls, metadata fields, and how de-identified files should be packaged.

Research methods

Scope before the first gigabyte moves

Metagenomic projects stall when read depth, controls, and metadata conventions are agreed only after transfer. CERA scopes these items in writing so bioinformatics time is not spent reconciling incompatible sample sheets.

  • Target depth and library type (16S, ITS, shotgun) aligned to the research question
  • Positive and negative controls named in the sample manifest
  • De-identified sample codes with no participant names in filenames or free text

Packaging and transfer

FASTQ or BAM bundles are accompanied by a machine-readable sample sheet and checksum manifest. Large transfers use encrypted channels agreed in the project contract; public links without access control are discouraged for research material.

Summary

Agree read depth, controls, and metadata before any large transfer.

Package de-identified FASTQ or BAM files with a sample sheet that uses study codes, not participant names.

CERA Medical confirms scope, timeline and deliverables in writing before analysis begins.