Reference and details below.

A visit is an object that represents a field rep's trip to a retail store or a customer location to perform certain tasks, such as selling products, conducting surveys, or taking orders1. A visit can be created from a work type, which is a template that defines the key parameters and skill requirements for the visit2. A visit can also be associated with a location, which is an object that stores the address and geolocation of a place where a visit can occur3.
A consultant should configure the visit object to track the surgical case visits for reps to sell their product leveraging Intelligent Sales. This way, the reps can use the Intelligent Sales app to create and manage their visits, view their assigned tasks, scan products, and capture signatures4. The consultant can also use work types to standardize the duration, preparation, and wrap-up time for each visit type, and use locations to specify the service territories where the visits can take place.
Reference:
1: Visit - Salesforce 2: WorkType | Field Service Developer Guide | Salesforce Developers

According to the Health Cloud Implementation Guide, two statements that are true about Care Teams are:
Care Team Members are optional on a Care Plan. This statement is true because a care plan can be created without any care team members assigned to it. However, adding care team members can help with collaboration and coordination of care.
A Care Plan must have a Coordinator as a member of the Care Team before a Care Plan Template can be applied. This statement is true because a coordinator is required to manage the tasks and goals of a care plan template. A coordinator can be either an internal or external user who has access to Health Cloud. If the Problem and Goal objects use Private Sharing, Care Team Membership provides access to these objects is not a true statement, as care team membership does not grant access to objects that use private sharing. Communities must be enabled before External Care Team members can be added is not a true statement, as external care team members can be added without enabling communities.

According to the Salesforce documentation, PurchasePlan is an object in Health Cloud that stores information about a plan purchased by an employer or an individual from a payer. PurchasePlan is to be used as a template for creating MemberPlan records for each member enrolled in the plan. MemberPlan is an object in Health Cloud that stores information about a member's enrollment in a plan, such as effective date, termination date, coverage type, and benefits.