ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Finan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CTAKES-17) include term rather than just CUI(s)
Date Mon, 08 Dec 2014 22:12:12 GMT

    [ https://issues.apache.org/jira/browse/CTAKES-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238553#comment-14238553

Sean Finan commented on CTAKES-17:

dictionary-lookup-fast has this ability.  The user can toggle the storage of preferred term
by specifying (or not specifying) "prefTermTable" in the cTakesHsql.xml resource file.

> include term rather than just CUI(s)
> ------------------------------------
>                 Key: CTAKES-17
>                 URL: https://issues.apache.org/jira/browse/CTAKES-17
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-dictionary-lookup
>            Reporter: James Joseph Masanz
>            Priority: Minor
> "I actually think it would really nice if cTAKES stores the snomed preferred term as
well as the CUI.  So the descriptions that downstream consumers could use should actually
be the preferred term instead of .getCoveredText()... Just my 2 cents..."
> I think it would be good to have an option to control this. perhaps with the default
being to include the description. but people in a production environment might not want it
included for performance or space reasons.
> One consideration is - do we include the SNOMED preferred term or the UMLS Concept name
-- probably the concept name because there can be more than one SNOMED code for a single CUI
(and therefore more than one SNOMED preferred term for a single CUI)

This message was sent by Atlassian JIRA

View raw message