GH100s, Telcor, & Epic

Hi Beverly!

Are your ADT locations within Telcor mapped to the GH100 device? I know sometimes if registration creates a new ADT location, I have to make sure I go in and map it and enable the GH100. 

Also-- When you set up your GEM100s, did you first install the Werfen CCM software? You may need to add your specific barcode types in CCM if you haven't already.
There are things that *must* be set in CCM because there's no other place to do it. We have RALS and this is the case with barcode settings and a few other things. Have you been working with Werfen tech support?

Yes we did map our locations so I don't think that's it. We have been working wtih Telcor and werfen but unfortunately werfen has not been the most helpful. I'm very disappointed in the support we have gotten from them. Their only suggestion at this point is to turn off the patient list which seems like such a bad idea. 

We recently deployed the GEM H 100s and realized it was not accepting Patient's barcode. It would read the barcode but gave an error-"Patient not found." We are also using Telcor. Two things had to be done. Telcor had to disable the Patient List. The second step was for the Werfen IT group to do what they called a downgrade on the device Firmware. We have 11 Gem H100s, so we're talking about each device.  What this is in simple terms-they need to remove the patient list option. We found out that Telcor knew about the issue and are working on an update. Werfen also knew about this, but was making it to be Telcor's fault. Anyway, it seemed to have fixed the problem! monitoring the whole thing closely. 

Yes, this is exactly what we have been dealing with and it is so frustrating, from it not working, to them knowing and playing the blame game. I also really do not like the lack of positive patient identification with these. 

We are also trying to implement forty (40) GEM H100s to replace aging Hemochron Elites. Our experience and the fix provided with the patient ID issue is exactly as you described. In addition, we recently identified the Wi-Fi connectivity specs of the GEM H100s are not compatible with our CISCO network.  Therefore, Werfen is requesting ethernet connection until a patch can be created. 
We also feel that Werfen was aware of these issues, but did not communicate them with its customers.    Overall, we are disappointed because we undertook a system wide replacement with a system that has too many unresolved issues. 

We also have the same issues with WiFi connectivity. I escalated this problem with their Systems and Hardware Engineering group. After many months, Werfen is claiming they are expecting Cisco to publish official service packs soon. Check with Werfen. Only clincher for us is compatibility the APSP is for Software 17.9.4a and 17.9.5 and 17.12.4. We are running version a slightly lower version. This means we would need to upgrade our controller.
 For us, the WiFi  feature was the selling point. Big disappointment indeed!