zakaria91 wrote on Wednesday, October 28, 2015:
Hi,
I’m new in OpenEmr and i’ve got a Problem with the Connection between OpenEmr and Mirth Connect.
My aim is to add a link on Openemr interface to a specific directory where i received my HL7 messages from Mirth Connect.
Had anybody the same problem or a suggestion how to solve the problem.
Thank you.
visolveemr wrote on Wednesday, October 28, 2015:
Hello Zack Ahmed
What specific problem/issue you got in implementing mirth connection to OpenEMR?
From your statement, we assume that you have got HL7 messages from mirth connect to a directory. To add a link of that directory in OpenEMR, you need to customize the specific file in OpenEMR, where you would like to have that link.
Thanks
OpenEMR Customization/Support Team,
ViSolve Inc
services@visolve.com | Phone: 408-850-2243
Demo’s @ ViSolve Demo Library
shangyujuan wrote on Sunday, January 17, 2016:
I have the same problem, as we want to do the link between openEMR procedure output results with the third-party LIS system with relational database. We have found specified tables in openEMR to store the lab results, and would construct a channel in mirth to connect LIS database table to the openEMR tables. But our question is that could we transform the LIS table into HL7 2.X message first, then insert into the openEMR system directly?
Many thanks.
Shang
teryhill wrote on Sunday, January 17, 2016:
Yes you can send information from your LIS to OpenEMR with Mirth directly. Mirth is a very powerful tool. It will be alot of work with in the transform section of Mirth. We have a client that we do that with and it was a very large project. Be ready for a lot of work, or hire a developer to do it.
Terry
cmswest wrote on Monday, January 18, 2016:
yes, you can save it as hl7 version 2 and then insert it directly thanks to Rod Roark’s development of importing from local filesystem or sftp, plus there’s been many updates due to the recent mu2 work
check out the navigation menu under Procedures->Providers and choose ‘Add New’
mdsupport wrote on Tuesday, January 19, 2016:
We may be talking about two different things here. If Mirth has direct access to LIS and EMR tables, understand the structure as order >> items on the send side and order >> report >> results on the receive side, then do the mapping. You can further simply by using few views to save lot of repeating ‘procedure_’ prefixes and make code readable.
Other case deals with hl7. Mirth shines there as it takes care of message validation and makes a xml structure available for mapping.
In both cases, bear in mind that EMR structures capture limited number of fields. Also you can ignore the catalog configuration if you plan results-only interface.