That was a SCHILS decision. Our goal was to be compatible with their shrine, and that is how they did it. We followed.
Phillip Sent from my iPhone On Oct 3, 2017, at 2:05 PM, Andrew Hangsleben <hangs...@umn.edu<mailto:hangs...@umn.edu>> wrote: Now that I've gotten it all set up it doesn't matter much to me, but it might be simpler in the future if we used the PCORnet ontology. Then we could use an adapter mappings file that maps every term to itself like the ACT Shrine setup. Plus there would be no need to maintain the duplicate ontology in the database. Regards, Andrew On Tue, Oct 3, 2017 at 1:47 PM, Dan Connolly <dconno...@kumc.edu<mailto:dconno...@kumc.edu>> wrote: Yay! Indeed, a simple demographics test gets counts from UMN as well as UTHSCSA, MCW, KUMC, and MCRF (but not UTSW? odd...). As to your question: If I understand correctly, SHRINE adapter mappings are not optional. At a minimum, it's a big CSV file with all the terms repeated in both the 1st and 2nd column. And the only difference between the PCORNet Ontology and our SHRINE ontology is a \SHRINE\ at the beginning. As to why that's there... I forget... I think somebody in the ACT network flipped a coin and it came up that way, and UTSW followed suit, and we followed from them. Formally, our decision was made Sep 5... it traces back to a proposal from Reeder @ UTSW in the March 22 - Apr 10 timeframe. https://informatics.gpcnetwork.org/trac/Project/ticket/525#comment:22 -- Dan ________________________________ From: Andrew Hangsleben [hangs...@umn.edu<mailto:hangs...@umn.edu>] Sent: Tuesday, October 03, 2017 1:18 PM To: Dan Connolly Cc: GPC-DEV@LISTSERV.KUMC.EDU<mailto:GPC-DEV@LISTSERV.KUMC.EDU> Subject: Re: SNOW Shrine Ontology Thanks Dan, we should be up and running at UMN now; I ran a few queries to verify we were returning results. Out of curiosity, is there any reason we aren't using the PCORnet ontology directly in shrine instead of the shrine ontology + adapter mappings? Regards, Andrew On Tue, Oct 3, 2017 at 10:54 AM, Dan Connolly <dconno...@kumc.edu<mailto:dconno...@kumc.edu>> wrote: Yes, that's how it works. #411<https://informatics.gpcnetwork.org/trac/Project/ticket/411> should have details. -- Dan ________________________________ From: Gpc-dev [gpc-dev-boun...@listserv.kumc.edu<mailto:gpc-dev-boun...@listserv.kumc.edu>] on behalf of Andrew Hangsleben [hangs...@umn.edu<mailto:hangs...@umn.edu>] Sent: Tuesday, October 03, 2017 10:43 AM To: GPC-DEV@LISTSERV.KUMC.EDU<mailto:GPC-DEV@LISTSERV.KUMC.EDU> Subject: SNOW Shrine Ontology Hi Everyone, We are working on getting our ontology and mappings configured here at UMN. I was hoping someone could help me understand which ontologies we are using for the SNOW network. My current understanding is that sites are using the PCORnet/SCIHLS locally, but we are using the shrine ontology for the network. If this is the case, couldn't we just use the SCIHLS ontology for the shrine network as well? Regards, Andrew Hangsleben -- Andrew Hangsleben Developer/Analyst Academic Health Center - Information Systems<http://hub.ahc.umn.edu/ahc-information-systems> University of Minnesota Phone: (612) 625-1285<tel:(612)%20625-1285> Email: hangs...@umn.edu<mailto:hangs...@umn.edu> -- Andrew Hangsleben Developer/Analyst Academic Health Center - Information Systems<http://hub.ahc.umn.edu/ahc-information-systems> University of Minnesota Phone: (612) 625-1285<tel:(612)%20625-1285> Email: hangs...@umn.edu<mailto:hangs...@umn.edu> -- Andrew Hangsleben Developer/Analyst Academic Health Center - Information Systems<http://hub.ahc.umn.edu/ahc-information-systems> University of Minnesota Phone: (612) 625-1285 Email: hangs...@umn.edu<mailto:hangs...@umn.edu> _______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu<mailto:Gpc-dev@listserv.kumc.edu> http://listserv.kumc.edu/mailman/listinfo/gpc-dev ________________________________ UT Southwestern Medical Center The future of medicine, today.
_______________________________________________ Gpc-dev mailing list Gpc-dev@listserv.kumc.edu http://listserv.kumc.edu/mailman/listinfo/gpc-dev
