Health-Cloud-Accredited-Professional Questions and Answers

According to the Health Cloud Implementation Guide, leveraging Person Accounts is the recommended approach to represent Members and Patients during the basic set-up of Health Cloud console for Care Coordinators and Managers. 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. The other options are not recommended approaches to represent Members and Patients.

According to the Health Cloud Data Model Developer Guide, Case is the Salesforce object that is used to model a Care Plan. Case is a standard object that represents an issue or request that requires resolution or action. Cases can be used to model care plans by adding custom fields and related objects such as problems, goals, tasks, and timeline events. Account, Lead, Opportunity, and Task are not objects that are used to model a Care Plan.

C is correct because the dataset required needs to read two SObjects with a clearly defined relationship is a scenario where a single DataRaptor can be used. A DataRaptor Extract can query data from one or more Salesforce sObjects and their related fields using SOQL. A DataRaptor Load can save data to one or more Salesforce sObjects by creating or updating records.

References: : DataRaptor Extract : DataRaptor Load

A is correct because obtaining verified parental consent before collecting and storing any personal information of children is one of the main requirements of COPPA. The consent must be obtained in a way that ensures that the person providing consent is the child’s parent or legal guardian, such as using a credit card, digital signature, or video conference.

B is correct because disclosing the organization’s privacy policy to parents and obtaining their consent is another requirement of COPPA. The privacy policy must explain what information the organization collects from children, how it uses and discloses it, and what rights parents have to review or delete their children’s information.

C is incorrect because ensuring that Bloomington Caregivers’ system implementation partner has met all COPPA regulations during the build phase is not a consideration for the company, but for the partner. The company is ultimately responsible for complying with COPPA, regardless of who builds their system.

D is correct because implementing appropriate security measures to safeguard children’s personal information is another requirement of COPPA. The organization must establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children.

References: : Children’s Online Privacy Protection Act (COPPA) : Children’s Online Privacy Protection Rule ("COPPA")

Salesforce Shield is the encryption solution that supports the encryption of files in this scenario. Salesforce Shield provides platform encryption, which allows the administrator to encrypt files and attachments stored in Salesforce. Platform encryption supports full sandbox instances and complies with data protection regulations

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.

Reference and details below.

According to the Salesforce documentation, to grant users read access to health insurance records and also create, read and update access to utilization management records, you need to assign them the HC Utilization Management permission set. This permission set grants users access to various objects, fields, tabs, apps, and components related to utilization management in Health Cloud.

A is correct because ensuring the user has the right object permissions is the first step in troubleshooting this issue. The Enhanced Timeline for Contact Center displays records from various objects, such as Case, Engagement Interaction, Engagement Topic, and Task. The user needs to have at least read access to these objects and their fields to view them on the timeline. The administrator can check and modify the user’s object permissions from their profile or permission set.

References: : Enhanced Timeline for the Contact Center : Object Permissions

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.

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.

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

Use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of search experience. 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.

Use provider search in an authenticated community page. The provider search allows customer service agents to use provider search in an authenticated community page where they can log in with their credentials and access more features and information than an unauthenticated community page.

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.

Reference and details below.

To enhance their assessment functionality with Discovery Framework, a consultant should configure the following capabilities with Health Cloud out-of-the-box:

Using Previously Submitted Responses: This capability allows users to pre-populate assessment questions with responses from previous assessments, saving time and effort. Users can also edit the responses if needed1.

Digital Signature Capture: This capability allows users to capture electronic signatures from patients or other parties on the assessment form, ensuring consent and compliance. Users can also view and download the signed document as a PDF file2.

Adding a QR Code: This capability allows users to generate a QR code for the assessment form, which can be scanned by patients or other parties to access and complete the assessment on their mobile devices. Users can also track the status of the QR code and send reminders if needed3. FHIR Question Bank or SMS Assessment Completion are not capabilities that are available with Health Cloud out-of-the-box.

According to the Health Cloud Data Model Developer Guide, Insurance Benefit, MemberPlan, and Insurance Coverage are three standard objects available for Insurance Management. Insurance Benefit represents a specific benefit or service covered by an insurance plan. MemberPlan represents an insurance plan that a member is enrolled in. Insurance Coverage represents an insurance policy that covers one or more members. PurchaserPlan and Coverage Benefit are not standard objects available for Insurance Management.

Reference and details below.

To get a patient’s allergy information from Bloomington Caregivers’ Health Cloud system, an external provider should use the Interoperability API. This API allows external systems to access and exchange clinical data with Health Cloud using FHIR standards. The Interoperability API supports various FHIR resources, including AllergyIntolerance, which represents a patient’s allergic or intolerant reaction to a substance1. AllergyMedication API, Patient Healthcare API, or Clinical Summary Healthcare API are not APIs that exist in Health Cloud.

The admin must configure all Lead field mappings including Medical Record Number, Source System and Source System ID (A), some Lead field mappings including Medical Record Number, Source System ID can be handled automatically by HC ©, and duplicate checks on Medical Record Number, Source System and Source System ID can be handled automatically by HC (E) are true statements about the steps the admin can take. The custom Convert to Patient button should be added to the Lead detail page, not the list view (B). The Lead to Individual Conversion apex class will not create a new Opportunity for the patient (D).

According to the Health Cloud Data Model Developer Guide, Orders is the underlying object that helps with sales compliance with sales agreements. Orders is a standard object that represents a confirmed request to purchase one or more products. Orders can be used to track the fulfillment and invoicing of products that are sold to customers. Orders can also be linked to contracts or agreements to ensure compliance with the terms and conditions of the sales. Opportunities, Contacts, and Forecasts are not objects that help with sales compliance with sales agreements.

Reference and details below.

To enable care providers to conduct video visits with patients and capture socioeconomic factors that impact their care, a consultant should recommend the Telehealth capability in Health Cloud. Telehealth allows care providers to connect with patients through video calls, chat messages, and surveys within Health Cloud. Telehealth also enables care providers to collect and analyze social determinants of health (SDOH) data from patients using assessments and surveys3. Telehealth helps improve patient engagement, satisfaction, and outcomes by providing convenient and personalized care. Integrated Care Management, Intelligent Appointment Management, or Virtual Care are not capabilities that can fulfill this use case.

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.

According to the Health Cloud Implementation Guide, Lead is the object that is leveraged to track patient referrals. Lead is a standard object that represents a potential customer or patient who has expressed interest in a product or service. Leads can be converted into person accounts or contacts when they are qualified. Care Request, Care Program Enrollee, and Cases are not objects that are used to track patient referrals.

The two integration patterns that a consultant should recommend to share patient medication information with an external pharmacy are Platform Event and Apex HTTP Callout. Platform Event allows Bloomington Caregivers to publish events when medication records are updated in Health Cloud, and the external pharmacy can subscribe to those events and receive notifications in near real time. Apex HTTP Callout allows the external pharmacy to send an HTTP request to Health Cloud with the medication interaction information, and Health Cloud can process the response and display it to the users.

The feature that the consultant should configure to leverage dependent intervention tasks as part of their care coordination solution using Integrated Care Management is Action Plan Templates. Action Plan Templates are reusable sets of tasks that can be assigned to patients or members based on their care needs. Action Plan Templates can include dependent tasks that are triggered by the completion of other tasks.

According to the Health Cloud Implementation Guide, the two permission set licenses that are required to utilize and access Health Cloud features and functionalities are Health Cloud and Health Cloud Permission Set License. Health Cloud is a base license that enables access to Health Cloud objects and tabs. Health Cloud Permission Set License is an add-on license that enables access to Health Cloud Lightning components and pages. Health Cloud for Community, Health Cloud Platform, and Health Cloud Standard are not valid permission set licenses for Health Cloud.

According to the Health Cloud Implementation Guide, the two steps that need to be taken during the set-up process for Utilization Management are:

Install the Health Cloud Care Request Extensions unmanaged package. This package contains custom objects, fields, layouts, tabs, and components for Utilization Management.

Assign the Health Cloud Permission Set License and the Health Cloud Platform Permission Set License to Salesforce Lightning users. These licenses enable access to Health Cloud features and functionalities for Lightning Experience. Assigning the Health Cloud Permission Set License and Health Cloud Platform Permission Set License to Salesforce Classic users is not necessary for Utilization Management. Installing the Utilization Management Extensions is not a valid step for Utilization Management.

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.

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.

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

Owner (A) and Status © are two fields that are required when creating a new care plan task. Problem (B), Goal (D), and Due Date (E) are optional fields when creating a new care plan task.

According to the Health Cloud Data Model Developer Guide, two ways that a data architect can ensure PHI/PII data visibility is minimized during the migration of patient data from an existing Service Cloud org to a new Health Cloud org are:

Use Salesforce Data Masking when moving data to a sandbox. Data Masking is a tool that helps you protect sensitive data in sandboxes by masking it with anonymized values.

Use Data Templates to exclude PHI/PII data from being added to partial copy sandboxes. Data Templates are files that specify which objects and fields to include or exclude when creating a partial copy sandbox. Exporting data to a spreadsheet to remove PHI before importing it into a sandbox is not a recommended way, as it can introduce errors and security risks. Ensuring sandboxes have Platform Shield enabled is not a valid way, as Platform Shield is not a feature of sandboxes. Platform Shield is a product that allows encryption of data at rest in production orgs.

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

To create Visit records for a Field Sales Agent using Intelligent Sales, the administrator must create Contacts, Locations, and Assets records for the agent. Contacts are the people that the agent visits or interacts with during their sales cycle. Locations are the places where the agent conducts their visits or activities. Assets are the products or devices that the agent sells or services during their visits. Opportunities and Accounts are not required for creating Visit records using Intelligent Sales.

To enable agents to answer questions from members regarding their benefits coverage, a consultant should recommend the Benefits Coverage component for the Member record page. This component displays information such as plan name, effective date, termination date, deductible amount, coinsurance percentage, copay amount, and out-of-pocket maximum for each benefit plan that the member is enrolled in. Benefits Verification, Eligibility Validation, or Coverage Confirmation are not components that exist in Health Cloud.

The three features in Health Cloud that the consultant should recommend to the health plan provider are Business Rules Engine, Utilization Management data model, and Out-of-the-box Process libraries. These features enable the provider to manage prior authorizations with predefined approval criteria, store and track care requests, and leverage best practices and templates for common scenarios .

According to the Salesforce documentation, PurchasePlan is an object in Health Cloud that stores information about a plan purchased by an employer or an individual from a payer. PurchasePlan is to be used as a template for creating MemberPlan records for each member enrolled in the plan. MemberPlan is an object in Health Cloud that stores information about a member’s enrollment in a plan, such as effective date, termination date, coverage type, and benefits.

According to the Salesforce documentation3, when setting up a new care request record, you need to choose a case record type to identify the care request type. The care request type determines what fields and values are available on the care request record. There are four predefined care request types in Health Cloud: Physician Request, Drug Request, Admission Request, and Appeal Request. You can also create custom care request types to suit your business needs3.

Reference and details below.

 According to the Salesforce documentation3, there are two ways to restrict access to an entire patient/member list or to specific columns of that list:

Sharing setting: Sharing settings control the access level that users have to records owned by other users. You can use sharing settings to grant or restrict access to an entire list of records based on criteria such as role hierarchy, public groups, or manual sharing3.

Field Level Security: Field level security controls the access level that users have to individual fields within a record. You can use field level security to grant or restrict access to specific columns of a list based on profiles or permission sets3.

A is incorrect because setting Person Accounts to Private is not a valid organization-wide default setting. Person Accounts inherit their sharing settings from Accounts and Contacts.

B is correct because setting Contact to Controlled by Parent ensures that the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI) stored in Contact records. This setting means that the access level for Contact records depends on the access level for their parent Account records.

C is correct because setting related clinical objects to Controlled by Parent or Private ensures that the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI) stored in clinical objects, such as Allergy, Diagnosis, Medication Order, and Procedure Order. These objects are related to either Account or Contact objects, and their sharing settings should match or be more restrictive than their parent objects.

D is incorrect because setting Health Details to Controlled by Parent or Private is not a valid organization-wide default setting. Health Details is a custom object that stores health information for patients and members. It is related to the Person Account object, and its sharing settings are controlled by its parent object.

E is correct because setting Account and Contract to Private ensures that the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI) stored in Account and Contract records. This setting means that users can only access the records that they own or are explicitly shared with them.

References: : Protect Privacy in Health Cloud : Organization-Wide Default Access Settings

Health Cloud does not support native HL7 messages out of the box, so option A is incorrect. Option B is also incorrect, because Salesforce Connect is not designed to handle HL7 messages. Option C is possible, but it would require a lot of custom code and maintenance, and it is not recommended by Salesforce. Option D is the best option, because it uses an external HL7 broker/engine to convert the HL7 message into JSON, which can be easily consumed by Health Cloud using the standard REST API or the Health Cloud Data Loader12.

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.

According to the Salesforce documentation1, the Feature Flag Setting custom metadata type within Health Cloud allows you to enable or disable certain features of Health Cloud. One of the features that can be enabled or disabled is the CTIDriverSetting, which controls whether the CTI adapter is used to display phone numbers in the patient console. To ensure that the phone numbers passing through the CTI settings display the matching contact record via screen pop, the administrator should update the Feature Flag Setting -> CTIDriverSetting custom metadata type and set the value to true1.

According to the Salesforce documentation, there are three steps that should be followed when setting up Intelligent Sales in Health Cloud:

Enable Intelligent Sales: This step allows you to turn on the Intelligent Sales feature in Health Cloud and configure some settings such as default visit duration, visit report template, and visit report email template.

Set up permission set for Intelligent Sales: This step allows you to assign the appropriate permission sets to users who need access to Intelligent Sales features such as visit management, product catalog, order authorization, and inventory management.

Set Visit Inventory Management to enabled: This step allows you to enable the inventory management feature in Health Cloud and configure some settings such as default inventory location, default inventory transfer status, and default order authorization status.

According to the Health Cloud Implementation Guide, the way to change the label ‘Patient Card’ to ‘Member Card’ to be more aligned with their specific business terminology and use case is to go to setup, navigate to Custom Labels, select the ‘Patient_Card_Header’ label, click the ‘New Local Translation/Overrides’ button, select the language and enter the new label. This method allows you to override the default label for a specific language. The other options are not valid ways to change the label.

Advanced Therapy Management can help the pharma company with its personalized medicine programs, as it enables them to coordinate the various steps involved in the process, such as apheresis and infusion. Advanced Therapy Management provides a set of features and tools that allow users to create and manage complex care plans, track the progress of each patient, and monitor the inventory and logistics of the therapy products.

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.

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 …

Advanced Therapy Management assists the healthcare organization with its complex scheduling requirements by allowing them to reschedule part of the appointment chain and book multi-step appointments. Rescheduling part of the appointment chain enables the organization to adjust the dates and times of individual appointments within a chain without affecting the rest of the chain. Booking multi-step appointments enables the organization to create a series of related appointments that follow a predefined sequence and duration.

According to the Salesforce documentation2, Remote Patient Monitoring is a feature in Health Cloud that enables healthcare organizations to use the data generated by connected devices used by patients to monitor their health and provide personalized care. Remote Patient Monitoring allows healthcare organizations to:

Use a meaningful subset of the data generated by connected devices to drive patient engagement and intervention. Remote Patient Monitoring helps healthcare organizations filter and prioritize the device data based on predefined rules and thresholds, and trigger actions such as alerts, tasks, or messages when certain conditions are met2.

Use the data generated by connected devices used by patients to monitor their health. Remote Patient Monitoring helps healthcare organizations collect and store the device data in Health Cloud, and display it in various views such as charts, dashboards, or reports. This helps healthcare professionals gain insights into the patients’ health status, trends, and outcomes2.

The approach that a consultant should use to set up this integration is a middleware integration solution that can handle data transformation if necessary. A middleware integration solution is a software layer that connects different systems and applications and facilitates data exchange between them. A middleware integration solution can also perform data transformation, which is the process of converting data from one format or structure to another. This is useful when the source system and the target system have different data models or standards.

n administrator can create tasks within a Care Plan that is related to a specific problem or goal from the Timeline Tab, the Care Plan page, or the Household Tab in the Health Cloud console. The Timeline Tab shows a chronological view of all the tasks, events, and notes related to a patient or member. The Care Plan page shows the details of a specific care plan, including the tasks, problems, goals, and interventions. The Household Tab shows a list of household members and their relationships with the patient or member3. The Care Team and the Patient List are not used to create tasks within a Care Plan.

According to the Salesforce documentation, a life sciences company can track the following terms about a care program using program management in Health Cloud:

The clinical indicators that need to be monitored in the care program, such as blood pressure, cholesterol level, or weight.

The products that are associated with a given care program, such as medications, devices, or services.

The plans that enrollees have been engaged in as part of the care program, such as education plan, adherence plan, or follow-up plan. Therefore, options A, B, and E are correct. Option C is incorrect, because marketing campaigns are not tracked by program management in Health Cloud. Option D is incorrect, because budget and expense are not tracked by program management in Health Cloud.

Reference and details below.

Graphical user interface, text, application Description automatically generated

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

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

Actionable Relationship Center can help Bloomington Caregivers to easily view all of the complex associations between patients, personal relationships, healthcare practitioners, other people, and organizations in healthcare. Actionable Relationship Center displays a graphical representation of the relationships between the record and other records in Health Cloud, such as Account, Contact, Care Team Member, Referral, and Care Plan. Users can also perform actions on the related records, such as creating tasks, sending messages, or updating fields.

According to the Health Cloud Data Model Developer Guide, Surveys, Intelligent Document Automation, and Care Coordination (Patient Services) are three features that are included with a Health Cloud License. Surveys allow you to create and send surveys to patients and providers to collect feedback and data. Intelligent Document Automation allows you to digitize your document management processes and extract data from documents using artificial intelligence. Care Coordination (Patient Services) allows you to manage patient care across multiple care plans and teams. EHR Mulesoft Templates and Intelligent Form Reader with Amazon Textract are not features that are included with a Health Cloud License.

According to the Salesforce documentation1, to install the health cloud claims unmanaged package, you need to have the health cloud managed package installed first. The health cloud managed package contains the core objects, fields, tabs, apps, components, and more that are required for health cloud functionality. The health cloud claims unmanaged package is an extension that contains additional objects, fields, tabs, apps, components, and more that are specific to claims management1.

Mask is a Salesforce product that helps you anonymize sensitive data in production copy sandboxes to ensure privacy, compliance, and regulatory requirements are met3. Mask replaces sensitive data with fictitious yet realistic data that preserves the characteristics of the original data. It also prevents unauthorized access to sensitive data by masking it before it is copied to a sandbox3.

Reference and details below.

The individual Data Model may be used to represent members ……(B) is the recommended approach to represent members and patients during the implementation by Patient Managers as per the Salesforce recommendation. Leveraging Person Accounts is not the recommended approach to ………(A), as Person Accounts are used to represent providers, not members or patients. Salesforce does not recommend using Member Accounts to represent members ……©, as Member Accounts are used to represent payer organizations, not members or patients. Leveraging Candidate Accounts are not the recommended approach to ………(D), as Candidate Accounts are used to represent potential members or patients, not existing ones.

Customizing the out of box enrollment flow to match requirements (A) and identifying the patient as approved candidate in the flow (D) are two steps that an administrator can take to configure the care program enrollment flow. Using the provider enrollment flow out of box (B) is not applicable, as it is for providers, not patients. Customizing the provider site flow © and customizing the care coordinator flow for patient (E) are not related to the care program enrollment flow.

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