Which Visual representation in Health Cloud would enable a care coordination to see all the relationships between a patient and the people and organizations participating in the patient’s, including those across multiple care plans?
A. Timeline view
B. Care Team
C. Lightning Empower Components
D. Householding Map
E. Patient Card
Explanation:
Householding Map is the visual relationship tool in Health Cloud that:
Displays all connections between a patient, their care team, providers, and organizations.
Shows cross-care-plan relationships (e.g., family members, caregivers, affiliated clinics).
Uses a network diagram format for clarity.
Why Not the Other Options?
❌ A. Timeline View: Shows chronological events (e.g., appointments, diagnoses) but not relationships.
❌ B. Care Team: Lists members but lacks visual mapping of broader relationships.
❌ C. Lightning Empower Components: Custom UI tools, not designed for relationship mapping.
❌ E. Patient Card: Summarizes patient details (e.g., demographics) but not relationships.
Which Three items can be a Life Science company track about a Care Programs using Program Management? (Choose Three. (Repeated question)
A. The multiple marketing campaigns that enrollees are subjected to as part of the Care Program.
B. The budget & Expenses of the company’s associate Care Program
C. The clinical indicators that need to be monitored in the care programs
D. The products that are associate with a given Care Program
E. The plans that enrollees have been engaged in as part of the care program
Explanation:
Program Management in Salesforce Health Cloud (especially for Life Sciences companies) enables organizations to track and manage structured Care Programs. These programs can involve services, products, clinical monitoring, and engagement plans for patients.
✅ C. Clinical Indicators
Program Management tracks clinical indicators (e.g., blood pressure, A1C levels) that need to be monitored throughout the program.
These are essential for measuring patient outcomes and adherence.
✅ D. Products Associated with Care Program
Many Care Programs are tied to specific therapies or medical products (e.g., specialty drugs).
Salesforce allows you to track which products are involved with or dispensed as part of the program.
✅ E. Engagement Plans
You can track the plans or tasks that patients (enrollees) are participating in — such as education sessions, follow-ups, or medication schedules.
❌ Incorrect Options:
A. Marketing Campaigns
Care Programs focus on clinical care and patient support, not marketing activity.
Marketing campaigns would be tracked in Marketing Cloud or Pardot, not Program Management.
B. Budget & Expenses
While financial tracking may happen in connected systems (like ERP), Program Management in Health Cloud is not primarily used to track budgets and expenses.
Which statement is true about using PurchaserPlan and MemberPlan together when onboarding new insurance members?
A. Multiple purchaser plans can be associated to multiple Member Plans.
B. Purchaser Plan and Member Plan has a master detail relationship
C. there is no relationship between MemberPlan and Purchaser Plan.
D. PurchasePlan is to be used as a template for creating MemberPlan.
Explanation:
In Salesforce Health Cloud, specifically when working with insurance data models, PurchaserPlan and MemberPlan are two standard objects used during member onboarding and benefit management.
✅ PurchaserPlan
Represents the plan offering purchased by an organization or employer (e.g., an insurance policy package).
Acts as a template or blueprint for individual member-level plans.
✅ MemberPlan
Represents the actual plan enrollment for an individual insurance member (the patient/insured person).
When onboarding a new member, a MemberPlan is created based on the PurchaserPlan.
❌ Incorrect Options:
A. This is misleading. While a PurchaserPlan can be linked to many MemberPlans, it’s not a many-to-many relationship.
B. This is not accurate. The relationship is a lookup, not master-detail.
C. False. There is a relationship — MemberPlans reference PurchaserPlans to inherit plan design details.
What are the two steps required to create Health care providers for Health program? Choose two
A. Add NPI for associated provider
B. Choose associated facility for Care Program.
C. Add the UPIN
D. Create Care Program Providers from the App Launcher
E. Create a care program health care provider with an associated care prgm provider
Explanation:
When creating Health Care Providers for a Care Program in Salesforce Health Cloud, there are two required steps to ensure the provider is correctly associated and functional within the program:
✅ D.
You begin by navigating to the Care Program Providers object through the App Launcher.
This is where you initiate the creation of providers who will participate in a specific Care Program.
✅ E.
You must link a Care Program Health Care Provider record to a Care Program Provider record.
This step associates the provider with a specific Care Program and ensures they appear in the program’s workflows.
❌ Incorrect Options:
A. Adding an NPI (National Provider Identifier) is good practice, but it's not a required step to create the provider in the context of a care program.
B. Associating a facility might be part of broader care team setup, but it's not a required step for setting up a care program provider.
C.The UPIN (Unique Physician Identifier Number) is deprecated in the U.S. and not a required field.
A Health Cloud administrator is working on a call center implementation and has to ensure that the phone numbers passing through the CTI settings display the matching contact record via Screen Pop. Which custom metadata type within Health Cloud should the administrator update to achieve this requirement?
A. Flow Session Setting -> CallCenterFlow
B. Feature Flag Setting -> CTIDriverSetting
C. Job Flow Setting -> ConsoleDisplayValue
D. Health Cloud Setting -> HcFeatureDriver
Explanation:
Health Cloud’s HcFeatureDriver Custom Metadata Type
This is the primary configuration point for enabling/disabling core Health Cloud features, including CTI (Computer Telephony Integration) settings.
To ensure phone numbers trigger Screen Pop (matching incoming calls to Contact records), the admin must:
Update HcFeatureDriver to enable CTI integration.
Configure call routing rules (e.g., matching caller ID to Contact phone fields).
Why Not the Other Options?
❌ A. Flow Session Setting – Not related to CTI; governs Flow runtime behavior.
❌ B. Feature Flag Setting – Generic feature toggles, not specific to Health Cloud CTI.
❌ C. Job Flow Setting – Unrelated to Screen Pop functionality.
Which entity in the new data model of Health Cloud can be used to store mappings between different coding systems such ICD and HCC codes?
A. Identifier
B. Codesets
C. ContactPoint
D. Codeset Bundle
Explanation:
Codesets in Health Cloud
The Codesets object is specifically designed to store mappings between different medical coding systems (e.g., ICD-10 → HCC, SNOMED → LOINC).
Enables interoperability and standardized reporting across systems.
Why Not the Other Options?
❌ A. Identifier – Tracks unique IDs (e.g., patient MRNs), not code mappings.
❌ C. ContactPoint – Stores communication details (phone/email), unrelated to coding.
❌ D. Codeset Bundle – A collection of codesets, not the mapping mechanism itself.
Which Permission Set Licenses are required to utilize and access Health Cloud feature and functionalities? (Choose two)
A. Health Cloud for Community
B. Health Cloud
C. Health Cloud Platform
D. Health Cloud Permission Set License
E. Health Cloud Standard
Explanation:
To access and use Salesforce Health Cloud features and functionality, users must be assigned the proper Permission Set Licenses (PSLs) and permission sets. The key licenses are:
✅ B.
This is the core Permission Set License (PSL) that grants access to standard Health Cloud features like clinical data models, care plans, timeline views, and more.
Users must have this license assigned before they can be assigned any Health Cloud-related permission sets.
✅ D.
This refers to the underlying license object required to assign permission sets for Health Cloud (such as Health Cloud Admin, Care Coordinator, etc.).
Without this PSL, you cannot assign the permission sets that unlock Health Cloud features.
❌ Incorrect Options:
A. Not a standard PSL. Health Cloud features can be extended to Experience Cloud (Community) users, but this is done using the main Health Cloud license in conjunction with community licenses — it's not a standalone PSL.
C.This is not a recognized Salesforce license. Likely a distractor.
E. Not an official name of any license or permission set in Salesforce Health Cloud.
If a Health Cloud administrator wanted to consume the content of an HL7 v2 – Simple Application message, which step would they need to take?
A. Do Nothing – Health Cloud works out of the box with native HL7 message
B. Use salesforce Connect
C. Write a custom apex class to consume parse and store a native HL7 message
D. Use an HL7 broker/engine to transform the text based HL7 message into JSON and pass it to the Health Cloud.
Explanation:
Salesforce Health Cloud does not natively parse or consume HL7 v2 messages out of the box. HL7 v2 is a text-based, delimited format that requires transformation before Salesforce can use it effectively.
✅ D. Use an HL7 broker/engine
This is the industry-standard approach.
HL7 brokers or integration engines like Mirth Connect, Rhapsody, or InterSystems Ensemble are used to:
1. Parse HL7 v2 messages
2. Transform them into JSON or FHIR format
3. Send them via APIs to Salesforce
Once in JSON or FHIR format, the data can be stored in custom objects or FHIR-enabled models in Health Cloud.
❌ Incorrect Options:
✖️ A. Incorrect — Salesforce does not natively understand HL7 v2 messages.
✖️ B. Incorrect — Salesforce Connect is used to reference external data (e.g., via OData), not to parse HL7 messages.
✖️ C. Incorrect — Technically possible but not recommended. HL7 parsing is complex and best handled by dedicated engines, not Apex.
Which three medication related FHIR resources are supported in the new data model of Health cloud (Choose Three)
A. Medical Administration
B. Medication
C. Dosage
D. Medication Dispense
E. Medical Request
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.
Which three of the following Health Cloud objects are part of the standard Care Management data Model? (Choose three)
A. CareSpeciality
B. CarePlan Template Task
C. TimelineViewConfiguration
D. CareProgramGoal
E. CarePlanGoal
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.
How does an administrator display device information on a patient card?
A. Create a custom field on the EHR_Patient object with a formula that returns the information to display on patient card
B. Create a custom field on the EHR_DeviceRequest with a formula that returns the information to display on patient card
C. Create a custom field on the FilterCondit»on_c with a formula that returns the information to display on patient card
D. Create an Asset record and create a Care Registered Device record that looks up to the Asset record and then looks up to the Account record for the Patient
E. Create a custom field on the EHR_MedicalDevices with a formula that returns the nf ormauon to display on patient card
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.
What is Health Cloud? (Choose two.)
A. Health Cloud is an engagement layer.
B. An AppExchange core package and third party service.
C. Health Cloud is part managed package and part core services.
D. Core services exposed by permission license.
E. Health Cloud is a new type of Electronic Health Record.
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.
| Page 2 out of 19 Pages |
| Previous |