Welcome to the project homepage of the i2b2 Research Data Warehouse at Cincinnati Children's Hospital Medical Center.
CCHMC researchers can access the warehouse by following the instructions listed here. Training material can be found on the Training tab.
For more information on i2b2, please see the Frequently Asked Questions (FAQ) page.
i2b2 (Informatics for Integrating Biology and the Bedside, http://www.i2b2.org) was an NIH-supported National Center for Biomedical Computing that developed a scalable informatics framework designed for translational research. The i2b2 framework is based on the Research Patient Data Registry (RPDR) developed at Massachusetts General Hospital.
This framework has a number of advantages, including extensive testing by the Partners Health System and Harvard faculty; an easily understood database schema; release under an open-source license; the existence of an organized users group to share information and applications; and the potential for translational research through collaboration and federated queries across other i2b2 institutions.
i2b2 was designed primarily for cohort identification, allowing users to perform an enterprise-wide search on a de-identified repository to determine the existence of a set of patients meeting certain inclusion or exclusion criteria. The i2b2 framework is packaged with a query tool that allows the user to drag-and-drop search terms from a hierarchical ontology into a Venn diagram-like interface. Investigators can perform an initial analysis on the de-identified cohort and if the results are promising, they can request approval from the IRB for a fully identified extract.
The i2b2 framework has been extended by the CCHMC i2b2 team, adding several new capabilities to the platform. These include the ability to view clinical data in a web-based form (similar to a chart review), the ability to enter data directly into i2b2, and the ability to run reports and perform other visualizations. These new features allow i2b2 to serve as a platform for research patient registries (either identified or de-identified), and when coupled with the SHRINE federated query platform, provide a mechanism for creating distributed, multi-center registries.
- What if I’m having trouble getting my research data out of Epic?
- Why do I have to enter my DocSite data into Epic (or vice versa)?
- Will the warehouse be able to change the data in Epic?
- What is the timeline for the project? When can I start using it?
- What if my question isn't listed? Who should I contact for further information?