cableops wrote on Tuesday, January 24, 2006:
Greetings all!
Is there a resource where I can download the OpenEMR HL7 specs and perhaps some sample ORU messages?
Thanks in advance.
sunsetsystems wrote on Tuesday, January 24, 2006:
I don’t think the HL7 parser does anything useful. Does anyone know where it came from?
– Rod
www.sunsetsystems.com
cableops wrote on Tuesday, January 24, 2006:
Pls correct me if I am wrong, I read in an earlier post that it is used to import lab results from text files. I believe the lab mentioned was Tricore.
drbowen wrote on Tuesday, January 24, 2006:
I believe it was included by Walt Pennington’s group. This code was not part of the Synitech version 2.0.
It does work. There is a test message included with the ditribution. The functionality has yet to be put to good use.
I have thoughts about using it to try to make a 1 or 2 way connection with my Lab vendor, LabCorp, as part of my nascent LIS.
I am not sure which version of HL7 it uses.
Sam Bowen
drbowen wrote on Tuesday, January 24, 2006:
Andres Paglayan had modified the parser to import labs from his vendor, Tricore, in Santa Fe, New Mexico.
He has not imported this to the OpenEMR distribution. My understanding is that he got tied up with his day job and had not progressed any further.
Sam Bowen
andres_paglayan wrote on Tuesday, January 24, 2006:
yup, that’s right,
the lab import is not finished yet,
it’s based on:
http://pear.php.net/package/Net_HL7
andres_paglayan wrote on Tuesday, January 24, 2006:
I can send you privately some dummy hl7 files,
although hl7 is a standard, each lab or facility have their own implementation on which goes where,
I have that of tricore, but don’t know of others.
connectivity is the other issue,
Tricore uses pptp vpn tunnels to access their internal ftp server where the results are placed,
for Linux to act as an pptp client trhough a windows vpn connections you may need some kernel re-comp with an extra encrypt option checked on,
cableops wrote on Tuesday, January 24, 2006:
Thanks for the responses. You can email the dummy files to: cableops at gmail dot com
voipbound wrote on Thursday, July 24, 2008:
How did U do with the parser and test file. I have just started looking into it and I am lost. Can U post your modified version up and the test file for me to learn what you had to do to make the interface. One other thing is that once an interface is created, what happens to the lab results? Does it get parse to the right patient to be view or what?
rpl121 wrote on Thursday, August 14, 2008:
Today the two IT persons from Quest Diagnostics came to our medical office to help us set up a new interface with their laboratory. Among other things, they gave us a windows executable that downloads HL7 lab reports at specified times and places them into any desired directory on our computer.
I tried the HL7 parser/viewer in the 2.4.8-dev version of OpenEMR and got some parsing errors.
Is anybody working on an HL7 laboratory interface for OpenEMR?
If it will help, I’d be glad to read up on laboratory HL7 reports and try to contribute, but at this point I’m still groping.
Ronald Leemhuis MD
cableops wrote on Thursday, September 04, 2008:
The problem with HL7 lab results is that each lab has their own format of sending results. Quest, LabCorp etc have enough small differences in their formats to prevent the messages from parsing correctly. In addition, the codesets used by each lab to identify test components (eg, HGB) is proprietary and vary for each lab.
I have developed a small application that I call SmartLink that functions as an aggregator to accomodate the differences between the different labs HL7 structure and codsets. The output is a unified format that can be modified specifically for OpenEMR or any other EMR that can accept HL7 lab results.
The application is browser based and can securely display reports in PDF, flowchart and graphical views.
The objective of the application is to make lab results easily accessible in electronic format for physician offices and allow other apps and EMRs to be able to import lab results minus the disparities.
Deployed in your environment, the application will pick up the files dropped by Quest, and convert to OpenEmr HL7 structure and codeset. The app can accomodate other labs as they are added.
Any lab and any emr using HL7 is supported.
Send me a message if you would like to see a demo of the application.
Thanks!
voipbound wrote on Thursday, September 04, 2008:
That is great news. Are you planning on contributing it to the community or is it still in alpha?
whimmel wrote on Saturday, September 06, 2008:
Does it interface with OpenEMR or is it a separate application?
voipbound wrote on Tuesday, September 09, 2008:
I had emailed him to the gmail address that he provided but have yet to receive a reply. Has he contact anyone? Does he plan to contribute this module to the community or hope to keep it proprietary? Does anyone know?
cesmall wrote on Wednesday, September 17, 2008:
Going back to the origin of this thread… Can anyone point a newbie to the HL7 structure that Open EMR uses? Or am I to understand, based on this thread that there isn’t really anything of value implemented yet to interop out of/into OpenEMR from an HL7 messaging perspective?
Another approach is to use an HL7 opensource integration application like Mirth (http://www.mirthproject.org/) to translate to the OpenEMR required structure.
cesmall wrote on Friday, September 19, 2008:
To add some context. As I was reviewing the CCHIT requirements, I see these HL7 standards for…
Admissions:
<<
The system shall provide the ability to receive patient registration data from an outside system
Transfer of registration and patient identification data between practice management systems and EHR is very desirable. Although earlier certification is desirable, without implementation guides, certification cannot happen.
>>
Appt Sched:
<<
The system shall provide the ability to receive scheduling information from a scheduling system
Transfer of data between a practice management scheduling system and an EHR is highly desirable and is essential for some EHR operations. Although earlier certification is desirable, without implementation guides, certification cannot happen.
HL7 2.4 Scheduling
>>
Labratory:
<<
The system shall provide the ability to receive and store general laboratory results (includes ability to differentiate preliminary results and final results and the ability to process a corrected result)
The test files are designed so that products implementing HL7 v2.5.1 standard will be found compliant. The test identifier will be encoded in LOINC, and will be drawn from among 52 common test codes. Refer to the 2008 CCHIT Laboratory Interoperability Test Instructions and Applicant Form for the list of these codes and more information on the current interoperability test procedures.
>>
Any insight into OpenEMR ability in these areas would be appreciated.
thanks.