Please note that the solution will not use a request/response cycle because
my main use case is with EMRs and I am batching up requests so as to not
exhaust cTAKES :)


Thanks,

Matthew Vita
www.matthewvita.com

On Wed, Oct 25, 2017 at 9:27 AM, Matthew Vita <[email protected]>
wrote:

> Gandhi,
>
> I am actually working on a series of Docker containers that expose an HTTP
> endpoint to send clinical text to and then it POSTs the results back to
> your application's HTTP endpoint in JSON. Please let me know if this
> approach interests you and we can schedule a Google Hangouts to talk about
> what work is left (I estimate that I will be done in a month and a half).
>
> Please do note that this solution is 100% free/open source :)
>
>
> Thanks,
>
> Matthew Vita
> www.matthewvita.com
>
> On Wed, Oct 25, 2017 at 6:20 AM, Gandhi Rajan Natarajan <
> [email protected]> wrote:
>
>> Hi All,
>>
>> We have extended the cTAKES web application available under
>> https://github.com/healthnlp/examples/tree/master/ctakes-temporal-demo
>> and added our custom annotator. We have tested the same and it works fine
>> with CVD. But we are facing problems while trying to expose this as rest
>> service.
>>
>> cTAKES uses Spring 3.1.2 version internally which don't have out of the
>> box support for rest controller. Can we go ahead and update the spring
>> version to 4x in cTAKES? Will it have any impact in the cTAKES behavior?
>> Also is there a better way to expose cTAKES as rest service apart from
>> spring?
>>
>> Please advise.
>>
>> Regards,
>> Gandhi
>>
>> This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they are
>> addressed. If you are not the named addressee you should not disseminate,
>> distribute or copy this e-mail. Please notify the sender or system manager
>> by email immediately if you have received this e-mail by mistake and delete
>> this e-mail from your system. If you are not the intended recipient you are
>> notified that disclosing, copying, distributing or taking any action in
>> reliance on the contents of this information is strictly prohibited and
>> against the law.
>>
>
>

Reply via email to