Hear, hear!
From: Peter Abramowitsch
Sent: Tuesday, December 7, 2021 1:17 PM
To: dev@ctakes.apache.org
Subject: Re: empty preferredText [EXTERNAL]
* External Email - Caution *
"but I might revisit it on a snowy afternoon this winter. " >
t it on a snowy afternoon this winter. Of course, if
> anybody out there in the dev world would like to take a first crack at it
> ...
>
> Sean
> ________
> From: Peter Abramowitsch
> Sent: Tuesday, December 7, 2021 12:34 PM
> To: dev@ctake
snowy afternoon this winter. Of course, if anybody out
there in the dev world would like to take a first crack at it ...
Sean
From: Peter Abramowitsch
Sent: Tuesday, December 7, 2021 12:34 PM
To: dev@ctakes.apache.org
Subject: Re: empty preferredText [EXTERN
I think the issue is that preferred text in the dictionary is only
populated by matches from the "dest" vocabularies and it uses *their*
preferred text. If there's no match in any of them, then it should put the
CUI's own preferred text entry in the dictionary, but it doesn't. I'm
pretty sure It'
OK, I thought this might be what's happening. I did check my 2021 UMLS release
and the cui does seem to have a preferred text but I think my container is
using an older release. For what it's worth the CUI is:
C0360554
and a sentence that reproduces the issue in CVD with the current release is:
Hi Tim,
Yes, I've definitely encountered it. It happens when the concept has a
CUI_TERM which has matched the text, but there is no corresponding entry in
the SNOMED or other vocab table mapping CUI to SNOMED. The obvious choice
is to use the covered text as a surrogate, but technically it coul
Hello,
I'm using the dictionary lookup (through ctakes-web-rest) and trying to read
off the preferredText that comes back as a human-readable way to display the
CUI. On a very small percentage, there does not seem to be any preferredText.
Has anyone else encountered this? Is this a limitation of
