We have always kept our race info in the fact table, but we did have a "HERON flattens multiple race facts out of Epic/O2 to 1" bug. It's fixed in the current epic_demographic_transform.sql<https://informatics.kumc.edu/work/browser/heron_load/epic_demographic_transform.sql>
(for my reference: #867 fixed in 9b71ed73fb6d 08/01/12) -- Dan ________________________________ From: Greater Plains Collaborative Software Development [[email protected]] on behalf of Phillip Reeder [[email protected]] Sent: Tuesday, February 04, 2014 10:31 AM To: [email protected] Subject: Re: optional columns in i2b2 dimension tables RE: Minutes of GPV-DEV call 20140128 I'd be curious on the performance of dimension vs observation_fact queries as well. I don't know if I've ever seen hard numbers. It's probably a very index sensitive measurement:). The dimension table can have some negative implications for things like race, for example. If race is implemented according to the NIH Standard, someone can be White, Black, and Asian, but in the patient dimension, you would be limited to a single concept. But in the observation_fact table, you could easily add three rows, one for each race. Phillip
