Epic User Group

We are in the early stages of our deployment. Sandbox and Production were both up and working. Recently we noticed that in Sandbox Aggregation started failing with the following error. [ InvalidResponseException ] [ Possible suggestions ] Not working SOAP service... [ Error details ] Failed to process response....javax.xml.stream.XMLStreamException: DOCTYPE is not allowed I have down the following. validated connectivity between VA and Epic endpoint. checked the Interconnect user in Epic and it shows an authentication. Our Epic Technical teams are saying that nothing has changed in Epic. Any suggestions on what to look at next? ... View more

The Epic SER connector has been released! In conjunction with this release, we’re holding two webcasts next week to showcase functionality and answer questions that may come up: On  September 7th  we’re showcasing the latest integration work with stronger Identity Security integration to Epic. This session will demonstrate how you can automate identity provisioning into Epic and highlights new functionality for EMP and SER Provisioning, and API Integration. Register here ! As an existing customer of SailPoint, we want to make sure you’re set up to succeed. We’re hosting a customer only session the day after, on  September 8th, where we’ll have resources available to address questions that relate to your specific implementation of SailPoint IdentityNow and IdentityIQ with Epic as your EHR. Register here ! ... View more

Hi Customers, We at SailPoint continuously thrive to help you govern your identities better. With this respect, we will like to work closely and deliver solutions that would ensure that you can focus on core business. To start with, our Product management would like to hear about the “Credentialing systems” that you use. If you could help us understand the various credentialing software that you might be using in your organization and its priority for integration with SailPoint, to help you manage what accesses you may grant your “Providers” in a more streamlined, automated and a highly governed fashion.     Looking forward to your responses.   Thank you, The SailPoint Team. ... View more

Hello, just starting our Epic EMP connector journey and would love to hear how others would approach the following scenario for cube to EMP correlation. IIQ cube Our source data (HR) has a unique Employee ID for every employee ever hired. We like to leverage this unique value for correlation to all managed applications, Epic included. AD user (login for Epic) Users AD object has their employee ID attached. Since we tie IIQ to AD with this value we can easily handle name / UPN changes Today EMP is configured like: .1 is uniquely generated by Epic .45 is the UPN of users AD object (for login) Problem EMP .1 Would be where I’d like to correlate to cube by having the employee ID value set, but with hundreds of users already created using unique epic generated numbers, and Epic stating .1 cannot be changed, we have to look at something else. EMP .45: on user renames this value would change, so I don’t want to use it for correlation. From Epic Our Epic TS suggested using "I EMP RPT GRP THREE", we also talked about leveraging "external" attributes (Sounds like these are typically used to link outside accounts like Medicare).  Suggestions? Anyone else using these values in EMP?  What values are you using? ... View more

We were wondering how everyone has handled the implementation with regards to migrating EMPs and/or SERs across environments.  I understand there are multiple ways to go about this, such as creating in PRD directly, creating in PRD and migrating down environment. Specifically, I was wondering if anyone has successfully created records in a lower environment like TST and using data courier or content management to move it up to PRD in a way that minimizes the manual data courier work. ... View more