Page History
...
| Info |
|---|
| It's important to understand that each institution will have its own protocols for coding diagnoses, procedures, medications, etc., in the patient electronic health records (aka EHR, as in Cerner or Epic databases), and that these protocols may use standard or non-standard codes. So, when preparing the CRC database for i2b2, it's necessary for the ETL process (extract-translatetransform-load) to map the codes from the patient EHR into the codes that are present in the i2b2 metadata. For instance, let's say a patient's EHR record includes an NDC code for a medication. And let's say that your institution's i2b2 ontology tree only has an RxNorm code for that type of medication. Then the surgery medication record from the EHR should be mapped into a patient record in the i2b2 CRC database that uses the appropriate RxNorm code. If the patient record in the CRC database has the NDC code from the EHR, then it would not be matched in a query when the query is using the RxNorm code. |
...
