Pei Chen created CTAKES-216:
-------------------------------

             Summary: Medication Route in DrugNER - "IV" not identified as 
intravenous route
                 Key: CTAKES-216
                 URL: https://issues.apache.org/jira/browse/CTAKES-216
             Project: cTAKES
          Issue Type: Bug
          Components: ctakes-drug-ner
    Affects Versions: 3.0-incubating
            Reporter: Pei Chen
            Assignee: Pei Chen
            Priority: Minor
             Fix For: 3.1


Any objections to adding 'IV' to the Inject/Intervenious machines-  
RouteFSM.java?
                iv_singleInjectWordSet.add("intervenously");    
                iv_singleInjectWordSet.add("injection");
                iv_singleInjectWordSet.add("injections");
                iv_singleInjectWordSet.add("injected");
                iv_singleInjectWordSet.add("iv");
I just tested it out that it worked fine after we added iv to the FSM.  
I'll create a Jira in the meantime.

--Pei

> -----Original Message-----
> From: Masanz, James J. [mailto:[email protected]]
> Sent: Wednesday, July 17, 2013 1:59 PM
> To: [email protected]
> Subject: RE: Medication Route in DrugNER
> 
> info from Sean:
> 
> I would expect 'intravenous' to be found, but 'IV' isn't included in 
> the list of route FSM
> 
> IV might be being found as a roman numeral
> 
> ________________________________________
> From: [email protected] [dev- 
> [email protected]] on behalf of 
> Chen, Pei [[email protected]]
> Sent: Wednesday, July 17, 2013 11:08 AM
> To: [email protected]
> Subject: Medication Route in DrugNER
> 
> Does anyone recall if the intravenous or IV could be picked up as a 
> route by the DrugNER module?
> For example: "cisplatin 2.5 mg IV every 24 hours." IV gets picked up 
> as a Medication Frequency (4) instead of Route.
> 
> --Pei
> 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to