Why Science? | proBAM and Genome-Mapped Proteomics Evidence

Science learning becomes powerful when students can tell a measured pattern from a model, a statistical decision from a mechanism, and a useful lead from a finished conclusion. proBAM 1.0 is a HUPO-PSI proteogenomics format for storing peptide-spectrum matches in genomic context. The official page says it builds on SAM and compressed BAM while adding proteomics information such as PSM scores and confidence, charge states and peptide-level modifications. It can connect mass-spectrometry identification results with genome coordinates for analysis and visualisation. A mapped peptide is reference- and annotation-dependent; proBAM does not by itself prove a novel coding region, genomic variant, transcript structure or biological function. This guide supports Primary Science, PSLE Science, Secondary Science, O-Level Science and STEM education as a longform evidence-reading route; it is not medical advice, a laboratory protocol, an admission promise or a career guarantee.

Related eduKate reading: SAM and human-readable sequence alignments; BAM and binary sequence alignment storage; mzIdentML and proteomics identification results; ProteomeXchange and public proteomics data; Science Learning Hub; Education Hub; STEM Education; Careers by Subject Capability.

Primary and official sources checked on 12 October 2026: HUPO-PSI official proBAM 1.0.0 page, specification and examples, checked 12 October 2026; Peer-reviewed HUPO-PSI proBAM and proBed standard article, Genome Biology 2018, checked 12 October 2026; Official SAM/BAM specification repository, checked 12 October 2026; 2026 Singapore–Cambridge O-Level Biology syllabus; MOE G2/G3 Lower Secondary Science teaching and learning syllabus; 2026 MOE G2 Computing syllabus. Specifications, drafts, vocabularies, tools and recommendations can change, so preserve dated documentation, exact source data and software versions.

A deeper reading route

Proteogenomics asks how peptide evidence relates to genomes and transcripts. A peptide-spectrum match begins in mass spectrometry, often as a result in mzIdentML or mzTab. To view it beside genes, variants and RNA alignments, software must map the peptide through a protein or translated sequence to genomic coordinates. proBAM packages that result in an alignment-style structure familiar to genomics tools.

The official PSI page identifies proBAM version 1.0.0 and explains that it is built upon SAM and BAM with additions for PSM scores, confidence, charge and modifications. Reusing a mature alignment ecosystem enables sorting, indexing and visualisation. It also inherits strict expectations about headers, references, coordinates, flags and CIGAR-like alignment geometry.

The peptide-to-genome bridge depends on reference resources. Protein accessions, transcript models, genome assembly and annotation release must agree. The same peptide can map to multiple proteins or genomic loci, and a transcript update can alter exon boundaries. A proBAM file should therefore preserve the database and mapping route rather than presenting coordinates as timeless facts.

Spliced mappings are important because peptide sequence may span exon junctions. Alignment operations represent genomic gaps while keeping the peptide evidence connected. Analysts should verify translation frame, strand and exon order. A visually impressive junction is not automatically evidence for a new isoform when the peptide is shared or the PSM is weak.

PSM evidence remains mass-spectrometric. Scores, false-discovery information, spectrum references, charge and modifications need their original definitions and thresholds. Mapping a PSM onto the genome does not improve its identification confidence; it adds a coordinate interpretation that introduces new possible errors.

Modified peptides require careful separation. A modification can change observed mass and biological meaning, yet it may not correspond to a genomic sequence change. proBAM can carry peptide-level modifications, but reports should distinguish post-translational modification, artefact and variant-derived amino-acid substitution.

The SAM/BAM header supplies reference sequence names and lengths, read groups or analogous grouping, and processing history. Numeric reference IDs in BAM depend on that dictionary. A mismatched header can relocate every peptide while leaving records structurally readable. Assembly name, chromosome sequences and checksums are essential.

Existing tools can manipulate the alignment container, but support is not identical to proteomics awareness. Sorting and indexing may work, while a viewer ignores proBAM-specific tags or assumes nucleotide reads. A feature-level test should show what each tool preserves, displays or drops.

A practical audit starts from one spectrum and its PSM, checks sequence, score, charge and modification, resolves the source database, reproduces the peptide-to-protein and protein-to-genome mapping, then compares strand and CIGAR geometry with the proBAM record. Every coordinate becomes the end of a traceable chain.

The optimistic benefit is a common map. Proteomics, genomics and transcriptomics teams can inspect evidence in one coordinate system while retaining the molecular origin of the peptide. The format encourages integration; honest reference provenance and uncertainty keep that integration scientifically useful.

Protein inference complicates genomic placement. A peptide shared by proteins may support several transcripts or loci, and choosing one canonical model can hide alternatives. A proBAM workflow should retain all valid mappings or document a conservative selection rule, while downstream summaries distinguish unique evidence from shared evidence.

Variant peptides require special care. The search database must contain the alternative sequence, the PSM must support it against competing explanations and the genomic mapping must agree with the variant and assembly. Orthogonal DNA or RNA evidence can strengthen the interpretation, but absence of such evidence should remain visible rather than being converted into certainty.

Contaminants and common laboratory proteins can map perfectly to a genome while belonging to another organism or source. Species-aware databases, decoy strategy and contamination review should precede novelty claims. Coordinate correctness answers where a sequence fits, not whether it originated from the intended sample.

Binary preservation follows BAM practice: store header, records and matching index together with hashes. Any rewrite, resort or header change requires a new index. Small decoded SAM fixtures help reviewers inspect fields while the original BAM preserves scale and typed representation.

Cross-omics overlays should align assembly, coordinate convention, sample identity and biological unit. RNA abundance from one sample and peptide evidence from another can be useful context but not direct confirmation. A manifest should state every join and the degree of sample matching.

A final methods diagram can show spectrum to PSM, peptide to protein or transcript, transcript to genome and record to browser. Each arrow names its database and software. This makes the integrated result welcoming to readers while exposing where uncertainty entered.

Coordinate liftover is not a label change. Moving proBAM records between genome assemblies requires mapping intervals, checking split or failed mappings and confirming that translated sequence still supports the peptide. Preserve the original file and report every unmapped, multi-mapped or altered record; never overwrite coordinates under a new assembly name.

False-discovery control should reflect the search space actually used. Proteogenomic databases can be much larger than canonical protein databases and can contain variant or six-frame translation candidates. Score thresholds calibrated on a small database may not transfer. Record target-decoy construction, search-space categories and any category-specific error assessment.

Sample identity must survive multi-omics integration. Read groups, filenames and external manifests should resolve to the correct biological material without exposing unnecessary identifiers. If genomic, RNA and proteomic layers come from different aliquots or people, the relationship belongs in the methods instead of being implied by shared coordinates.

Tool compatibility should be recorded feature by feature. Sorting and indexing may preserve every record, while duplicate marking, pileup or variant-calling commands may apply assumptions designed for nucleotide reads and produce meaningless output. A safe workflow lists allowed operations and rejects inappropriate generic commands rather than trusting format recognition.

Index validation should test actual retrieval, not merely the presence of an index file. Query representative chromosomes, junction-spanning mappings and boundary regions, then compare returned records with a complete scan. This catches stale indexes, altered headers and reference-name mismatches that can otherwise make valid peptide evidence disappear from a regional view.

Methods should report whether secondary and supplementary mappings were retained. Filtering them may simplify a view but can erase genuine ambiguity. Keep the complete mapping set, state display filters separately and count primary-looking placements only under a published rule.

A four-step claim ladder for this method

Stage	Question	Evidence	Responsible output
Identify	Which spectrum supports which peptide?	PSM, score, charge, modification and spectrum reference	A bounded peptide identification
Map	How does peptide sequence reach the genome?	Protein or transcript database, assembly and exon model	A reference-dependent placement
Encode	How is placement represented?	Header, coordinates, flags, CIGAR and proteomics tags	An alignment-style record
Interpret	What does the placement support?	Alternatives, validation, novelty rules and other omics evidence	A qualified proteogenomic claim