Data Change Request configuration for governed account fields
Key Takeaway
To require approval for edits to a field, create a Life Science Data Change Definition Managed Fields record for that field. Edits to fields without such a record save directly, with no Data Change Request.
A Data Change Request (DCR) is a governance process in Life Sciences Cloud for Customer Engagement. When a user saves a change to a governed, or managed, field on an account or related record, the change goes to an approver as a separate request instead of landing straight in live data. As the consultant, you decide four things: which fields are governed, who validates changes (your organization or OneKey), whether new records wait for approval, and when users see a change.
How a Data Change Request works
When a user saves a change to a managed field, the system creates a separate Data Change Request record and routes it to an approver, such as an admin or a manager. The approver accepts or rejects the request.
Because changes wait for approval, unapproved edits stay out of live data, which reduces manual corrections.
DCR is supported for the following objects, so governance covers addresses, phones, specialties, and affiliations as well as the account itself:
- Account
- HealthcareProvider
- HealthcareProviderSpecialty
- HealthcareProviderNpi
- ContactPointAddress
- ContactPointPhone
- ContactPointEmail
- ContactPointSocial
- BusinessLicense
- ProviderAffiliation