According to the Salesforce documentation2, to display device information on a patient card, you need to create an asset record and a care registered device record that look up to the patient. An asset record represents the device that is used by the patient, such as a blood pressure monitor, a glucose meter, or a pulse oximeter. A care registered device record represents the relationship between the patient and the device, such as the device name, serial number, status, and start and end dates2.

Goal and Problem (D) are optional fields when creating a new Care plan task. Status (A) and Task Owner (E) are required fields when creating a new Care plan task. Due Date (B) is not a field on Care plan task, but rather on Task object.

Reference and details below.

According to the Salesforce documentation3, the following Salesforce and Health Cloud objects can be used to represent providers and their relationships in a provider management data model:
Contact: A contact is a standard object in Salesforce that stores information about an individual person, such as name, phone, email, address, etc. A contact can be used to represent a provider who is a person, such as a physician, nurse, or therapist3.
Healthcare Practitioner Facility: A healthcare practitioner facility is a custom object in Health Cloud that stores information about the relationship between a provider and a facility where they practice, such as hospital, clinic, or pharmacy. A healthcare practitioner facility can be used to track each of the different locations where a provider practices3.
Healthcare Provider: A healthcare provider is a custom object in Health Cloud that stores information about a provider who is an organization or a group of providers, such as hospital system, clinic network, or physician group3.

In Salesforce Health Cloud's Intelligent Sales module, the Visit object is specifically designed to track field representatives' interactions, such as surgical case visits, with healthcare providers. Configuring this object enables MedTech companies to monitor and manage their sales activities effectively.
Understanding the Visit Object:
Purpose: The Visit object captures essential information about a sales representative's engagement at a healthcare facility, including details like the associated account, visit timings, status, and outcomes.
Key Fields:
AccountId: Reference the healthcare facility associated with the visit.
PlannedVisitStartTime / PlannedVisitEndTime: Denote the scheduled start and end times of the visit.
ActualVisitStartTime / ActualVisitEndTime: Record the actual start and end times when the visit occurs.
Status: Indicates the current state of the visit, such as Planned, InProgress, Completed, or Abandoned.
VisitorId: Identifies the sales representative conducting the visit.
Implementation Steps:
Configure the Visit Object:
Ensure that the Visit object is enabled and accessible within your Salesforce Health Cloud instance.
Customize the object as needed to align with your organization's specific tracking requirements.
Set Up Related Records:
Accounts: Create records for healthcare facilities where visits will occur.
Contacts: Add contacts for individuals at these facilities involved in the visits.
Schedule and Manage Visits:
Utilize the Visit object to plan and record details of surgical case visits.
Monitor visit statuses and outcomes to assess sales activities and effectiveness.
Reference:
Visit Object Details: For comprehensive information on the Visit object and its fields, refer to the Salesforce Health Cloud Developer Guide: Visit | Salesforce Health Cloud Developer Guide Intelligent Sales Overview: To understand how the Visit object integrates within the Intelligent Sales framework, consult the Salesforce Help documentation: Use Intelligent Sales Conclusion:
By configuring the Visit object, MedTech companies can effectively track and manage surgical case visits, providing valuable insights into sales activities and facilitating better coordination between sales representatives and healthcare providers.