BioCompute is a standardized way to communicate an analysis pipeline. BioCompute substantially improves the clarity and reproducibility of an analysis, and can be packaged with other standards, such as the Common Workflow Language. An analysis that is reported in a way that conforms to the BioCompute specification is called a BioCompute Object (BCO). A BCO provides the structure that dictates what information must be present in a report.

The main citations for BioCompute are: Biocompute Objects-A Step towards Evaluation and Validation of Biomedical Scientific Computations and Enabling precision medicine via standard communication of HTS provenance, analysis, and results.

The open source repository for the project can be accessed here. Several tools have been developed to read or write an analysis as a BCO. The most popular ones are below. Other resources can be found here.


Cloud-based tools for working with BioCompute

See the resources page for additional resources.



Use HIVE, the High-Performance Integrated Virtual Environment, on AWS. HIVE is a cloud-based environment optimized for the storage and analysis of extra-large data, such as biomedical data, clinical data, next-generation sequencing (NGS) data, mass spectrometry files, confocal microscopy images, post-market surveillance data, medical recall data, and many others.



Use the BCO Portal on AWS, a platform-free, form-based editor. The portal walks a user through building a BCO through drop down menus and text boxes, indicating which entries are required to adhere to the IEEE standard. Legacy Editor site can be found here.



Use Galaxy on AWS, the open source, web-based platform for data intensive biomedical research. Assemble your pipeline in the workspace, designate the outputs in the module boxes, and record the entire pipeline as a BCO.