Setting up the EMIS API User for eSP: GP Record Viewer

James Harley -

Set up a new EMIS User

Set up a new user within EMIS:

Configuration > Organisation Configuration > Add > Add New User:

1_New_user.PNG

Create a new user with the username ‘BLACKPEAR’ and a password of your choice.

2_Black_Pear_User_1.PNG

When you enter a password for the account, untick the ‘User must change password’
box.

Set up the user roles: User Role Profiles > Additional RBAC Activities:

2_Black_Pear_User_2.PNG

Add the roles individually by entering the code in the search bar. Within the search
results, double click the appropriate item to ensure the role appears in the Selected
Items:

  • B0360: View detailed health records
  • B0380: Perform detailed health record
  • B0560: Perform patient administration
  • B0820: View patient demographics

2_Black_Pear_User_3.PNG

Click OK. The additional roles should display as follows:

2_Black_Pear_User_4.PNG

Save the new user

Configure User for Partner API

Go to: System Tools > EMAS Manager > Partner API

Highlight Black Pear Core and make sure the product is active by checking that a green tick is next to the name. If this is not the case, click on the ‘Activate Application’ button on the toolbar.

 

BlackPear eSP Updated.png

 

Click the Edit Users button on the toolbar.

Edit_Users.PNG

Tick the new user created (PEAR, Black) and enter a password.

Black_Pear_User_Password.PNG

NOTE: This password will need to be sent to Black Pear (see below)

Click the Login Access button on the toolbar

Login_Access.PNG

For the new user tick Auto Login and Allow Login.

Logins.PNG

 

Send Details to Black Pear

Please provide details of the new user to Black Pear (support@blackpear.com )to enable the practice to be connected. You will have been advised on an agreed method of sending this information in advance:

- practice ODS code
- practice CDB no
- username (BLACKPEAR)
- API password
- email address for notifications (if appropriate for the project)

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk