Profiles
Collapse / Expand
Profiles is the operational workspace for profiles within customer 360, where teams manage concrete records, dependencies, and execution decisions rather than static summaries. The business and compliance goal is to keep hcp/hco/patient/payer profiles aligned with approved claims, consent controls, market rules, and audit evidence at every step. This page presents role-scoped actions, linked downstream impacts, and policy-aware guardrails so users can work quickly without violating promotional or safety obligations. Next, use this profiles workspace to execute governed tasks and route outcomes to connected teams.
Access Boundaries
SSO + RBAC/ABAC controls are evaluated by brand, market, function, agency zone, and risk tier before actions are enabled.
Operational Focus
- Inspect interaction history and channel eligibility.
- Validate profile affiliation accuracy.
- Check suppression and consent posture.
What To Do Next
- Open related segment.
- Review approved content eligibility.
- Publish profile updates to CRM mock.
Stakeholder 360 Studio
Maintain HCP/HCO/patient/payer profile views with interaction and consent context.
| ID | Title | Market | Owner | Status | Risk | Related |
|---|---|---|---|---|---|---|
| PROF-0001 | Profiles · Stakeholder profile 1 | JP | CRM Ops | In Review | Critical | View SegmentConsent |
| PROF-0002 | Profiles · Interaction summary 2 | AU | Field Ops | Approved | Low | View SegmentConsent |
| PROF-0003 | Profiles · Affiliation record 3 | BR | Patient Services | Active | Moderate | View SegmentConsent |
| PROF-0004 | Profiles · Eligibility flag 4 | MX | CRM Ops | Blocked | High | View SegmentConsent |
| PROF-0005 | Profiles · Stakeholder profile 5 | SG | Field Ops | Escalated | Critical | View SegmentConsent |
| PROF-0006 | Profiles · Interaction summary 6 | US | Patient Services | Draft | Low | View SegmentConsent |
| PROF-0007 | Profiles · Affiliation record 7 | CA | CRM Ops | In Review | Moderate | View SegmentConsent |
| PROF-0008 | Profiles · Eligibility flag 8 | UK | Field Ops | Approved | High | View SegmentConsent |
| PROF-0009 | Profiles · Stakeholder profile 9 | DE | Patient Services | Active | Critical | View SegmentConsent |
| PROF-0010 | Profiles · Interaction summary 10 | FR | CRM Ops | Blocked | Low | View SegmentConsent |
| PROF-0011 | Profiles · Affiliation record 11 | IT | Field Ops | Escalated | Moderate | View SegmentConsent |
| PROF-0012 | Profiles · Eligibility flag 12 | ES | Patient Services | Draft | High | View SegmentConsent |
Page-Specific Data
Profile data joins stakeholder identity, affiliations, interactions, and eligibility constraints. Current page path: /profiles.
Relationship Graph
Linked entities are enabled so users can traverse parent-child dependencies and downstream impacts without manual lookup.
Stakeholder Tools
Resolve duplicates and merge history.
Create HCP-HCO affiliation records.
Check content eligibility by consent and role.
| Execution Step | Owner | ETA |
|---|---|---|
| Validate input | Ops | 5m |
| Policy checks | Compliance | 8m |
| Route next action | Workflow | 3m |
Governance Notes
- Every approval, publication, policy block, and AI output writes an audit event.
- Consent and frequency caps are evaluated before deployment packaging.
- Expiry and withdrawal controls maintain cross-channel evidence status.
- Safety routing is always flag-and-route with human adjudication.