CHWC battled this for years hoping that Paragon would fix the tie in between person file and security but it was like talking to a wall. In the end we create a ‘person’ for every employee that is only used for security purposes as users of the system. If the employee becomes a patient (we are rural so that happens a lot as we are the only show in town) then there is a ‘person’ record & medical record. This allows us to deal with the timings of licensed name changes and other name changes for employees who need access to Paragon.
We use a DOB something like 01/01/1901 and other minor details on the ‘phantom’ employee person that alerts registration to NEVER use for admitting employees as patients. Kind of a hassle to set up but a lot better than messing up patient charts and dealing with the timing of license name changes vs legal name change that never occur at the same time.
Again, Paragon should fix this but they do not fully understand what a problem is or they just don’t care.
Greg
From: parag...@googlegroups.com [mailto:parag...@googlegroups.com]
Sent: Thursday, January 29, 2015 12:36 AM
To: Abridged recipients
Subject: Abridged summary of parag...@googlegroups.com - 2 updates in 1 topic
· Name Change practices around userID - 2 Updates
Jim Roberts <JRob...@kvhealthcare.org>: Jan 28 12:50PM -0800
|
"Follett, Rick" <RFOL...@GSHLEB.ORG>: Jan 28 08:52PM
|
You received this digest because you're subscribed to updates for this group. You can change your settings on the
group membership page. |