We're also looking at another approach using i2b2 queries, or at least SQL queries built the way i2b2 builds them from i2b2 metadata.
See the harmonize-114 shared folder on babel. More later, I hope. Gotta go just now... -- Dan ________________________________ From: [email protected] [[email protected]] on behalf of Nathan Graham [[email protected]] Sent: Monday, April 28, 2014 5:19 PM To: [email protected] Subject: Feedback on GPC ticket 114 (Milestone 2.7) Dr. Campbell, I took a look at the queries – here are the main points I noticed. Dan or Russ may have further comments. The actual SQL I ran against our database (based on your queries in GPC ticket 114<https://informatics.gpcnetwork.org/trac/Project/ticket/114>) is attached. · Ethnicity_cd isn’t part of the patient dimension · Facility_location isn’t part of the visit dimension, but perhaps the location_cd (linking to the code_lookup table) gets what we need (see CRC Design Document<https://www.i2b2.org/software/files/PDF/current/CRC_Design.pdf>). At KU, we don’t fill in the provider dimension. · Encountertype_cd isn’t part of the visit dimension and I don’t see anything that I think might be analogous. · At KU, we don’t have any LOINC concepts loaded to my knowledge, but I think we have most of the concepts you mentioned in our flowsheet category (height, weight, bp, etc). We also have discharge disposition as facts (rather than modifiers). We do have modifiers for some billing types (clinic, hospital, and primary diagnosis). Minor points: · I2b2 calls it the visit_dimension now, not encounter_dimension · A few column names are different – I noted them in the attached SQL. Thanks. Regards, Nathan
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
