GPC - Are there any sites that populated FACILITY_LOCATION in PMNENCOUNTER? Based on the code in i2p-transform, my understanding is that this field is based on OBSERVATION_FACT.LOCATION_CD in i2b2.
Here is the PCORI definition of this field for the CDM v3 specification: FACILITY_LOCATION RDBMS Text(3) SAS Char(3) . Geographic location (3 digit zip code). Should be null if not recorded in source system (modification made from "blank" to "null" in v3.0). My interpretation below is based on our Epic EMR implementation at the University of Wisconsin Medical Foundation (WISC). Typically during an Epic implementation, the CLARITY_DEP (clinical department of a visit or hospital unit of an admission) and CLARITY_LOC (location of the department) don't have the address populated. The Chronicles report grouper items may be populated with address values, but only for Epic customer specific (custom implementation) reasons, and only on some records. CLARITY_DEP comes from the DEP Masterfile in Chronicles (Epic's InterSystems Cache based DBMS) and CLARITY_LOC is extracted out of Clarity from EAF (Location and Service Area master file). The Epic Model System (standard implementation of Epic) uses POS_CODE as a pointer to CLARITY_POS.POS_ID, which contains the actual address of the location, for that given Place of Service (of the LOCATION or EAF record of the encounter). So that is where we will be getting the 3-digit zip code from. (First three digits of CLARITY_POS.ZIP) The Epic term "facility" has a completely different meaning for Epic customers than what PCORI is using the term for, so I wanted to make that distinction. So we are planning to use the Place of Service record as our facility location, since that is where the encounter physically took place, which is probably what PCORI needs to know. So we'll be populating OBSERVATION_FACT.LOCATION_CD to this 3-digit value and ultimately to PMNENCOUNTER.FACILITY_LOCATION in CDM v3. Are other sites populating OBSERVATION_FACT.LOCATION_CD using different logic than this, based on Epic EMR data? If you have a different EMR implementation, feel free to share as it may be helpful to other sites who have this field blank. Keith Wanta (WISC)
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
