Extending standard health objects versus building custom objects
Key Takeaway
Look for a standard object first, and create a custom object or field only when it won't duplicate existing functionality.
Agentforce Health comes with industry data models, which are standard objects and fields built for healthcare processes such as households, providers, care plans, and utilization management. Staying on the standard model matters for two reasons: features like provider search keep working, and the customer benefits from new functionality as Salesforce releases it.
What a data model is
Objects are like database tables, fields are like columns, and records are like rows. You need to understand the data models to implement and adopt Agentforce Health successfully.
Knowing the data models tells you what Agentforce Health can already do, so you can avoid custom objects and fields that duplicate existing functionality. You can also use new and enhanced functionality as Salesforce releases it.