implementation strategy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago - last edited 3 hours ago
We are implementing a CRM system for a medical device manufacturing company (Company X). The system will be used by sales representatives, system administrators, and team members managing sales rep shelf inventory.
Before Company X can sell or deliver a medical device to a hospital or healthcare facility (Company Z), the specific physician at that facility must be approved through a third-party Value Analysis Committee (VAC) system. Approval is required once per physician per facility.
When a sales representative delivers a device to a customer, they must pick the unit from their shelf inventory, and the system must verify that the target physician is approved before allowing the transaction.
Questions for CRM Architecture & Design:
1. Data Modeling & System Architecture:
• what is the optimal data model to handle this credentialing workflow?
• Should we use the standard Lead object for pending approvals, or transition directly to Accounts, Contacts (physicians), and a dedicated Custom Object for VAC approvals?
• Why is adding a simple "Status" or "State" field to the Company record insufficient for tracking approval logic in this scenario?