You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ctakes.apache.org by "Omkar Natu (JIRA)" <ji...@apache.org> on 2015/10/29 17:44:28 UTC
[jira] [Commented] (CTAKES-369) UmlsConcept subject is not
recognized propely
[ https://issues.apache.org/jira/browse/CTAKES-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980751#comment-14980751 ]
Omkar Natu commented on CTAKES-369:
-----------------------------------
Does anyone have an update on this issue? We're seeing the same thing and it is pivotal that we get a fix for it. Even if someone can point us in the right direction (i.e. the file and approximate time the issue arose), we'd be happy to help out.
Thanks!
> UmlsConcept subject is not recognized propely
> ---------------------------------------------
>
> Key: CTAKES-369
> URL: https://issues.apache.org/jira/browse/CTAKES-369
> Project: cTAKES
> Issue Type: Bug
> Components: ctakes-assertion, ctakes-clinical-pipeline
> Affects Versions: 3.2.2
> Environment: Linux
> Reporter: Tomasz Oliwa
> Attachments: family_history.txt
>
>
> Hi,
> I think there is a regression in the way cTAKES discovers the subject status ("patient", "familiy_member", etc.) of an UmlsConcept. Using cTAKES 3.2.2 and the AggregatePlaintextFastUMLSProcessor of the clinical pipeline in the CVD:
> 1. "Patient's brother has a myocardial infarction."
> "myocardial infarction" and "infarction" have subject = "patient"
> 2. "Father had a myocardial infarction."
> "myocardial infarction" and "infarction" have subject = "patient"
> 3. "Sister was diagnosed with a myocardial infarction."
> "myocardial infarction" and "infarction" have subject = "patient"
> 4. "Family member had a myocardial infarction."
> "myocardial infarction" and "infarction" have subject = "family_member" (this is correct)
> I am looking at the code of the SubjectCleartkAnalysisEngine. It looks like this is the code the pipeline calls to inferr the subject. How can this be fixed?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)