Master the Salesforce Health Cloud Accredited Professional (WI24) Health-Cloud-Accredited-Professional Exam with Confidence!

According to the Health Cloud Implementation Guide, the recommended best practice for modeling members in Health Cloud for a payer service cloud org that uses accounts and contacts to model health insurance members is to model them as person accounts, whether they are using Health Cloud capabilities or not. Person accounts are a type of account that combines account and contact information in a single record. They are suitable for representing individual consumers in healthcare and life sciences. Using person accounts for all members can simplify data management and avoid data duplication. Only groups needing Health Cloud capabilities need to use person accounts is not a recommended best practice, as it can create inconsistency and complexityin data modeling. Account record types for existing members can remain as-is is not a recommended best practice, as it can limit the functionality and integration of Health Cloud features. Using the individual model with Health Cloud is not a valid option, as the individual model is not supported by Health Cloud.

To implement remote monitoring functionalityin Health Cloud, an administrator should populate the following records:

• Code Sets: These are records that define the codes and descriptions for various types of data, such as care metrics, care observations, or units of measure. Code sets help standardize the data and enable interoperability with external systems1.
• Units of Measure: These are records that define the units of measurement for various types of data, such as weight, blood pressure, or temperature. Units of measure help convert the data into a common format and enable comparison and analysis2.
• Care Metric Targets: These are records that define the target values or ranges for various types of care metrics, such as blood glucose level, heart rate, or oxygensaturation. Care metric targets help monitor the patient’s health status and identify any deviations or risks3.
• Care Observations: These are records that store the data collected from patient devices, such as blood pressure monitors, glucose meters, or pulse oximeters. Care observations help track the patient’s health progressand provide insights for care management4. Remote Monitoring Device Types, Biometrics, Chart Metrics, or Care Episodes are not records that are required for remote monitoring functionality.

Reference and details below.

According to the Health Cloud Data Model Developer Guide, Risk scores are only recalculated for patients who are affiliated with acare program is the most likely reason why recalculation score for the patient is not displaying. Risk scores are calculated based on CMS-HCC (Centers for Medicare & Medicaid Services - Hierarchical Condition Categories) model, which assigns risk factors to patients based on their diagnoses and demographic factors. Risk scores are used to adjust payments for health plans and providers. Risk scores are only recalculated when the recalculate flag is set to TRUE and the patient is affiliated with a care program. Using CMS recalculation API is not a valid reason, as CMS recalculation API is not a feature of Health Cloud. CMS scores cannot be recalculated in health cloud is not a valid reason, as CMS scores can be recalculated in health cloud by setting the recalculate flag to TRUE. Using a third party API to recalculate CMS risk score is not a valid reason, as it has nothing to do with displaying the recalculation score.

According to the Salesforce documentation1, the Health Cloud Reports for Patient Referral Management is an unmanaged extension package that provides a prebuilt dashboard with reports on important aspects of referral management, such as referral status, referral source, referral age, and referral efficiency. The package also includes custom fields, custom objects, and custom report types to support the dashboard. To use this package, a consultant should install it in their org and assign the appropriate permissions to the users who need to access the dashboard. The package is compatible with Health Cloud and CRM Analytics.

References:

1: Provide Referral Management Reports | Health Cloud Administration | Salesforce Developers

According to the[Intelligent Sales for Medical Devices Implementation Guide], to set up a warehouse that serves as a product fulfillment location to salesforce representatives in a specific region, irrespective of the account, a salesforce administrator should complete the following steps:

• Create Inventory Location and add Visitor Address as Location Address. This step creates a record for the warehouse location and associates it with a visitor address.
• Create Record in Product Fulfillment Location. This step defines theproduct fulfillment location for the inventory location and assigns it to a specific region.
• Create a product item entry inventory, a single entry for each product that will be replenished from industry. This step adds the products that will be available in the warehouse location and specifies their quantity and expiration date. Setting up Product Transfer and Product Request are not required steps for setting up a warehouse location. Selecting inventory location while creating visit is not a step for setting up a warehouse location, but for creating a visit record.

Shield is a Salesforce product that allows encryption of protected health information (PHI) data at rest to enhance Health Cloud2. Shield Platform Encryption encrypts sensitive data at rest without compromising critical platform functionality. It helps you address privacypolicies, regulatory requirements, and contractual obligations for data protection2.

The two steps that an administrator should take as part of the implementation of a Crisis Support Center are installing the Crisis Support Center unmanaged package and reviewing and modifying the Crisis Center Intake flow in Flow Builder to meet requirements. The Crisis Support Center unmanaged package provides out-of-the-box features for managing crisis situations, such as a custom object, a Lightning component, a Lightning app, and a Flow template. The Crisis Center Intake flow is a prebuilt flow that guides users through collecting information from callers and creating records in Health Cloud.

According to the Health Cloud Implementation Guide, the three steps that an administrator should take to ensure all tasks identify the role ‘Care Consultant’ are:

• Update/Add the organization roles in the CarePlan_Role_Patient key:value pair in Health Cloud Setting. This step allows the administrator to define or modify the roles that are available for assigning tasks to patients.
• Update the organization roles in the CarePlan_Role_Care_Coordinator key:value pair in Health Cloud Setting. This step allows the administrator to define or modify the roles that are available for assigning tasks to care coordinators.
• Update the corresponding roles in theAssigned To picklist for the Care Plan Template Task object. This step allows the administrator to update the values in the picklist field that determines who is responsible for completing a task in a care plan template. Creating an ETL script to update the previously assigned To picklist values of Tasks created in the past is not a recommended step, as it can introduce errors and data loss. Updating the Care Plan Record Type custom metadata type to reflect the care coordination processes specific to the Care Coordinators is not a relevant step for changing the role name.

Add NPI for associated provider (A) and create a care program health care provider with an associated care program provider (E) are twosteps required to create health care providers for health program. Choose associated facility for care program (B) is not a valid step, as facilities are not related to health care providers. Add the UPIN © is not a required step, as UPIN is an optional field for health care providers. Create care program providers from the app launcher (D) is not a valid step, as care program providers are created from the related list on the care program record.