Several weeks ago, we had to grant LinkLogic access to almost all our Chart users. This is due to a 'defect' in Centricity, where users without this permission are unable to link an appended document to an appointment.
Ever since then, I as the LinkLogic manager, has been receiving a large number of flags on my desktop that say something like 'The L3ID 999 appears to already be in use on this station (the users name) ". The ID and name varies by user. I have opened a ticket with GE but as of yet no solution from them.
We are on Citrix and people are randomly assigned servers they connect to.
I thought you use to be able to control access to LinkLogic via the shortcut (-ll) but this does not seem to exist in CPS.
Any thoughts or suggestions are very much appreciated!
I get these all the time and just delete them. I was concerned at first only to the extent that GE support was. Since they put minimal effort into talking about it I just decided to let it go. It has been about 4 or 5 years now and there hasn't been a detrimental effect for us. It does seem like an informational thing, because it asks the question "OK to use this L3ID?". I don't know where that question is being presented in a form where you or the user could actually answer. I felt like there may be processes just sitting around waiting for a human to reply YES/NO but that doesn't seem to be the case because there are no complaints. GE should just change that message to a non query informational warning which can be ignored. Support did theorize that it was a duplicate EMR.INI workstation name entry but I even tried changing the names there but it had no effect. We don't usually clone machines so there should not be any duplicate EMR.INI entries anyway.
The -ll shortcut option went away quite a while ago. I think it disappeared with version 6/CPS due to the shared EMR/PM login thing.
Mike Zavolas
Tallahassee Neurological Clinic
We have been having this same issue for years. I just do like mike said and delete them, but it is still extremely annoying. The duplicate EMR.INI entry is an interesting theory. We DO clone all of our workstations so that may very well be the problem in our case. The hard part is, it would take me forever to go through emr.ini on 80+ computers.