We use first initial of last and first name + 6 digit employee #. We don't change mnemonics if users marry/divorce.
And the employee nos are assigned permanently to an employee and never re-used. We use alternative solutions for our students, consultants, docs, etc.. Carol Lapointe Senior Systems Analyst Régie de la santé du Restigouche/Restigouche Health Authority Campbellton, NB, Canada [EMAIL PROTECTED] 506-789-5902 ________________________________ From: meditech-l@MTUsers.com [mailto:[EMAIL PROTECTED] On Behalf Of Julia Carter Sent: June 5, 2007 8:47 AM To: Renae Kendall/mhhcc.org; meditech-l@MTUsers.com Subject: RE: [MEDITECH-L] Setting up mnemonics Hi, Renae, At my former hospital, we went with Meditech's recommendation of first two letters of first name, last three letters of last name. So my mnemonic was JUMCL, based on my last name at that time. (I have divorced and remarried since then, so I was stuck with that mnemonic because we also made the decision that we would change user names, but not mnemonics). That did cause some issues with users being unhappy with old mnemonics as well as a mnemonic not "matching" a user name. However, Meditech's explanation was that documentation in some areas was linked to the mnemonic, so that was the justification. This naming convention could work in a single facility, but with multiple facilities, you'd inevitably have duplicates. Even in our single facility, we had duplicates and then had to move out of the naming convention and into the alternative of three first, two last. At the sites where I'm currently working, they chose a role-based mnemonic, so I see lots of mnemonics such as IT.JFC, PFS.JFC, ADM.JFC or something similar. In this situation, if a person changes jobs, their mnemonic is likely to change, which would leave you with inactive users. As attrition hits and users leave, by necessity you'll have to inactivate them, so you're going to have inactive users. You need to choose the naming convention that makes the most sense for your facility, have valid justification for it and then address the changes equitably. Hope this helps because I haven't run across the perfect answer yet! Julia Julia Carter, CPAR Consultant Consultant People 396 W Main Street Lewisville, TX 75057-3866 * 469.948.4000 Ext 308 * [EMAIL PROTECTED] e http://www.cpeople.org <http://www.cpeople.org/> ________________________________ From: meditech-l@mtusers.com [mailto:[EMAIL PROTECTED] On Behalf Of Renae Kendall/mhhcc.org Sent: Monday, June 04, 2007 4:04 PM To: meditech-l@mtusers.com Subject: [MEDITECH-L] Setting up mnemonics We are a new MEDITECH site and are having the discussion on how to set up mnemonics. How have other hospitals done it? We want to assign one mnemonic that does not change irregardless of name change, marriage or divorce. We basically do not want inactive users in the database. Any thoughts or lessons learned. We would like to just to first initial and last name, but know that with divorces that could get sticky if we do not change the mnemonic for sign on. Thanks, Renae Renae Kendall, RN Clinical Systems Supervisor Information Systems Memorial Hospital and Health Care Center Jasper, IN 812.481.0152 Fax 812.482.0541
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= To subscribe or unsubscribe to the meditech-l, visit MTUsers.NET. To check the status of the meditech-l, visit MTUsers.NET. For help, email [EMAIL PROTECTED] Visit the MTUsers WikiPedia at MTUsers.NET/mwiki ______________________________________ meditech-l mailing list meditech-l@MTUsers.com http://mtusers.com/mailman/listinfo/meditech-l
