RCMI Coordinating Center (RCMI CC) Header Logo

James Chambers

Co-Authors (11)

Co-Authors are people in Profiles who have published together.
The timeline below shows the dates (blue tick marks) of publications James Chambers co-authored with other people in Profiles. The average publication date for each co-author is shown as a red circle, illustrating changes in the people that James Chambers has worked with over time.
Janakiran Seshu, 4 publications between 2009 and 2012, average publication date October 2010. Jose L. Lopez-Ribot, 1 publications between 2011 and 2011, average publication date December 2011. Karl E. Klose, 8 publications between 2009 and 2019, average publication date June 2013. Thomas Forsthuber, 9 publications between 2009 and 2022, average publication date July 2013. M. Neal Guentzel, 38 publications between 2009 and 2021, average publication date May 2014. George Perry, 2 publications between 2013 and 2015, average publication date June 2014. Bernard Arulanandam, 50 publications between 2006 and 2022, average publication date December 2014. Christopher Navara, 3 publications between 2012 and 2018, average publication date September 2015. Mark Eppinger, 2 publications between 2014 and 2018, average publication date April 2016. Yufeng Wang, 1 publications between 2019 and 2019, average publication date June 2019. Chiung-Yu Hung, 2 publications between 2018 and 2022, average publication date July 2020.

To see the data from this visualization as text, click here.
Chambers's Networks
Click the
Explore
buttons for more information and interactive visualizations!
Concepts (623)
Explore
_
Co-Authors (11)
Explore
_
Similar People (60)
Explore
_
Same Department Expand Description
Explore
_
RCMI CC is supported by the National Institute on Minority Health and Health Disparities, National Institutes of Health (NIH), through Grant Number U24MD015970. The contents of this site are solely the responsibility of the authors and do not necessarily represent the official views of the NIH

For technical support please contact support