Success Story

EHR access, automated down to the template.

An academic medical center built its own role-based access layer for its electronic health record system with READI, avoiding a license increase of about $100,000 and handling data its IGA platform could not.

Extending SailPoint & IGA

Medical team consulting digital medical records

$100K Approximate license increase avoided, with no change to the READI license.

At a glance

Customer Academic medical center and health sciences university.
Challenge Automate role-based EHR access without a license increase of about $100,000, including EHR data the IGA platform could not process.
Solution A role-based access layer built in READI Bot Studio, extended to Active Directory, onboarding notifications, and ServiceNow ticket routing.
Result About $100,000 in license cost avoided; thousands of EHR permissions assigned automatically; no change to the READI license.

The challenge

The electronic health record (EHR) system is the most sensitive application in a hospital. Access to it is granular, spread across thousands of individual permissions, and it changes constantly as clinicians, residents, and staff join, rotate, and leave.

The medical center’s IGA platform could integrate with the EHR, but only with a license increase of about $100,000. Even with that license, the integration could not handle the EHR’s multi-response fields, which hold several values in one field separated by a special control character.

The EHR was also only part of the job. A new employee needs the right Active Directory groups, and the teams who support that person need to know they are coming.

What changed with READI

The team built its own role-based access layer using READI Bot Studio and database tables. Five attributes drive it: company, vendor, location, department, and job code. Together they map each person to an EHR template.

Each template acts as an access profile. Assigning one template grants thousands of granular EHR permissions at once, multi-response fields included.

Every use case runs on three bots: one to view the mappings, one to add rows, and one to update them. Changing who gets what is a matter of updating a row.

The team then applied the same formula beyond the EHR:

Active Directory: role-based group assignment.
Email notifications: role-based onboarding instructions sent to the right people.
ServiceNow: tickets routed to the right team.

A new employee now triggers the AD group assignment and the right team notification at the same time. Assigning the group is half the job; making sure the people who support the new hire know what to do is the other half.

Because READI is priced per human identity with unlimited connectors and automations, none of this added to the existing READI license.

The result

About $100,000 avoided. The medical center did not take on the IGA license increase.
Thousands of permissions, assigned automatically. Five attributes select the EHR template, and the template grants the access.
Data the IGA integration could not handle. Multi-response fields are processed correctly.
One rule set, four outcomes. The same mappings drive EHR access, AD groups, onboarding notifications, and ticket routing.
No added READI cost. All of it runs within the existing READI license.