Page History
...
| Info |
|---|
| For some institutions, the ETL mapping from the EHR to the i2b2 CRC databases database is the most problematic process in the setup. Those institutions may decide to minimize the complexity of their ETL, and simply copy the coding scheme from their EHR into the patient records in the CRC database. If the coding schemes in their EHR are not standard coding schemes, then they may will likely have to customize their i2b2 ontology to reflect the coding schemes present in their CRC database. In this case, they can may reduce the complexity of the ETL mapping, but this will surely likely increase the complexity of setting up the ontology tree. |
| Info |
| If your local institution does not have data in the CRC database for a certain domain in your chosen i2b2 ontology, then user queries referencing that domain may come back empty. To avoid that, you can exclude that domain from the i2b2 user interface, so that the domain without matching data in the CRC database is never used in a queryFor details on how to customize the ontology tree, see Ontologies 201 – Custom Metadata – Additions and Modifications. |
What if my institution records new concepts into the EHR that are not already included in the ontology?
...
