RE: Sundry; Problem Lists

Hi John, as the simplest answer to your comment/request: > I'd be interested in hearing more of what you meant by: " - if not completely > necessary for any real clinical use of nlp". I'll answer with your own words: > a good problem list, whether the physician admits to it or not, is > interpre

Re: Sundry; Problem Lists

Thank you Sean for taking the time to respond to me, it was much appreciated. I'm learning a lot about a lot. >I briefly discussed the first idea (acute vs. historical) with another physician (after you brought it up) and there was concurrency that such a feature would be extremely useful - if not

RE: Create a cTAKES patch 3.1.1 release?

Sounds even better to me -Original Message- From: dev-return-2193-Masanz.James=mayo@ctakes.apache.org [mailto:dev-return-2193-Masanz.James=mayo@ctakes.apache.org] On Behalf Of Chen, Pei Sent: Monday, November 04, 2013 4:08 PM To: dev@ctakes.apache.org Subject: RE: Create a cTAKES

RE: Create a cTAKES patch 3.1.1 release?

James, CTAKES-253 were only patches to existing ctakes (didn't include the actual ytex extensions yet.) I think we should make that separate and keep 3.1.1 just a patch release with bug fixes etc. --Pei > -Original Message- > From: Masanz, James J. [mailto:masanz.ja...@mayo.edu] > Sent

RE: Create a cTAKES patch 3.1.1 release?

Yes, I'll be release manager for 3.1.1 - thinking of starting a build for 3.1.1. next week. My assumptions are we would use 3.1.0 documentation. I see CTAKES-253 (YTEX) shows fixed in 3.1.1. So I suggest creating a small page or two about the specific differences (such as the inclusion of yte

RE: Create a cTAKES patch 3.1.1 release?

Thanks James. Not sure what happened earlier- probably some default filters in Jira to filter only outstanding issues. But yeah- I think there are plenty of good minor but critical patch fixes since the last release.. I take it you'll be the RM for this patch release as well :) --Pei > -Orig

RE: Create a cTAKES patch 3.1.1 release?

Hi Pei and all, For me, the link listed previously doesn't show as many items as this page does [1] We might want to refer to [1] in discussing what will be in 3.1.1 Specifically CTAKES-245 was not in the other list, apparently because it is already marked as Resolved/Implemented [1] https://

VM update

Contacted iDASH and UIMA teams about a potential VM distribution path. summary: 1. iDASH is circling back with us because the iDASH tools for NLP VIrtual Machine is out of date and they are looking for new iDASH members to keep it updated. 2. dev@UIMA suggested a potential "WAR" distribution

RE: Sundry; Problem Lists

Excellent! By the by, I know next to nothing about nlp - I'm just a software developer that (for some reason) jumped down this (nlp) particular rabbit hole. When it comes to nlp background, research, state and direction I'm hoping that somebody much more knowledgable than I will jump in. >aft

RE: Create a cTAKES patch 3.1.1 release?

There were several I marked as 3.1.1 that I thought were candidates for a point release. That list doesn't seem to show them all. Today I will also look through the rest and see if I have any others I'd like included in 3.1.1 -Original Message- From: dev-return-2183-Masanz.James=mayo..

RE: specificity in selecting EntityMentions when using AggregatePlaintextUMLSProcessor

Hi Ted, In addition to performing searches, > the hyperSql ( http://hsqldb.org/ ) database tool should allow you to perform inserts into the umls dictionary database used by cTakes. You can also create your own customized dictionary and run cTakes using only that dictionary or with umls plus

RE: Sundry; Problem Lists

Hi John, I hope that you didn't think that I was belittling your ideas or saying that anything has been done (and done). I was just throwing in two resources for further thought. You have brought forward some great applications for cTakes and nlp! Sean