I think simply changing the query to be similar to the following would take care of Dan’s objection. We need a demographics tree structure created and added to Babel.
Select count(*) from observation_fact join concept_dimension on observation_fact.concept_cd=concept_dimension.concept_cd and concept_dimension.concept_path like ‘\GPC\Demographics\Ethnicity\%’ NOTE: Where '\GPC\Demographics\Ethnicity\’ has the code ‘LOINC: 21838-8’in the common terminology. Phillip From: Dan Connolly <[email protected]<mailto:[email protected]>> Date: Tuesday, May 27, 2014 at 10:21 AM To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Cc: John Steinmetz <[email protected]<mailto:[email protected]>> Subject: RE: [gpc-informatics] #114: Milestone 2.7 GPC harmonizes with PCORI CDM V1.0 These documents still have SQL queries in them that directly constrain the observation_fact_table: Select Count(*) >From Observation_Fact Where Concept_CD = ‘LOINC: 21838-8’ (Ethnicity) My May 4 objection<http://listserv.kumc.edu/pipermail/gpc-dev/2014q2/000128.html> to this approach stands. i2b2 concept paths are necessary and sufficient; the generated sql from an i2b2 query using standardized paths may (a) indirect via the concept_dimension to map standard codes to local EMR codes; e.g. LOINC codes to local ethnicity codes and (b) may use other dimensions. The HERON ETL code currently results in (a) though not (b). -- Dan ________________________________________ From: GPC Informatics [[email protected]<mailto:[email protected]>] Sent: Monday, May 26, 2014 9:52 AM To: [email protected]<mailto:[email protected]>; Dan Connolly; [email protected]<mailto:[email protected]> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]>; John Steinmetz Subject: Re: [gpc-informatics] #114: Milestone 2.7 GPC harmonizes with PCORI CDM V1.0 #114: Milestone 2.7 GPC harmonizes with PCORI CDM V1.0 ----------------------------------------------+---------------------------- Reporter: campbell | Owner: campbell Type: task | Status: accepted Priority: major | Milestone: initial-data- Component: data-stds | domains Keywords: PCORI CDM V1, GPC data standards | Resolution: Blocking: | Blocked By: 23, 67, 120 ----------------------------------------------+---------------------------- Comment (by campbell): During discussion two weeks ago, GPCDEV reached consensus on elements of the GPC standard model to align with PCORI CDM V1. I have revised the reference model presentation, added code sets where applicable to the data domains and updated the test SQL scripts for assessing CDM adherence. At the DSSNI meeting in Washington we were told that finalization of CDM would be issued shortly with response to the 210+ concerns that were submitted. The task force leader further stated that the Enrollment class in CDM was a placeholder for now and not to be concerned about details of implementing that feature of CDM for time being. Jim -- Ticket URL: <http://informatics.gpcnetwork.org/trac/Project/ticket/114#comment:14> gpc-informatics <http://informatics.gpcnetwork.org/> Greater Plains Network - Informatics ________________________________ UT Southwestern Medical Center The future of medicine, today.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
