Basically follow the procedure you used to setup the Celldyne.

If the test profile for the new instrument is the same as the old then you can use the existing file #60 tests. You may need to add/remove tests from any panel test that is used as an orderable test.

Create a new entry in the auto instrument file #62.4 for the new instrument and configure it appropriately with the test characteristics for the new instrument - result tests the instrument transmits and test codes the instrument sends (UI Test Code). You can use your existing entry for the Celldyne as a template.

You can use the existing load/list file (#62.8). Just adjust for any new tests that the new instrument supports which the old instrument did not.

With the release of patch LR*5.2*286 you can use the same tests (file #60) and datanames (file #63) for the results. Just change the units/normals if any for the new instrument. LR*5.2*286 retrieves the units/normals stored with the results from file #63 instead of using the values from file #60 when reporting/displaying test results. When the results are verified the units/normals specified in file #60 for the test/specimen are copied and stored with the results. The one "gotcha" here is if you are using a file #63 data name that have results for specimens that are several years old and predate the storing of units/normals. When old results are accessed which do not have the units/normals stored with the results, the software retrieves the current units normals from file#60 for the related test.

This assumes your running a currently patch VistA system, i..e your current on the released Laboratory patches and have not implemented local changes (Class III) to any of the lab verifying software.

You may want to review the documentation for the Lab UI patch (LA*5.2*27).




Steven Cuneo/HOSPOPS/VET/UTIA wrote:


Hi

Right now our Celldyne is interfaced to a Data Innovations box. We are working on getting a driver from them. We are expecting to modify the WORKLIST file.

Thanks, Steve


*"Carlson, Larry G" <[EMAIL PROTECTED]>*
Sent by: [EMAIL PROTECTED]

06/02/2005 02:45 PM
Please respond to
hardhats-members@lists.sourceforge.net


        
To
"'hardhats-members@lists.sourceforge.net'" <hardhats-members@lists.sourceforge.net>
cc
        
Subject
        RE: [Hardhats-members] Lab Instruments



        





Hi there,
How are you interfaced now? Dawning, Data Innovations, local direct connect interface, LSI and Lab Job??? Depending on this answer, you may have to make modifications to AUTO INSTRUMENT file and the LOAD/WORK LIST files etc.
-poo
-----Original Message-----*
From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of *Steven Cuneo/HOSPOPS/VET/UTIA*
Sent:* Thursday, June 02, 2005 11:21 AM*
To:* [EMAIL PROTECTED]
Subject:* [Hardhats-members] Lab Instruments


We are changing hematology instruments from Celldyne to a Bayer Advia 120 and getting ready to redefine our hematology tests. Can anyone point us to a procedure? Do we need to redefine the corresponding entries in the Lab Data file? Any other potential "gotchas" we should look out for?

Thanks
Steven Cuneo
University of Tennessee
College of Veterinary Medicine




-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members

Reply via email to