Re: [Gnumed-devel] Mirth setup, versions etc was Lab importing ....

[richard terry]

On Wed, 23 Jan 2008 12:46:24 pm James Busser wrote:

Mirth is conceptually fabulous, but I don't think from my understanding it is 
designed in anyway to display the HL7, it is simply a 'black box', to channel  
and manipulate hl7 in any way you want. Of course it lets you put sample 
files in to help design your queries, and allows you do to all sorts of 
checking/forwarding etc.

I've found the beta 1.7 a little unstable as well.

Your software will still have to do the ultimate displaying, however the 
transformer, properly configured will save the appropriate records to 
postgres or your chosen database.

I stand to be corrected if I'm wrong.

Richard

> Karsten had listed steps as follows:
>
> - document how to setup Mirth on Debian/testing in general
>    - beyond what is documented already elsewhere
>    - content might go to our Wiki under, say LegacyAppConfiguration
>
> - obtain sample hl7 data from Jim
>
> - make Mirth pickup those file from a directory
>
> - make Mirth "properly display" those files
>
> - match hl7 content to target (GNUmed) database fields
>    - once you have a list of which data I can fairly
>      easily match them up and add necessary fields
>
> - use Mirth facilities to map hl7 data into GNUmed fields
>
> - document the above setup in the Wiki
>
> - export the Mirth channel for inclusion in our CVS
>
> I don't mind us doing the documentation in the second cycle, if it is
> more direct to get it working and if those who got it working could
> be available as we rebuild the steps to make it reproducible for
> others to do.
>
> Sounds like we are somewhere between
>       - make Mirth "properly display" those files
>       - match hl7 content to target (GNUmed) database fields
>         - once you have a list of which data I can fairly
>           easily match them up and add necessary fields
>
> Karsten had also suggested
>       Using Mirth would probably disallow use of existing Python
>       middleware. Which may prompt us to move some functionality
>       (like create_or_activate_encounter) into a backend stored
>       procedure. Which isn't that bad a thing after all.
>
> On 22-Jan-08, at 5:25 PM, Dave Cramer wrote:
> > Ok, at this point I have 1.7 installed and running. I can take one
> > of James' files and do a file input, file output . Has anyone
> > managed to figure out anything else ?
> >
> > Dave
> >
> > On 22-Jan-08, at 8:52 AM, Karsten Hilbert wrote:
> >> On Tue, Jan 22, 2008 at 08:41:03AM -0500, Dave Cramer wrote:
> >>> X-Mailer: Apple Mail (2.915)
> >>> Subject: [Gnumed-devel] Mirth setup, versions etc was Lab
> >>> importing ....
> >>>
> >>> Changing the thread subject to be more in line.
> >>>
> >>> OK, after viewing the 1.7 webinar it looks like Mirth could make
> >>> some
> >>> things easy.
> >>>
> >>> What I'd like to do is establish the baseline here.
> >>>
> >>> What version of Mirth do we want to work on. I vote 1.7, since it
> >>> appears
> >>> to have a much easier scripting engine.
> >>
> >> Agree.
> >>
> >> Karsten
> >> --
> >> GPG key ID E4071346 @ wwwkeys.pgp.net
> >> E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346
> >>
> >>
> >> _______________________________________________
> >> Gnumed-devel mailing list
> >> address@hidden
> >> http://lists.gnu.org/mailman/listinfo/gnumed-devel
> >
> > _______________________________________________
> > Gnumed-devel mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/gnumed-devel
>
> _______________________________________________
> Gnumed-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/gnumed-devel