Notifications
Clear all
Topic starter
Hi everyone,
I was trying to add a suffix to one of our existing providers in CPS 12.12. I added the suffix from Admin>Application Users. The suffix seems to have taken effect in the Admin module itself but when I go to chart it doesn't seem to have update the suffix. I have tried it with other users in the past and have had mixed results. Has anyone had this issue before?
Thanks.
Posted : February 28, 2017 11:35 am
Yeah we have all sorts of issues when existing users have name changes/updates. the only way we have been able to get the correct name in all of CPS is to have our Database Guru find all the tables that record a suffix and to update it manually. I'm bummed to hear that it is not solved in 12.2
Posted : February 28, 2017 11:54 am
I believe its only in one table and we have to do it in the database.
Posted : February 28, 2017 2:21 pm
Hello Aashish,
Interesting this conversation has just come up. I have seen this issue ever since 2012 when integrated the EMR mod to our PM mod. I just spent a very large amount of time over the last week updating our user’s credentials with suffix for licensure / signature compliancy.
When a Suffix is added to the User, the USR table gets updated with the new suffix by concatenating the LAST field in the DB (<Last Name> + “ “ + <Suffix> = Smith MD). There is not a Suffix attribute to store this field in the USR table. The issue with the chart area (document provider or user dropdown lists) is the fact that it uses the DOCTORFACILITY table, not the USR table. Interesting fact is the DOCTORFACILITY table has a Suffix attribute available. This is where the bug shows with updating of the tables with new suffix entries on existing users.
Here is what I found with testing the naming fields in the user admin:
- New User entry
- Enter <First> <Last> <Suffix>
- both USR and DOCTORFACILITY table update with all fields
- Suffix will appear in the chart mod
- Enter <First> <Last> <Suffix>
- Existing User Update
- Update <First> <Middle> <Last>
- both USR and DOCTORFACILITY table will update all fields
- change can be seen in the chart mod
- Update Suffix only – ONLY the USR table will update
- NO suffix will appear in the chart mod
- Update (<First> or <Middle> or <Last>) AND add <Suffix
- Suffix will appear in the chart mod
- Update <First> <Middle> <Last>
As you can see, I found it was not an issue with the inception of a new user but found the change does not push to both tables when updating an existing user. I was able to determine the catalyst for pushing the suffix field across both the USR and DOCTORFACILITY tables for an existing user is to apply a ‘change’ to one of the name fields at the same time I added the suffix.
Steps to follow when updating an existing user:
- Add suffix
- Apply a change to last name by adding a character on the end (ex. Smith = Smithx)
- Click OK to save changes
- Open the user update screen again
- Change the last name field back (ex. Smithx = Smith)
- Check chart and you will see the suffix appear
Hope this helps. I am saddened to hear from Daniel that this is not fixed in 12.2, especially with the application of EPCS. Would have imagined the data migration across the tables as a priority action. Send me an email if you have any issues or need help walking through the steps.
Best,
Dennis
Posted : March 1, 2017 12:48 am
I have been told that this is not a bug, but actually designed this way on purpose. The reason I was told is that the signature line is not actually stored with the Chart Note when it is signed but is actually created from the USR table every time a document is loaded into the Centricity Documents screen. You will notice that if you update last name of a Provider that all of their signed documents that were signed before their name change now reflect their new name, the same would happen with their Credentials. I was given the following example as to why the Credentials do not update the signature when updating their suffix.
You have a Registered Nurse (RN) who retires and lets her RN license lapse. She later rehires as a Medical Assistant without her nursing license, you do not want to update her credentials on her old User ID and have that go back to all of her signatures from when she was an RN and change all of those to look like they were signed by an MA. I was told that what we should do is create a brand new User ID for this user since they have different credentials now.
This of course does not address the issue of hiring a new Provider and you do not want to add their Credentials until after they have provided proof or the case where credentials were initially entered incorrectly. In these cases, we use an SQL script to update their signature.
update USR
set LASTNAME ='Smith RN'
where LOGINNAME ='msmith2'
Posted : March 1, 2017 5:32 am
Topic starter
Thank you much for sharing Dennis.
Posted : March 2, 2017 6:54 am
