Kevin, simply interfacing the devices into a Data Innovations or Dawning system would "do the trick", of course there may be so interface writing but that is not too terribly complex.
At our site in the VHA we use Dawning, if collects the results from the modalities and then sends HL7 to VistA. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlson, Larry G Sent: Tuesday, August 16, 2005 8:12 PM To: '[email protected]' Subject: RE: [Hardhats-members] Lab interfacing... In the past direct connect interfaces would be written to accept the data stream from each device, push it into the ^LA global. The listening interface would then parse it into the ^LAH global in an acceptable pattern. Each interface depended on a listener connected to a device in the device file. Each instrument would read the barcode label on the specimen container and send (by serial originally) the test results with the barcode - which was unique to this patient's test request. With the ^LA global set appropriately, the lab techs would enter the lab options to verify auto-instrument data and would verify each result. The Load/Worklist and AutoInstrument files were set accordingly for each instrument. I have written (stolen too) about 20 such interfaces in the past for the Seattle VA. We now use Data Innovations for all but 4 of our interfaces. Paying for DI results in a stable environment that doesn't depend on having programming expertise on board. Also, writing local direct connect interfaces - although fun - is a never ending job as the labs continue to purchase new instrumentation. Nonetheless, it may be that interfaces written for similar equipment for VA labs may run with little modification in instances where avoiding annual license fees are an issue. -poo -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Toppenberg Sent: Tuesday, August 16, 2005 10:21 AM To: Hardhats Sourceforge Subject: [Hardhats-members] Lab interfacing... We talked about this about 2 weeks ago. I'd like to come back to it again. I want to interface the lab in my office into VistA. The suggestion that I was given was to get the equipment to send HL-7 messages to VistA. So I went to our lab and pulled the technical manual for each of the pieces of equipment. I can't tell that a single one will generate HL-7 messages. Here is what we have: 1. Beckman Coulter Synchron CX5 delta http://www.beckman.com/products/instrument/genchem/cx5delta.asp This is our chemistries machine 2. Beckman Coulter Access Immunoassay system http://www.beckman.com/products/instrument/immunoassay/access.asp This runs our PSA's and TSH's 3. Cell-Dyn 1700 http://www.abbottdiagnostics.com/Instruments/default.cfm?syscat_id=4&sys_id= 16&path=1 This does our CBC's 4. Helena Labs Cascade M4 http://www.helena.com/catalog/CascadeM.htm This does our Protimes/INR's 5. Hologic QDR dexascanner http://www.hologic.com/wh/discov.htm This does our osteoporosis evaluations (This one DOES have a DICOM interface) 6. Other lab tests that we do that would likely have to have valued entered directly into VistA would be: UA, monoscreen, strep screen, pregnancy tests, ESR, manual differentials for CBC's Our Beckman Coulter machines are designed to connect to a limited "data-link" computer system that maintains a database of patient names and test results. The manual for the "datalink" doesn't mention anything about how to communicate to other computers. Our other equipments have RS232 ports. Would I have to manually create "drivers" for these devices? Any help would be appreciated. Thanks Kevin ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
