Groups | Search | Server Info | Login | Register


Groups > comp.databases.pick > #2219

Re: The Wish List

From "Jeff Caspari" <munge@idt.net>
Newsgroups comp.databases.pick
References <4d4444c5$0$20170$607ed4bc@cv.net>
Subject Re: The Wish List
Date 2011-01-30 08:17 -0500
Message-ID <4d4564d0$0$24249$607ed4bc@cv.net> (permalink)
Organization Optimum Online

Show all headers | View raw


I explained this poorly.  I'm sorry.

I am talking about send HL7 (medical) data over socket connections.  We 
regularly need to interface our Laboratory Information System to remote 
systems using TCP socket based protocol.

This might be receiving and acknowledging incoming lab orders from a 
practice management system such as eClinical and sending HL7 laboratory 
results back to their system.  All using TCP socket connections.

Or we might need to interface our LIS to a laboratory analyzer, which we 
typically do using serial connections, using a socket interface.

These scenarios present real challenges to us.  We usually resort to coding 
in a D3 program socket level code.  However this is really difficult and 
every new job is a new headache.

So I was hoping to handle all of this through a windows service where we 
simply place the [HL7] files from D3 into an outgoing folder and let the 
windows service handle all of the socket layer work.  Given that there are a 
number of different requirements regarding the way the data is 'wrapped' 
based on who we are interfacing with we would also need the ability to set 
parameters for how the wrapper is defined as well as other information.

A product that does all of this is called NeoTools (now I see it's called 
CorePoint):
http://www.corepointhealth.com/sites/default/files/products/datasheets/corepoint-integration-engine-features-overview.pdf

However this is way more than we need and way too expensive.

Thanks again and sorry for the poor original explanation.

Jeff

"Jeff Caspari" <munge@idt.net> wrote in message 
news:4d4444c5$0$20170$607ed4bc@cv.net...
> This is something I've always wanted and would be happy to pay for:
>
> We often need to transfer files to other systems.  One of the methods is 
> using TCP/IP over a VPN.  We avoid this because doing this from D3 is a 
> bit of a nightmare.
>
> I would love to have a windows program/service that allows us to define a 
> particular task (there might be many different transfers to many different 
> systems) and then all of the parameters associated with the task such as: 
> send file(s), received file(s), 'wrapper' info (stx, etc.), ack/nak, port 
> number...
>
> I don't care what it's written in as long as it works and is readable.
>
> Anyone interested?
> Jeff
> 

Back to comp.databases.pick | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

The Wish List "Jeff Caspari" <munge@idt.net> - 2011-01-29 11:49 -0500
  Re: The Wish List "Jeff Caspari" <munge@idt.net> - 2011-01-30 08:17 -0500
  Re: The Wish List Tony Gravagno <tony_gravagno@nospam.invalid> - 2011-01-29 17:52 -0800
  Re: The Wish List Scott Ballinger <scott.ballinger@gmail.com> - 2011-01-29 11:01 -0800
  Re: The Wish List Robert Joslyn <bobjoslynalt@gmail.com> - 2011-01-29 09:28 -0800

csiph-web