I got a copy of ACT from Debbie Yoshihara at Madison.....Jim
________________________________
From: GPC Informatics <d...@madmode.com>
Sent: Wednesday, February 28, 2018 1:36 PM
To: lpa...@kumc.edu; ngra...@kumc.edu; dconno...@kumc.edu; Campbell, James R
Cc: rwait...@kumc.edu; Campbell, Walter S; rachel.h...@hsc.utah.edu
Subject: Re: [gpc-informatics] #201: Align c_table_cd in table_access
(item_key) across sites
Non-UNMC email
#201: Align c_table_cd in table_access (item_key) across sites
--------------------------+----------------------------
Reporter: preeder | Owner: lpatel
Type: design-issue | Status: assigned
Priority: major | Milestone: snow-shrine-2
Component: data-stds | Resolution:
Keywords: | Blocked By:
Blocking: 411 |
--------------------------+----------------------------
Comment (by lpatel):
Hi Jim,Scott or/and Phillip,
Can you please forward me contact information for persons who are
developing ontology at ACT network and at Harvard(ontology link below)? I
would like to understand why they chose different prefix and if they have
plan to move to one prefix. I would also like take look at ACT ontology. I
could not google it. Is there a way I can get it.
'''Details:'''
[https://open.med.harvard.edu/svn/shrine-
ontology/PCORI/releases/PCORI%20Ontology%202.1/ORACLE/PCORI_SHRINE_2-1_DEMO_ORACLE.sql
Harvard/PCORI] uses `\SHRINE` as prefix, GPC also uses `\SHRINE` as
prefix.
FYI: [https://github.com/SCILHS/scilhs-
ontology/tree/master/Ontology/MSSQL_ORACLE/pcornet_demo_mssql.txt
ARCH/scilhs] uses `\PCORI` as prefix.
--
Ticket URL:
<http://informatics.gpcnetwork.org/trac/Project/ticket/201#comment:17>
gpc-informatics <http://informatics.gpcnetwork.org/>
gpc-informatics<http://informatics.gpcnetwork.org/>
informatics.gpcnetwork.org
nearby: GPC * DevTeams * SoftwareDev * DataSecurity * GovernanceMaterials *
PatientEngagement * gpc-dev. Work toward technical milestones continues with ...
Greater Plains Network - Informatics
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
Gpc-dev@listserv.kumc.edu
http://listserv.kumc.edu/mailman/listinfo/gpc-dev
