Return-Path: 
 <dev-return-2770-apmail-ctakes-dev-archive=ctakes.apache.org@ctakes.apache.org>
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 2DA9C11FA0
	for <apmail-ctakes-dev-archive@www.apache.org>;
 Thu,  3 Jul 2014 17:33:18 +0000 (UTC)
Received: (qmail 56180 invoked by uid 500); 3 Jul 2014 17:33:18 -0000
Delivered-To: apmail-ctakes-dev-archive@ctakes.apache.org
Received: (qmail 56125 invoked by uid 500); 3 Jul 2014 17:33:18 -0000
Mailing-List: contact dev-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ctakes.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ctakes.apache.org>
List-Post: <mailto:dev@ctakes.apache.org>
List-Id: <dev.ctakes.apache.org>
Reply-To: dev@ctakes.apache.org
Delivered-To: mailing list dev@ctakes.apache.org
Received: (qmail 56112 invoked by uid 99); 3 Jul 2014 17:33:17 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 17:33:17 +0000
X-ASF-Spam-Status: No, hits=3.2 required=5.0
	tests=HTML_IMAGE_ONLY_20,HTML_MESSAGE,HTML_SHORT_LINK_IMG_3,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL,T_REMOTE_IMAGE
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [74.125.82.180] (HELO mail-we0-f180.google.com) (74.125.82.180)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2014 17:33:15 +0000
Received: by mail-we0-f180.google.com with SMTP id x48so593942wes.11
        for <dev@ctakes.apache.org>; Thu, 03 Jul 2014 10:32:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:date:message-id:subject:from:to
         :content-type;
        bh=Zt9OJnVrCz0EeqmHI2IManxbhSAzu7AI0v3e6quQcus=;
        b=dt1EDIuAAFiNjXFvvLUaEtiXpMAALkqLrAAt5GyFNGjlE8O3AbX1fKyQB1mCi344Zk
         1C8DCyL3mNR+aJ82UIZeh2++8lfuI8RNYLU9Ct/dlS20lQeyulEioeax+9vXYTVUEfs/
         wg8Wxl8Yze2LGmMOrMtp6RTd7X0yQNkjAusIK2bs26dVKYaVbiZMu7sLX+KIvCErHG88
         84TNZAoTmUqP6V0NYBfpFPEmgquogC3hyUv9EvDPQJA3DMeK3vw/s+bhosyok9OUAma6
         dwjGxPDgCKsGv2Y/qDCN4Mv3GCQU4WU2Hkwq/xb0BXWNjiBeea4VfLur+Ha+Sx4UcSRF
         2R9Q==
X-Gm-Message-State: 
 ALoCoQnhukX7bhuyA2Cu+j/tkNF2jNNAAzj7AVLhvjMIimA4r3Y3CNrf831VI7n6xbCM5SU++n2y
MIME-Version: 1.0
X-Received: by 10.194.92.148 with SMTP id cm20mr6458924wjb.57.1404408769921;
 Thu, 03 Jul 2014 10:32:49 -0700 (PDT)
Received: by 10.194.139.173 with HTTP; Thu, 3 Jul 2014 10:32:49 -0700 (PDT)
Date: Thu, 3 Jul 2014 11:32:49 -0600
Message-ID: 
 <CAOVrvubwAXEofYsknW6ZCC-RF4DApr_oUtpBH6xDY=ZFFcXy-A@mail.gmail.com>
Subject: Converting UMLS codes to SNOMED codes using the YTEX pipeline
From: Bruce Tietjen <bruce.tietjen@perfectsearchcorp.com>
To: dev@ctakes.apache.org
Content-Type: multipart/alternative; boundary=047d7bfd0166d9dd3604fd4d659e
X-Virus-Checked: Checked by ClamAV on apache.org

--047d7bfd0166d9dd3604fd4d659e
Content-Type: text/plain; charset=UTF-8

I've been playing around with 3.1 and 3.2 rc1 using the YTEX pipeline.

I noticed that the output generated by the YTEX pipeline outputs the UMLS
codes. Is there an easy way to convert the UMLS codes to SNOMED codes?

I had expected that the LookupDesc_SNOMED.xml might handle that, but then
noticed that the LookupConsumer identified there specifically uses the UMLS
codingscheme.

Or is there a reason why the ytex pipeline should not produce SNOMED codes?

Thanks,

Bruce Tietjen



 [image: IMAT Solutions] <http://imatsolutions.com>
 Bruce Tietjen
Senior Software Engineer
[image: Mobile:] 801.634.1547
bruce.tietjen@imatsolutions.com

--047d7bfd0166d9dd3604fd4d659e--