The Patient Medication Manager component in Salesforce Health Cloud surfaces data from FHIR-aligned medication objects . When customers request field updates on this UI component, the consultant can configure fields from the underlying objects.
* A. Medication Details # Stores key information about a patient's medications. Fields from this object can be exposed or customized on the Patient Medication Manager.
* C. Medication Request # Represents a provider's request or order for a medication. Fields from this object are also available to configure in the Patient Medication Manager.
Together, these two objects form the basis of what's displayed and editable in the Patient Medication Manager .
Why not the others?
* B. Medication Dispense - Tracks when and how a medication was dispensed. It is not directly configurable for field-level updates in the Patient Medication Manager component.
* D. Medication Strength - Captures clinical details about dosage strength, but it isn't one of the configurable objects in the Patient Medication Manager UI.
Salesforce Health Cloud Reference:
# Salesforce Health Cloud Medication Management:
* "The Patient Medication Manager component displays information from Medication Details and Medication Request objects. Administrators can add or remove fields from these objects to tailor the component."

Step-by-Step Explanation:
* Supported Data Exchange Standards:Health Cloud natively supports modern clinical data standards such as FHIR R4 and traditional messaging formats like HL7 v2 for interoperability and data exchange.
* Exact Extract:
"Health Cloud supports industry standards for data exchange, including FHIR R4 and HL7 v2, to enable clinical interoperability with EHR systems and other healthcare platforms." Reference: Administer Health Cloud - Interoperability Why Not Other Options?
DICOM 3.0: Used for imaging, not clinical data exchange in Health Cloud.
SDTM v3.2: Used for clinical trials data, not general patient/clinical data exchange in Health Cloud.
Conclusion:FHIR R4 and HL7 v2 are the two standards officially supported for clinical data in Health Cloud.

To improve appointment scheduling and provide patient self-service, these three Health Cloud features should be configured:
* Experience Cloud for Health Cloud :
* Allows creation of patient-facing portals for self-service appointment booking and information access.
* Extract:
"Experience Cloud enables self-service portals for patients, supporting appointment scheduling and other interactions." ( Source: Administer Health Cloud - Experience Cloud )
* Intelligent Appointment Management :
* Offers advanced scheduling features and automation to reduce wait times and manual booking.
* Extract:
"Intelligent Appointment Management in Health Cloud supports both self-service and agent-assisted scheduling workflows." ( Source: Administer Health Cloud - Intelligent Appointment Management )
* Provider Search :
* Lets patients find the right clinic or provider based on specialty, availability, and other criteria.
* Extract:
"Provider Search empowers patients to search for providers and book appointments online through self- service portals." ( Source: Administer Health Cloud - Provider Search )
* Why not A or D?
* Intelligent Form Reader is used for document capture, not for scheduling or self-service.
* Assessments and Recommendations are used for care management, not scheduling.

The use case mentions:
Plan and track surgical case visits
Manage device inventory
Run cycle counts
These requirements directly align with the Health Cloud Inventory Management data model.
Inventory Management in Health Cloud is designed for MedTech and Life Sciences companies to track:
Surgical case planning and scheduling
Medical device and implant inventory management
Cycle counts and stock levels across facilities
It supports end-to-end surgical case tracking, ensuring the right devices are available at the right place and time.
Why not the others?
A . Life Sciences - Broader model used for clinical trials, patient programs, and pharma engagement, but not focused on surgical case + device inventory.
B . Provider Engagement - Used for managing provider relationship data (e.g., physician affiliations, facilities), not inventory or surgical planning.
C . Intelligent Sales - Focused on sales optimization and customer engagement, not surgical case or inventory management.
Salesforce Health Cloud Reference:
* Salesforce Health Cloud - Inventory Management Guide:
"Use the Inventory Management data model to manage device inventory, surgical case planning, cycle counts, and medical device tracking across healthcare facilities."