Choose 1 option.

Option C is correct because Life Sciences Cloud separates the overall visit activity from provider-specific visit details. In the Life Sciences Cloud data model, the Visit object tracks information related to a field representative’s visit to a healthcare provider and is used for Customer Engagement. Salesforce’s ProviderVisit object represents the details of a field user’s visit to a healthcare provider. The Customer Engagement data model also explains that information entered in a provider visit typically includes product details, product messages, presentations, marketing items, and samples.

For a group visit such as a “Lunch and Learn” with three HCPs, the overall event is represented by the parent Visit record. Each attendee requires their own provider-specific visit detail record because each HCP may have different product discussions, messages, samples, signatures, or follow-up activities. Therefore, the system creates one parent Visit and separate child Provider Visit records for each HCP attendee.

Option A is incorrect because a multi-select lookup field is not the correct Life Sciences Cloud visit data model pattern. Option B is also not correct because it implies individual parent-level Visit records for every attendee, which would duplicate the overall group interaction. The correct structure is one parent Visit for the group interaction and three child Provider Visit records, one for each Healthcare Provider attendee.