http://mndoci.disqus.com/At the interface of science and computingenFri, 21 Sep 2007 13:03:11 -0000http://mndoci.com/2007/09/19/learning-from-tech-better-apis/#comment-1303653<p>I'll second Peter's opinion, and tell you that our company realized from its inception the value of an API and integration with public resources such as NCBI and Ensembl. As someone who straddles both worlds (molecular oncology/biomedical informatics) it is imperative that scientists have good access to BI/IT resources and that tools such as standardized APIs actually become..standard. We've all done our fair share of "grunt work" however, and I am not sure it is going to go away anytime soon; standardization in life sciences in general lags behind a lot of other industries. If you are interested in checking out some good data management software tools to help standardize data collection for translational research/biobanking/biomarker discovery, look us up at <a href="http://www.biofortis.com" rel="nofollow noopener" target="_blank" title="www.biofortis.com">www.biofortis.com</a>.</p>Ethel RubinFri, 21 Sep 2007 13:03:11 -0000http://mndoci.com/2007/09/19/learning-from-tech-better-apis/#comment-1303652<p>I couldn't agree more. Would suggest folks interested in open, standardized APIs check out some of the cancer Biomedical Informatics Grid (caBIG) software tools. caBIG has established conventions for creating standardized object-oriented APIs for any system, regardless of what kind of life science data it is hosting. The tools that currently implement these APIS are are listed at <a href="https://cabig.nci.nih.gov/guidelines_documentation/Silver_Review/#silver" rel="nofollow noopener" target="_blank" title="https://cabig.nci.nih.gov/guidelines_documentation/Silver_Review/#silver">https://cabig.nci.nih.gov/g...</a>.</p>Peter CovitzThu, 20 Sep 2007 14:59:28 -0000