Gathering legacy data, provider data and data quality requirements
Key Takeaway
Model each practitioner once, as a person account plus a Healthcare Provider record, and give each location where they work its own Healthcare Practitioner Facility record.
Discovery for Agentforce Health includes finding out what provider data and legacy data a customer has, where it lives, and how reliable it is. Provider data must fit a specific set of Agentforce Health objects. Data quality is judged by whether the data is fit for the business purpose it serves. Getting these requirements right affects how providers are modeled, how legacy data is prepared, and whether features such as provider search work.
Two records for each provider
Each provider in Agentforce Health is modeled with two records. One record says who the provider is, either a person or an organization. A Healthcare Provider record says what the provider does and stores business-level details such as the provider type.
Provider organizations, such as hospitals, clinics, and labs, use the Account object with a Business record type. Individual practitioners can be person accounts or contacts, but Salesforce strongly recommends person accounts. Person accounts fit practitioners who are independent entities with practicing rights at many locations. Contacts have limited capabilities for these records.
Features such as provider search may not work if providers are modeled only as person accounts. Modeling providers with both the Healthcare Provider object and person accounts aligns them to the FHIR Practitioner resource and lets them appear in provider search. In the FHIR Practitioner representation, the Healthcare Provider record is the base, and it references the person account through the AccountId field.
One person account can have more than one related Healthcare Provider record, because one person can hold several provider roles.