Hi All,
We are not live yet (next month) but are setting up CPS 12 with Active Directory authentication. Our workflow currently uses a triage nurse per site, and a prescription nurse per site. At many of our sites the staff filing these positions may change day-to-day. The current request is to setup a generic triage and prescription user for each site in CPS. Users will not login as these generic users but will subscribe to their alerts and flags. Is there a better process in CPS 12 for this? I am really not fond of generic users in Active Directory even if they never sign on.
Thanks,
Steve
We use many phantom accounts in Centricity exactly like this. It works very well. We prefix them all with a . to make them easier to organize. Any users qualified for a particular role checks the desktop of these phantom accounts when they have time available. For example, a patient needs a follow-up scheduled 6 months out but doesn't want to make the appointment during check-out. A future flag is set for 5 months out on the .frontdesk desktop. 5 months later it pops up for one of the front desk staff to take care of.
It is our experience that we have had to set up the generic user also in active directory because the login field is required and since we are linked to active directory, it has to be a valid user there as well. If someone has found a way around this, please share how.
Linda
We also use this method and have had great sucess with it. In our IT department the user is created in AD, the user is then setup and linked in CPS and then no one ever logs in as that generic user.
Unless I'm mistaken, generic accounts are a HIPAA violation unless the actual user can be traced.
You are correct, generic accounts are a HIPAA violation. Since others are using the same method and the notifications are a requirement for us here is how we have set it up: In AD these accounts have pretty much no permissions, and only the IS security group knows the password. In CPS it's the same, no permissions and cannot login.
Steve