Serveur d'exploration Cyberinfrastructure

Attention, ce site est en cours de développement !
Attention, site généré par des moyens informatiques à partir de corpus bruts.
Les informations ne sont donc pas validées.

Bio and health informatics meets cloud : BioVLab as an example

Identifieur interne : 000193 ( Pmc/Corpus ); précédent : 000192; suivant : 000194

Bio and health informatics meets cloud : BioVLab as an example

Auteurs : Heejoon Chae ; Inuk Jung ; Hyungro Lee ; Suresh Marru ; Seong-Whan Lee ; Sun Kim

Source :

RBID : PMC:4336112

Abstract

The exponential increase of genomic data brought by the advent of the next or the third generation sequencing (NGS) technologies and the dramatic drop in sequencing cost have driven biological and medical sciences to data-driven sciences. This revolutionary paradigm shift comes with challenges in terms of data transfer, storage, computation, and analysis of big bio/medical data. Cloud computing is a service model sharing a pool of configurable resources, which is a suitable workbench to address these challenges. From the medical or biological perspective, providing computing power and storage is the most attractive feature of cloud computing in handling the ever increasing biological data. As data increases in size, many research organizations start to experience the lack of computing power, which becomes a major hurdle in achieving research goals. In this paper, we review the features of publically available bio and health cloud systems in terms of graphical user interface, external data integration, security and extensibility of features. We then discuss about issues and limitations of current cloud systems and conclude with suggestion of a biological cloud environment concept, which can be defined as a total workbench environment assembling computational tools and databases for analyzing bio/medical big data in particular application domains.


Url:
DOI: 10.1186/2047-2501-1-6
PubMed: 25825658
PubMed Central: 4336112

Links to Exploration step

PMC:4336112

Le document en format XML

<record>
<TEI>
<teiHeader>
<fileDesc>
<titleStmt>
<title xml:lang="en">Bio and health informatics meets cloud : BioVLab as an example</title>
<author>
<name sortKey="Chae, Heejoon" sort="Chae, Heejoon" uniqKey="Chae H" first="Heejoon" last="Chae">Heejoon Chae</name>
<affiliation>
<nlm:aff id="Aff1_8">School of Informatics and Computing, Indiana University, Bloomington, Indiana USA</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Jung, Inuk" sort="Jung, Inuk" uniqKey="Jung I" first="Inuk" last="Jung">Inuk Jung</name>
<affiliation>
<nlm:aff id="Aff2_8">Interdisciplinary Program in Bioinformatics, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Lee, Hyungro" sort="Lee, Hyungro" uniqKey="Lee H" first="Hyungro" last="Lee">Hyungro Lee</name>
<affiliation>
<nlm:aff id="Aff1_8">School of Informatics and Computing, Indiana University, Bloomington, Indiana USA</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Marru, Suresh" sort="Marru, Suresh" uniqKey="Marru S" first="Suresh" last="Marru">Suresh Marru</name>
<affiliation>
<nlm:aff id="Aff3_8">Pervasive Technology Institute, Bloomington, Indiana USA</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Lee, Seong Whan" sort="Lee, Seong Whan" uniqKey="Lee S" first="Seong-Whan" last="Lee">Seong-Whan Lee</name>
<affiliation>
<nlm:aff id="Aff4_8">Department of Brain and Cognitive Engineering, Korea University, Seoul, Korea</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Kim, Sun" sort="Kim, Sun" uniqKey="Kim S" first="Sun" last="Kim">Sun Kim</name>
<affiliation>
<nlm:aff id="Aff2_8">Interdisciplinary Program in Bioinformatics, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
<affiliation>
<nlm:aff id="Aff5_8">Computer Science Department, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
<affiliation>
<nlm:aff id="Aff6_8">Bioinformatics Institute, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
</author>
</titleStmt>
<publicationStmt>
<idno type="wicri:source">PMC</idno>
<idno type="pmid">25825658</idno>
<idno type="pmc">4336112</idno>
<idno type="url">http://www.ncbi.nlm.nih.gov/pmc/articles/PMC4336112</idno>
<idno type="RBID">PMC:4336112</idno>
<idno type="doi">10.1186/2047-2501-1-6</idno>
<date when="2013">2013</date>
<idno type="wicri:Area/Pmc/Corpus">000193</idno>
</publicationStmt>
<sourceDesc>
<biblStruct>
<analytic>
<title xml:lang="en" level="a" type="main">Bio and health informatics meets cloud : BioVLab as an example</title>
<author>
<name sortKey="Chae, Heejoon" sort="Chae, Heejoon" uniqKey="Chae H" first="Heejoon" last="Chae">Heejoon Chae</name>
<affiliation>
<nlm:aff id="Aff1_8">School of Informatics and Computing, Indiana University, Bloomington, Indiana USA</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Jung, Inuk" sort="Jung, Inuk" uniqKey="Jung I" first="Inuk" last="Jung">Inuk Jung</name>
<affiliation>
<nlm:aff id="Aff2_8">Interdisciplinary Program in Bioinformatics, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Lee, Hyungro" sort="Lee, Hyungro" uniqKey="Lee H" first="Hyungro" last="Lee">Hyungro Lee</name>
<affiliation>
<nlm:aff id="Aff1_8">School of Informatics and Computing, Indiana University, Bloomington, Indiana USA</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Marru, Suresh" sort="Marru, Suresh" uniqKey="Marru S" first="Suresh" last="Marru">Suresh Marru</name>
<affiliation>
<nlm:aff id="Aff3_8">Pervasive Technology Institute, Bloomington, Indiana USA</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Lee, Seong Whan" sort="Lee, Seong Whan" uniqKey="Lee S" first="Seong-Whan" last="Lee">Seong-Whan Lee</name>
<affiliation>
<nlm:aff id="Aff4_8">Department of Brain and Cognitive Engineering, Korea University, Seoul, Korea</nlm:aff>
</affiliation>
</author>
<author>
<name sortKey="Kim, Sun" sort="Kim, Sun" uniqKey="Kim S" first="Sun" last="Kim">Sun Kim</name>
<affiliation>
<nlm:aff id="Aff2_8">Interdisciplinary Program in Bioinformatics, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
<affiliation>
<nlm:aff id="Aff5_8">Computer Science Department, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
<affiliation>
<nlm:aff id="Aff6_8">Bioinformatics Institute, Seoul National University, Seoul, Korea</nlm:aff>
</affiliation>
</author>
</analytic>
<series>
<title level="j">Health Information Science and Systems</title>
<idno type="eISSN">2047-2501</idno>
<imprint>
<date when="2013">2013</date>
</imprint>
</series>
</biblStruct>
</sourceDesc>
</fileDesc>
<profileDesc>
<textClass></textClass>
</profileDesc>
</teiHeader>
<front>
<div type="abstract" xml:lang="en">
<p>The exponential increase of genomic data brought by the advent of the next or the third generation sequencing (NGS) technologies and the dramatic drop in sequencing cost have driven biological and medical sciences to data-driven sciences. This revolutionary paradigm shift comes with challenges in terms of data transfer, storage, computation, and analysis of big bio/medical data. Cloud computing is a service model sharing a pool of configurable resources, which is a suitable workbench to address these challenges. From the medical or biological perspective, providing computing power and storage is the most attractive feature of cloud computing in handling the ever increasing biological data. As data increases in size, many research organizations start to experience the lack of computing power, which becomes a major hurdle in achieving research goals. In this paper, we review the features of publically available bio and health cloud systems in terms of graphical user interface, external data integration, security and extensibility of features. We then discuss about issues and limitations of current cloud systems and conclude with suggestion of a biological cloud environment concept, which can be defined as a total workbench environment assembling computational tools and databases for analyzing bio/medical big data in particular application domains.</p>
</div>
</front>
<back>
<div1 type="bibliography">
<listBibl>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Kanz, C" uniqKey="Kanz C">C Kanz</name>
</author>
<author>
<name sortKey="Aldebert, P" uniqKey="Aldebert P">P Aldebert</name>
</author>
<author>
<name sortKey="Althorpe, N" uniqKey="Althorpe N">N Althorpe</name>
</author>
<author>
<name sortKey="Baker, W" uniqKey="Baker W">W Baker</name>
</author>
<author>
<name sortKey="Baldwin, A" uniqKey="Baldwin A">A Baldwin</name>
</author>
<author>
<name sortKey="Bates, K" uniqKey="Bates K">K Bates</name>
</author>
<author>
<name sortKey="Browne, P" uniqKey="Browne P">P Browne</name>
</author>
<author>
<name sortKey="Van Den Broek, A" uniqKey="Van Den Broek A">A van den Broek</name>
</author>
<author>
<name sortKey="Castro, M" uniqKey="Castro M">M Castro</name>
</author>
<author>
<name sortKey="Cochrane Ea, G" uniqKey="Cochrane Ea G">G Cochrane ea</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Stein, Ld" uniqKey="Stein L">LD Stein</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Siva, N" uniqKey="Siva N">N Siva</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Oinn, T" uniqKey="Oinn T">T Oinn</name>
</author>
<author>
<name sortKey="Addis, M" uniqKey="Addis M">M Addis</name>
</author>
<author>
<name sortKey="Ferris, J" uniqKey="Ferris J">J Ferris</name>
</author>
<author>
<name sortKey="Marvin, D" uniqKey="Marvin D">D Marvin</name>
</author>
<author>
<name sortKey="Senger, M" uniqKey="Senger M">M Senger</name>
</author>
<author>
<name sortKey="Greenwood, M" uniqKey="Greenwood M">M Greenwood</name>
</author>
<author>
<name sortKey="Carver, T" uniqKey="Carver T">T Carver</name>
</author>
<author>
<name sortKey="Glover, Kpm" uniqKey="Glover K">KPM Glover</name>
</author>
<author>
<name sortKey="Wipat, Alp" uniqKey="Wipat A">ALP Wipat</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Hong, D" uniqKey="Hong D">D Hong</name>
</author>
<author>
<name sortKey="Rhie, A" uniqKey="Rhie A">A Rhie</name>
</author>
<author>
<name sortKey="Park, S" uniqKey="Park S">S Park</name>
</author>
<author>
<name sortKey="Lee, J" uniqKey="Lee J">J Lee</name>
</author>
<author>
<name sortKey="Ju, Y" uniqKey="Ju Y">Y Ju</name>
</author>
<author>
<name sortKey="Kim, S" uniqKey="Kim S">S Kim</name>
</author>
<author>
<name sortKey="Yu, S" uniqKey="Yu S">S Yu</name>
</author>
<author>
<name sortKey="Bleazard, T" uniqKey="Bleazard T">T Bleazard</name>
</author>
<author>
<name sortKey="Park, H" uniqKey="Park H">H Park</name>
</author>
<author>
<name sortKey="Rhee, H" uniqKey="Rhee H">H Rhee</name>
</author>
<author>
<name sortKey="Chong, H" uniqKey="Chong H">H Chong</name>
</author>
<author>
<name sortKey="Yang, K" uniqKey="Yang K">K Yang</name>
</author>
<author>
<name sortKey="Lee, Y" uniqKey="Lee Y">Y Lee</name>
</author>
<author>
<name sortKey="Kim, I" uniqKey="Kim I">I Kim</name>
</author>
<author>
<name sortKey="Lee, J" uniqKey="Lee J">J Lee</name>
</author>
<author>
<name sortKey="Kim, J" uniqKey="Kim J">J Kim</name>
</author>
<author>
<name sortKey="Seo, J" uniqKey="Seo J">J Seo</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Giardine, B" uniqKey="Giardine B">B Giardine</name>
</author>
<author>
<name sortKey="Riemer, C" uniqKey="Riemer C">C Riemer</name>
</author>
<author>
<name sortKey="Hardison, Rc" uniqKey="Hardison R">RC Hardison</name>
</author>
<author>
<name sortKey="Burhans, R" uniqKey="Burhans R">R Burhans</name>
</author>
<author>
<name sortKey="Elnitski, L" uniqKey="Elnitski L">L Elnitski</name>
</author>
<author>
<name sortKey="Shah, P" uniqKey="Shah P">P Shah</name>
</author>
<author>
<name sortKey="Zhang, Y" uniqKey="Zhang Y">Y Zhang</name>
</author>
<author>
<name sortKey="Blankenberg, D" uniqKey="Blankenberg D">D Blankenberg</name>
</author>
<author>
<name sortKey="Albert, I" uniqKey="Albert I">I Albert</name>
</author>
<author>
<name sortKey="Taylor, J" uniqKey="Taylor J">J Taylor</name>
</author>
<author>
<name sortKey="Miller, W" uniqKey="Miller W">W Miller</name>
</author>
<author>
<name sortKey="Kent, Wj" uniqKey="Kent W">WJ Kent</name>
</author>
<author>
<name sortKey="Nekrutenko, A" uniqKey="Nekrutenko A">A Nekrutenko</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="O Onnor, B" uniqKey="O Onnor B">B O’Connor</name>
</author>
<author>
<name sortKey="Merriman, B" uniqKey="Merriman B">B Merriman</name>
</author>
<author>
<name sortKey="Nelson, S" uniqKey="Nelson S">S Nelson</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Lee, H" uniqKey="Lee H">H Lee</name>
</author>
<author>
<name sortKey="Yang, Y" uniqKey="Yang Y">Y Yang</name>
</author>
<author>
<name sortKey="Chae, H" uniqKey="Chae H">H Chae</name>
</author>
<author>
<name sortKey="Nam, S" uniqKey="Nam S">S Nam</name>
</author>
<author>
<name sortKey="Choi, D" uniqKey="Choi D">D Choi</name>
</author>
<author>
<name sortKey="Tangchaisin, P" uniqKey="Tangchaisin P">P Tangchaisin</name>
</author>
<author>
<name sortKey="Herath, C" uniqKey="Herath C">C Herath</name>
</author>
<author>
<name sortKey="Marru, S" uniqKey="Marru S">S Marru</name>
</author>
<author>
<name sortKey="Nephew, K" uniqKey="Nephew K">K Nephew</name>
</author>
<author>
<name sortKey="Kim, S" uniqKey="Kim S">S Kim</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Lee, H" uniqKey="Lee H">H Lee</name>
</author>
<author>
<name sortKey="Yang, Y" uniqKey="Yang Y">Y Yang</name>
</author>
<author>
<name sortKey="Chae, H" uniqKey="Chae H">H Chae</name>
</author>
<author>
<name sortKey="Nam, S" uniqKey="Nam S">S Nam</name>
</author>
<author>
<name sortKey="Choi, D" uniqKey="Choi D">D Choi</name>
</author>
<author>
<name sortKey="Tangchaisin, P" uniqKey="Tangchaisin P">P Tangchaisin</name>
</author>
<author>
<name sortKey="Herath, C" uniqKey="Herath C">C Herath</name>
</author>
<author>
<name sortKey="Marru, S" uniqKey="Marru S">S Marru</name>
</author>
<author>
<name sortKey="Nephew, K" uniqKey="Nephew K">K Nephew</name>
</author>
<author>
<name sortKey="Kim, S" uniqKey="Kim S">S Kim</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Angiuoli, S" uniqKey="Angiuoli S">S Angiuoli</name>
</author>
<author>
<name sortKey="Matalka, M" uniqKey="Matalka M">M Matalka</name>
</author>
<author>
<name sortKey="Gussman, A" uniqKey="Gussman A">A Gussman</name>
</author>
<author>
<name sortKey="Galens, K" uniqKey="Galens K">K Galens</name>
</author>
<author>
<name sortKey="Vangala, M" uniqKey="Vangala M">M Vangala</name>
</author>
<author>
<name sortKey="Riley, D" uniqKey="Riley D">D Riley</name>
</author>
<author>
<name sortKey="White, J" uniqKey="White J">J White</name>
</author>
<author>
<name sortKey="White, O" uniqKey="White O">O White</name>
</author>
<author>
<name sortKey="Fricke, W" uniqKey="Fricke W">W Fricke</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Krampis, K" uniqKey="Krampis K">K Krampis</name>
</author>
<author>
<name sortKey="Chapman, B" uniqKey="Chapman B">B Chapman</name>
</author>
<author>
<name sortKey="Tiwari, B" uniqKey="Tiwari B">B Tiwari</name>
</author>
<author>
<name sortKey="Bicak, M" uniqKey="Bicak M">M Bicak</name>
</author>
<author>
<name sortKey="Field, D" uniqKey="Field D">D Field</name>
</author>
<author>
<name sortKey="Nelson, K" uniqKey="Nelson K">K Nelson</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Deluca, Tf" uniqKey="Deluca T">TF Deluca</name>
</author>
<author>
<name sortKey="Wu, Ih" uniqKey="Wu I">IH Wu</name>
</author>
<author>
<name sortKey="Pu, J" uniqKey="Pu J">J Pu</name>
</author>
<author>
<name sortKey="Monaghan, T" uniqKey="Monaghan T">T Monaghan</name>
</author>
<author>
<name sortKey="Peshkin, L" uniqKey="Peshkin L">L Peshkin</name>
</author>
<author>
<name sortKey="Singh, S" uniqKey="Singh S">S Singh</name>
</author>
<author>
<name sortKey="Wall, Dp" uniqKey="Wall D">DP Wall</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Schatz, M" uniqKey="Schatz M">M Schatz</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Langmead, B" uniqKey="Langmead B">B Langmead</name>
</author>
<author>
<name sortKey="Schatz, M" uniqKey="Schatz M">M Schatz</name>
</author>
<author>
<name sortKey="Lin, J" uniqKey="Lin J">J Lin</name>
</author>
<author>
<name sortKey="Pop, M" uniqKey="Pop M">M Pop</name>
</author>
<author>
<name sortKey="Salzberg, S" uniqKey="Salzberg S">S Salzberg</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Dean, J" uniqKey="Dean J">J Dean</name>
</author>
<author>
<name sortKey="Ghemawat, S" uniqKey="Ghemawat S">S Ghemawat</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Langmead, B" uniqKey="Langmead B">B Langmead</name>
</author>
<author>
<name sortKey="Trapnel, Lc" uniqKey="Trapnel L">lC Trapnel</name>
</author>
<author>
<name sortKey="Pop, M" uniqKey="Pop M">M Pop</name>
</author>
<author>
<name sortKey="Salzberg, S" uniqKey="Salzberg S">S Salzberg</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Li, R" uniqKey="Li R">R Li</name>
</author>
<author>
<name sortKey="Li, Y" uniqKey="Li Y">Y Li</name>
</author>
<author>
<name sortKey="Fang, X" uniqKey="Fang X">X Fang</name>
</author>
<author>
<name sortKey="Yang, H" uniqKey="Yang H">H Yang</name>
</author>
<author>
<name sortKey="Wang, J" uniqKey="Wang J">J Wang</name>
</author>
<author>
<name sortKey="Kristiansen, K" uniqKey="Kristiansen K">K Kristiansen</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Wang, Z" uniqKey="Wang Z">Z Wang</name>
</author>
<author>
<name sortKey="Wang, Y" uniqKey="Wang Y">Y Wang</name>
</author>
<author>
<name sortKey="Tan, K" uniqKey="Tan K">K Tan</name>
</author>
<author>
<name sortKey="Wong, L" uniqKey="Wong L">L Wong</name>
</author>
<author>
<name sortKey="Agrawal, D" uniqKey="Agrawal D">D Agrawal</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Marru, S" uniqKey="Marru S">S Marru</name>
</author>
<author>
<name sortKey="Chae, H" uniqKey="Chae H">H Chae</name>
</author>
<author>
<name sortKey="Tangchaisin, P" uniqKey="Tangchaisin P">P Tangchaisin</name>
</author>
<author>
<name sortKey="Kim, S" uniqKey="Kim S">S Kim</name>
</author>
<author>
<name sortKey="Pierce, M" uniqKey="Pierce M">M Pierce</name>
</author>
<author>
<name sortKey="Nephew, K" uniqKey="Nephew K">K Nephew</name>
</author>
</analytic>
</biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Nam, S" uniqKey="Nam S">S Nam</name>
</author>
<author>
<name sortKey="Li, M" uniqKey="Li M">M Li</name>
</author>
<author>
<name sortKey="Choi, K" uniqKey="Choi K">K Choi</name>
</author>
<author>
<name sortKey="Balch, C" uniqKey="Balch C">C Balch</name>
</author>
<author>
<name sortKey="Kim, S" uniqKey="Kim S">S Kim</name>
</author>
<author>
<name sortKey="Nephew, K" uniqKey="Nephew K">K Nephew</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Zhang, Y" uniqKey="Zhang Y">Y Zhang</name>
</author>
<author>
<name sortKey="Liu, T" uniqKey="Liu T">T Liu</name>
</author>
<author>
<name sortKey="Meyer, Ca" uniqKey="Meyer C">CA Meyer</name>
</author>
<author>
<name sortKey="Eeckhoute, J" uniqKey="Eeckhoute J">J Eeckhoute</name>
</author>
<author>
<name sortKey="Johnson, Ds" uniqKey="Johnson D">DS Johnson</name>
</author>
<author>
<name sortKey="Bernstein, Be" uniqKey="Bernstein B">BE Bernstein</name>
</author>
<author>
<name sortKey="Nusbaum, C" uniqKey="Nusbaum C">C Nusbaum</name>
</author>
<author>
<name sortKey="Myers, Rm" uniqKey="Myers R">RM Myers</name>
</author>
<author>
<name sortKey="Brown, M" uniqKey="Brown M">M Brown</name>
</author>
<author>
<name sortKey="Li, W" uniqKey="Li W">W Li</name>
</author>
<author>
<name sortKey="Liu, Xs" uniqKey="Liu X">XS Liu</name>
</author>
</analytic>
</biblStruct>
<biblStruct></biblStruct>
<biblStruct>
<analytic>
<author>
<name sortKey="Chen, Y" uniqKey="Chen Y">Y Chen</name>
</author>
<author>
<name sortKey="Peng, B" uniqKey="Peng B">B Peng</name>
</author>
<author>
<name sortKey="Wang, X" uniqKey="Wang X">X Wang</name>
</author>
<author>
<name sortKey="Tang, H" uniqKey="Tang H">H Tang</name>
</author>
</analytic>
</biblStruct>
</listBibl>
</div1>
</back>
</TEI>
<pmc article-type="review-article">
<pmc-dir>properties open_access</pmc-dir>
<front>
<journal-meta>
<journal-id journal-id-type="nlm-ta">Health Inf Sci Syst</journal-id>
<journal-id journal-id-type="iso-abbrev">Health Inf Sci Syst</journal-id>
<journal-title-group>
<journal-title>Health Information Science and Systems</journal-title>
</journal-title-group>
<issn pub-type="epub">2047-2501</issn>
<publisher>
<publisher-name>BioMed Central</publisher-name>
<publisher-loc>London</publisher-loc>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="pmid">25825658</article-id>
<article-id pub-id-type="pmc">4336112</article-id>
<article-id pub-id-type="publisher-id">8</article-id>
<article-id pub-id-type="doi">10.1186/2047-2501-1-6</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Review</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Bio and health informatics meets cloud : BioVLab as an example</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Chae</surname>
<given-names>Heejoon</given-names>
</name>
<address>
<email>heechae@cs.indiana.edu</email>
</address>
<xref ref-type="aff" rid="Aff1_8">1</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Jung</surname>
<given-names>Inuk</given-names>
</name>
<address>
<email>inuk@snu.ac.kr</email>
</address>
<xref ref-type="aff" rid="Aff2_8">2</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Lee</surname>
<given-names>Hyungro</given-names>
</name>
<address>
<email>lee212@indiana.edu</email>
</address>
<xref ref-type="aff" rid="Aff1_8">1</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Marru</surname>
<given-names>Suresh</given-names>
</name>
<address>
<email>smarru@cs.indiana.edu</email>
</address>
<xref ref-type="aff" rid="Aff3_8">3</xref>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Lee</surname>
<given-names>Seong-Whan</given-names>
</name>
<address>
<email>sw.lee@korea.ac.kr</email>
</address>
<xref ref-type="aff" rid="Aff4_8">4</xref>
</contrib>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Kim</surname>
<given-names>Sun</given-names>
</name>
<address>
<email>sunkim.bioinfo@snu.ac.kr</email>
</address>
<xref ref-type="aff" rid="Aff2_8">2</xref>
<xref ref-type="aff" rid="Aff5_8">5</xref>
<xref ref-type="aff" rid="Aff6_8">6</xref>
</contrib>
<aff id="Aff1_8">
<label>1</label>
School of Informatics and Computing, Indiana University, Bloomington, Indiana USA</aff>
<aff id="Aff2_8">
<label>2</label>
Interdisciplinary Program in Bioinformatics, Seoul National University, Seoul, Korea</aff>
<aff id="Aff3_8">
<label>3</label>
Pervasive Technology Institute, Bloomington, Indiana USA</aff>
<aff id="Aff4_8">
<label>4</label>
Department of Brain and Cognitive Engineering, Korea University, Seoul, Korea</aff>
<aff id="Aff5_8">
<label>5</label>
Computer Science Department, Seoul National University, Seoul, Korea</aff>
<aff id="Aff6_8">
<label>6</label>
Bioinformatics Institute, Seoul National University, Seoul, Korea</aff>
</contrib-group>
<pub-date pub-type="epub">
<day>4</day>
<month>2</month>
<year>2013</year>
</pub-date>
<pub-date pub-type="pmc-release">
<day>4</day>
<month>2</month>
<year>2013</year>
</pub-date>
<pub-date pub-type="collection">
<year>2013</year>
</pub-date>
<volume>1</volume>
<elocation-id>6</elocation-id>
<history>
<date date-type="received">
<day>24</day>
<month>5</month>
<year>2012</year>
</date>
<date date-type="accepted">
<day>26</day>
<month>9</month>
<year>2012</year>
</date>
</history>
<permissions>
<copyright-statement>© Chae et al.; licensee BioMed Central Ltd. 2013</copyright-statement>
<license license-type="open-access">
<license-p>This article is published under license to BioMed Central Ltd. This is an Open Access article distributed under the terms of the Creative Commons Attribution License(
<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by/2.0">http://creativecommons.org/licenses/by/2.0</ext-link>
), which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<abstract id="Abs1_8">
<p>The exponential increase of genomic data brought by the advent of the next or the third generation sequencing (NGS) technologies and the dramatic drop in sequencing cost have driven biological and medical sciences to data-driven sciences. This revolutionary paradigm shift comes with challenges in terms of data transfer, storage, computation, and analysis of big bio/medical data. Cloud computing is a service model sharing a pool of configurable resources, which is a suitable workbench to address these challenges. From the medical or biological perspective, providing computing power and storage is the most attractive feature of cloud computing in handling the ever increasing biological data. As data increases in size, many research organizations start to experience the lack of computing power, which becomes a major hurdle in achieving research goals. In this paper, we review the features of publically available bio and health cloud systems in terms of graphical user interface, external data integration, security and extensibility of features. We then discuss about issues and limitations of current cloud systems and conclude with suggestion of a biological cloud environment concept, which can be defined as a total workbench environment assembling computational tools and databases for analyzing bio/medical big data in particular application domains.</p>
</abstract>
<kwd-group xml:lang="en">
<title>Keywords</title>
<kwd>Bioinformatics</kwd>
<kwd>Cloud computing</kwd>
<kwd>Big data</kwd>
<kwd>Workflow</kwd>
<kwd>User interface</kwd>
<kwd>Data integration</kwd>
<kwd>Analysis</kwd>
<kwd>Security</kwd>
</kwd-group>
<custom-meta-group>
<custom-meta>
<meta-name>issue-copyright-statement</meta-name>
<meta-value>© BioMed Central Ltd 2013</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec id="Sec1_8">
<title>Review</title>
<p>High throughput, massive parallel sequencing technologies, called the next generation sequencing (NGS) technologies, were first introduced in the late 1990s. The leap of sequencing technology by NGS dropped sequencing cost dramatically and caused the exponentially increasing volume of data. Comparing NGS to the traditional Sanger sequencing technology that was used for the first human genome project, a three billion dollar project over a span of 10 years, the cost and time for sequencing a single human genome has dropped by 3,000,000 and 3000 times respectively [
<xref ref-type="bibr" rid="CR1_8">1</xref>
,
<xref ref-type="bibr" rid="CR2_8">2</xref>
]. As a result, the nucleotide sequence resource in the EMBL-Bank DB has approximately doubled over the past 5 years [
<xref ref-type="bibr" rid="CR3_8">3</xref>
,
<xref ref-type="bibr" rid="CR4_8">4</xref>
]. The sequencing throughput rate has increased five fold per year, whereas computer performance generally follows the Moore’s Law, doubling only every 18 or 24 months. Thus the gap between the production rate of sequencing data and computing power to process them is widening. On January 10, 2012, the Life Technologies company announced the Benchtop Ion Proton Sequencer [
<xref ref-type="bibr" rid="CR1_8">1</xref>
] claiming the opening of the US $1000 human genome sequencing era. The new sequencing technology is not only affordable in price, but also allows human genome to be sequenced within a single day compared to weeks or months with conventional technologies. In addition, the Pacific Biosciences company recently announced new technology which can sequence DNA fragments of several thousand bps in length [
<xref ref-type="bibr" rid="CR2_8">2</xref>
]. The higher multi fold coverage with longer sequences will make human genome sequencing much easier and the quality of the sequencing data is also expected to be more accurate. Thus, it is increasingly likely that biological sequence information is used for clinical applications with more confidence.</p>
<sec id="Sec2_8">
<title>Importance of big and high quality data in bio/health informatics</title>
<p>The low cost, high quality sequencing data has begun to impact bio/medical research fields. Higher resolution of genomic information, acquired through the improved fold coverage, makes it possible to associate genomic features, such as single nucleotide polymorphism, gene copy number variations, genome re-arrangement, and gene fusion, with disease phenotypes. In addition, sequencing data makes it possible to measure epigenetic features within cells, such as DNA methylation, histone modification, and microRNA. By measuring comprehensive epigenetic events in cells, it is now possible to understand how important genes, such as cancer suppressors and oncogenes, are activated or suppressed in cells. Thus we have an opportunity to not only measure disease susceptibility but also make prognostic measurements for treatment outcomes. However, each genetic and epigenetic event is measured independently, thus, to realize these possibilities, it is critical to integrate data of multiple types from genetic and epigenetic events and information systems along with powerful bioinformatics tools that should serve the research and clinical communities.</p>
</sec>
<sec id="Sec3_8">
<title>Challenges from biomedical big data and expensive computation</title>
<p>The two major challenges in terms of biological data analysis are how to obtain computation power and how to perform data analysis for the bio/medical big data. The increase in cost for analyzing large biomedical data has become a major bottleneck for initiating biological research projects, especially with the introduction of NGS technology that produces data multiple folds in size compared to conventional sequencing technologies. Since acquisition (or sequencing) of data is becoming easier, the trend is that biomedical researchers formulate complicated questions investigating relationship among genetic and epigenetic elements in multiple cells of different phenotypes. Comparing omics data from multiple cell lines will be a significant challenge since the computing power and information systems are barely handling omics data from a few cell lines. Bio/medical researchers are proactive in leveraging the sequencing data. According to a recent poll on biomedical research facilities, a significant number of research institutions are already performing multi-omics research projects and most of them are experiencing the capacity limit of their computing facilities. The current situation is “data acquisition is affordable but data analysis is not.”</p>
<p>The need for computing capacity in the bio/medical applications varies dramatically for different stages. For example, processing a huge omics data or assembling short reads to reconstruct genome sequences requires a very big computing power with huge storage space. However, steps following these computationally expensive applications may not require as much computing power in the previous steps. It implies that the computing resources do not need to be maintained at the maximum capacity at all times, which makes use of public computing facilities highly desirable. Although there has been significant effort to provide high performance computing service to the public domain, e.g., the Grid projects, most of bio/medical researchers are not comfortable with such service due to technical issues and due to the lack of configurability of the computing systems. In addition to the computing power and storage space, there are significant number of computational tools and several thousands of biological databases. Thus collecting and configuring suitable tools and resources for certain research purposes is non-trivial job, even for bioinformatics experts.</p>
</sec>
<sec id="Sec4_8">
<title>Cloud computing as an emerging solution</title>
<p>As an affordable and efficient way to overcome the hurdles mentioned in the previous section,
<italic>cloud computing</italic>
is gaining attention. This is because a cloud delivers computing resources as service rather than a physical product. Softwares and shared resources are pre-installed and provided on the cloud for all users. Cloud is analogous to the Internet as it can be simply a space where information and resource is shared among users.</p>
<p>Cloud computing has been successful in delivering computing resource (e.g computation power, servers, storage, applications) in terms of three forms of services such as Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS). Among cloud computing service models, the Virtual Machine (VM) type provided as IaaS is most suitable for biomedical data analyses since researchers are mostly looking for computation power to analyze their big data. With the IaaS model, users can easily configure computer systems with the computing power necessary to analyze the data. Thus users can enjoy computing power and storage on a “pay as you go” basis. However, IaaS model provides only computing machines, thus users need to configure softwares and databases that are necessary for data analysis. This is a significant barrier for bio/medical researchers. Thus some cloud service providers try to provide pre-installed packages including necessary tools and databases. For example, Amazon provides many genomic resources such as NCBI sequence data and the 1000 genome project data pre-installed and also provide APIs to the NCBI data sources. While this does not provide a total solution, users’ burden to configure softwares and databases is certainly relieved. Alternatively, PaaS and SaaS can be more user friendly models. However, the field of bioinformatics changes very fast and PaaS and SaaS models have not been successful for bio/medical application since service providers need to constantly re-configure PaaS and SaaS based cloud systems. We will discuss the cloud service model issue later in depth. In addition to the service model issues, due to the nature of cloud computing being a third party service, cloud service is still being questioned for other issues such as security and system outage.</p>
</sec>
<sec id="Sec5_8">
<title>Advent of cloud systems for bio/medical informatics</title>
<p>The availability of high resolution, high throughput data from the NGS technologies has begun to transform conventional biological sciences to data-driven sciences. A number of very large scale science projects were launched to measure and accumulate data for genetic and epigenetic events, rather than starting from specific scientific questions. Examples of such projects include Encyclopedia of DNA Elements (ENCODE) [
<xref ref-type="bibr" rid="CR5_8">5</xref>
], modENCODE [
<xref ref-type="bibr" rid="CR6_8">6</xref>
], The Cancer Genome Atlas (TCGA) [
<xref ref-type="bibr" rid="CR7_8">7</xref>
], and the 1000 Genome project [
<xref ref-type="bibr" rid="CR8_8">8</xref>
]. From the deluge of the NGS data, analyzing and mining this big data is the key issue of the current research trend. Since only a handful of large research organizations can afford computer facility to utilize such data, many researchers have turned their attention to the potential benefits of cloud computing to handle biological data.</p>
<p>Many bio/medical cloud systems have emerged and some systems began to meet increased biological and computational needs. Most bio/medical cloud systems provide simple command-line execution of scripts or pipelines to the user. Although they are systems for elementary, a single task, they are well-suited for the IaaS concept of cloud computing as users can configure systems with the capacity to analyze the data. Some bio/medical cloud systems are more tightly coupled with cloud resources. Existing non-cloud applications have been redesigned to launch service on the cloud by utilizing features of cloud computing such as flexible resource allocation on demands, automatic system configuration, cost efficiency, and unlimited resources.</p>
<p>Recently bio/medical cloud services have begun evolving from simple and primitive applications to offering integrated and complex systems. This is because researchers have begun to formulate comprehensive scientific questions by utilizing data from various cellular events. This requires integration of various tools and biological databases. To keep pace with this trend, the cloud service providers have widely used computational tools and databases pre-installed and also provided libraries that can be used to access data from the source directly. Thus users have begun utilizing bioinformatics cloud service not only without worrying about the manual system installation and data integration processes, but also with reduced data uploading/transferring time.</p>
<sec id="Sec6_8">
<title>Survey of current bio/medical cloud systems</title>
<p>In this section we survey current bio/medical cloud systems in terms of user interface (UI), extensibility and data integration.</p>
<p>Taverna [
<xref ref-type="bibr" rid="CR9_8">9</xref>
] is a workflow management system that provides interoperability between cloud and various types of research projects in multiple disciplines, such as astronomy, bioinformatics, chemistry and music composition. Through the Taverna web portal, users can upload their input data to the cloud and invoke multiple computing units. While the analysis is being performed, the user can monitor the progress and when the analysis is complete, the web portal gets notifications. Taverna also allows the user to define how the data flows between services or pipelines by composing a graphical workflow diagram. This is done by drag and dropping resources from specific function blocks. Optionally, Taverna allows workflows to be composed and run by using a command interface. Once a workflow is composed, it can be shared with other researchers for collaboration. Since Taverna’s usage is designed for multiple science disciplines, it is not tailored for biology applications and some biological tools may not be present, in which the user need to provide them. Nevertheless, in the bioinformatics community, many projects preferably used Taverna as the workflow supporting analysis tool.</p>
<p>FX [
<xref ref-type="bibr" rid="CR10_8">10</xref>
] is another recently released cloud system that provides a user-friendly web-based interface to provide high usability of biological tools for users who are not familiar with softwares. Utilizing the cloud computing infrastructure, FX provides analysis tasks such as estimating gene expression level and genomic variant calling from the RNA-seq reads using transcriptome-based references. Based on the Amazon Web Service (AWS), it provides a web-based working environment where the user can upload data and configure analysis settings based on options that the system provides. The analysis steps are however not as flexibly arrangeable as the workflow composing systems, but may be set with specific parameters for each analysis task (e.g., hit count for SNP, INDEL or alignment options). Since it is designed for specific tasks, it doesn’t require manual arrangement of function pipelines. Parameter settings and execution of the analysis are done by using a web-interface.</p>
<p>Systems such as Galaxy [
<xref ref-type="bibr" rid="CR11_8">11</xref>
] are designed to provide complex multi-functioned open research frameworks. Galaxy offers generalized tools and libraries as analysis components. With a functional built-in workflow composer followed by fundamental editing tools, Galaxy allows users to construct user-defined pipelines. Galaxy also has its own visualization functionality that shows the progression of the workflow. Instead of fixed analysis tools and purpose, users may contribute additional tools (i.e., pipelines or function blocks) to the Tool Shed repository provided by Galaxy, extending the functionality of Galaxy. The Galaxy Tool Shed enables creating and sharing of Galaxy tools across the Galaxy community. Galaxy integrates multiple biological DBs, such as UCSC table data, BioMart Central, and modENCODE server.</p>
<p>Similarly SeqWare [
<xref ref-type="bibr" rid="CR12_8">12</xref>
] is also a large biological workbench that provide an open workframe like Galaxy. In terms of extensibility, SeqWare supports the tool extension function, allowing users to write pipeline modules in Java. SeqWare provides four tools specifically designed to be compliant with massive parallel sequencing technologies (e.g., Illumina, ABI SOLiD, and 454), a web application (i.e., Laboratory Information Management System (LIMS)), pipelines for processing and annotating sequenced data, a query tool (SeqWare Query Engine), and a MetaDB that provides a common database to store the metadata used by all components. The SeqWare MetaDB imports data from other DBs and adds the metadata for further analysis. Hence, different DBs can be integrated and semi-unified to enable utilization of such data using different tools (or pipelines) provided by SeqWare, without worrying about data handling at each analysis step.</p>
<p>DNAnexus [
<xref ref-type="bibr" rid="CR13_8">13</xref>
] like Galaxy supports data integration features in the system. DNAnexus is designed for the next generation sequencing data management, and it is also integrated with LIMS systems that can directly pass the experiment metadata to the system. One of the key benefits of integrating the external data with the system is that it supports automatic data conversion, which is then easily processed by various analysis tools. Research utilizing data from multiple sources often suffers from incompatible data formats and types. Manual data conversion for integrated analysis is not only a huge burden and a time consuming task but it also prevents automation of analysis tasks. Hence, data integration, along with data conversion, is an important feature of bio/medical cloud systems.</p>
<p>Another cloud based system, BioVLab [
<xref ref-type="bibr" rid="CR14_8">14</xref>
,
<xref ref-type="bibr" rid="CR15_8">15</xref>
], is coupled with a graphical workflow composer called XBaya [
<xref ref-type="bibr" rid="CR16_8">16</xref>
]. We review the BioVLab architecture later to provide detailed discussion on the design features and also to discuss the concept of the environment.</p>
<p>There are bio/medical cloud systems that serve as a virtual operating system with pre-installed packages and libraries required for analysis. CloVR [
<xref ref-type="bibr" rid="CR17_8">17</xref>
] is a virtual machine with a specific purpose for analyzing biological data, such as large-scale on-demand BLAST searches, whole-genome assembly, gene finding and 16S ribosomal RNA sequence analysis. CloVR is implemented as a standalone workbench and an online application over the Internet. However, CloVR does not provide a good UI like workflow composers. Instead, CloVR provides command-line based automated analysis pipelines using pre-configured software packages for composing workflows. Such pre-configured software packages may be arranged in sequential or parallel manner as a workflow for analysis and it can be executed within a single virtual system. CloudBioLinux [
<xref ref-type="bibr" rid="CR18_8">18</xref>
] is a Linux distribution with a pre-installed analysis packages and libraries available as an image loaded on the cloud. As an open source project, researchers and developers can extend the pool of libraries and packages.</p>
<p>We now survey cloud based systems that are designed for single or a few tasks rather than for providing analysis environments. Examples of systems of this type are CloudRSD, the cloud version of Roundup [
<xref ref-type="bibr" rid="CR19_8">19</xref>
], CloudBurst [
<xref ref-type="bibr" rid="CR20_8">20</xref>
], and Crossbow [
<xref ref-type="bibr" rid="CR21_8">21</xref>
]. CloudRSD is a reciprocal smallest distance algorithm to compute orthologs using RSD on the cloud. It uses the maximum likelihood of the evolutionary distance to compute an ortholog score.</p>
<p>Cloudburst is a cloud version of RMAP, a well-known short-read alignment tool. It utilizes the MapReduce [
<xref ref-type="bibr" rid="CR22_8">22</xref>
] framework, Hadoop [
<xref ref-type="bibr" rid="CR23_8">23</xref>
], to map short reads to reference genomes in a parallel fashion utilizing the cloud environment. Cloudburst allows any number of mismatches or differences, and reports either all alignments or the best alignment for each read.</p>
<p>Crossbow is a package consisting of Bowtie [
<xref ref-type="bibr" rid="CR24_8">24</xref>
], a fast and memory efficient read aligner, and SoapSNP [
<xref ref-type="bibr" rid="CR25_8">25</xref>
], a consensus sequence builder and genotyper. It uses Amazon’s Elastic MapReduce [
<xref ref-type="bibr" rid="CR26_8">26</xref>
] for parallel computation. It is shown that Crossbow can analyze over 35 fold the coverage of human genome in three hours with a 320-core cluster on the Amazon cloud.</p>
<p>eCEO designed and implemented a Cloud-based Epistasis cOmputing (eCEO) model for large scale epistatic interaction in genome-wide association study (GWAS) [
<xref ref-type="bibr" rid="CR27_8">27</xref>
]. GWAS study needs to consider a large number of combinations of SNPs, which requires huge computing power. The eCEO model has shown its power to compute GWAS in terms of phenotypes using cloud computing.</p>
<p>Table
<xref rid="Tab1" ref-type="table">1</xref>
shows comparison of features of cloud-based bio/medical applications. Features that are considered for comparison among each application are: ‘Graphical UI’ for the frontend graphical interface, ‘External data integration’ for the availability of external data or databases for analysis, ‘Security’ for security features used for securing data or transactions of analysis processes, ‘Extensibility’ for the system feature that allows users to implement their own analysis functions in extend to the cloud application and ‘Cloud usage’ for adopting the cloud system.
<table-wrap id="Tab1">
<label>Table 1</label>
<caption>
<p>
<bold>Comparison of bio/medical cloud systems</bold>
</p>
</caption>
<table frame="hsides" rules="groups">
<thead>
<tr>
<th align="left">Cloud application</th>
<th align="left">Graphical UI</th>
<th align="left">External data integration</th>
<th align="left">Security</th>
<th align="left">Extensibility</th>
<th align="left">Cloud Usage</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left">BioVLab</td>
<td align="left">Xbaya</td>
<td align="left">O</td>
<td align="left">MyProxy, AWS Credential</td>
<td align="left">GFac</td>
<td align="left">Pre-built system</td>
</tr>
<tr>
<td align="left">Cloudburst</td>
<td align="left">-</td>
<td align="left">-</td>
<td align="left">AWS Credential</td>
<td align="left">-</td>
<td align="left">Parallel processing</td>
</tr>
<tr>
<td align="left">Cloud Bio Linux</td>
<td align="left">-</td>
<td align="left">-</td>
<td align="left">AWS Credential</td>
<td align="left">-</td>
<td align="left">Pre-built system</td>
</tr>
<tr>
<td align="left">Cloud RSD</td>
<td align="left">-</td>
<td align="left">-</td>
<td align="left">AWS Credential</td>
<td align="left">-</td>
<td align="left">Parallel processing</td>
</tr>
<tr>
<td align="left">CloVR</td>
<td align="left">CloVR portal</td>
<td align="left">-</td>
<td align="left">AWS Credential</td>
<td align="left">-</td>
<td align="left">Pre-built system</td>
</tr>
<tr>
<td align="left">Crossbow</td>
<td align="left">-</td>
<td align="left">-</td>
<td align="left">AWS Credential</td>
<td align="left">-</td>
<td align="left">Parallel processing</td>
</tr>
<tr>
<td align="left">DNAnexus</td>
<td align="left">DNAnexus Web</td>
<td align="left">O</td>
<td align="left">ISO 27002</td>
<td align="left">-</td>
<td align="left">Computing resource</td>
</tr>
<tr>
<td align="left">Galaxy</td>
<td align="left">Galaxy Web</td>
<td align="left">O</td>
<td align="left">AWS Credential</td>
<td align="left">Tool Shed</td>
<td align="left">Pre-built system</td>
</tr>
<tr>
<td align="left">Myrna</td>
<td align="left">-</td>
<td align="left">-</td>
<td align="left">AWS Credential</td>
<td align="left">-</td>
<td align="left">Parallel processing</td>
</tr>
<tr>
<td align="left">SeqWare</td>
<td align="left">SeqWare Portal</td>
<td align="left">O</td>
<td align="left">GnuPG</td>
<td align="left">Java Modules</td>
<td align="left">Computing resource</td>
</tr>
<tr>
<td align="left">Taverna</td>
<td align="left">Taverna Workbench</td>
<td align="left">O</td>
<td align="left">WS-Security</td>
<td align="left">API consumer tool</td>
<td align="left">Interoperability</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<p>This is a comparison table of bio/medical cloud systems in terms on their features.</p>
</table-wrap-foot>
</table-wrap>
</p>
</sec>
</sec>
<sec id="Sec7_8">
<title>Bio/medical cloud environment</title>
<p>In this section, we discuss design issues of bio/medical cloud systems and then introduce a concept of “cloud environment” for bio/medical applications.</p>
<sec id="Sec8_8">
<title>Limitation of current bio/medical cloud systems</title>
<p>Although cloud-based bioinformatics systems are gaining attention, there are several important system design issues that should be resolved to be useful in practice. System usability is the main system design issue for bio/medical cloud systems. Although many cloud systems relieve users’ burden for system configurations and try to improve system usability, it is still challenging to perform complicated analysis tasks by combining multiple tools and databases. Handling big input data is an open problem. Delivering analysis results (output from the analysis tasks) is also an open problem that needs to be studied extensively.</p>
<p>Another important issue comes from a plethora of bioinformatics resources and the breadth of the bio/medical fields. Since there are too many bioinformatics tools and databases, it is very difficult even for bioinformatics experts to identify which tools can be used for specific research or clinical purposes, locate, install, and assemble them. As of now, there is little effort to handle this situation. System extensibility is also an important issue. For example, consider a situation where a scientist believes that a new bioinformatics tool is most suitable for a scientific goal. How can she/he hook in the tool to existing bioinformatics cloud systems?</p>
<p>Some bioinformatics cloud systems are designed to address these issues and we will describe BioVLab systems that use a graphical workflow composer, as an example of systems whose design goals are to address these issues.</p>
</sec>
<sec id="Sec9_8">
<title>BioVLab: Virtual Collaborative Lab for Bio/medical Applications</title>
<p>BioVLab [
<xref ref-type="bibr" rid="CR28_8">28</xref>
] is a computational infrastructure on the cloud, coupled with a graphical workflow composer. It is a three layer architecture where a graphical workflow composer and web browsers are used at the user front end, a cloud is used as a computing server, and all necessary controls are done at the gateway server at the middle layer. One important goal of the BioVLab infrastructure is to develop and implement a novel system design principle for genome analysis by utilizing the
<italic>virtual collaborative lab</italic>
, a suite of tools that give a team of scientists the ability to orchestrate a sequence of data analysis tasks using remote computing resources and data storage facilities “on-demand” from the scientists’ desktop computers. The virtual lab also addresses how to dynamically configure a virtual system tailored to a specific research project by combining multiple computational tools and resources using the drag-and-drop workflow composer and genome data type. The system design principle is to provide a new, effective paradigm for small biology research labs to handle the ever-increasing amount of biological data. The current BioVLab uses Amazon EC2 and S3 as cloud computing and XBaya as a graphical workflow composer.</p>
</sec>
<sec id="Sec10_8">
<title>The three layer architecture in BioVLab</title>
<p>The first layer, XBaya is a graphical workflow engine that enables the composition and management of scientific workflows on a desktop. The XBaya window consists of four panels as shown in Figure
<xref rid="Fig1" ref-type="fig">1</xref>
. On the top left is a panel for resources that are pre-assembled in connection with a gateway server. XBaya’s enhanced user interface simplifies composition of a workflow using scientific applications by drag-and-dropping tools and databases on the top left resource panel. Information for each resource component in the resource panel is displayed in the left bottom panel. These resource components, tools and databases are compiled for specific analysis task. Selection of these resources often requires expert knowledge for the analysis task. The compilation of these resources can help users or the workflow composer to focus only on resources that are needed for the task. By selecting a resource in the resource panel and drag-and-dropping each resource to the top right workflow panel, the user can easily compose a workflow using the resources in the resource panel. In the workflow panel, the output from a resource icon can be input to another resource icon if the input and output types are compatible. The bottom right panel is a console that monitors the execution of a workflow, showing which application (icon) is being executed and also ensuring the execution of each application by repeatedly trying the execution of each application if not successful. The execution is monitored in connection with the gateway server in an asynchronous way so that a long running workflow can be monitored. XBaya sends a request for the computation to the middle layer, and then the gateway in turn ensures the execution of an application on the cloud using the Web Service Definition Language (WDSL). The modular architecture of BioVLab is built on top of the Open Grid Computing Environments (OGCE) toolkit, that provides a web interface, database, and pub/sub system. Middle layer is a gateway that consists of Gfac, XRegistry, OGCE, and the Pub/Sub system. All resource components used in the workflow for a certain project should be registered at the gateway using XRegistry. Gfac is an application factory service for wrapping command-line tools as Web services. Utilizing the Gfac and Xregistry services, BioVlab allows users to integrate their own tools to the system or to include existing tools for the analysis task. This way, Biovlab handles system extensibility issues. The Pub/Sub system is a publish-subscribe based message broker implemented on top of Apache Axis2 web services stack. It implements the web service eventing and web service notifications specifications and incorporates a message box component that facilities communications with clients behind firewalls and overcomes network glitches (
<ext-link ext-link-type="uri" xlink:href="http://airavata.apache.org/">http://airavata.apache.org/</ext-link>
). Figure
<xref rid="Fig2" ref-type="fig">2</xref>
shows the illustration of the three-layered architecture of the BioVLab system.
<fig id="Fig1">
<label>Figure 1</label>
<caption>
<p>
<bold>BioVLab-MMIA workflow execution in XBaya.</bold>
</p>
</caption>
<graphic xlink:href="13755_2012_8_Fig1_HTML" id="d30e731"></graphic>
</fig>
<fig id="Fig2">
<label>Figure 2</label>
<caption>
<p>
<bold>Three-layered architecture of BioVLab system.</bold>
The first layer is XBaya, graphical workflow composer, the second layer is gateway, and the third layer is cloud environment.</p>
</caption>
<graphic xlink:href="13755_2012_8_Fig2_HTML" id="d30e743"></graphic>
</fig>
</p>
</sec>
<sec id="Sec11_8">
<title>Bio/medical cloud environment with BioVLab</title>
<p>On top of the BioVLab infrastructure, several systems have been built and they are available for researchers. For a specific research task, all necessary tools and databases are pre-installed as a virtual machine image. The availability of such machine image removes the user’s burden to collect and install resources and compose a workflow. In addition, the loaded biological big resources by the cloud vendors makes cloud-based systems easy to use. A workflow is pre-composed using the resources so that users do not have to survey, locate, install computational tools and databases. This way, a cloud environment for a specific science project is constructed and served to the public. Having the cloud environment for a specific science project, scientists can easily perform an analysis task by simply downloading a pre-composed workflow, creating an account on the Amazon cloud, and executing the workflow with the user’s own data. This download-workflow-and-execute computing model is a very easy to use cloud service for a specific science project. In addition, an expert user can modify the pre-composed workflow using the Xbaya workflow composer. Biovlab handles the usability issue by providing the download-and-execute pre-composed workflow model and the extensibility issue by utilizing a workflow where the user can modify the pre-composed workflow using pre-collected resources.</p>
<p>Two systems, BioVLab-MMIA and BioVLab-mCpG, are developed using the BioVLab infrastructure.</p>
<p>MMIA (MicroRNA and MRNA Integrated Analysis) [
<xref ref-type="bibr" rid="CR29_8">29</xref>
] is a web-based analysis tool for the integrated analysis of microRNA and mRNA expression data. The complexity of the analysis comes from the fact that two different genetic elements are of different types and also from the fact that information about their relationship of microRNA’s target genes are inaccurate. Since microRNA degrades their target genes, MMIA utilizes inversely correlated expression patterns between microRNA and mRNA (perfect seed-pairing between microRNA and mRNA is associated with mRNA destabilization) and reports the results of two computational analyses. Migrating the functionality of MMIA to BioVLab as a biological cloud environment was recently done. Based on the architecture of BioVLab, MMIA’s analysis is performed over the cloud, which was formerly done locally or over a server. Expression data of microRNA and mRNA are uploaded to the cloud via the Amazon S3 Interface, which are analyzed and reported back to the user. The reference genome data, hg18, is pre-loaded on the cloud, which is downloaded from the UCSC genome browser. Once users have the input files on Amazon S3, access control for the Amazon S3 bucket (ACLs) is prepared for analysis execution. Parameter configuration, including workflows, for the analysis may be done via the web page generated by the Amazon S3 component for the specific user. The results are provided in the Amazon S3 buckets, which are accessible by clicking the View icon in the XBaya workflow or through the web browser. BioVLab-MMIA cloud is available as Amazon Machine Id: ami-957291fc.</p>
<p>BioVLab-mCpG [
<xref ref-type="bibr" rid="CR30_8">30</xref>
] performs integrated analyses of DNA methylation, sequence variation, and gene expression for phenotypically distinct cell lines. Methylation profiling of genomes and sequence variation detection (i.e., SNPs) on a genome scale can be routinely done using next generation sequencing and microarray technologies. An integrated analysis of global methylation, SNPs, and gene expression profiles would have the potential to reveal biological relationships between altered cytosine methylation, sequence variations, and mRNA levels. In BioVLab-mCpG, pre-composed workflows for the integrated analysis are performed, beginning with differentially expressed genes, differentially methylated regions, and information theoretic-integrated analysis of DNA methylation and sequence variation data. Furthermore, the integrated analysis can be performed using input gene sets for specific biological pathways of interest. BioVLab-mCpG is implemented using R, Perl, and Python programming languages and utilizes Samtools [
<xref ref-type="bibr" rid="CR31_8">31</xref>
], the MACS peak finding package [
<xref ref-type="bibr" rid="CR32_8">32</xref>
], and the Bioconductor package [
<xref ref-type="bibr" rid="CR33_8">33</xref>
]. By deploying the package on the Amazon EC2 Cloud Computing as an Amazon machine image, users can simply use the image to perform the integrated analysis, thereby ensuring that the integrated analysis package is readily available to the entire research community.</p>
</sec>
</sec>
<sec id="Sec12_8">
<title>Standardization and security</title>
<p>In addition to cloud features that we have discussed so far, there are remaining important issues for bio/medical cloud systems, such as standardization and security. Without resolving these issues, many companies and research facilities can hardly use cloud systems even if cloud systems become powerful enough to handle bio/medical big data. Standardization of tools and data formats is required for massive and parallel analysis of bio/medical bio data. Otherwise analysis tasks of multiple types can be hardly composed and performed by mundane users.</p>
<p>Security is the most sensitive issue since biomedical data has personal information that has legal and ethical repercussions. Because a cloud system is a third-party service provider, users may not be comfortable allowing expensive pre-analyzed and personal data stored in cloud systems. Appropriate authentication for the entire analysis process, while providing automatic execution of multi-step analysis tasks, is very important. BioVLab uses MyProxy from the TeraGrid project for authentication. However, this is still primitive. Recently there has been interesting approach that uses a novel hybrid MapReduce on the private and public cloud [
<xref ref-type="bibr" rid="CR34_8">34</xref>
] by partitioning genome sequence data on the public and private spaces where computationally intensive tasks are performed on the public cloud using encrypted data and computation with sensitive data is performed on the private cloud utilizing computational results on the public cloud.</p>
<p>We believe that there will be more interesting approaches for standardization and security issues on the cloud.</p>
</sec>
</sec>
<sec id="Sec13_8" sec-type="conclusions">
<title>Conclusions</title>
<p>The analysis of big data in the bio and medical fields requires very big computing power and many research facilities and clinics are unable to afford such computing facilities. Thus cloud computing has gained great interest in the bio and medical fields to analyze big data and a growing number of bioinformatics cloud systems have been developed. In this paper we surveyed current bioinformatics cloud systems and discussed design issues. To handle big data of multiple types, analysis tasks require use of appropriate tools and databases from a vast number of tools and databases. Thus simply using cloud computing does not resolve the issue of big data analysis in the bio and medical fields. We discussed this issue by introducing a concept of cloud environment for specific scientific research goals.</p>
</sec>
<sec id="Sec14_8">
<title>Authors’ information</title>
<p>Chae, H. is a Ph.D candidate in Computer Science Department, School of Informatics and Computing, Indiana University at Bloomington (IUB). After receiving his M.S. degree in Computer Science in 2007 from IUB, his research interest has lain mainly in Systems in Bioinformatics. He recently joined Bioinformatics Institute in Seoul National University (SNU) as a researcher and working in development of cloud-based biological systems.</p>
<p>Jung, I. received his M.S. degree from the Department of Computer Science at Yonsei University in 2007 with a major interest in sensor networks. He has been with LG Electronics as a research engineer for 4G LTE and WiMAX standards. He know has interest in bioinformatic technologies and is currently researching at the Interdisciplinary Program in Bioinformatics in Seoul National University.</p>
<p>Hyungro Lee received BSc degree from the Sungkyunkwan University, Seoul, Korea, in 2007 and MSc degree from the Indiana University, Bloomington, IN, in 2010. Since September of 2010, he is following a doctoral track in Computer Science at Indiana University Bloomington and he is working as a researcher of the FutureGrid project, an NSF funded significant new experimental computing grid and cloud test-bed to the research community, together with user supports. His research interests are parallel and distributed systems, and cloud computing.</p>
<p>Suresh Marru (
<ext-link ext-link-type="uri" xlink:href="http://people.apache.org/~smarru/">http://people.apache.org/~smarru/</ext-link>
) directs the Science Gateways program within the NSF funded Extreme Science and Engineering Discovery Environment (XSEDE). In this role he is responsible for specialized scientific community interfaces to large scale cyberinfrastructure. Marru is also the principal research systems architect within Pervasive Technology Institute of Indiana University and is a founding member of the Apache Airavata project management committee. Marru’s current research focuses on working alongside multidisciplinary experts in the field of eScience to developed open community driven web and service-based scientific workflow and gateway systems for individual research, collaboration, outreach, and cross-disciplinary collaboration. These systems assist scientists to focus on their research without the need to be distracted my emerging information technology and cyberinfrastructure.</p>
<p>Seong-Whan Lee is the Hyundai-Kia Motor Chair Professor at Korea University, where he is the head of the Department of Brain and Cognitive Engineering and the director of the Institute for Brain and Cognitive Engineering. He received the B.S. degree in computer science and statistics from Seoul National University, Seoul, Korea, in 1984, and the M.S. and Ph.D. degrees in computer science from Korea Advanced Institute of Science and Technology in 1986 and 1989, respectively. His research interests include pattern recognition, computer vision, and brain engineering. He has more than 250 publications in international journals and conference proceedings, and authored 10 books.</p>
<p>Sun Kim is an associate professor at Seoul National University and director of Bioinformatics Institute in Seoul National University (SNU). Before joining SNU, he was Chair of Faculty Division-C, Director of Center for Bioinformatics Research, an Associate Professor in School of Informatics and Computing, an Adjunct Associate Professor of Cellular and Integrative Physiology, Medical Sciences Program at Indiana University (IU) - Bloomington. Prior to IU, he worked at DuPont Central Research from 1998 to 2001, and at the University of Illinois at Urbana-Champaign from 1997 to 1998. Sun Kim received B.S and M.S and Ph.D in Computer Science from Seoul National University, Korea Advanced Institute of Science and Technology (KAIST), and the University of Iowa respectively. He is on the board of directors for ACM SIG Bioinformatics, vice chair for education at IEEE Technical Committee on Computational Life Sciences (TCCLS), co-editor for International Journal of Data Mining and Bioinformatics, and co-organizing many scientific meetings including ACM Conference on Bioinformatics, Computational Biology, and Biomedicine 2011, IEEE International Conference on Bioinformatics and Biomedicine (BIBM) 2008 and 2009.</p>
</sec>
</body>
<back>
<fn-group>
<fn>
<p>
<bold>Competing interests</bold>
</p>
<p>The authors declare that they have no competing interests.</p>
</fn>
<fn>
<p>
<bold>Authors’ contributions</bold>
</p>
<p>HC and SK defined the scope of the paper and drafted the manuscript. IJ participated in drafting the bio health cloud feature part. HL participated in drafting the BioVLab part. SM participated in drafting the cloud computing part. SWL participated in drafting the cloud systems’ trend. All authors read and approved the final manuscript.</p>
</fn>
</fn-group>
<ack>
<title>Acknowledgements</title>
<p>This work was supported by the new faculty research support grant from Seoul National University (SNU). Thank you to all members in the Bio and Health Informatics lab at SNU for their great support.</p>
<p>This work was also supported by the World Class University Program through the National Research Foundation of Korea funded by the Ministry of Education, Science, and Technology, under Grant R31-10008 and Next-Generation Information Computing Development Program through the National Research Foundation of Korea(NRF) funded by the Ministry of Education, Science and Technology (No.2012M3C4A7033341).</p>
</ack>
<ref-list id="Bib1">
<title>References</title>
<ref id="CR1_8">
<label>1.</label>
<mixed-citation publication-type="other">
<bold>Life-techologies, Bechtop Ion Proton</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://www.lifetechnologies.com/global/en/home/about-us/news-gallery/press-releases/2012/life-techologies-itroduces-the-bechtop-io-proto.html">http://www.lifetechnologies.com/global/en/home/about-us/news-gallery/press-releases/2012/life-techologies-itroduces-the-bechtop-io-proto.html</ext-link>
]</mixed-citation>
</ref>
<ref id="CR2_8">
<label>2.</label>
<mixed-citation publication-type="other">
<bold>Pacific Biosciences</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://www.pacificbiosciences.com/">http://www.pacificbiosciences.com/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR3_8">
<label>3.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kanz</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Aldebert</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Althorpe</surname>
<given-names>N</given-names>
</name>
<name>
<surname>Baker</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Baldwin</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Bates</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Browne</surname>
<given-names>P</given-names>
</name>
<name>
<surname>van den Broek</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Castro</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Cochrane ea</surname>
<given-names>G</given-names>
</name>
</person-group>
<article-title>The EMBL Nucleotide Sequence Database</article-title>
<source>Nucleic Acids Res</source>
<year>2005</year>
<volume>33</volume>
<fpage>D29</fpage>
<lpage>D33</lpage>
<pub-id pub-id-type="doi">10.1093/nar/gki098</pub-id>
<pub-id pub-id-type="pmid">15608199</pub-id>
</element-citation>
</ref>
<ref id="CR4_8">
<label>4.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Stein</surname>
<given-names>LD</given-names>
</name>
</person-group>
<article-title>The case for cloud computing in genome informatics</article-title>
<source>Genome Biol</source>
<year>2010</year>
<volume>11</volume>
<fpage>207</fpage>
<pub-id pub-id-type="doi">10.1186/gb-2010-11-5-207</pub-id>
<pub-id pub-id-type="pmid">20441614</pub-id>
</element-citation>
</ref>
<ref id="CR5_8">
<label>5.</label>
<mixed-citation publication-type="other">
<bold>Encyclopedia of DNA Elements (ENCODE) Project</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://genome.ucsc.edu/ENCODE/">http://genome.ucsc.edu/ENCODE/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR6_8">
<label>6.</label>
<mixed-citation publication-type="other">
<bold>modENCODE Project</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://www.modencode.org/">http://www.modencode.org/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR7_8">
<label>7.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<collab>Network TCGAR</collab>
</person-group>
<article-title>Comprehensive genomic characterization defines human glioblastoma genes and core pathways</article-title>
<source>Nature</source>
<year>2008</year>
<volume>455</volume>
<fpage>1061</fpage>
<lpage>1068</lpage>
<pub-id pub-id-type="doi">10.1038/nature07385</pub-id>
<pub-id pub-id-type="pmid">18772890</pub-id>
</element-citation>
</ref>
<ref id="CR8_8">
<label>8.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Siva</surname>
<given-names>N</given-names>
</name>
</person-group>
<article-title>1000 Genomes project</article-title>
<source>Nat Biotechnol</source>
<year>2008</year>
<volume>26</volume>
<fpage>256</fpage>
<pub-id pub-id-type="pmid">18327223</pub-id>
</element-citation>
</ref>
<ref id="CR9_8">
<label>9.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Oinn</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Addis</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Ferris</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Marvin</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Senger</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Greenwood</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Carver</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Glover</surname>
<given-names>KPM</given-names>
</name>
<name>
<surname>Wipat</surname>
<given-names>ALP</given-names>
</name>
</person-group>
<article-title>Taverna: a tool for the composition and enactment of bioinformatics workflows</article-title>
<source>Bioinformatics</source>
<year>2004</year>
<volume>20</volume>
<fpage>3045</fpage>
<lpage>3054</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/bth361</pub-id>
<pub-id pub-id-type="pmid">15201187</pub-id>
</element-citation>
</ref>
<ref id="CR10_8">
<label>10.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hong</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Rhie</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Park</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Ju</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Yu</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Bleazard</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Park</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Rhee</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Chong</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>I</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Seo</surname>
<given-names>J</given-names>
</name>
</person-group>
<article-title>FX: an RNA-Seq analysis tool on the cloud</article-title>
<source>Bioinformatics</source>
<year>2012</year>
<volume>28</volume>
<fpage>721</fpage>
<lpage>723</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/bts023</pub-id>
<pub-id pub-id-type="pmid">22257667</pub-id>
</element-citation>
</ref>
<ref id="CR11_8">
<label>11.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Giardine</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Riemer</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Hardison</surname>
<given-names>RC</given-names>
</name>
<name>
<surname>Burhans</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Elnitski</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Shah</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Blankenberg</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Albert</surname>
<given-names>I</given-names>
</name>
<name>
<surname>Taylor</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Miller</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Kent</surname>
<given-names>WJ</given-names>
</name>
<name>
<surname>Nekrutenko</surname>
<given-names>A</given-names>
</name>
</person-group>
<article-title>Galaxy: a platform for interactive large-scale genome analysis</article-title>
<source>Genome Res</source>
<year>2005</year>
<volume>15</volume>
<fpage>1451</fpage>
<lpage>1455</lpage>
<pub-id pub-id-type="doi">10.1101/gr.4086505</pub-id>
<pub-id pub-id-type="pmid">16169926</pub-id>
</element-citation>
</ref>
<ref id="CR12_8">
<label>12.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>O’Connor</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Merriman</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Nelson</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>SeqWare Query Engine: storing and searching sequence data in the cloud</article-title>
<source>BMC Bioinformatics</source>
<year>2010</year>
<volume>11</volume>
<fpage>S2</fpage>
<pub-id pub-id-type="doi">10.1186/1471-2105-11-S12-S2</pub-id>
<pub-id pub-id-type="pmid">21210981</pub-id>
</element-citation>
</ref>
<ref id="CR13_8">
<label>13.</label>
<mixed-citation publication-type="other">
<bold>DNAnexus</bold>
[
<ext-link ext-link-type="uri" xlink:href="https://dnanexus.com/">https://dnanexus.com/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR14_8">
<label>14.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Lee</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Chae</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Nam</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Choi</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Tangchaisin</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Herath</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Marru</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Nephew</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>BioVLAB-MMIA: A Reconfigurable Cloud Computing Environment for microRNA and mRNA Integrated Analysis</article-title>
<source>IEEE International Conference on Bioinformatics and Biomedicine (IEEE BIBM 2011)</source>
<year>2011</year>
<publisher-loc>Atalanta, GA</publisher-loc>
<publisher-name>IEEE</publisher-name>
</element-citation>
</ref>
<ref id="CR15_8">
<label>15.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lee</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Chae</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Nam</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Choi</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Tangchaisin</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Herath</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Marru</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Nephew</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>BioVLAB-MMIA: A Cloud Environment for microRNA and mRNA Integrated Analysis (MMIA) on Amazon EC2</article-title>
<source>IEEE Trans Nanobioscience 11</source>
<year>2012</year>
<volume>11</volume>
<fpage>266</fpage>
<lpage>272</lpage>
<pub-id pub-id-type="doi">10.1109/TNB.2012.2212030</pub-id>
</element-citation>
</ref>
<ref id="CR16_8">
<label>16.</label>
<mixed-citation publication-type="other">
<bold>XBaya: A Graphical Workflow Composer for Web Services</bold>
[
<ext-link ext-link-type="uri" xlink:href="https://cwiki.apache.org/confluence/display/AIRAVATA/XBaya">https://cwiki.apache.org/confluence/display/AIRAVATA/XBaya</ext-link>
]</mixed-citation>
</ref>
<ref id="CR17_8">
<label>17.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Angiuoli</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Matalka</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Gussman</surname>
<given-names>A</given-names>
</name>
<name>
<surname>Galens</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Vangala</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Riley</surname>
<given-names>D</given-names>
</name>
<name>
<surname>White</surname>
<given-names>J</given-names>
</name>
<name>
<surname>White</surname>
<given-names>O</given-names>
</name>
<name>
<surname>Fricke</surname>
<given-names>W</given-names>
</name>
<collab>C A</collab>
</person-group>
<article-title>CloVR: a virtual machine for automated and portable sequence analysis from the desktop using cloud computing</article-title>
<source>BMC Bioinformatics</source>
<year>2011</year>
<volume>12</volume>
<fpage>356</fpage>
<pub-id pub-id-type="doi">10.1186/1471-2105-12-356</pub-id>
<pub-id pub-id-type="pmid">21878105</pub-id>
</element-citation>
</ref>
<ref id="CR18_8">
<label>18.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Krampis</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Chapman</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Tiwari</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Bicak</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Field</surname>
<given-names>D</given-names>
</name>
<name>
<surname>Nelson</surname>
<given-names>K</given-names>
</name>
<collab>T B</collab>
</person-group>
<article-title>SNP detection for massively parallel whole-genome resequencing</article-title>
<source>BMC Bioinformatics</source>
<year>2012</year>
<volume>13</volume>
<fpage>42</fpage>
<pub-id pub-id-type="doi">10.1186/1471-2105-13-42</pub-id>
<pub-id pub-id-type="pmid">22429538</pub-id>
</element-citation>
</ref>
<ref id="CR19_8">
<label>19.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Deluca</surname>
<given-names>TF</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>IH</given-names>
</name>
<name>
<surname>Pu</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Monaghan</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Peshkin</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Singh</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Wall</surname>
<given-names>DP</given-names>
</name>
</person-group>
<article-title>Roundup: a multi-genome repository of orthologs and evolutionary distances</article-title>
<source>Bioinformatics</source>
<year>2006</year>
<volume>22</volume>
<fpage>2044</fpage>
<lpage>2046</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/btl286</pub-id>
<pub-id pub-id-type="pmid">16777906</pub-id>
</element-citation>
</ref>
<ref id="CR20_8">
<label>20.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Schatz</surname>
<given-names>M</given-names>
</name>
</person-group>
<article-title>Cloudburst: highly sensitive read mapping with mapreduce</article-title>
<source>Bioinformatics</source>
<year>2009</year>
<volume>25</volume>
<fpage>1363</fpage>
<lpage>1369</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/btp236</pub-id>
<pub-id pub-id-type="pmid">19357099</pub-id>
</element-citation>
</ref>
<ref id="CR21_8">
<label>21.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Langmead</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Schatz</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Lin</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Pop</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Salzberg</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Searching for SNPs with cloud computing</article-title>
<source>Genome Biol</source>
<year>2009</year>
<volume>11</volume>
<fpage>R134</fpage>
<pub-id pub-id-type="doi">10.1186/gb-2009-10-11-r134</pub-id>
<pub-id pub-id-type="pmid">19930550</pub-id>
</element-citation>
</ref>
<ref id="CR22_8">
<label>22.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Dean</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Ghemawat</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>MapReduce: simplified data processing on large clusters</article-title>
<source>Proceedings of the 6th conference on Symposium on Operating Systems Design & Implementation</source>
<year>2004</year>
<publisher-loc>San Francisco, CA</publisher-loc>
<publisher-name>ACM</publisher-name>
</element-citation>
</ref>
<ref id="CR23_8">
<label>23.</label>
<mixed-citation publication-type="other">
<bold>Hadoop</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://hadoop.apache.org/">http://hadoop.apache.org/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR24_8">
<label>24.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Langmead</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Trapnel</surname>
<given-names>lC</given-names>
</name>
<name>
<surname>Pop</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Salzberg</surname>
<given-names>S</given-names>
</name>
</person-group>
<article-title>Ultrafast and memory-efficient alignment of short DNA sequences to the human genome</article-title>
<source>Genome Biol</source>
<year>2009</year>
<volume>10</volume>
<issue>3</issue>
<fpage>212</fpage>
<pub-id pub-id-type="doi">10.1186/gb-2009-10-3-r25</pub-id>
<pub-id pub-id-type="pmid">19344490</pub-id>
</element-citation>
</ref>
<ref id="CR25_8">
<label>25.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>R</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Fang</surname>
<given-names>X</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Kristiansen</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>SNP detection for massively parallel whole-genome resequencing</article-title>
<source>Genome Res</source>
<year>2009</year>
<volume>19</volume>
<fpage>1124</fpage>
<lpage>1132</lpage>
<pub-id pub-id-type="doi">10.1101/gr.088013.108</pub-id>
<pub-id pub-id-type="pmid">19420381</pub-id>
</element-citation>
</ref>
<ref id="CR26_8">
<label>26.</label>
<mixed-citation publication-type="other">
<bold>Amazon Elastic MapReduce (Amazon EMR)</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://aws.amazon.com/elasticmapreduce/">http://aws.amazon.com/elasticmapreduce/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR27_8">
<label>27.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wang</surname>
<given-names>Z</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Tan</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Wong</surname>
<given-names>L</given-names>
</name>
<name>
<surname>Agrawal</surname>
<given-names>D</given-names>
</name>
</person-group>
<article-title>eCEO : an efficient Cloud Epistasis cOmputing model in genome-wide association study</article-title>
<source>Bioinformatics</source>
<year>2011</year>
<volume>27</volume>
<fpage>1045</fpage>
<lpage>1051</lpage>
<pub-id pub-id-type="doi">10.1093/bioinformatics/btr091</pub-id>
<pub-id pub-id-type="pmid">21367868</pub-id>
</element-citation>
</ref>
<ref id="CR28_8">
<label>28.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Marru</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Chae</surname>
<given-names>H</given-names>
</name>
<name>
<surname>Tangchaisin</surname>
<given-names>P</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Pierce</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Nephew</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>Transitioning BioVLab cloud workbench to a science gateway</article-title>
<source>Proceedings of the 2011 TeraGrid Conference: Extreme Digital Discovery</source>
<year>2011</year>
<publisher-loc>Salt Lake City, UT</publisher-loc>
<publisher-name>ACM</publisher-name>
<fpage>40:1</fpage>
<lpage>40:2</lpage>
</element-citation>
</ref>
<ref id="CR29_8">
<label>29.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Nam</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Choi</surname>
<given-names>K</given-names>
</name>
<name>
<surname>Balch</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>S</given-names>
</name>
<name>
<surname>Nephew</surname>
<given-names>K</given-names>
</name>
</person-group>
<article-title>MicroRNA and mRNA integrated analysis (MMIA): a web tool for examining biological functions of microRNA expression</article-title>
<source>Nucleic Acids Res</source>
<year>2009</year>
<volume>37</volume>
<fpage>W356</fpage>
<lpage>W362</lpage>
<pub-id pub-id-type="doi">10.1093/nar/gkp294</pub-id>
<pub-id pub-id-type="pmid">19420067</pub-id>
</element-citation>
</ref>
<ref id="CR30_8">
<label>30.</label>
<mixed-citation publication-type="other">
<bold>BioVLAB-mCpG</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://biohealth.snu.ac.kr/mcpg-snp-express/">http://biohealth.snu.ac.kr/mcpg-snp-express/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR31_8">
<label>31.</label>
<mixed-citation publication-type="other">
<bold>SAM (Sequence Alignment/Map) tools</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://samtools.sourceforge.net/">http://samtools.sourceforge.net/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR32_8">
<label>32.</label>
<element-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>T</given-names>
</name>
<name>
<surname>Meyer</surname>
<given-names>CA</given-names>
</name>
<name>
<surname>Eeckhoute</surname>
<given-names>J</given-names>
</name>
<name>
<surname>Johnson</surname>
<given-names>DS</given-names>
</name>
<name>
<surname>Bernstein</surname>
<given-names>BE</given-names>
</name>
<name>
<surname>Nusbaum</surname>
<given-names>C</given-names>
</name>
<name>
<surname>Myers</surname>
<given-names>RM</given-names>
</name>
<name>
<surname>Brown</surname>
<given-names>M</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>W</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>XS</given-names>
</name>
</person-group>
<article-title>Model-based Analysis of ChIP-Seq (MACS)</article-title>
<source>Genome Biol</source>
<year>2008</year>
<volume>9</volume>
<fpage>R137</fpage>
<pub-id pub-id-type="doi">10.1186/gb-2008-9-9-r137</pub-id>
<pub-id pub-id-type="pmid">18798982</pub-id>
</element-citation>
</ref>
<ref id="CR33_8">
<label>33.</label>
<mixed-citation publication-type="other">
<bold>Bioconductor: Open Source Software for Bioinformatics</bold>
[
<ext-link ext-link-type="uri" xlink:href="http://www.bioconductor.org/">http://www.bioconductor.org/</ext-link>
]</mixed-citation>
</ref>
<ref id="CR34_8">
<label>34.</label>
<element-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Chen</surname>
<given-names>Y</given-names>
</name>
<name>
<surname>Peng</surname>
<given-names>B</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>X</given-names>
</name>
<name>
<surname>Tang</surname>
<given-names>H</given-names>
</name>
</person-group>
<article-title>Large-Scale Privacy-Preserving Mappings of Human Genomic Sequences on Hybrid Clouds</article-title>
<source>Proceedings of the 19th Annual Network and Distributed System Security Symposium (NDSS)</source>
<year>2012</year>
<publisher-loc>San Diego, CA</publisher-loc>
<publisher-name>Internet Society</publisher-name>
</element-citation>
</ref>
</ref-list>
</back>
</pmc>
</record>

Pour manipuler ce document sous Unix (Dilib)

EXPLOR_STEP=$WICRI_ROOT/Ticri/CIDE/explor/CyberinfraV1/Data/Pmc/Corpus
HfdSelect -h $EXPLOR_STEP/biblio.hfd -nk 000193 | SxmlIndent | more

Ou

HfdSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd -nk 000193 | SxmlIndent | more

Pour mettre un lien sur cette page dans le réseau Wicri

{{Explor lien
   |wiki=    Ticri/CIDE
   |area=    CyberinfraV1
   |flux=    Pmc
   |étape=   Corpus
   |type=    RBID
   |clé=     PMC:4336112
   |texte=   Bio and health informatics meets cloud : BioVLab as an example
}}

Pour générer des pages wiki

HfdIndexSelect -h $EXPLOR_AREA/Data/Pmc/Corpus/RBID.i   -Sk "pubmed:25825658" \
       | HfdSelect -Kh $EXPLOR_AREA/Data/Pmc/Corpus/biblio.hfd   \
       | NlmPubMed2Wicri -a CyberinfraV1 

Wicri

This area was generated with Dilib version V0.6.25.
Data generation: Thu Oct 27 09:30:58 2016. Site generation: Sun Mar 10 23:08:40 2024