The GPC c_dimcode for the PCORI paths need to be instantiated with the standard LOINC and ICD-9-CM codes as we have agreed to be standards for the network and I have published with PCORI DSSNI. Hubert is loading our final copy from UNMC and the GPC model for PCORI should mirror that...I thought that he had pushed a copy to Nathan? Jim
James R. Campbell MD [email protected] Office: 402-559-7505 Secretary: 402-559-7299 Pager: 402-888-1230 > On Dec 17, 2014, at 11:19 AM, "GPC Informatics" <[email protected]> wrote: > > #145: transform (ETL) GPC i2b2 data to PCORNet CDM > --------------------------+---------------------------- > Reporter: dconnolly | Owner: ngraham > Typethought th: enhancement for | Status: assigned > Priority: major | Milestone: data-domains2 > Component: data-sharing | Resolution: > Keywords: | Blocked By: 109 > Blocking: 160 | > --------------------------+---------------------------- > > Comment (by ngraham): > > Dan and I sketched out some next steps after talking with Dr. Waitman this > morning: > * Install the PCORI CDM in i2b2 ontology on the test environment at KU > * Utilizing `c_fullname` and `c_dimcode` in the i2b2 terms table, make it > such that querying for a PCORI CDM ontology item actually uses the paths > for the equivalent HERON path. > - so, as per [https://bitbucket.org/njgraham/pcori-annotated-data- > dictionary/src/1c1c0f980377bbd1adbe839edf84d8de92f5b1de/heron_to_pcori.csv?at=default > heron_to_pcori.csv], a `c_fullname` like > `\\PCORI_\PCORI\ENCOUNTER\ENC_TYPE\AV\` will have a `c_dimcode` like > `\i2b2\Visit Details\Encounter Type\102\"`. > - Or, really, the path common to GPC long-term. > * Then, we can likely use code similar to [https://bitbucket.org/njgraham > /pcori-annotated-data-dictionary pcori-annotated-data-dictionary] to build > CDM tables using PCORI CDM paths. > > -- > Ticket URL: > <http://informatics.gpcnetwork.org/trac/Project/ticket/145#comment:13> > gpc-informatics <http://informatics.gpcnetwork.org/> > Greater Plains Network - Informatics > _______________________________________________ > Gpc-dev mailing list > [email protected] > http://listserv.kumc.edu/mailman/listinfo/gpc-dev The information in this e-mail may be privileged and confidential, intended only for the use of the addressee(s) above. Any unauthorized use or disclosure of this information is prohibited. If you have received this e-mail by mistake, please delete it and immediately contact the sender. _______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
