Labcorp module

anonymous wrote on Thursday, August 06, 2009:

I am working right now with a client who has custom developed code to work with labcorp and it pulls labs right into the patient file from tables within the database.  I have taken out the code that pertains to the lab module and am having my developer look through the code to see if there needs to be any changes to the code since it was developed using php4 coding.

The only thing is that it uses a program that must be loaded called "hypersend" I am working with labcorp right now and hypersend seems to be the program that sends/receives the hl7 messages.  The only thing is I believe that hypersend is only compatible with windows.  I am looking further into it and will keep everyone updated.

I need to work with someone on the openemr side of things to see if we can get this integrated so that other people can use it as well.

cfapress wrote on Monday, August 10, 2009:

Hi Chris,

I’ll step up and help you on this one.

Part of CCHIT certification includes interoperability with external systems, specifically labs. I have volunteered to be the lead for the parts of the code in OpenEMR focused on integration with external data sources.

I have some limited experience with HL7 data but years of experience with data integration in other systems.

So, fire away with questions!

Jason

jpmd wrote on Tuesday, August 11, 2009:

I do not know much about 'hypersend" but we are using Mirth to test sending and receiving labs from a major lab in Floirda.  We have coded changes in OpenEMR to send and recieve labs and should be testing connectivity with Labcorp to send and recieve labs to them.  I mention this as to make sure that we are not duplicating efforts.  Mirth is a great HL7 engine and it is free.  We have not released the code yet as we are not done but should have something to show in the next couple of weeks.

Jude Pierre, MD
Phyaura, LLC

cfapress wrote on Tuesday, August 11, 2009:

I’ve heard of Mirth and tried to understand what their software does but just can’t wrap my head around it. At first I thought it was just software. Then I realized it is more of a service. That’s about where my understanding stopped.

With OpenEMR how can we automatically send and receive lab data through Mirth?

Or perhaps we can’t, and instead we must build a custom UI to the Mirth service?

I’d really like to see some automated processes for batch sending and receiving lab data from any lab (Labcorp, Quest, etc) in such a way that human interaction is removed other than for clicking on a ‘send’ button to send the lab out and ‘view’ to see the lab results when they return. A notification would also be nice to know when results are available.

Sorry for my ignorance here. I haven’t seen anything that clearly describes how Mirth integrates with systems such as OpenEMR.

Jason

whimmel wrote on Tuesday, August 11, 2009:

We’re developing the order forms and user interface for the EMR and using Mirth to query our database, map fields in both directions, and communicate in both directions with the labs.

The lab order forms will work like any other encounter form. Mirth will poll for new orders periodically and send them as HL7 to the appropriate laboratory. Mirth is also listening for results. When they come back, it populates our tables on the EMR to be viewed and/or manipulated by the user. 

anonymous wrote on Tuesday, August 11, 2009:

Now, I am guessing since you’ve set it up in a way that Mirth queries your database then anyone who wants to use the lab module would have to connect to your database as well from the OpenEMR end?  Correct?

If so, is there a fee from your end as well?  Because if there is a fee then my way would be better for the OpenEMR community… because there is no fee. 

The lab module that I plan on donating to OpenEMR is already working in one practice with labcorp… the code is all done.  Just need to migrate it to OpenEMR and place some instructions on how to implement the server end software.

jpmd wrote on Tuesday, August 11, 2009:

We also plan on donating the code to OpenEMR.  Mirth is open source and can be manipulated however one wants.  There would be no fee if one wants to use the code.  This engine will be the bridge to other interoperability portions of OpenEMR.

Thanks.

Jude Pierre, MD
Phyaura, LLC

cfapress wrote on Wednesday, August 12, 2009:

So, I now understand that Mirth is a standalone application. It can run alongside OpenEMR. OpenEMR will pass information to Mirth, which in turn sends the HL7 messages to the lab and also retrieves the results. Sounds good. It takes a lot of work off from our shoulders.

Can some standard Mirth channels that can be built and distributed with OpenEMR?

That would save lots of time for future users.

Jason

drbowen wrote on Wednesday, August 12, 2009:

This is what Jude Pierre’s group in Florida has been working on.  They have invested about 4 months of development time.  Currently they are trying to finish up their code.  Jude Pierre / Bill Himmmelstoss have constructed extensive lab tables.  They have an alpha version with Axiom labs in Florida.  This will be a big improvement in our interoperability.

I have offered to pay for the LabCorp interface.  He and his group are thinking over my proposal.  A Quest Diagnostics is planned for after the LaCorps interface.

Sam Bowen, MD