As previously explained, you need to determine how to generate this text file from your Epic EHR system. The next step is to create a text file that contains information about employees' access to patient health records in your organization's Epic EHR system. Step 2: Prepare a text file with Epic EHR audit records These values will be used in later steps.Īzure AD application ID (also called the app Id or client Id)Īzure AD application secret (also called the client secret)įor step-by-step instructions for creating an app in Azure AD, see Register an application with the Microsoft identity platform. During the creation of this Azure AD app, be sure to save the following information. Creating this app allows Azure AD to authenticate the push request for text file containing Epic EHR audit records. The app will correspond to the Epic connector that you create in Step 3. The first step is to create and register a new app in Azure Active Directory (Azure AD). Step 1: Create an app in Azure Active Directory In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages. The entire risk arising out of the use or performance of the sample script and documentation remains with you. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The sample script is provided AS IS without warranty of any kind. This sample script isn't supported under any Microsoft standard support program or service. The sample script that you run in Step 4 pushes the Epic EHR audit records from text file to the connector API so that it can be used by the insider risk management solution.
The script that you run in Step 4 will push the data in the text file to the API endpoint. You need to determine how to retrieve or export the data from your organization's Epic EHR system (on a daily basis) and create a text file that's described in Step 2. For instructions, see the "Create a custom role group" section in Permissions in the Microsoft Purview compliance portal. Alternatively, an admin in your organization can create a custom role group, assign the Data Connector Admin role, and then add the appropriate users as members. For a list of these role groups, see the "Roles in the security and compliance centers" section in Permissions in the Security & Compliance Center. This role is added by default to multiple role groups. This role is required to add connectors on the Data connectors page in the compliance portal. The user who creates the Epic connector in Step 3 must be assigned the Data Connector Admin role. Optionally, scheduling the script to run automatically to import audit records. Running a script to push Epic EHR audit records to the API endpoint. Setting up an Epic connector consists of the following tasks:Ĭreating an app in Azure Active Directory (Azure AD) to access an API endpoint that accepts a tab-separated text file containing Epic EHR audit records.Ĭreating a text file with all the required fields as defined in the connector schema.Ĭreating an Epic connector instance in the compliance portal.
Epic EHR audit records can be used by the Microsoft 365 insider risk management solution to help protect your organization from unauthorized access to patient information. Audit records from your Epic EHR system include records for events related to accessing a patient's health records. You can set up a data connector in the Microsoft Purview compliance portal to import audit records for user activity in your organization's Epic Electronic Healthcare Records (EHR) system.
For more information about Microsoft Purview, see the blog announcement and the What is Microsoft Purview? article. Microsoft 365 compliance is now called Microsoft Purview and the solutions within the compliance area have been rebranded.
0 kommentar(er)
