Broad-based proteomic strategies: A practical guide to proteomics and functional screening

David R.M. Graham, Steven T. Elliott, Jennifer E. Van Eyk

Research output: Contribution to journalArticlepeer-review

Abstract

Proteomics, the study of the proteome (the collection of all the proteins expressed from the genome in all isoforms, polymorphisms and post-translational modifications), is a rapidly developing field in which there are numerous new and often expensive technologies, making it imperative to use the most appropriate technology for the biological system and hypothesis being addressed. This review provides some guidelines on approaching a broad-based proteomics project, including strategies on refining hypotheses, choosing models and proteomic approaches with an emphasis on aspects of sample complexity (including abundance and protein characteristics), and separation technologies and their respective strengths and weaknesses. Finally, issues related to quantification, mass spectrometry and informatics strategies are discussed. The goal of this review is therefore twofold: the first section provides a brief outline of proteomic technologies, specifically with respect to their applications to broad-based proteomic approaches, and the second part provides more details about the application of these technologies in typical scenarios dealing with physiological and pathological processes. Proteomics at its best is the integration of carefully planned research and complementary techniques with the advantages of powerful discovery technologies that has the potential to make substantial contributions to the understanding of disease and disease processes.

Original languageEnglish (US)
Pages (from-to)1-9
Number of pages9
JournalJournal of Physiology
Volume563
Issue number1
DOIs
StatePublished - Feb 15 2005

ASJC Scopus subject areas

  • Physiology

Fingerprint Dive into the research topics of 'Broad-based proteomic strategies: A practical guide to proteomics and functional screening'. Together they form a unique fingerprint.

Cite this