Content deleted Content added
Tom.Reding (talk | contribs) m WP:GenFixes on, 3+ incoming mainspace links, removed orphan tag using AWB |
|||
Line 9:
== 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|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.
== 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|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>
| |||