Consent save workflow and compliance snapshot audit trail
Key Takeaway
Every consent save creates a new compliance snapshot. The consent record is updated if an active one exists for the same consent giver, Communication Subscription Channel Type, and contact point, and is created if none does.
Consent Management in Life Sciences Cloud records a healthcare professional's Opt-In or Opt-Out choices for each communication subscription and channel. Each time a rep saves consent, Life Sciences Cloud creates a new compliance snapshot and creates or updates the current consent record. The consent record holds the latest status. The compliance snapshots, one per save, form the audit trail.
The consent data model
The Communication Subscription Consent record, called the consent record here, is the center of the consent data model. Each consent record stores the Opt-In or Opt-Out status for one combination of Communication Subscription Channel Type and contact point. A consent record requires these three values:
- A consent giver, which is the record whose consent is captured. A consent giver can generally be an account, contact, user, or individual. In Life Sciences Cloud, the consent giver is an account, even when consent is captured from a healthcare professional.
- A Communication Subscription Channel Type. Consent is always saved against a Communication Subscription Channel Type, never against a channel alone.
- A contact point, which is an email, phone, address, or social contact for the consent giver. The engagement channel type's contact point type determines which contact points are available.