The information contained in this document is confidential, privileged, and only for the use of internal Birdeye users. This document may not be used, published or redistributed.

This integration is supported for both SMB & Enterprise businesses.

Integrating Birdeye with Allscripts
User Manual - SUPPORT ARTICLE

Client Activation Process

Allscripts is an Electronic Health Records (EHR) system used by small-to-midsize physician practices. Allscripts allows the users to manage appointments, e-prescriptions, patient portals, and clinical charts. Integrating Allscripts with Birdeye will automate the process of sending out review requests on a daily basis.

Table of Contents

Birdeye allows you to fetch data from your CRM using a predefined trigger. Here is the supported trigger for Allscripts:

To successfully set up the integration, the client needs to ensure that Birdeye has access to the following actions: GetPatientDemographics, GetSchedule, GetServerInfo, GetUserAuthentication, and LastLogs.

Business IDs of all locations

Login to your Birdeye account, go to Left Navigation Rail and click on ‘Settings’. Once the new page appears, click on ‘Profile’ and select ‘Business Profiles.’

To view Location ID, hover over the ‘Status’ of location.

To raise a request for access to a client’s PMS, use the credentials detailed below:

URL: https://developer.allscripts.com/Account/Login
​Username : integration-support@Birdeye.com
​Password : Birdeye@12345

On the new screen, click on the ‘Request Client Activation’ button under the ‘Activations’ section.

Now, enter all the relevant details provided by the client on the setup call. Once all the details have been entered, click on the ‘Save’ button to finish the process.

NOTE: When the activation request is successfully completed, a confirmation email will be sent to integrations-support@Birdeye.com. If you are not a part of this email group, you need to get yourself added to it in order to access the confirmation email.

Check the current status of the activation request.

Log in to the portal using the credentials mentioned in the ‘Client Activation Process’. Then click on the ‘Usage Dashboard’ button under the ‘API Usage’ section.

Then click on the ‘View Report’ button under the ‘Client Activations’ section.

On the next screen, you can view the current status of the activation request.

Before you can integrate Allscripts with Birdeye, you will need to set up the following configurations on the integrations support dashboard:

To set up native integration, we have an integration support dashboard, where we need to set up the integration and then follow these steps to complete the configuration.

https://integrations.Birdeye.com/sign-in/

The trigger is automatically selected as only one trigger is supported.

Note: To fetch information for all the triggers available using curl commands, use this command. To replace triggers use this curl command.

Here, you can manage group level properties, which will be applied for all locations under a CRM.

Note: This step will create a group for our integration. Alternatively, you can do it via curl commands.
For SMB accounts you can access the curl command.
For Enterprise accounts you can access the curl command.

For Single Location/Multi Location Accounts, select the drop down and click on ‘Add.’
(In case of Single Location accounts, it will give you only one option).

A drawer will appear on the right-hand side.

The Status, Frequency and Next RunTime will be set by default. You can make changes if required.

Override Group Properties: With this, you can override the Customer Fetch Delay property added at group level, specific to each location.

Click on ‘Next’ and click on ‘Save.’

Note: For SMB and Enterprise you can use ‘manage the locations’ using this curl command.

Copy this Curl Command

NOTE: We will get the group ID once we run the first curl (Integration Group) and make a note of group ID as that will required while we will be doing the integration mapping.

Copy this Curl Command

Sample response: A sample response like this would appear after you run the curl command. The response will have the trigger name, description and the ID. This trigger ID will be utilized while creating the integration group. An integration can have one or more triggers. To use more than one trigger, enter comma separated values while creating the integration group.

Copy this Curl Command

Sample Response:

Copy this Curl Command

Once the Integration Group is created, the next step is to create the Integration Mapping.

Copy this Curl Command

Copy this Curl Command

NOTE: Location Name is mandatory in case of multilocation.

NOTE: Get User Details from Email

The ServiceUser displayed here represents “ubiquity_id”.
The username and password here, represent “Pms_user_name” and “PM_Password”. 3

These details will be shared by Allscripts team to allscripts@Birdeye.com under the file named “message.html”.

Configuring Group property details

NOTE: ServiceUser displayed here “10220c34e:0010220^1^” is a combination of three values: (i) ubiquity_id: 10220c34e (ii) client_id: 0010220 (iii) tenent_id: 1

These values will be used to create group properties.

Sometimes it happens the credentials entered were wrong during setup or are expired so we receive 401 Unauthorized Error while running the Integration and as a result Integration will be marked unauthorized. It will not run until the credentials are corrected and the business is authorized again which involves the steps as given in the below document.

Re-Authorise Document

Restriction reason is used to identify the contacts which have been opted-out(restricted) from sending a review request. This reason can be fetched from Kibana for contacts that are checked in already.

Possible restriction reasons for Allscripts are:

Troubleshooting steps: