140, T191, MTHICD9 233.1]
If you want an icd9 code that isn't in the cTakes umls dictionary then you can
find it online ... but that won't do you much good wrt cTakes.
Sean
-Original Message-
From: Assur, Ted [mailto:theodore.as...@providence.org]
Sent: Wednesday, September 04, 20
Hi:
Although we're testing a proof of concept with version 3.0 right now, I ran
into a couple issues in parsing with the AggregatePlanTextUMLSProcessor. In
testing the same processing with 3.1, I see significant improvements in
performance and accuracy, but schema changes in the output.
Specif
gt;>> similarly the LookupWindowAnnotator handles them both identically.
>>> So that suggests it is a problem with the actual lookup of the
>>> tokens in the LookupWindow.
>>>
>>> That's all I can do for now but maybe someone else who knows more
>>>
I'm trying to understand what would prevent the AggregatePlaintextUMLSProcessor
AE from correctly parsing specific problems that are defined in the UMLS
version used by cTAKES.
For example,
CIN (Cervical Intraepithelial Neoplasia) in its general usage is parsed out as
UMLS CUI C0206708.
CIN co
u are getting?
Also, are you running cTAKES behind a proxy?
--Pei
> -Original Message-
> From: Assur, Ted [mailto:theodore.as...@providence.org]
> Sent: Tuesday, July 16, 2013 1:29 PM
> To: dev@ctakes.apache.org
> Subject: UMLS login and pw
>
> Hello:
>
> First off, I
Hello:
First off, I apologize: I'm a newb to cTakes, and if this question's been asked
before on the listserv, I'm new to that, too:
I've followed the instructions for installing cTAKES, and can run it just fine
without the UMLS Analysis Engine for a test run.
I have a valid and current UMLS l