Johnsd11 opened a new issue, #55: URL: https://github.com/apache/ctakes/issues/55
### What happened? Hi All I've been working on creating a dictionary for the 2023AA UMLS, specifically incorporating SNOMED and RxNorm. However, I've encountered two main challenges that I'm hoping to get assistance with: 1. Combining SNOMED and RxNorm in Dictionary Creation: To initiate the process, I extracted data from umls-2023AA-full and RxNorm_full. After utilizing NLM Metamorphosys to install UMLS, the conversion of SNOMED from umls-2023AA-full into RRF files was successfully accomplished. However, when I proceeded to employ cTAKES Dictionary Creator for transforming UMLS SNOMED and RxNorm into a singular dictionary, I encountered an issue. The challenge lies in the fact that I can only select one "UMLS Installation" source, limiting me to either SNOMED or RxNorm. Is there a viable solution that would enable me to effectively incorporate both SNOMED and RxNorm into the dictionary generation process? 2. Error Message During Dictionary Build: Following the selection of the NLM Metamorphosys output folder as the "UMLS Installation" source and checking all relevant boxes for Vocabulary and Semantic Type, I clicked on "Build Dictionary". Unfortunately, this action resulted in an error message being displayed. I'm seeking guidance on how to address and resolve this error in order to successfully complete the dictionary creation process. Error Message: Dictionary ctakesdictionary could not be built in F:\cTAKESLog Message: user lacks privilege or object not found: MED in statement [insert into MED-RT (CUI,MED-RT) values (?,?)] I truly appreciate any assistance that can be provided in overcoming these challenges. ### Relevant log output ```shell ``` ### cTAKES.error.log contents ```shell ``` ### Version 5.1.0 ### What operating system are you seeing the problem on? _No response_ ### Contact Details _No response_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
