Patient and member record modeling
Key Takeaway
Always model patients and members as person accounts: one person gets one record, even when that person is both a patient and a member.
In Agentforce Health, every patient or member is stored as a person account. The standard Salesforce model assumes people belong to organizations, but patients usually don't. Person accounts let the patient sit at the center of the data model, with providers, caregivers, care plans and clinical data connected around the patient.
Why patients and members are person accounts
In the standard Salesforce model, accounts represent organizations and contacts represent people. A contact exists only in relation to an account. For example, a sales rep's contact record is related to the business account for the MedTech company he works for.
Most healthcare organizations don't think of their patients or members as part of an organization, so Agentforce Health represents each patient or member as a person account.
Person accounts store information that applies to people rather than organizations, such as first name, last name, title, address and date of birth.
A single person account record represents one patient or member. Patients and members are both modeled as person accounts, so a person who is both a patient and a member stays on the same single record. You don't create a separate record for each role.
Always model patients and members as person accounts. If you don't, you can't fully use Agentforce Health functionality.
Person accounts are a basic setup dependency, so two things must happen before you can use them for patients, members and providers. They must be enabled in the org, and the Person Account record type must be assigned to user profiles.