ProVue and Wyndgate Interface

[CMedina84]

Hello Everyone,

Hope someone out there is experiencing the same issue(s) we are. To briefly explain our current status we currently have actively interfaced two Ortho ProVue analyzers. On these analyzers we have successfully mapped orders for ABORh testing, Antibody Screens, DAT testing, Unit Confirmations, and Rh Phenotyping. During our validation testing was smooth and PERFECT. Once we went live and switched to production we noticed two issues:

1. Unit confirmations download beautifully but its on the upload where problems occur. Since we are not ISBT, we still have units with codabar. When Wyndgate/SafeTrace sends a unit confirmation order through the Instrument Interface it will translate a unit number 33FQ42432 to a numeric only 3142432. When the Provue processes this order and sends the result it sends it to the instrument interface with a specimen id of 3142432. The problem with this is, the Instrument Interface will compare this specimen id to the entire database to make sure there are no discrepancies. Well, our database is so large and patient id's which drive specimen id's are already in to the 7 digits so we are experiencing about 3-4% of our unit confirmations will error out in the Instrument Interface because the specimen id already exists in the database. Anyone experiencing this same issue? What is your work around for it?

2. Secondly, we are experiencing a significant amount of lag in our Two Way Holding table due to the size of our database. We opted not to have results autoupdate without user intervention. Has anyone chosen the same set up and experience the same lag when you query and try to release results? If so, Haemonetics said the Two Way Holding was not intended for the use of releasing results but only to catch results that fail the auto update criteria. Has anyone tried switching to Auto Update and has it improved lag times and the posting of results?