[daveloyall]

Do you know anybody who might be interested in wiring Apache Camel up to be a Rhapsody replacement?

The NEDSS Base System has an expensive dependency on Rhapsody, but all it does is grab incoming HL7, do some transformations, and dump the result into a NBS table.

(For the uninitiated: State Health Departments are generally the users of NEDSS Base System... Rhapsody is a graphical ETL tool.)

[karmajunkie]

Just out of curiosity, any reason you're using Camel for that instead of Mirth? I've been out of the healthcare sector for a few years but at one time was doing essentially that same thing to build out the state biosurveillance network in TX. Mirth was a great fit for it at the time, I'd imagine it still is.

[daveloyall]

I haven't started yet. Just putting feelers out.

I haven't evaluated Mirth. It seems like a consumer oriented product. The marketing around it is so deep that I can't find a list of it what it's not good at...

Camel appears to be basically a library. As a programmer, I find that appealing.

[karmajunkie]

I'd take a closer look at mirth. It's highly capable, and I never had any major issues with it. You have a number of options for integrating with it, and I imagine those have expanded since last I looked at it. Email is in my profile, feel free to drop me a line, I kind of miss my public health work :)

[pjungwir]

I could do this. I'm not from Atlanta, but two other developers and myself have a small company, Columbia Ops, that has done a lot of HL7 work. Usually we use Mirth, but we could do it in Camel instead if you prefer something lighter. My email is in my profile.

[daveloyall]

Second plug in this thread for Mirth. Noted. And...