anonymous wrote on Sunday, December 20, 2009:
Hi All,
We have come up with an approach to put this piece together with CPOE and Lab Exchange Network. The goal is to make it easy for individual practices to place lab orders and receive the results electronically from Quest and Labcorp.
anonymous wrote on Sunday, December 20, 2009:
Here’s the correct link:
jpmd wrote on Monday, December 21, 2009:
Hello All,
We have made significant strides with the goal of donating the lab interface to the community with a complete user interface for OpenEMR and connectivity to LabCorp and Axiom Labs now (Sonic Healthcare) via LifePoint. Quest to follow which should takes weeks after certification from Labcorp. In addition, the interface has the ability to route results to other users and order lab results from the lab’s respective commpendium of files. Reports have also been created to allow for further customization and meaningful use to be met.
I would hate to see the community throw money at another user interface and spend the time that we spent going back and forth with these lab companies (very painful at times).
Sam has already seen a demo of the interface but we cannot release it until certified by at least one of the 2 vendors.
Rod can we send you the database schema and changes for your review?
Jude A. Pierre, MD<br>
Phyaura LLC
sunsetsystems wrote on Monday, December 21, 2009:
Jude, is your work GPL-licensed? If so I’d love to see it. I do not want to see anything that is subject to non-disclosure (which has been my problem with LabCorp in the past).
jpmd wrote on Monday, December 21, 2009:
Yes it is and LabCorp is fully aware that we are OpenSource. They will likely require that we have a version locked for certification but we can work around that. Bill H is working on getting the database schema to me. We have been collaborating with Mirth on this and they are also GPL licensed as well. We plan to make the routing mechanism compatible for documents as well.
Jude A. Pierre, MD<br>
Phyaura, LLC
anonymous wrote on Monday, December 21, 2009:
Hi Jude,
Thanks for your suggestion. I know you have talked to Dr. Bowen in the past and may want to connect with him again. I know there are a number of issues related to certification and individual practices’ connection with Quest and Labcorp.
anonymous wrote on Tuesday, December 22, 2009:
I have uploaded the Lab Exchange Network solution proposed by Yijin of Maviq. Please review and comment. Thanks.
sunsetsystems wrote on Wednesday, December 23, 2009:
Re the Lab Exchange Network… I’m concerned about liability issues for such a service. Seems like a lot of things could go wrong, actual or perceived.
wooyi wrote on Thursday, December 24, 2009:
Rod - can you please list out your concerns? The Lab Exchange Network would be a like a 3rd party service run by the OpenEMR non-profit, similar to a clearing house, ePrescription or drug interaction service.
sunsetsystems wrote on Thursday, December 24, 2009:
Just the concern of liability. If something goes wrong and the results are lost or incorrect with severe consequences to the patient, what is the likely outcome? This is a legal and business planning issue and might also impact the technology design. That’s all I have to say about it.
wooyi wrote on Thursday, December 24, 2009:
Rod - that’s a good point and certainly something to consider in the design. This concern is also relevant to the ePrescription piece. BTW, Does OpenEMR have a way to listen to outside messages securely at the moment?
sunsetsystems wrote on Thursday, December 24, 2009:
Not sure about the context of your question, but since OpenEMR is a web application, I’d say the easiest way to send a secure message to it is via HTTPS. So you could write a suitable PHP script and configure the web server accordingly.
Or you can use a web services protocol, probably SOAP since that is what PHP supports best.
bradymiller wrote on Thursday, December 24, 2009:
hey,
By having OpenEMR be a listener, you’d then have it open to the internet. A better strategy may be to have a script in OpenEMR incrementally connect “scrape” to your OSMS server to collect information and/or get status of information. Then no need to open it to the internet.
-brady
anonymous wrote on Wednesday, January 06, 2010:
Diane Carter has pulled together a list of 354 lab tests out of a bigger list of 1,000+. She has also identified 185 of them as common tests, which cover 80% of all lab orders. Please review the list and let us know which common tests should be included in OpenEMR lab catalog. For those who don’t know Diane, she’s a licensed CLS in California and a lab manager for 8 years.
: http://www.openmedsoftware.org/mw/images/b/bd/Lab_Orders_Selection.pdf
wooyi wrote on Wednesday, January 06, 2010:
Brady
I agree that we can use a polling mechanism, but the problem there is that the lab exchange server would then have to store the messages/results from the labs. I was considering of doing a straight route through from the external lab to the OpenEMR application to decrease the complexity of the lab exchange server functionality. I guess, it is easier to secure the server than open up every OpenEMR site.
sunsetsystems wrote on Wednesday, January 06, 2010:
I wouldn’t count on any given OpenEMR server being available for connections at any given time. Stuff happens.
jpmd wrote on Wednesday, January 06, 2010:
In response to the lists of labs…. This is great but, Labcorp requires that every client have there own unique compendium of labs used by the provider and distributed for each interface connection. Different lab companies will have different display names and tests available. Once we are able to upload our lab code (to the wiki site), you will notice that we have grouped ordering by lab facility and listed codes specific to that lab. Later we may want to have a relational table to reference similar labs from multiple companies to an OpenEMR lab codes.
Jude A. Pierre, MD<br>
Phyaura, LLC
anonymous wrote on Wednesday, January 06, 2010:
Hi Jude,
Yes, we know that and have planned to do mapping for Quest and Labcorp. Do you have permission to share the relational table. If so, please email it to me at thomaswong.usa@gmail.com. Thanks.
dlee5400 wrote on Monday, February 08, 2010:
Does either Quest or Labcorp accept a “webservice” connection for transmitting data? And did this project fail to get someone from either company to interact with the project?
dlee5400
jpmd wrote on Monday, February 08, 2010:
Labcorp requires a separate VPN per enduser and you need an HL7 engine to tranlate the data. We are using Mirth. Quest uses SOAP interfaces to make the connections. We are in direct communication with both parties and will be releasing code soon.
Jude A. Pierre, MD
Phyaura, LLC
www.phyaura.com