rnozick

Hi, Hope you will give us a call so we can talk. Robin

We are currently working with 2 sites that are converting from Cerner to El Dorado. We would be glad to speak to you directly about our work. Please email me at rnozick@rfnozick.com so I can get your email address. Thanks, Robin

It is actually a very nice system that seems to do everything all the American systems do. Delphyn is sold by Hemasoft. I've seen a demo for some African countries. What else would you like to know? Robin

I agree with angonzalez the costs of a system are not the software only. Part of the BB'er's responsibility is to ask these tough questions befoe they buy. Vendor Qualification is an important Quality Assurance step in the selection process. If the system tha is the "winner' in your analysis, lacks features that are absolutely necessary, make sure you get that in the contract. Happy Holidays everyone!

The company is knowledge Forge at www.knowledge-forge.com and they have some very nice e-learning modules for cGMP's in Donor and Transfusion. I thought they were very well done and Lucia Berte helped write them. Hope this helps, Robin

Our understanding is that you may be able to clean them up after you export the data from Classic and before you import them it into Millennium. If you are working with a Cerner Migration team on this, they would be the best resources. If not you can send me an email at rnozick@rfnozick.com and I will see if we can help you.

It's true that ARC is probably more than a year away from implementing ISBT 128 around the country. Richard Kroziere, the King of ISBT 128 Label Printing, is a great resource for information on this important label change. The AABB expects everyone to be in compliance and even if you get units from ARC now that are codabar you are expected to be printing labels for Pooled Products at a minimum, because they need a new DIN (Donor Identification Numbers) and they need to be labeled in ISBT 128 right now unless you have a variance. So why wait, if you are doing an update to your Blood Bank Computer system do it during that. You have to validate anyways because the system is changing so add the ISBT 128 implementation to the project and use a good firm (I happen to know one!) to help you get the whole thing done within the same timeframe of the update. Hope this helps...Robin P.S. Hope you feel better Richard!!!

The FDA usually expects the vendor to tell their clients any restrictions on software version and/or Equipment needed to make the system work according to specs. If there are no restrictions, then it is up to the client to validate their entire system works according to their requirements. I might call my vendor and make sure Vx of something works with Vy of something else as far as they know. It IS, after all, up to you as the user to make sure of this, but most of the vendors will help you with this verification if you ask. The FDA knows that not all parts of a system will be the same version, however the Vendor has to prove to the FDA that these versions work together as a system or that's when there might be restrictions placed on versions. Hope this helps. Robin

In BIQ, Sunquest displays the BMA 3 translation in the Transfusion History so it would depend on how you defined that. Hopefully your translations mean something. Also, there is a button in BIQ on the Transfusion History screen that links to the Unit History so the tech can get more information. I hope this helps.

Yes in V5.3 and V5.4 it is challenging to comply with the ISBT 128 Standards, but we are helping 2 sites right now. There are workarounds for several issues but you may consider getting a variance with the AABB for such as "/" numbers, appending component types, etc. For Divided Products we are using the unit's comment field to record the A0, B0 etc. because the system creates the "/" number and there needs to be a documented cross reference in some form and to be able to print the correct label through either Computype or Hematrax. In Version 6.4 the system is being designed to predict and assign the proper division during Component Preparation so have faith it will get better.

You can't have an Alpha character followed by a string of numerics followed by another Alpha character. That is the scenario that looks to Sunquest like a Codabar. So 'A1234B' would not be a good choice for a Sunquest Component Type code.

You are not spending money for nothing....Hematrax is the system that Sunquest will always use...they will not have their own printing system included in the Sunquest system...it will be an interface to Hematrax, so I don't understand your issue. It is either pay now, get the standalone version and then when the interface is available you will get it...or wait for the interface and pay then. You absolutely need Hematrax to print labels and if you do more than thawing units...like splitting, pooling etc. you need to print labels.

Are you on Version 6.X version? If you are, using the Hematrax system I have several Sunquest clients that are as compliant as possible right now. They have to print labels through Hematrax without an interface to Sunquest, however they have built their codes using the "E" code from ISBT 128 to ensure a safer system. It's not perfect but I feel very good about the solution we are promoting.

Dr. Drew: I have found that although alot of people are sometimes uncomfortable with "Frankness", they are generally the "Jellyfish" of life who do not like to hear the truth. I for one adhere to the "truth always" and have sacraficed being liked for speaking the truth. Congratulations! We need more people like you in the BB business. Robin:cool:

I could help you please email me at rnozick@rfnozick.com if you are interested. It would be less than you are being quoted.