[MT-L] Meditech and Single Sign-on
Pidgeon, Mark
Andrews Chris
We are Magic/CS 5.67 and looking at potentially implementing SSO as well, would love to hear the same feedback!
Chris
|
|
Chris Andrews
|
Bill Wohlers
Gevaert,Gary
We attempted to go with Meditech MSO and abandoned the project after testing it as it became too painful/confusing for our end users. We ended up purchasing a SSO solution which will help us bridge the conversion gap and also provide us with other features like badge login, obscure screen, dynamic printer assigns, etc.
Some of our pain points were:
1. Public PC’s, we had to set them up in a separate domain for Meditech to recognize them as ‘public pc’s’ and therefore present the appropriate login screen (multiple login screens in fact as it will prompt you for both the AD one and the typical Meditech on a public PC as it doesn’t know whether the user sitting down is already converted or not)
2. Public PC’s – users logging on had to follow an extremely precise process :
a. They cannot use Tab
b. They have to remember to ‘escape’ past the first login screen if they weren’t converted yet to using AD
c. They have to enter in the correct domain (we have a multi domain environment); it did not default the domain to the correct one like windows does
d. If they did not follow the order of user/pass/domain when filling in the login screen then the screen would simply go back to asking for your login info again, no alert/error
3. Multi-role accounts – For every role a person had they needed to have a unique windows AD account. Wow! We have a lot of multirole users who have a single windows AD Account and multiple Meditech accounts. (just one of the issues around this is – which account gets the email address attached to it?)
4. Conversion process – depending on what kind of user you were there were different conversion steps. It got to the point where I had a 4 page document (with lots of pictures) and users had to find their correct section which was a no-go.
5. There is a conversion list that users go on when you enable the system (i.e. live), you take them off the list when you want them to get the conversion confirmation screen and then get converted (which takes a second). Sounds great but unfortunately that quickly became a problem because:
a. The list is not sorted alphabetical or any manner that we could see so if you wanted to convert by department you had to scroll through the list to find the users one at a time. (and when you have 5000 users it can be a real pain)
b. Second, you cannot add anyone new to the list so our plan to convert by department would not have worked as all new hires (of which we have dozens per week) would have been live right away thereby short-circuiting our rollout plan
That’s just off the top of my head…
Once we had it working in test (for our core group) it worked great, it was nice and fast but it was decided that all the other issues made it a no-go and we looked at purchasing an app.
Hope this helps
Gary Gevaert PMP | Project Manager, Information Services | Niagara Health
IT 2South, Welland Site, 65 Third Street, Welland, Ontario, L3B 4W6
(905) 378-4647 ext 44806 | gary.g...@niagarahealth.on.ca
>>>> Practice Random Acts of Kindness and Senseless Acts of Beauty <<<<
From: Meditech-l [mailto:meditech-...@mtusers.com]
On Behalf Of Pidgeon, Mark
Sent: Wednesday, February 1, 2017 9:56 AM
To: medit...@mtusers.com
Subject: [MT-L] Meditech and Single Sign-on
Hello.