Territory, product, and team-specific account details
Key Takeaway
An account's territory, product, and team details live on relationship objects, not on the Account record. Each account-territory pairing has its own Provider Account Territory Information record, so values in one territory don't overwrite values in another.
In Life Sciences Cloud, one healthcare provider (HCP) or healthcare organization (HCO) account can carry different details depending on its context. That context is the territory that covers it, the product being discussed, and the team working it. The Account record doesn't hold all of these values. Instead, they live on relationship objects that join the account to a territory, a product, or a user group. Because each context has its own record, the same doctor can be a top priority in one region, high-potential for one brand, and a Tier 1 target for one launch team at the same time.
Where account details are stored
Life Sciences Cloud extends the core Account data model. The Account record holds the details that apply across all products, territories, and teams. Details that depend on context live on three relationship objects.
| Object | API name | Joins the account to |
|---|---|---|
| Provider Account Territory Information | ProviderAcctTerritoryInfo | A territory (a Territory2 record) |
| Provider Account Product Information | ProviderAcctProductInfo | A product |
| Provider Account User Group Info | PrvdAccountUserGroupInfo | A user group (a standard Salesforce Group) |