In the njgraham fork, pcornet_mapping.csv<https://github.com/njgraham/i2p-transform/blob/master/Oracle/pcornet_mapping.csv> goes between GPC* and PCORnet ontologies.
* Specifically, HERON to PCORNet ontologies...GPC where we have the paths implemented. As to the constraints in your DB environment, is there some documentation you can share? If those constraints support best practices, perhaps we can all head that direction. It's worth a bit of extra effort to get to where we can share the exact same code. (And yes, I'm aware of the irony of saying this when the pcornet_mapping.csv has KUMC/HERON-specific tweaks.) -- Dan ________________________________ From: [email protected] [[email protected]] on behalf of French, Tony [[email protected]] Sent: Thursday, March 10, 2016 1:46 PM To: [email protected] Subject: gpc_terms --> pcornet_terms mapping Is there a mapping file to go between the GPC and PCORNet ontologies? The SCILHS code includes a mapping between the SCILHS terms and PCORNet, but I know both have slight differences from the GPC terms. I have been reviewing gpc-pcorenet-cdm/pcori_to_gpc.csv but I immediately notice that it doesn’t align with the GPC paths from GPC_TERMS.zip In general, we have been using the following projects as templates. Unfortunately, we apparently have more restrictive DB environment where as we need to extract ddl scripts from the ETL itself. https://github.com/njgraham/i2p-transform/ https://github.com/njgraham/scilhs-ontology https://bitbucket.org/gpcnetwork/gpc-pcornet-cdm Thank you, Tony Tony French | Software Development Manager Tools and Shared Resources Center for Biomedical Informatics [cid:09A1C8C9-59EF-4180-A386-15A6F81ECE78] 1101 West Tenth Street Indianapolis, IN, 46202 Tel 317-274-9087 | Fax: 317-274-9305 Twitter: @Regenstrief | Facebook.com/regenstriefinstitute<http://facebook.com/regenstriefinstitute> www.regenstrief.org<http://www.regenstrief.org/> Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical or other information is not sufficient for this purpose. If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention, disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.
_______________________________________________ Gpc-dev mailing list [email protected] http://listserv.kumc.edu/mailman/listinfo/gpc-dev
