Content deleted Content added
Tom.Reding (talk | contribs) m WP:GenFixes on, 3+ incoming mainspace links, removed orphan tag using AWB |
GreenC bot (talk | contribs) Rescued 1 archive link. Wayback Medic 2.5 per WP:URLREQ#fda.gov |
||
| (48 intermediate revisions by 19 users not shown) | |||
Line 1:
{{Infobox technology standard
| title = BioCompute Object
| long_name =
| image =
| caption =
| status = [https://saaem-stg.ieee.org/project/2791.htm Active IEEE Working Group]{{dead link|date=January 2025|bot=medic}}{{cbignore|bot=medic}}
| year_started = <!-- {{Start date|2014|07|10|df=y}} -->
| first_published = <!-- {{Start date|YYYY|MM|DD|df=y}} -->
| version = <!-- 1.0 -->
| version_date = <!-- {{Start date|2016|07|08|df=y}} -->
| preview =
| preview_date =
| organization =
| committee =
| editors =
| authors =
| base_standards =
| related_standards = [[Common Workflow Language]]
| abbreviation = BCO
| ___domain =
| license = [[BSD licenses#3-clause license ("BSD License 2.0", "Revised BSD License", "New BSD License", or "Modified BSD License")|BSD-3-clause]]
}}
The '''BioCompute Object''' ('''BCO
Originally started as a collaborative contract between the [[George Washington University]] and the [[Food and Drug Administration]], the project has grown to include over 20 universities, biotechnology companies, public-private partnerships and pharmaceutical companies including Seven Bridges and [[Harvard Medical School]].<ref>{{Cite web|url=https://www.europeanpharmaceuticalreview.com/news/67524/biocompute-genomic-data/|title=BioCompute Objects specifications to advance genomic data analysis|website=www.europeanpharmaceuticalreview.com|language=en|access-date=2017-12-21}}</ref> The BCO aims to ease the exchange of HTS workflows between various organizations, such as the FDA, pharmaceutical companies, contract research organizations, bioinformatic platform providers, and academic researchers. Due to the sensitive nature of regulatory filings, few direct references to material can be published. However, the project is currently funded to train FDA Reviewers and administrators to read and interpret BCOs, and currently has 4 publications either submitted or nearly submitted.
== Background ==
One of the biggest challenges in bioinformatics is documenting and sharing [[Scientific workflow system#Scientific workflows|scientific workflows]] in
== Utility ==
As a standardization for genomic data, BioCompute Objects are mostly useful to three groups of users: 1) academic researchers carrying out new genetic experiments, 2) pharma/biotech companies that wish to submit work to the FDA for regulatory review, and 3) clinical settings (hospitals and labs) that offer genetic tests and [[personalized medicine]]. The utility to academic researchers is the ability to reproduce experimental data more accurately and with less uncertainty. The utility to entities wishing to submit work to the FDA is a streamlined approach, again with less uncertainty and with the ability to more accurately reproduce work. For clinical settings, it is critical that HTS data and clinical metadata be transmitted in an accurate way, ideally in a standardized way that is readable by any stakeholder, including regulatory partners.
The BioCompute Object is in [[JSON|json]] format and, at a minimum, contains all the software versions and parameters necessary to evaluate or verify a computational pipeline. It may also contain input data as files or links, reference genomes, or executable Docker components. A BioCompute Object can be integrated with [[FHIR|HL7 FHIR]] as a Provenance Resource<ref>{{Cite web|url=https://www.hl7.org/fhir/provenance-example-biocompute-object.html|title=Provenance-example-biocompute-object|last=|first=|date=|website=HL7 FHIR Release 3 (STU)|archive-url=|archive-date=|dead-url=|access-date=}}</ref> or [[Common Workflow Language]] as a [[Research Object]].<ref>{{Citation|last=Soiland-Reyes|first=Stian|title=hive-cwl-examples: Example BioCompute as Research Object with CWL|date=2016-12-19|url=https://github.com/stain/hive-cwl-examples|accessdate=2017-12-21}}</ref>▼
== Format ==
▲The BioCompute Object is in [[JSON|json]] format and, at a minimum, contains all the software versions and parameters necessary to evaluate or verify a computational pipeline. It may also contain input data as files or links, reference genomes, or executable Docker components. A BioCompute Object can be integrated with [[FHIR|HL7 FHIR]] as a Provenance Resource.<ref>{{Cite web|url=https://www.hl7.org/fhir/provenance-example-biocompute-object.html|title=Provenance-example-biocompute-object
== BCO Consortium ==
The BioCompute Object working group
== Implementations ==
The simple R package biocompute<ref name="biocompute-r">{{cite web|url=https://cran.r-project.org/package=biocompute|title=CRAN - Package biocompute|publisher=cran.r-project.org|accessdate=2019-11-28}}</ref> can create, validate, and export BioCompute Objects. The [https://github.com/sbg/gcs Genomics Compliance Suite] is a Shiny app that offers similar features to regular expressions found in all modern text editors. There are several internally developed [[Open-source software|open source]] software packages and web applications that implement the BioCompute specification, three of which have been deployed in a publicly accessible [[Amazon Web Services|AWS]] [[Amazon Elastic Compute Cloud|EC2]] [[Cloud computing|cloud]]. These include an instance of the [[High-performance Integrated Virtual Environment]], the [https://github.com/biocompute-objects/bco_editor BioCompute Portal]<ref name="bco_editor">{{cite web|url=https://github.com/biocompute-objects/bco_editor|title=BioCompute Portal|publisher=github.com/biocompute-objects|accessdate=2020-06-25}}</ref> (a form-based web application that can create and edit BioCompute Objects based on the IEEE-2791-2020 [[Open standard|standard]], and a BioCompute compliant instance of [https://usegalaxy.org/ Galaxy].
Some bioinformatics platforms have built-in support for Biocompute, which let a user automatically create a BCO from a workflow and edit the descriptive content.
* DNAnexus and PrecisionFDA facilitate the generation of BCOs by importing workflows, allowing users to edit descriptive content. The platform supports metadata import and export of WDL and CWL scripts, and offers the BCOnexus tool, which is a high-level, platform-free tool with a graphical user interface that lets a user merge BCOs.
* Velsera's Seven Bridges Genomics and Cancer Genomics Cloud also have support for BioCompute by enabling direct pre-population of BCO fields from workflows.
* BioCompute has also been integrated into [https://hivelab.biochemistry.gwu.edu/ HIVE] and the main Galaxy instance, both of which similarly enable users to automatically generate BCOs and edit content within these platforms.
* BioCompute has also been implemented in the Common Fund Data Elements Playbook Partnership project. This implementation lets a user save a workflow when they're satisfied with the results, which aids in traceability through the network of independently-versioned resources, allowing users to save queries and annotate them for future use, sharing, or repeatability, aligning with its role in advancing bioinformatics practices.
Integration into platforms is meant to improve data handling and collaboration and provide effective ways for users to execute a workflow, and graphical representations of BCOs are often more intuitive ways of browsing or reading BCOs.
== References ==
Line 18 ⟶ 54:
== External links ==
*[http://biocomputeobject.org/ Official Website]
▲*{{official website|https://osf.io/h59uh/}}
*[https://opensource.ieee.org/2791-object/ieee-2791-schema/ IEEE 2791-2020 open source project]
[[Category:Bioinformatics software]]
| |||