Has anyone set up a Cerner integration at a sight where MyExperiance is used?
We are working to set up provisioning positions in Cerner using roles.
On a Cerner HNA account a user can only have one position. however if they have MyExperiance enabled it allows them to toggle which position they are using. We have noticed that when the MyExperiance position is toggled it seems to update the primary position that is showed on the user's account.
Our main concern is if they have a position set by a role in Sailpoint, and then they toggle the position to something else using MyExperiance, Sailpoint will then see this change and provision the original position that they have by role.
Has anybody dealt with this, or come up with any workarounds?
Thanks
@jhaasel did you have any luck with this? We are running into this as well. While SP will switch them back to their qualified role, the change would not impact the caregiver's role while logged on in power chart.
This has been my concern also, about using Positions as Roles. Love to hear if anyone has found a solution! Or how you're using the position, orgs and personnel groups!
Sorry for the delayed reply.
The workaround that we came up with for this is a little complicated. We built a JDBC application that we called "Cerner Positions" This app is connected to our SQL server DB, and we built it to act like a connected app. (using the create,update, and Delete Provisioning rules).
we then backloaded the app with all of our positions as entitlements. and all users into the app with each of their myExperiance positions.
For the provisioning rules we have it set up to if the user already has positions in this app we trigger a manual task for a provisioning team to manually update their myExperience with the new position.
If they don't have any positions we trigger a workflow that creates a provisioning plan to add the position to their Cerner account. (This only happens one time)
Since this JDBC app is abstracted out from cerner the provisioning will only happen one time for each position, and if they change their position in MyExperiance Sailpoint won't override that change when it sees the new primary position on the account.
Are roles are all provisioning to our "Cerner Positions" JDBC app just to be clear.
Hopefully this makes sense. there is obviously a lot of other things to consider like handling removes and terminations.
Hi Experts,
When we got an issue of Authentication failed issue in the application while testing could anyone has an idea