In Salesforce Health Cloud's Visit Management, a group visit is represented using a standard parent-child data model. A single parent Visit record is created to capture the common details of the interaction, such as the date, time, and location. For each Healthcare Provider (HCP) who attended, a separate child record on the Attendee object is created. This Attendee record links the specific HCP (Contact) to the parent Visit record, ensuring data integrity and simplifying reporting on both individual and group interactions.

A: Using a multi-select lookup field is not a scalable or standard Salesforce data modeling practice for this type of relationship, as it complicates reporting and automation.

B: Creating individual Visit records for each attendee is incorrect; it would represent multiple separate visits, not a single group visit, and is an inefficient data structure.

Salesforce Health Cloud Developer Guide, "Data Model for Visits". The guide details the Visit object and the Attendee junction object, which links a Visit to Contact or User records. This structure corresponds to the parent-child model described in the correct answer.

Salesforce Health Cloud Administrator Guide, "Set Up Visit Management". This section explains the objects involved in scheduling and logging visits, including how multiple attendees are associated with a single visit event.