Return-Path: X-Original-To: apmail-ctakes-dev-archive@www.apache.org Delivered-To: apmail-ctakes-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E937510434 for ; Tue, 22 Oct 2013 20:26:32 +0000 (UTC) Received: (qmail 63022 invoked by uid 500); 22 Oct 2013 20:25:52 -0000 Delivered-To: apmail-ctakes-dev-archive@ctakes.apache.org Received: (qmail 62940 invoked by uid 500); 22 Oct 2013 20:25:50 -0000 Mailing-List: contact dev-help@ctakes.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ctakes.apache.org Delivered-To: mailing list dev@ctakes.apache.org Received: (qmail 62914 invoked by uid 99); 22 Oct 2013 20:25:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 20:25:44 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_FRT_BELOW2 X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vngarla@gmail.com designates 74.125.82.182 as permitted sender) Received: from [74.125.82.182] (HELO mail-we0-f182.google.com) (74.125.82.182) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 22 Oct 2013 20:25:37 +0000 Received: by mail-we0-f182.google.com with SMTP id t61so8845411wes.13 for ; Tue, 22 Oct 2013 13:25:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Hx16u0reK6vPGIWJ5Lel14QNKlKla7YCQ+dL82boEr4=; b=uR2XBTpK2jzAACKRsXzceQyawRkUNvWes3tDEWsueJHMf0i22shfpC8g7vQxUeZQCM vORZXt1DNMcRWLzxe3vM5QYAkq00G/7pb45vSaaFERHSxSs3oZ8JC3wDAKSX3ZSS/rz5 BfKlwMVBAO1HStRxHyY8dMSbOMXDZxgoVa76bDPh7glkhcmbANCKK3lmgIkzzhf+VY2T vek58TapSc65W7qHo6x5Tkm+3B5RN/vLhrNtehgE48sLXxQ19MhzI5BuFIyTD90Q8/lR w/t/OV0YW+zm9zSowmOlzgJyS6iTbe2eTSg1o7X+jbgpEXx5qs+2vA/qQ/FfZYIacHXX cVxw== MIME-Version: 1.0 X-Received: by 10.194.63.228 with SMTP id j4mr11808937wjs.34.1382473517317; Tue, 22 Oct 2013 13:25:17 -0700 (PDT) Received: by 10.227.60.69 with HTTP; Tue, 22 Oct 2013 13:25:17 -0700 (PDT) In-Reply-To: <996FC801C05DF64A84246A106FACACD01F2A20@MSGPEXCHA08A.mfad.mfroot.org> References: <1382399850.5607.YahooMailNeo@web140301.mail.bf1.yahoo.com> <1382399951.16947.YahooMailNeo@web140306.mail.bf1.yahoo.com> <996FC801C05DF64A84246A106FACACD01F2898@MSGPEXCHA08A.mfad.mfroot.org> <924DE05C19409B438EB81DE683A942D9105D3DC8@CHEXMBX1A.CHBOSTON.ORG> <996FC801C05DF64A84246A106FACACD01F2A20@MSGPEXCHA08A.mfad.mfroot.org> Date: Tue, 22 Oct 2013 16:25:17 -0400 Message-ID: Subject: Re: Synonymous terms From: vijay garla To: dev@ctakes.apache.org Content-Type: multipart/alternative; boundary=047d7ba97f3ae9440504e95a327e X-Virus-Checked: Checked by ClamAV on apache.org --047d7ba97f3ae9440504e95a327e Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable I'm curious as to how you decide which is 'the' preferred term; maybe this is clear if you are just using SNOMED-CT. However, if you use multiple UMLS vocabularies, there can be multiple (or no) preferred terms among the MRCONSO entries with the same CUI. -vj On Tue, Oct 22, 2013 at 12:22 PM, Masanz, James J. w= rote: > Just in case it wasn't clear, when I said it only contains SNOMED-CT > codes, I pointing out that it doesn't have entries for ICD9 or MeSH or NC= I > Thesaurus, even though those are used when doing the dictionary lookup. = I > wasn't thinking about the codes vs. text part. > > -----Original Message----- > From: dev-return-2126-Masanz.James=3Dmayo.edu@ctakes.apache.org [mailto: > dev-return-2126-Masanz.James=3Dmayo.edu@ctakes.apache.org] On Behalf Of > Chen, Pei > Sent: Tuesday, October 22, 2013 11:17 AM > To: dev@ctakes.apache.org; 'samir chabou' > Subject: RE: Synonymous terms > > > if I need to get term name do I have to do a lookup on umls ? > FYI: I was proposing adding an additional attribute to store the > description/preferredText(term) [1] since this information is already > available in the dictionary lookup. > I think most folks would find this useful in additional to just saving th= e > CUI/Code. Otherwise, they would have to do another lookup further > downstream to get the description of the CUI/Code. > > [1] https://issues.apache.org/jira/browse/CTAKES-224 > --Pei > > > -----Original Message----- > > From: Masanz, James J. [mailto:Masanz.James@mayo.edu] > > Sent: Tuesday, October 22, 2013 10:57 AM > > To: 'dev@ctakes.apache.org'; 'samir chabou' > > Subject: RE: Synonymous terms > > > > > > ontologyConceptArray only contains SNOMED-CT codes (except for > > medications, where it contains RxNorm codes or CUIs) > > > > -----Original Message----- > > From: dev-return-2119-Masanz.James=3Dmayo.edu@ctakes.apache.org > > [mailto:dev-return-2119-Masanz.James=3Dmayo.edu@ctakes.apache.org] On > > Behalf Of samir chabou > > Sent: Monday, October 21, 2013 6:59 PM > > To: dev@ctakes.apache.org > > Subject: Fw: Synonymous terms > > > > > > > > > > > > > > On Monday, October 21, 2013 7:58:01 PM, samir chabou > > wrote: > > > > Synonymous > > terms > > > > > > > > Given a C0001621 I need to get its synonyms terms for example in MeSH, > > ICD, SNOMED (as shown bellow)=85Is that possible ? > > > > > > > > Synonymous > > terms Adrenal gland diseases MeSH D000307 Disease= s > of the > > adrenal glands SNOMED DB-70000 > > ... > > > > Are the > > synonyms kept in ontologyConceptArray ? If yes, then in the > > ontologyConceptArray the information displayed is about identifier (cod= e, > > cui, tui, oid =85) if I need to get term name do I have to do a lookup = on > umls ? > > thanks > > Samir > --047d7ba97f3ae9440504e95a327e--