anonymous wrote on Monday, August 31, 2009:
Phyaura, do you have an update on your lab module. Is there any way you can give a brief technical breakdown on how it’s going to work with OpenEMR? Will it do both Physician Ordering and also Result Retrieval? What’s the timeline for the different lab companies such as Quest, Labcorp, and Axiom?
jpmd wrote on Tuesday, September 01, 2009:
The lab interface will include an interface to order, result, route, display, store, and trend lab orders from the labs mentioned. We are making sure that it will meet CCHIT requirments.
The ordering will take place in the encounter as a form with tabs or links specific to the laboratory company. Once ordered by the user, the order will populate the OpenEMR database. Mirth (the third party HL7 engine) will poll the database for new orders and submit them to the appropriate lab company currently via a VPN tunnel. Once a lab is resulted Mirth will then populate the OpenEMR database with results and certify that the results are received. The labs will be routed with a notes section that will allow providers/users to forward or close the labs.
There will be extensive logging of every event. We are coming near completing our test plan with Axiom. Labcorp and Quest will follow. I have learned to not give definite time frames but I can assure you that we are very close. Once testing on our clients is complete we will release the user interface to the community and will help others connect to LabCorp and Quest.
Jude A. Pierre, MD
Phyaura, LLC
cfapress wrote on Friday, September 11, 2009:
So, does this mean we ought to figure out how to incorporate Mirth into the OpenEMR distribution much like phpMyAdmin and phpGACL ??
Jason
bradymiller wrote on Friday, September 11, 2009:
hey,
Isn’t this a java server. Somebody should install this thing just to get an idea what we’d be dealing with. If indeed a java server, then an appliance would deal with it well. Seems like lots of work would be required making all the "channels" in mirth that pull/place data into OpenEMR. Maybe a good secure interface for the patient portal to talk to also.
-brady
drbowen wrote on Friday, September 11, 2009:
I don’t trying to incorporate Mirth into OpenEMR is a very good idea. Mirth is a heavy weight Java application. The professional support companies may want to perate as portals for their clients but Mirth is going to be too complex for the majority of installations.
drbowen wrote on Friday, September 11, 2009:
Sorry that last post went out unedited.
I don’t think trying to incorporate Mirth into OpenEMR is a very good idea. Mirth is a heavy weight Java application that takes a lot of study by a IT professional. The professional support companies may want to operate Mirth portals for their clients but Mirth is going to be too complex for the majority of installations.
PhpMyAdmin is a security risk that will have to be taken out of OpenEMR to pass CCHIT certification.
Sam Bowen, MD
http://oemr.org
jwallace00 wrote on Friday, September 11, 2009:
it is a java web start project.
Mixing technologies will do a lot to confuse our userbase, but that aside, isn’t mirth just one of many possible implementations of information exchange? I think it would be a lot cleaner if we offered support for different HIE’s but steered clear of bringing one or more into the project itself. Integrating them with the project seems like a great way to bloat things unnecessarily.
whimmel wrote on Friday, September 11, 2009:
Mirth doesn’t need to be distributed with OpenEMR. If a user chooses to make use of it to connect to labs or elsewhere, it can be installed separately as a prerequisite. Much like OpenEMR doesn’t include MySQL or Apache.
If Mirth channels are developed and made available to the community, OpenEMR could distribute those (plain old XML files) in the /contrib directory.