We discussed encounters a bit at HackathonTwo; the only thing I remember is that I'm supposed to split ticket #155. More on that in due course. Meanwhile...
It's by design (limitation) that NAACR encounters don't show up in the Encounters portion of the i2b2 tree, at least the KUMC i2b2 tree. And yes, they're unique; i.e. we don't (yet) support same-encounter queries between the tumour registry and anything else; we're considering per-patient-day encounter support that should result in a bit of integration. (for KUMC folks: #333 and nearby tickets tagged encounter-mapping) Encounter type support is weak in HERON ETL. The only encounter types you'll see from HERON ETL come from Epic, and then only for in-patient, I think. In the visit_dimension generated by HERON ETL, the encounter types are all null. I hope other (Hubert, ...) take the lead on this and produce something we can integrate into HERON ETL. -- Dan ________________________________ From: [email protected] [[email protected]] on behalf of Lenon Patrick [[email protected]] Sent: Friday, January 30, 2015 9:12 AM To: [email protected] Subject: NAACCR Encounter type? Hey all, I’m close to loading our NAACCR data into our I2B2 instance, which involves generating encounter records (per the tumor_reg_visits table referenced in KUMC’s naaccr_facts_load.sql). These encounters don’t line up with any existing encounters, they’re all unique. My question is, should these NAACCR “encounters” be represented in the Encounters portion of the I2B2 tree? I checked Babel and spot-checked a few setups and didn’t see any reference to NAACCR under Encounter Type, which is where I’d expect to find it. Has this been considered/discussed/rejected? Your thoughts are welcome. Patrick Lenon HIMC Informatics Specialist 608 890 5671
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
