Notifications
Clear all
Topic starter
Hi,
We are trying to figure out where to add the providers credentials MD, DO, PAC,..etc in user management.
We have been putting it in the last name since this seems to be the place that will populate the credentials in the chart module. However, we have been getting claims rejected because the provider's last name doesn't match because it has MD next to it.
What is best practice? if you add it in the suffix field then the credentials may not show in all components of the chart. Even when we use the .sign quick text, there is no symbol for suffix.
Any thoughts about this issue would be appreciated.
Thanks,
Jude
Posted : April 3, 2018 9:40 am
I believe this is a long-term known bug. IIRC, the GUI combines the last name and suffix field into a single string before writing it to the last name field in the database.
I don't recall offhand if we edit the database suffix field manually. It seems like there's a trick in the GUI to get it to work correctly. Hopefully someone has more specifics on this.
-dp
Posted : April 3, 2018 10:04 am
There is definitely a bug with the suffix field. In my view, the best (and probably only) practice is to put the suffix (MD/PA/NP) in the last name field.
If claims are being rejected, this field will need to be modified/scrubbed before transmitting to the payor(s). Without knowing how this happens at your organization, I cannot really advise HOW to accomplish this, but it can certainly be accomplished.
Posted : April 4, 2018 8:21 am
We place our Credentials in the Suffix for the User's name, these get concatenated into the Last Name field in the USR table for Signature purposes.
The thing to remember is that when you create a new user it creates the user's Centricity Signature in the database at that time. So if you have left off the credentials and try to add them back on after the fact then they do not get added to the user's Signature (unless you add them the Credentials into the person's last name in the database in the USR table). Likewise, if you need to change the Credentials on an existing user, the USR table does not get updated for Signature purposes.
GE states that this is by design, because the actual signature is not part of the actual document and is stored separately. So if you change the Credentials in the Signature, then you retroactively change the electronic signature on every document that user has ever signed.
GE states that the best practice is to create a new user account for these users in these cases, so that their new profile uses their new signature. The same thing happens with name changes.
Posted : April 4, 2018 9:06 am
You can try to modify the user name in the USR.dbo table in SQL so it prints out correctly by adding the credentials in the suffix field manually.
Posted : April 13, 2018 1:08 am
