Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C15122009C5 for ; Mon, 16 May 2016 17:35:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BFFF9160A16; Mon, 16 May 2016 15:35:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id E09DA160131 for ; Mon, 16 May 2016 17:35:45 +0200 (CEST) Received: (qmail 99545 invoked by uid 500); 16 May 2016 15:35:45 -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 99521 invoked by uid 99); 16 May 2016 15:35:44 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 May 2016 15:35:44 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 38A1BC0CD5 for ; Mon, 16 May 2016 15:35:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.387 X-Spam-Level: ** X-Spam-Status: No, score=2.387 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, HTML_NONELEMENT_30_40=0.001, MISSING_HEADERS=1.207, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id R3FP-zM1CXXj for ; Mon, 16 May 2016 15:35:41 +0000 (UTC) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id F400D5F36D for ; Mon, 16 May 2016 15:35:40 +0000 (UTC) Received: by mail-pa0-f45.google.com with SMTP id xk12so66336609pac.0 for ; Mon, 16 May 2016 08:35:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:cc:message-id:in-reply-to:references:subject:mime-version; bh=eRJGcQ3ZEBU5U+eehC3+ZkCnHBBtMhpwtKXMUMEFMEI=; b=fR2b2zt2eJNYymIeIv5zeLRw77FfAlNypfI6h7gWMRZNsOVazVz213ta5f6QCwtT25 ICzBsSoW8Gwq80dFNZqaBtXhL7qX/2tb0H89/K0t76PFOYaUGBExPWxwRnOSwBZ07ePV L9FJkYTEGiIEBxOShcVRJGRDmgqRko6/tVX8mz/G9sd8X6MZXhBOAUTdkg1gXAzXDprw aR2JRALsZS76PVD2Pe8+Q84nDHiLCSUVxG08W6tixNtHKIsnpO+nExDl0WWsQ1yJT0hY Jc2Z2DfL6S0hQg6sPAJJMu86lC6gAOFqAzO3kHMTGfdeTGrlejdFmkrXzxnU95ggB3Gr Nqvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:cc:message-id:in-reply-to:references :subject:mime-version; bh=eRJGcQ3ZEBU5U+eehC3+ZkCnHBBtMhpwtKXMUMEFMEI=; b=J4JO2+YAPvYID62dZp7nDZcgCRGV5hKB5aPiPM6byRIg2dvaXMJYR2hOM/JR+IkHgT RghQTpn/ctPkZ2TtLY5lBFHB5IJDvbt+3yVVKJ+WcgF+VdtdZnCcsKcqj26rNpv2kZDT eKkJmWvlpVxSlkSQfOoDiz3Rofi2pM8pKaVw7/AIMA0y6q+YHT+2cORF0kd/O/d+TN62 qiNN1RO6G5BojFHorsE4F9KxGpYdgFUCczo5oq2DiKquoBQfBuNqkO7w2+4I3UHeb5O2 oJwtXA3ArXkhj8ZyM3DllcD8SPsw7oqGMQTyQ0/4RcM05NKvG6KplydERkOmXtrwKPXI EvjQ== X-Gm-Message-State: AOPr4FWQxrD/9dYOBI/8jKx9b9JEDM6L0r9g+Oc/4uvDbn3tP5FadM2tEWpMzOnboe8r9A== X-Received: by 10.66.112.34 with SMTP id in2mr46661294pab.52.1463412934023; Mon, 16 May 2016 08:35:34 -0700 (PDT) Received: from John-Greens-iPhone ([2600:1011:b00f:82db:658b:ea88:cc6a:fa2a]) by smtp.gmail.com with ESMTPSA id ry2sm7134356pac.9.2016.05.16.08.35.32 for (version=TLSv1/SSLv3 cipher=OTHER); Mon, 16 May 2016 08:35:33 -0700 (PDT) Date: Mon, 16 May 2016 09:35:31 -0600 From: John Travis Green Cc: "dev@ctakes.apache.org" Message-ID: In-Reply-To: <7D6629E3-BF6F-4823-82EF-8E558914029A@wiredinformatics.com> References: <1463250507883.30200@childrens.harvard.edu> <03fbab5006d647038b6153b25f4dc203@CHEXMAIL1A.CHBOSTON.ORG> <7D6629E3-BF6F-4823-82EF-8E558914029A@wiredinformatics.com> Subject: Re: Offline access X-Mailer: Boxer 6.0.4 (321) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5739e8c3_41b71efb_1d64" archived-at: Mon, 16 May 2016 15:35:46 -0000 --5739e8c3_41b71efb_1d64 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It seems odd they would require repeated checke when you can download the= whole thing for input into a db with mmsys.=C2=A0 How is the documentati= on on building the fast lookup from a local copy of the umls=3F A quick g= lance at the website didnt reveal much.=C2=A0 ytex reportedly works this = way but Ive been getting an error with the section annotator that others = addressed back in early 15 but no resolution was posted to the listserv.=C2= =A0 Thanks all for your help on this. I have an active irb here in the ar= my using ctakes but dod security requirements are so strict the entire se= rver is offline. Best, John =20 Having a hosted web site which hosts UMLS resources and checks for a lice= nse before downloading locally(via the NLM/UMLS license validation web se= rvice) is indeed the norm and a more common way. (YTEX originally and UM= LS itself does this when one downloads their resources.) The responsibil= ity for any UMLS license adherence afterwards is essentially done by the = one downloading it since the check is done at that time. The online/upon= initialization license check/bundled solution for cTAKES was really done= for convenience to end users and historical reasons. It just boils down= to who wants to build, manage, maintain, host such a site that distribut= es and ensure the license check before downloading for these specially fo= rmatted resources. =E2=80=94Pei > On May 16, 2016, at 9:12 AM, =46inan, Sean wrote: > =20 > The agreement that the ctakes core group was able to achieve with the N= LM (distributor of UMLS) was that ctakes would check a user's access righ= ts upon every use of any database derived from the UMLS. The reason for = this was that the NLM did not want one valid UMLS user to download the da= tabase and then distribute it for use by unaccredited third parties. We = have stuck to that agreement. Upon every initial load of either of the d= istributed ctakes dictionary modules the user's entered password is check= ed online with the NLM user registry. > =20 > I think that a great compromise would be if somebody could create a =22= remote checkout=22 tool, something that checks-out a virtual license for = use while you are on the road. Maybe coordinate with the NLM on getting = such a thing approved. As ctakes is open source software you could start= toying with such a client first. To start, delegate to JdbcRareWordDict= ionary as does the UmlsJdbcRareWordDictionary, and delegate to JdbcConcep= t=46actory as does the UmlsJdbcConcept=46actory (for the -fast module). = Then point to the new trial =22remote checkout=22 classes in your .xml se= tup file (the default being cTakesHsql.xml). However, do NOT use these c= lasses directly or in any production scenario as that would not abide by = our agreement with the NLM. Do not even check them into sandbox without = us getting a new agreement to use such a system with the NLM. I must emp= hasize that publicly doing so could cause us to lose our privileges to di= stribute a default dictionary. You would still be able to download your = own UMLS database and create your own dictionary for use with ctakes, but= not every user can do that. And when creating your client code favor co= mposition over inheritance as the remote checkout client should not have = IS-A, not that I can enforce anything that you do. > =20 > I repeat, NEVER use the JdbcRareWordDictionary and/or JdbcConcept=46act= ory directly unless you are pointing to a database that was not created u= sing the UMLS as a source. > =20 > Sean > =20 > -----Original Message----- > =46rom: Geise, Brandon D. =5Bmailto:bdgeise=40geisinger.edu=5D > Sent: Monday, May 16, 2016 8:01 AM > To: dev=40ctakes.apache.org > Subject: RE: Offline access > =20 > I haven't tried it and is a guess based on reading the code, but you mi= ght be able to change the dictionary implementation name in the xml file = from UmlsJdbcRareWordDictionary to Concept=46actory, since Umls factory i= mplements from Concept=46actory. > =20 > -----Original Message----- > =46rom: Miller, Timothy =5Bmailto:Timothy.Miller=40childrens.harvard.ed= u=5D > Sent: Saturday, May 14, 2016 2:28 PM > To: dev=40ctakes.apache.org > Subject: Re: Offline access > =20 > Well, before we had online verification ctakes required downloading uml= s, extracting the right subset, and building a database for the dictionar= y tool. You can still do that - it is often necessary for use cases that = our default dictionary doesn't have coverage, and while I'm not sure the = state of documentation there have been several threads on the list about = it. I think if you do it this way you can skip the UMLS verification step= (though I don't remember exactly how that works) because you will have b= een verified at download time. > =20 > Can Sean or someone verify that this is true=3F If he builds his own di= ctionary (with the same subsets) can he skip the online verification=3F > Thanks > Tim > =20 > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > =46rom: John Travis Green > Sent: Saturday, May 14, 2016 10:12 AM > To: dev=40ctakes.apache.org > Subject: Offline access > =20 > I have a dod use case that requires offline umls verification. Anyone a= ccomplish this yet=3F I recall some chatter awhile back but initial flirt= ations with google were unsuccessful. thanks=21John > =20 > =20 > =20 > =20 > IMPORTANT WARNING: The information in this message (and the documents a= ttached to it, if any) is confidential and may be legally privileged. It = is intended solely for the addressee. Access to this message by anyone el= se is unauthorized. If you are not the intended recipient, any disclosure= , copying, distribution or any action taken, or omitted to be taken, in r= eliance on it is prohibited and may be unlawful. If you have received thi= s message in error, please delete all electronic copies of this message (= and the documents attached to it, if any), destroy any hard copies you ma= y have created and notify me immediately by replying to this email. Thank= you. > =20 > Geisinger Health System utilizes an encryption process to safeguard Pro= tected Health Information and other confidential data contained in extern= al e-mail messages. If email is encrypted, the recipient will receive an = e-mail instructing them to sign on to the Geisinger Health System Secure = E-mail Message Center to retrieve the encrypted e-mail. --5739e8c3_41b71efb_1d64--