Salesforce Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional Exam (SU24) Exam Practice Test

To extend the reporting capability of Health Cloud, a consultant should recommend CRM Analytics for Health Cloud. This is a feature that provides pre-built dashboards and reports that help users analyze various aspects of health care delivery, such as care plan adherence, patient outcomes, referral management, network performance, and more12. CRM Analytics for Health Cloud also allows users to customize and create their own dashboards and reports based on their specific needs13. Care Management Extension, Insights for Health Cloud, or Reporting unmanaged package are not features that can extend the reporting capability of Health Cloud.

D is correct because Identity Verification Parameter Item is the record that defines the search parameters for identity verification. A consultant can create and configure Identity Verification Parameter Items to add new search parameters or modify existing ones.

References: : Identity Verification Parameter Item : Create a Flow Using the Verify Customer Identity V2 Flow Template

To better plan and track surgical case visits, manage device inventory and run cycle counts, a consultant should recommend the MedTech company use the Life Sciences data model in Health Cloud. This data model provides objects and fields to store and manage information related to surgical cases, devices, inventories, cycle counts, and more5. Intelligent Sales, Inventory Management, or Provider Engagement are not data models that exist in Health Cloud.

According to the Salesforce documentation2, the following standard objects are used in the workflow to manage utilization data:

Care Request Plan: A care request plan is an object that stores information about the plan of care for a member. It includes details such as the diagnosis, the service type, the start and end dates, and the status of the plan2.

Care Authorization: A care authorization is an object that stores information about the approval or denial of a service or payment by a payer. It includes details such as the authorization number, the decision date, the decision reason, and the status of the authorization2.

Care Request: A care request is an object that stores information about the request for a service or payment by a provider or a member. It includes details such as the request type, the request date, the priority, and the status of the request2.

Concurrent review is a type of care request review that ensures that a member is getting the right care in a timely and cost-effective way. It involves reviewing the medical necessity and appropriateness of an ongoing service or admission3. Disposition review, care review, preauthorization review, and retrospective review are not the correct terms for this type of review.

According to the Salesforce documentation1, there are two ways to request a rep-to-rep transfer in Health Cloud:

When creating an order authorization for a visit, you can request a transfer from another rep’s inventory location by selecting the Transfer option in the Product Selection screen1.

To request a transfer from a specific inventory location, you can navigate to Products, select the product you want to transfer, and then click Request Transfer in the Related list1.

 Code Sets are the entity in the new data model of Health Cloud that can be used to store mappings between different coding systems such as ICD and HCC codes. Code Sets are a collection of codes that represent a specific concept or value in a terminology system1.

To implement remote monitoring functionality in 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 oxygen saturation. 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 progress and 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.

HL7v2 and FHIR R4 are two data exchange standards that support clinical data in Health Cloud. HL7v2 is a widely used standard for exchanging healthcare information electronically, such as patient demographics, orders, results, and billing1. FHIR R4 is the latest version of the Fast Healthcare Interoperability Resources standard, which defines a set of resources for representing and sharing healthcare data in a granular and interoperable way2. Health Cloud supports both HL7v2 and FHIR R4 data exchange through its Clinical Data Model, which maps various FHIR resources to Salesforce standard objects3.

References:

1: Review the Data Exchange Standards Unit | Salesforce Trailhead 2: FHIR R4 Support for Better Interoperability - Salesforce 3: Mapping FHIR v4.0 to Salesforce Standard Objects | Salesforce Health …

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

Timeline (A), Life Events ©, and Patient Card (D) are components that are customizable in HC. EHR Data (B) is not a component, but a type of data that can be integrated with HC. Custom Label (E) is not a component, but a metadata type that can be used to create labels for components.

According to the Salesforce documentation, care programs and care plans are different concepts in Health Cloud:

Care programs track a patient’s overall health journey from enrollment to completion. They provide guidance and support for patients to proactively manage their health by increasing their adherence to treatment plans.

Care plans are practical, actionable steps to support the health of a patient. They break health problems down into doable, trackable actions. They serve as the source of truth for all the individuals involved in the care of a patient. Therefore, option A is correct. Option B is incorrect, because both care programs and care plans can be exposed in a community. Option C is incorrect, because both care programs and care plans can be used by providers, payers, and life sciences companies. Option D is incorrect, because care programs are not a different type of care plan, but a separate object in Health Cloud. Option E is incorrect, because care programs are not an extension of care plans, but a related object in Health Cloud.

According to the [Health Cloud Integration and Interoperability Guide], the new clinical data model in Health Cloud is aligned with FHIR R4 standards, which is the latest version of the FHIR specification. Health Cloud supports data exchange with both HL7 and FHIR enabled systems, using different methods such as MuleSoft connectors, Salesforce APIs, or third-party integrations. Most EHR data exchange today is still done via legacy HL7 v2 – simple application interface, which is a widely adopted standard for exchanging clinical and administrative data. Health Cloud does not have a FHIR server, but it can connect to external FHIR servers using APIs or MuleSoft connectors. The new clinical data model in Health Cloud is not aligned with HL7 v2-simple application standard, which is a different standard from FHIR.

Events can be specified to appear when the Health Cloud home page first loads (B), the patient timeline supports standard and custom objects (D), and filters can be used to limit the number of records shown in the patient timeline (E) are three statements that are true about the patient timeline view. The patient timeline cannot be used in any Salesforce application (A), as it is specific to Health Cloud. The patient timeline is not a Health Cloud Empower component ©, but a standard component in Health Cloud.

D is correct because leveraging Person Account is the recommended way to model a patient in Health Cloud. A Person Account is a special type of account that combines the attributes of an account and a contact. It allows users to store information about individual people, such as name, address, phone number, email, and health details. Health Cloud uses Person Accounts to represent patients and members, and to enable various features and functionality, such as household data model, clinical data model, care management, and provider network management.

References: : Health Cloud Data Models for Healthcare : Take a Look at the Household Data Model

SourceSystemIdentifier is a custom object in Health Cloud that stores the business identifier for patient records from external systems like EHRs3. Option B is incorrect, because Contact is a standard object in Salesforce that stores the personal information of patients or members. Option C is incorrect, because Account is a standard object in Salesforce that stores the organizational information of providers or payers. Option D is incorrect, because Identifier is a field on the EhrPatient object in Health Cloud that stores the unique identifier for patient records within Health Cloud3.

B is correct because if a user cannot access a field used in a filter on a patient or member list, they will not be able to see the list. This is because the filter criteria are applied to the user’s query, and if the user does not have permission to view the field, the query will return no results. To avoid this issue, the administrator should ensure that the user has the appropriate field-level security settings for the fields used in the filter.

References: : Manage Your Patient or Member Lists : Control Access to Patient or Member Lists

According to the Salesforce documentation1, the Timeline View Configuration is a custom metadata type that defines the appearance and behavior of a timeline in Health Cloud. Each timeline has its own Timeline View Configuration record, which can be accessed and edited from the Health Cloud - Lightning Admin app2. One of the settings that can be changed in the Timeline View Configuration is the Orientation, which controls whether the timeline is displayed horizontally or vertically1. Therefore, to alter the appearance of the timeline so that it displays vertically instead of horizontally, the administrator should find the Timeline View Configuration for each relevant timeline in the Health Cloud - Lightning Admin app and change the Orientation to vertical.

A visit is an object that represents a field rep’s trip to a retail store or a customer location to perform certain tasks, such as selling products, conducting surveys, or taking orders1. A visit can be created from a work type, which is a template that defines the key parameters and skill requirements for the visit2. A visit can also be associated with a location, which is an object that stores the address and geolocation of a place where a visit can occur3.

A consultant should configure the visit object to track the surgical case visits for reps to sell their product leveraging Intelligent Sales. This way, the reps can use the Intelligent Sales app to create and manage their visits, view their assigned tasks, scan products, and capture signatures4. The consultant can also use work types to standardize the duration, preparation, and wrap-up time for each visit type, and use locations to specify the service territories where the visits can take place.

References:

1: Visit - Salesforce 2: WorkType | Field Service Developer Guide | Salesforce Developers

FHIR V4 and HL7 V2 are two interoperability standards that are supported by Salesforce to facilitate the exchange of health data32. Option A is incorrect, because EDI ANSI X12 is a standard for exchanging business transactions, not health data. Option C is incorrect, because The Direct Standard is a standard for secure email communication, not health data. Option E is incorrect, because DICOM (Digital Imaging and Communications in Medicine) is a standard for storing and transmitting medical images, not health data.

Custom label (A), Patient Card ©, and Timeline (D) are components that are customizable within Health Cloud. EHR data (B) is not a component, but a type of data that can be integrated with Health Cloud. Life Events (E) is not a customizable component, but a standard object in Health Cloud.

 FHIRR4 is the industry data standard that a consultant should use with Health Cloud. FHIRR4 stands for Fast Healthcare Interoperability Resources Release 4, and it is a standard for exchanging healthcare information electronically. FHIRR4 enables interoperability between different systems and applications, and supports a variety of use cases, such as clinical, administrative, and financial.

Reference and details below.

Salesforce Surveys is the best solution for moving existing PROMs surveys to Health Cloud. It allows for question banks and version control for this standardized survey.

C is correct because enabling Field Audit Trail, implementing encryption for sensitive data, and configuring two-factor authentication for all users are some key considerations and recommended practices for supporting compliance in Salesforce. Field Audit Trail helps to track data changes and retain data history for up to 10 years. Encryption helps to protect data at rest from unauthorized access or theft. Two-factor authentication helps to strengthen user login security and prevent account compromise.

References: : Field Audit Trail : Platform Encryption : Two-Factor Authentication

Care Provider Searchable Field is the denormalized object that holds data to support the Provider Search feature in Health Cloud. Care Provider Searchable Field is a custom object that stores searchable fields from the Healthcare Provider and Healthcare Provider Facility objects. It allows users to search for providers based on various criteria such as name, location, specialty, and availability. Healthcare Provider Facility, Provider Search Sync Logs, and Healthcare Provider are not denormalized objects in Health Cloud.

The design considerations that the administrator has to be aware of when creating the application for utilization management are:

Each care request has to have an associated case. A case is the standard Salesforce object that represents a care request in Health Cloud4.

New care requests can be created using the ‘Create Care Request’ component. This component allows users to create a new care request from any page in the Health Cloud console5.

Path can be used to visually represent the status of a care request. Path is a standard Salesforce feature that displays the stages of a process, such as a care request, and guides users along the steps in Salesforce Lightning Experience6.

Care request functionality is not included in the Health Cloud managed package. It requires installing the Utilization Management unmanaged package for Health Cloud and assigning the Health Cloud Utilization Management permission set to users along with Health Cloud permission set licenses.

Care requests do not have empower components that can be exposed within Communities. Empower components are custom Lightning components that allow patients or members to view and manage their health information in Communities. Care requests are not part of the empower components.

To help the payer organization electronically receive requests for services from Bloomington Caregivers, a consultant should recommend the following business level APIs:

Prior Authorization API: This API allows Bloomington Caregivers to create requests for prior authorization for services that require approval from the payer organization. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests9.

Care Services API: This API allows Bloomington Caregivers to create requests for care services that are covered by the payer organization’s benefit plans. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests10.

Referral Request API: This API allows Bloomington Caregivers to create requests for referrals to other providers that are part of the payer organization’s network. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests11. Admission, Discharge, and Transfer (ADT) API or Benefit Verification API are not business level APIs that can fulfill this requirement.

To set up care requests, you need to do the following steps3:

Install the Utilization Management unmanaged package for Health Cloud and assign the Health Cloud Utilization Management permission set to users along with Health Cloud permission set licenses.

Create a new case record type for each care request type.

Choose the Case Care Request record type for each care request configuration.

Reference and details below.

According to the Salesforce documentation2, Health Cloud uses Business APIs that should be used instead of object level APIs when creating records in Health Cloud objects. Business APIs are custom REST APIs that perform complex business logic and validations on Health Cloud objects. Object level APIs are standard REST or SOAP APIs that perform CRUD operations on individual objects. Business APIs ensure data integrity and consistency across Health Cloud objects, while object level APIs may result in data errors or inconsistencies2.

The set of Health Cloud capabilities that should enable the company to build this business process are Intelligent Document Automation, Intelligent Appointment Management, Intelligent Document Reader, and Benefits Verification. Intelligent Document Automation allows the company to upload a patient’s insurance card and automatically create a Member Plan record. Intelligent Appointment Management allows the company to schedule on behalf of the patient with a provider. Intelligent Document Reader allows the company to extract data from the insurance card and populate the Member Plan fields. Benefits Verification allows the company to run a benefits verification check using a third-party service.

FlexCards are Health Cloud features that allow users to view and navigate to critical information on a patient’s profile, such as insurance, clinical, and primary care physician information1. FlexCards can also display data from external sources, such as EHR systems or medical devices2.

Integration Procedures are OmniStudio features that enable users to read and write data from Salesforce and from external systems3. An Integration Procedure can be called from an OmniStudio component such as an OmniScript or FlexCard, an API, or even from an Apex method3.

DataRaptors are OmniStudio features that allow users to read, transform, and write Salesforce data4. DataRaptors can also trim, map, restructure, and transform data in JSON, XML, or Custom Schema4.

These three features can be used together to display patient information from both Salesforce standard objects and data from an external system on the patient record page. For example, a FlexCard can call an Integration Procedure that uses a DataRaptor to query and transform the data from both sources, and then display the data on the FlexCard component.

References:

1: Use the Advanced Patient Card - Salesforce 2: Display Data from External Sources in the Advanced Patient Card - Salesforce 3: Get Started with OmniStudio Integration Procedures - Trailhead 4: Discover DataRaptor Types - Trailhead

According to the Salesforce documentation, Health Cloud is a health IT solution that helps healthcare organizations deliver personalized and collaborative care across every touchpoint. Some of the characteristics of Health Cloud are:

Health Cloud is an engagement layer that connects patients, providers, payers, and partners on a single platform. It enables seamless communication and collaboration across the healthcare ecosystem.

Health Cloud is part managed package and part core services. The managed package contains custom objects, fields, tabs, apps, components, and more that are specific to healthcare use cases. The core services include standard Salesforce features and functionality that are available across all Salesforce products.

The best approach is to define a PGI Library and care plan templates using the library. This will enable the care coordinators to track PGIs in a standardized way, and also leverage best practices and evidence-based guidelines.

Reference and details below.

The two capabilities that a consultant should customize to implement Utilization Management in Health Cloud and submit and track prior authorizations are creating a new Support Process to match the customer’s process steps and customizing the Service Request object. A Support Process defines the picklist values available for the Status field on a Service Request record, which represents a prior authorization request. The consultant can create a new Support Process to match the customer’s process steps, such as Submitted, Approved, Denied, or Pending. The Service Request object stores information about the prior authorization request, such as the patient, the provider, the service type, and the outcome. The consultant can customize this object by adding or removing fields, creating validation rules, or defining page layouts.

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.

To enable care managers to call patients after they are discharged from a hospital and assign them personalized care plans based on their answers, a consultant should leverage Discovery Framework and Salesforce Surveys together. Discovery Framework is a feature that allows care managers to create assessments with questions and answers that are linked to care plan templates. Salesforce Surveys is a tool that allows care managers to create and send surveys to patients and capture their responses in Health Cloud. By using these two capabilities together, care managers can automate the process of assigning care plans based on patient responses.

Expression Set Templates are the prebuilt feature that the payer should leverage to implement predefined rules for its prior authorization request review process. Expression Set Templates are reusable sets of expressions that can be used to evaluate business logic and trigger actions based on the results.

 The two connectivity options that a consultant should leverage as the scheduling engine for Intelligent Appointment Management in Health Cloud are Electronic Health Record (EHR) System and Salesforce Scheduler. An EHR System is an external system that stores and manages clinical data and appointments for patients or members. Salesforce Scheduler is a native Salesforce feature that allows users to schedule appointments with customers or prospects.

B is correct because Care Request and Care Request Item are the standard objects in Health Cloud that are used to set up prior authorizations. Care Request represents a request for authorization of a service or procedure, and Care Request Item represents a specific service or procedure within the request. These objects can be integrated with an external system that manages the end-to-end prior authorization process, and display the preauthorization outcomes from that system.

References: : Care Request : Care Request Item : Prior Authorization in Health Cloud

To leverage Utilization Management features in Health Cloud, users need to have Health Cloud Permission Set License, Health Cloud Utilization Management Permission Set, and Health Cloud Foundation Permission Set. Health Cloud Permission Set License grants access to the Health Cloud platform objects and features. Health Cloud Utilization Management Permission Set grants access to utilization management objects so users can manage care requests and reviews. Health Cloud Foundation Permission Set assigns read access to additional Health Cloud platform capabilities4. Health Cloud Analytics Permission Set and Health Cloud Platform Permission Set License are not required for Utilization Management.

 To migrate from the legacy Health Cloud EHR data model to the FHIR R4 clinical data model, a consultant needs to leverage the Health Cloud FHIR API and map objects and fields to the target objects. The Health Cloud FHIR API enables interoperability between Health Cloud and external systems that use FHIR standards. The mapping process ensures that the data is transformed and loaded into the correct objects and fields in Health Cloud. Using the Health Cloud Clinical Transition tool, using Data Loader to load the respective data, or creating an Apex class and leveraging Intelligent Appointment Management are not recommended steps for this migration2.

The developer should modify the Extract DataRaptor to concatenate the address fields by using a formula to handle this bug. An Extract DataRaptor is a component in OmniStudio that allows the developer to query data from Salesforce objects and display it on a FlexCard. The developer can use a formula to concatenate the address fields into one field and avoid adding an extra line when Address Line 2 contains data.

To get a comprehensive view of a patient’s prescriptions, including history, to improve health outcomes, a consultant should leverage the Medication Management capability in Health Cloud. Medication Management is a feature that helps providers and care coordinators manage the medication regimen of their patients, helping to improve patient safety and reduce healthcare costs. Medication Management allows providers and care coordinators to develop a curated list of current medications, review medications with the patient, make clinical decisions and recommendations based on the review, and communicate the recommendations to the patient and the patient’s prescriber6. Intelligent Appointment Management, Integrated Care Management, or Virtual Care are not capabilities that can fulfill this use case.

Some entities have additional non-FHIR attributes to increase the usability of the data within Salesforce (A), the cardinality of a few attributes has been changed (e.g. in picklist scenarios) (B), and not all attributes in a given FHIR resource may be supported © are three options that explain why the new clinical data model in Health Cloud is labeled as FHIR aligned and not FHIR compliant. It does utilize the latest FHIR R4 standards (D), so this is not a reason for being FHIR aligned. It aligns with both FHIR DSTU2 and FHIR R4 specs (E), so this is not a reason for being FHIR aligned either.

FHIR V4 and HL7 V2 are two interoperability standards that are supported by Salesforce to facilitate the exchange of health data32. Option A is incorrect, because EDI ANSI X12 is a standard for exchanging business transactions, not health data. Option C is incorrect, because The Direct Standard is a standard for secure email communication, not health data. Option E is incorrect, because DICOM (Digital Imaging and Communications in Medicine) is a standard for storing and transmitting medical images, not health data.

B is correct because giving the site user profile Read access to the Care Provider Searchable Field object is a change that allows an external user to access search results. The Care Provider Searchable Field object stores the searchable data for Provider Search, and users need to have Read access to this object and its fields to perform searches and view results.

D is correct because using Experience Builder to add the Provider Search component to a page on the site is a change that allows an external user to access search results. The Provider Search component is a Lightning web component that enables users to search for providers by various criteria and view their details. Administrators can use Experience Builder to drag and drop the Provider Search component onto any page on their site.

References: : Set Up Data for Provider Search : Let Site Users Search for Providers

The underlying component that the consultant should customize to achieve this is OmniScript. OmniScript is a component in OmniStudio that allows the consultant to create guided scripts or wizards for users to follow. OmniScript can be used to create the Care Plan creation wizard, and it can be customized using various elements, such as steps, prompts, inputs, outputs, and actions.

To ensure compliance with HIPAA regulations, a Health Cloud feature that is essential is user authentication and access control. This feature allows Health Cloud administrators to verify the identity of users who access patient health information and assign appropriate permissions and sharing rules to limit their access to the minimum necessary2. User authentication and access control helps protect patient privacy and prevent unauthorized access or disclosure of protected health information (PHI). Real-time monitoring and alerts, social media integration, or data visualization and analytics are not features that directly help ensure HIPAA compliance.

B is correct because Health Cloud Reports for Patient Referral Management is an unmanaged package that delivers a prebuilt dashboard and reports for analyzing patient referrals. The dashboard shows metrics such as referral volume, referral status, referral source, and referral outcome. The reports provide more details on each metric and allow users to filter by various criteria.

References: : Health Cloud Reports for Patient Referral Management

Reference and details below.

Graphical user interface, text, application Description automatically generated

Reference and details below.

According to the Health Cloud Data Model Developer Guide, two ways that an administrator can ensure that Patient Risk scores are recalculated periodically are:

Set up a scheduled Apex batch job. This method allows the administrator to create an Apex class that implements Database.Batchable interface and Schedulable interface, and schedule it to run at specified intervals using Apex Scheduler.

Set up an Apex batch job and run it manually. This method allows the administrator to create an Apex class that implements Database.Batchable interface, and execute it manually using anonymous Apex code or developer console. Using CMS recalculation API is not a valid way, as CMS recalculation API is not a feature of Health Cloud. Using a third party API to recalculate CMS risk score is not a recommended way, as it can introduce security and integration risks. Creating a Healthcare Provider enrollment flow is not a relevant way, as it has nothing to do with patient risk scores.

C is correct because Integration Procedures are components that can be used to update an existing field on a custom SObject. Integration Procedures are reusable processes that can perform various actions on data, such as reading, writing, transforming, or validating. Integration Procedures can be invoked from an OmniScript or a DataRaptor, and can accept input parameters and return output values.

D is correct because DataRaptors are components that can be used to update an existing field on a custom SObject. DataRaptors are data transformation tools that can extract, load, or transform data from any Salesforce object or external data source. DataRaptors can be invoked from an OmniScript or an Integration Procedure, and can accept input parameters and return output values.

References: : Integration Procedure : DataRaptor

Reference and details below.

According to the Health Cloud Data Model Developer Guide, Risk scores are only recalculated for patients who are affiliated with a care 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.

A is correct because Remote Device Monitoring can help the MedTech company to manage its run rate business by enabling them to monitor the performance and usage of their devices remotely, and alert them of any issues or anomalies that may affect contract compliance.

B is incorrect because MedTech Accelerator is not a feature of Health Cloud, but a program that provides funding and mentorship for early-stage medical device and health technology companies.

C is incorrect because Advanced Account Forecasting is not a feature of Health Cloud, but a feature of Sales Cloud that helps sales teams to predict their revenue and quota attainment.

D is correct because Sales Agreements can help the MedTech company to manage its run rate business by allowing them to create contracts that commit the customer to buy products in a specific quantity or for a specific amount over time, and track the fulfillment and invoicing of those contracts.

References: : Remote Device Monitoring : Sales Agreements

When creating a care plan with a template you can unselect tasks so they will not be included (A), the sort order of the Task group by Fields can be changed under custom setting task group (B), and care plan templates must include at least 1 problem, 1 goal and 1 task © are true statements about Care Plan Templates. When creating a care plan with a template you can change the offsets of the tasks (D) is false, as you can only change the offsets of the tasks when creating a care plan without a template. Care plan templates can only be used when creating a new care plan (E) is false, as you can also use care plan templates when editing an existing care plan.

The two objects that a consultant is able to add and/or remove fields from in the UI on the Patient Medication Manager component are Medication Dispense and Medication Request. These objects are part of the Health Cloud data model and store information about the medication orders and deliveries for a patient.

According to the Salesforce documentation, the following capabilities of the provider search would a customer service agent use to help payers find the right provider:

Control the list of fields displayed in the search panel and search results. The provider search allows customer service agents to customize which fields are displayed in the search panel and search results for different types of providers or facilities. This helps them find the most relevant information quickly and easily.

Use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of the search provider. The provider search allows customer service agents to use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of the search criteria or filters. This helps them narrow down their search results based on specific attributes or preferences.

The two best practice recommendations to upload information to support Provider Search and Provider Relationship Card are using Composite API Request and Data Loader. Composite API Request is a REST API resource that allows the administrator to execute multiple requests in a single call, which reduces the number of API calls and improves performance. Data Loader is a tool that allows the administrator to insert, update, delete, or export data from Salesforce objects in bulk.

To configure Health Cloud, the following steps are required1:

Enable the option for contacts to relate to multiple accounts. This feature allows contacts to be associated with more than one account, which is essential for modeling complex relationships in healthcare.

Install the Health Cloud Managed Package. This package contains the core objects, fields, tabs, components, and other elements that make up Health Cloud.

Configure the console view. This step involves customizing the Health Cloud console app to suit your needs and preferences. You can add or remove tabs, components, page layouts, and other features to optimize your user experience.

Verify that Chatter is enabled. Chatter is a collaboration tool that allows users to communicate and share information within Health Cloud. Chatter is enabled by default in most orgs, but you can check your settings to make sure.

Install Health Cloud Unmanaged Packages. These packages are optional and provide additional functionality for specific use cases, such as utilization management, care programs, or provider search.

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 complexity in 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.

A is correct because Intelligent Appointment Management (IAM) is a solution for care coordinators to book appointments without having to manually check availability and resources themselves. IAM aggregates multiple scheduling engines, such as Salesforce Scheduler or Electronic Health Record (EHR) scheduling engines, or both, so that schedulers and patients can see all available appointments in one place. IAM also supports complex appointment types, such as infusions, that require multiple steps or resources.

References: : Meet Intelligent Appointment Management : Intelligent Appointment Management

Utilization Management is the capability in Health Cloud that helps the payer accomplish its goal of balancing quality care and managing the cost of care effectively. It enables the payer to streamline its approval processes for care requests using predefined rules and workflows.

Deterministic encryption is a type of encryption policy that allows you to encrypt fields that are used as search criteria, such as FirstName and LastName fields on the Account object. Deterministic encryption ensures that identical plaintext values always result in identical ciphertext values, which enables searching and filtering on encrypted fields. This is suitable for PHI data that needs to be encrypted at rest but also searchable by users.