Record access model for patient and member person accounts
Key Takeaway
Start from restrictive organization-wide defaults, then open access on purpose. A sharing rule opens only records of the object it is defined on.
Agentforce Health stores each patient or member as a person account, which is a single record that combines certain account and contact fields for one person. Who can see and edit those records comes from Salesforce's layered access model. To meet a customer's security and compliance requirements, you choose the right tool at each layer.
How patients and other people are stored
Always model patients and members as person accounts in Agentforce Health, because you can't fully use Agentforce Health functionality if they aren't person accounts. Salesforce also strongly recommends person accounts for providers who are their own independent entity with practicing rights at several locations. Separate record types and page layouts for patient accounts and provider accounts let each one show different data.
People around the patient, such as family members and specialists outside your organization, are contacts. Every contact must be related to an account. With Contacts to Multiple Accounts, one provider contact can relate to an organization's account and to a patient's person account.