Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional Exam (SU24) Questions and Answers

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

D is correct because Patient Provider Relationship is the standard object in Health Cloud that is used to track patient relationships to healthcare practitioners, such as cardiologist, primary care physician, and oncologist. Patient Provider Relationship represents the association between a patient and a healthcare practitioner who provides care for the patient. This object can store information such as the practitioner’s specialty, role, contact details, and relationship status.

References: : Patient Provider Relationship : Healthcare Practitioner Data Model

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 Health Cloud Care Request Extensions package provides out-of-the-box record types and page layouts for prior authorizations, as well as other features for managing care requests1.

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.

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.

Intelligent document automation supports the following file formats for upload: .jpg, .jpeg, .png, .pdf, and .tif2. Therefore, .png is the only acceptable format among the options.

 Encrypting the data using shield (A) and using field level security setting, record access setting and object permission (E) are two ways to prevent unauthorized users from accessing the data. Installing shield and enabling mask (B) is not enough to protect the data, as masking only obscures the data in reports and dashboards, but does not prevent access to the underlying data. Creating sharing sets © and optimizing data using mask (D) are not relevant to data security.

The administrator needs to add the custom object to the Timeline after deployment, then add it to the Timeline component. This will allow the custom object records to be displayed on the Enhanced Timeline2.

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

 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.

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.

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.

 Health Cloud Consent Management provides features such as email for signature and e-signature. Email for signature allows users to send consent documents to participants via email and track their status. E-signature allows participants to electronically sign consent documents using a third-party service such as DocuSign1. Capture Data Use Purpose, Delegated Signing, and Capture IP Address during completion are not features of Health Cloud Consent Management.

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.

According to the Salesforce documentation1, when setting up Intelligent Sales in Health Cloud, you need to create records for accounts, contacts, and locations. Accounts represent the organizations or individuals that you sell to, such as hospitals, clinics, or pharmacies. Contacts represent the people who work at those accounts, such as physicians, nurses, or pharmacists. Locations represent the physical places where you visit your contacts, such as offices, wards, or labs1.

Claims data model leverages external objects to support the use case of integrating claims data from external systems into Health Cloud. External objects are similar to custom objects, except that they map to data that’s stored outside your Salesforce org1.

According to the Salesforce documentation2, the Patient Card configuration allows you to customize how patient information is displayed in the patient console. You can create different tabs for different types of information, such as demographics, medications, or referrals. To indicate which tab should appear when a patient record is opened in the patient console, you need to edit the Patient Card configuration for that tab and enable Default Subtab. This will make that tab the default subtab for all patient records2.

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.

The two permission sets that an administrator should ensure are assigned so the users can access Provider Network Management are Health Cloud Standard permission set and Provider Network Management permission set. Health Cloud Standard permission set grants users access to Health Cloud features, such as Care Team, Care Plan, Timeline, etc. Provider Network Management permission set grants users access to Provider Network Management features, such as Provider Search, Provider Relationship Card, etc.

According to the Salesforce documentation2, there are two ways to capture consent from enrollees of a care program:

By talking to an agent via phone who then enrolls the patient using the Enroll in Program quick action in Health Cloud2.

By using a self-service portal via a community where the enrollee can view and sign the consent document electronically using DocuSign or Adobe Sign2. Therefore, options C and E are correct. Option A is incorrect, because web chat is not a supported channel for capturing consent in Health Cloud. Option B is incorrect, because email-to-case is not a supported feature for enrolling in a care program. Option D is incorrect, because SMS is not a supported channel for capturing consent in Health Cloud.

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

Reference and details below.

The consultant should create a criteria-based Account sharing rule to expand this access. A criteria-based Account sharing rule allows the consultant to share accounts that meet certain criteria with a specific group of users, such as auditors. This way, the auditors can view patient records that they do not own in Health Cloud.

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

According to the Health Cloud Data Model Developer Guide, CareProviderSearchableField is the object that external users need read access to allow patients to search and find providers that fit selected criteria. CareProviderSearchableField is a custom object that defines which fields on the CareProvider object are searchable by external users. CareProvider is a custom object that represents a provider who delivers care or services to patients. CareProviderFacilitySpeciality, HealthcarePractitionerFacility, and CareProviderSearchConfig are not objects that external users need read access to for provider search.

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.

Record Alerts can be used to inform agents about changes in information, such as a change in address or phone number. Record Alerts display a banner on the record page with a custom message and an optional link to another record or URL.

Action Launcher can be used to view basic details about a patient’s insurance, such as the plan name, coverage type, and eligibility status. Action Launcher displays a FlexCard component that shows key information from a related record or external data source.

Timeline can be used to have a complete view of all engagement interactions in one place, such as calls, emails, tasks, and events. Timeline displays a chronological list of past and upcoming activities related to the record.

References: : Record Alerts : Action Launcher : Timeline

To drive performance and scalability for Provider Search, a consultant should leverage the Data Processing Engine tool in Health Cloud. This tool allows pharma companies to map and transform the source data from the Provider Data Model into a searchable object called Care Provider Searchable Field. The Data Processing Engine also syncs the data with the Care Provider Searchable Field object once a day or manually as needed12. This process reduces the search time and improves the accuracy of the results. Flow for Industries, Pipeline Analytics, or Business Rules Engine are not tools that can fulfill this requirement.

The best way to conduct discovery to define a workflow for the call center users is to identify personas and ask them to walk through a day in their life, taking notes and identifying opportunities for optimization. This approach will help the consultant understand the current state of the process, the pain points and challenges, the goals and expectations, and the potential solutions.

Care request reviews (B), Care request drug ©, and Care request diagnosis (D) are three types of ancillary information that can be included in a single care request. Care request providers (A) and Care request facility (E) are not types of ancillary information, but types of related records that can be associated with a care request.

An administrator can configure the Care Program enrollment flow by using the provided enrollment flow out of the box or by customizing the out of the box enrollment flow template to match requirements. Health Cloud delivers an automated process for enrolling patients in care programs using Flow Builder. The flow lets the users select a program, add related products and providers, and capture the participant’s consent. The administrator can use the default flow or modify it to suit their needs2. Customize the provider site flow, customize the care coordinator flow for patient, and use the patient approval flow are not steps to configure the Care Program enrollment flow.

According to the [Health Cloud Implementation Guide], the three actions that are possible in the program enrollment flow when adding in ‘Enroll in Program’ quick action to a record are:

Starting a new blank care plan. This action allows you to create a new care plan for the patient based on their needs and goals.

Signing enrollment consent form. This action allows you to capture the patient’s consent for enrolling in a program using an e-signature tool.

Selecting the provider associated with a product. This action allows you to choose the provider who will deliver the product or service to the patient as part of the program. Seeing a list of all products and selecting applicable products is not an action in the program enrollment flow. Creating a new care program is not an action in the program enrollment flow.

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.

Coverage data model (B) is the data model that is used to represent information via standard object and record types on standard objects to manage how care is covered. Health Insurance data model (A), Payer data model ©, Plan data model (D), and Benefit data model (E) are not valid data models in Health Cloud.

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.

According to the Health Cloud Implementation Guide, Contact Tracing is a feature in Health Cloud that allows providers to perform contact tracing of their internal employees or their patients during an infectious disease outbreak or pandemic. Contact Tracing helps providers identify and monitor people who have been exposed to an infected person and provide them with guidance and resources. With the help of Contact Tracing, providers can perform the following three actions:

Perform contact tracing of their internal employees during an infectious disease outbreak or pandemic. This action allows providers to track and manage the health status of their employees who may have been exposed to an infection at work or in the community.

Perform contact tracing of their patients during an infectious disease outbreak or pandemic. This action allows providers to track and manage the health status of their patients who may have been exposed to an infection during a visit or in the community.

Track the location, duration, and number of participants in each contact encounter that the infected person was involved in. This action allows providers to collect and analyze data about the exposure risk and transmission patterns of an infection. Performing an audit of the Contact Record to keep track of the changes made to the Contact record by users is not an action that providers can take with the help of Contact Tracing. Tracking their patients as contacts by using Contact entity in Salesforce is not an action that providers can take with the help of Contact Tracing.

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.

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

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.

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

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.

According to the Salesforce website, The Social Determinants feature in Health Cloud helps providers perform the following activities:

Integrate services such as transportation and meal delivery into their patient care plans and programs. The Social Determinants feature allows providers to connect patients with community resources that can help them overcome nonclinical barriers to care, such as lack of transportation, food insecurity, or social isolation.

Track determinants and barriers to care across their patient populations. The Social Determinants feature allows providers to collect and analyze data on various social factors that affect patients’ health outcomes, such as income, education, housing, or environment.

Plan interventions to help address the barriers to care within their patient populations. The Social Determinants feature allows providers to create and manage action plans that target specific social needs of patients and measure their impact on health indicators.

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.

Reference and details below.

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

To help streamline caller authentication for Contact Center agents, a consultant should recommend Bloomington Caregivers use the Identity Verification Flow Templates feature in Health Cloud. This feature allows agents to launch a flow from the utility bar or a record page to verify a caller’s identity before processing their requests involving sensitive information. The flow prompts the agent to search for the caller in Health Cloud, select a reason for the call, ask verification questions based on predefined rules, and capture engagement details8. Customer Identity OmniScript Templates, Reusable Verification FlexCards, or Verify Customer Identity Process Flow are not features that exist in Health Cloud.

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.

C is correct because Social Determinants of Health (SDOH) are the non-medical factors that influence health outcomes, such as socioeconomic and cultural barriers. Health Cloud provides a feature that allows users to capture and track SDOH data for patients, such as housing status, food security, transportation access, and education level. This feature can help the pharmaceutical company to support patients throughout their clinical journey by identifying and addressing their SDOH needs.

References: : Social Determinants of Health at CDC

Reference and details below.

According to the Health Cloud Implementation Guide, Program Enrollee Settings is the place within Health Cloud Settings where a Health Cloud administrator can make changes to accomplish the requirement of enabling the members to enroll in and out of Care Program multiple times. Program Enrollee Settings allow the administrator to configure how members can be enrolled in or removed from care programs, such as allowing multiple enrollments, setting enrollment statuses, and defining enrollment criteria. Care Program Settings, Health Cloud Settings, and Care Request Settings are not places where the administrator can make changes to enable multiple enrollments.

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

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

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

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.

Install HC managed package (B), verify that chatter is enabled ©, and configure the console view (D) are three steps required to configure HC. Install HC unmanaged Package (A) is not a valid step, as there is no unmanaged package for HC. Enable the options for contact to related with multiple accounts (E) is not a required step, as it is only needed if using Contacts instead of Person Accounts.

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.

 To display device information on a patient card, an administrator can 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. Asset records represent devices that are owned by patients or members. Care Registered Device records link assets to patients or members and store information such as device type, status, serial number, and manufacturer5. Creating custom fields on other objects such as EHR_Patient, EHR_DeviceRequest, FilterCondition_c, or EHR_MedicalDevices will not display device information on a patient card.

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.

Goal © and Problem (D) are optional fields when creating a new Care plan task. Status (A) and Task Owner (E) are required fields when creating a new Care plan task. Due Date (B) is not a field on Care plan task, but rather on Task object.

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.

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.

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

A is correct because Intelligent Appointment Management (IAM) for Health Cloud helps patients schedule appointments through the channel of their choice: agent-assisted or self-service. 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.

References: : Intelligent Appointment Management

B is incorrect because Intelligent Form Reader is not a Health Cloud capability, but a Salesforce Platform capability that allows users to extract data from forms and documents using artificial intelligence.

References: : Intelligent Form Reader

C is correct because Provider Search helps patients find and connect with care providers that match their needs and preferences. Provider Search allows patients to search for providers by various criteria, such as name, location, specialty, availability, and ratings.

References: : Provider Search

D is incorrect because Assessments and Recommendations are not Health Cloud capabilities that directly improve patient satisfaction with appointment scheduling. Assessments and Recommendations are tools that help users gather information and provide guidance for patients based on their responses.

References: : Assessments and Recommendations

E is correct because Experience Cloud for Health Cloud enables patients to schedule their own appointments using a self-service portal or website. Experience Cloud for Health Cloud provides a prebuilt template that integrates with IAM and Provider Search to allow patients to book appointments online.

References: : Experience Cloud for Health Cloud

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.

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