You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ctakes.apache.org by "Finan, Sean" <Se...@childrens.harvard.edu> on 2017/08/30 14:59:42 UTC

RE: CTAKES lookup [EXTERNAL]

Hi Mathew,

When you ran the dictionary creator gui, did you select those 4 vocabularies as both sources and targets?  If you did so then the dictionary should contain tables named after them and the DefaultJCasTermAnnotator (must create better named façade ...) will add those codes to each discovered term.  If you look at your configuration xml in resources/../fast/ it should have lines mentioning those tables that are not commented out.

If everything looks ok in the xml, how are you checking for codes?  You can try using one of the OntologyConceptUtil.getAnnotationsByCode( .. ); methods to get annotations, or one of the getCodes( .. ) or getSchemeCodes( .. ) methods to see what codes were discovered.  

Sean

-----Original Message-----
From: Abilash.Mathew@cognizant.com [mailto:Abilash.Mathew@cognizant.com] 
Sent: Wednesday, August 30, 2017 10:34 AM
To: dev@ctakes.apache.org
Subject: CTAKES lookup [EXTERNAL]

Hi Team

I created a custom dictionary with SNOMED, RXNORM, ICD codes and CPT vocabularies.

The annotator "DefaultJCasTermAnnotator" performs look up only with CUI_TERMS table

The annotator "UmlsDictionaryLookupAnnotator" performs look up only with SNOMED and RXNORM  Dictionaries.

But I want the look up to occur with ICD and CPT dictionary tables also.

Please let me know if there is any other prebuilt way in CTAKES to perform look up with customized dictionary (as their metadata need to be configured in code) or the code has to be extended.

Thanks,
Abilash Mathew
This e-mail and any files transmitted with it are for the sole use of the intended recipient(s) and may contain confidential and privileged information. If you are not the intended recipient(s), please reply to the sender and destroy all copies of the original message. Any unauthorized review, use, disclosure, dissemination, forwarding, printing or copying of this email, and/or any action taken in reliance on the contents of this e-mail is strictly prohibited and may be unlawful. Where permitted by applicable law, this e-mail and other e-mail communications sent to and from Cognizant e-mail addresses may be monitored.