Health-Cloud-Accredited-Professional Practice Test Questions

Explanation:

Supported FHIR Resources in Health Cloud’s New Data Model:
1. Medication (B): Represents the drug/product (e.g., formulary details, ingredients).
2. Medication Dispense (D): Tracks dispensing events (e.g., pharmacy fulfillment).
3. Medication Request (E): Captures prescriptions/orders (e.g., provider instructions).

Why Not the Other Options?

❌ A. Medication Administration – Not yet supported in Health Cloud’s FHIR model (though it exists in FHIR standards).
❌ C. Dosage – Part of MedicationRequest (embedded within it), not a standalone resource.

Explanation:

Standard Care Management Data Model Objects:
1. CarePlan Template Task (B): Defines reusable tasks (e.g., "Schedule follow-up") for Care Plans.
2. CareProgramGoal (D): Tracks high-level program objectives (e.g., "Reduce readmissions").
3. CarePlanGoal (E): Specifies patient-specific goals (e.g., "Lower blood pressure to 120/80").

Why Not the Other Options?

❌ A. CareSpeciality – Not part of the standard model (may be custom).
❌ C. TimelineViewConfiguration – Administrative (UI configuration), not a care data object.

Explanation:

In Salesforce Health Cloud, to display device information on a patient card, you need to follow the data model designed for connected devices or medical devices. This typically includes:

Asset: Represents the actual physical device (e.g., glucose monitor, heart rate tracker).
Care Registered Device: A Health Cloud object used to link a device (Asset) with a Patient (Person Account).
This association allows the device data to be shown on the Patient Card, especially in the Health Timeline or Patient 360 view.

By creating:

An Asset record for the device, and
A Care Registered Device that links the Asset to the Patient (Account),
...the Health Cloud system can surface this device information automatically in the patient card.

❌ Why the other options are incorrect:

A. EHR_Patient – Not the standard object for showing device info; formula fields on this object won't link to device records.
B. EHR_DeviceRequest – This object relates more to ordering devices, not tracking or displaying registered devices on the patient card.
C. FilterCondition_c – This is more likely a metadata/config object for filtering views, not actual device or patient data.
E. EHR_MedicalDevices – Not a standard object used in the Health Cloud Care Registered Device framework.

Explanation:

Engagement Layer (A)

Health Cloud is a CRM-based engagement platform built on Salesforce, designed to connect patients, providers, and payers with workflows for care coordination, outreach, and analytics.

Hybrid of Managed Package + Core Services (C)

Managed Package: Adds Health Cloud-specific objects (e.g., CarePlan, CareProgram).
Core Services: Leverages standard Salesforce features (e.g., Lightning, Flows, APIs).

Why Not the Other Options?

❌ B. AppExchange/Third-Party – Incorrect. Health Cloud is a native Salesforce product, not a third-party package.
❌ D. Core services exposed by license – Misleading. While licenses enable access, Health Cloud is not just "core services."
❌ E. Electronic Health Record (EHR) – False. Health Cloud is a CRM, not an EHR (e.g., Epic, Cerner). It integrates with EHRs but doesn’t replace them.

Explanation:

Enable Person Accounts (C)
Person Accounts must be activated in Salesforce Setup (Account Settings → Enable Person Accounts). This is a prerequisite.

Configure Record Type Mapping (A)
During migration, Individual Record Types must be mapped to corresponding Person Account Record Types to maintain data structure.

CSV Mapping for PersonRecordTypeId (E)
The migration tool requires a CSV file to explicitly map Individual records to the correct Person Account Record Type (using the PersonRecordTypeId field).

Why Not the Other Options?

❌ B. Enable ‘Individual to Person Account Migration’ in custom settings – No such setting exists; migration is done via Data Loader or Salesforce-provided tools.
❌ D. Log a case with Salesforce – Salesforce Support does not perform this migration; it’s the admin/architect’s responsibility.

Explanation:

Install Health Cloud Managed Package (B)
Health Cloud is delivered as a managed package, which must be installed to access its custom objects (e.g., CarePlan, CareProgram).

Verify Chatter is Enabled (C)
Health Cloud uses Chatter for care team collaboration (e.g., updates on patient status). Ensure it’s activated in Setup → Chatter Settings.

Enable "Contacts to Multiple Accounts" (E)
Patients (Contacts) often have relationships with multiple providers/Accounts (e.g., PCP + specialist). Enable this in Setup → Account Settings.

Why Not the Other Options?

❌ A. Install unmanaged package – Health Cloud is only available as a managed package.
❌ D. Configure console view – While useful, this is not a setup prerequisite (it’s a post-configuration step).

Explanation:

Correct Answers:
✅ A. Custom label – Health Cloud allows customization of labels for branding or terminology adjustments.
✅ C. Patient Card – Patient Cards can be modified to display relevant patient data in different layouts.
✅ D. Timeline – The Timeline component is customizable to show events, encounters, or other time-based records.

Why not the others?

❌ B. HER data – EHR (Electronic Health Record) data is typically imported and not directly customizable in Health Cloud.
❌ E. Life Events – While Life Events can be configured, they are not a "component" in the same way as the others.

Explanation:

Correct Answer:
✅ B. Life Events – Life Events in Health Cloud allow tracking significant moments in a patient’s life (e.g., marriage, job changes) to provide context for care plans.

Why not the others?
❌ A. Life Goals – Tracks patient objectives (e.g., "Lose weight") but not life changes.
❌ C. Household Map – Shows relationships but not life milestones.
❌ D. Milestones – Typically tied to care plan progress, not personal life events.
❌ E. Life Map – Not a standard Health Cloud feature.

Explanation:

The FHIR-Aligned Data Model org preference is the preference that Bloomington Caregivers’ administrator should ensure is enabled to use the objects for the Clinical data model as part of its new Health Cloud implementation. This preference enables the Clinical data model, which is a FHIR R4-aligned data model that captures information from an Electronic Health Record (EHR) system via integration middleware1. The Clinical data model is built on Salesforce core, with no reference to package entities, and supports only the attributes that Health Cloud users need, not all attributes in every FHIR R4 resource2. The Clinical data model is the successor to the original EHR Data Model, which was built on the managed package and followed the FHIR R1 standard2.

References:

1: Clinical Data Model | Salesforce Health Cloud Developer Guide | Salesforce Developers
2: Explore the Clinical Data Model Unit | Salesforce Trailhead

Explanation:

To modify the out-of-the-box Advanced Patient Card to display the Category, SubjectID, and Date for active Clinical Alerts, a developer should take the following steps:

Create and activate a new child card: This step allows the developer to create a custom card that inherits the properties of the parent card and displays additional information from Clinical Alerts object4.

Create a DataRaptor to extract necessary data: This step allows the developer to create a DataRaptor Extract that queries the Clinical Alerts object and returns the Category, SubjectID, and Date fields for active records5.

Change the child card state to show active: This step allows the developer to change the state of the child card from inactive to active, so that it is visible on the Advanced Patient Card component6. Cloning the parent card, defining session variables, or creating an Integration Procedure are not required steps for this task.