Health-Cloud-Accredited-Professional Sample Questions Answers

To create Salesforce reports to analyze patient outcomes and patient referrals, a consultant should recommend the following steps:

• Create custom report types for clinical objects, such as Condition, Medication, or Encounter, to access the data stored in Health Cloud’s clinical data model1.
• Assign appropriate permissions to internal users, such as the Health Cloud Analytics permission set, to enable them to view and create reports and dashboards2.
• Adjust template care management reports and dashboards, such as Patient Outcomes or Patient Referrals, to customize them for the customer’s specific needs34. Enabling the enhanced Analytics for Healthcare setting or leveraging the Patient Referral Management unmanaged package are not required steps for this requirement.

Benefits Eligibility and Verification is a Health Cloud capability that allows users to verify a patient’s insurance plan information and coverage in real time, directly on the patient record1. Users can connect with verification partners easily by integrating with third-party benefits and eligibility services1. Users can also check benefits for medical services, pharmacy, and medical equipment to ensure patients have the required coverage before their visit1.

This capability can help a provider’s office to verify a patient’s insurance plan information and coverage when they call into the call center to book an appointment. The call center agent can access the patient’s account record, click the tab that contains the Benefits Verification component, and see a list of the available health insurance plans for the patient2. The agent can then verify the plan benefits, such as eligibility, coverages, and copayments, by clicking Verify Benefits2. The page then updates with real-time details of the patient’s benefits for the selected plan2.

References:

1: Get Started with Benefits Verification Unit | Salesforce Trailhead 2: Work with Benefits Verification Unit | Salesforce Trailhead

• 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

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 documentation, a healthcare facility network is a custom object in Health Cloud that stores information about a network of facilities that are affiliated with each other, such as hospital system, clinic network, or pharmacy chain. A healthcare facility network can be used to track each of the different networks where a provider is affiliated.

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.

 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.

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.

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.

• 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

To enable call center agents at Bloomington Caregivers to look up providers by appointment on behalf of their patients, a consultant should recommend the following capabilities in Health Cloud:

• Provider Search: This is a feature that allows call center agents to search for providers based on various criteria, such as location, specialty, availability, network status, ratings, languages spoken, etc. Provider Search helps call center agents find the best match for their patients’ needs4.
• Intelligent Appointment Management: This is a feature that allows call center agents to schedule appointments with providers based on their availability and preferences. Intelligent Appointment Management helps call center agents optimize appointment booking by considering factors such as travel time, urgency level, patient history, provider capacity, etc5. Experience Cloud for Health Cloud or Integrated Care Management are not capabilities that can fulfill this requirement.

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.

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.

• A is correct because identifying personas involved and their existing pain points can help the consultant understand the current state of the business and the needs and expectations of the users.
• B is incorrect because writing Apex code to customize Health Cloud is not a discovery activity, but a development activity that should be done after the requirements and design are finalized.
• C is correct because building an architecture diagram depicting Health Cloud integrations can help the consultant understand how Health Cloud fits within the application architecture and what data sources and systems need to be connected.
• D is incorrect because creating business process diagrams to understand information flow is not a discovery activity, but a design activity that should be done after the requirements are gathered and validated.
• E is correct because identifying key stakeholders and how they measure success can help the consultant understand the vision and goals of the project and the expected outcomes and benefits of Health Cloud.

References: : Health Cloud Implementation Guide : Health Cloud Implementation Best Practices

According to the Salesforce documentation2, Care Observations is an object in Health Cloud that is used to store the data for patient’s smartwatch to display within the Remote Monitoring charts. Care Observations include information such as the observation type, value, unit, date, and time. Care Observations can be created from various sources, such as connected devices, manual entry, or external systems2.

Medication Review and Medication Reconciliation are two Health Cloud solutions that can help a company based in the United States to track medications that patients take in a standardized format and detect potential drug-to-drug interactions.

Medication Review is a Health Cloud feature that allows users to capture standardized information related to medication, such as drug name, dosage, frequency, route, and indication1. Users can also add notes and recommendations for each medication, and view the medication history of a patient1. Medication Review supports the RxNorm standard, which is a normalized naming system for generic and branded drugs in the US2.

Medication Reconciliation is a Health Cloud feature that allows users to efficiently manage and reconcile a patient’s medications list using the Patient Medication Manager lightning component3. Users can easily review the patient’s medication information, identify errors and adverse drug interactions, and add recommendations and notes, all from one place3. Medication Reconciliation also supports the RxNorm standard, and uses the National Library of Medicine API to check for drug-to-drug interactions4.

References:

1: Medication Management and Medication Review - Salesforce

• B is correct because enabling person accounts from Setup is a prerequisite to install the Health Cloud managed package. Person accounts are a special type of account that combines the attributes of an account and a contact. 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.
• C is correct because enabling Chatter settings from Setup is a prerequisite to install the Health Cloud managed package. Chatter is a collaboration tool that allows users to communicate and share information with each other. Health Cloud uses Chatter to enable features such as care team collaboration, patient engagement, and social determinants of health.
• D is correct because enabling contacts to relate to multiple accounts is a prerequisite to install the Health Cloud managed package. This feature allows users to create relationships between a contact and multiple accounts, and specify the role and status of each relationship. Health Cloud uses this feature to enable features such as actionable relationship center, patient provider relationship, and referral management.
• A is incorrect because making data protection details available in records is not a prerequisite to install the Health Cloud managed package, but an optional step that can be done after the installation. Data protection details for records allow users to view and edit the data protection level and data classification for each record on leads, contacts, and person accounts.
• E is incorrect because logging a support case to have person accounts enabled is not a prerequisite to install the Health Cloud managed package, but an alternative way to enable person accounts if they are not available in Setup. However, this method requires contacting Salesforce Customer Support and waiting for their response, which may take longer than enabling person accounts from Setup.

According to the Health Cloud Implementation Guide, a Health Cloud administrator can change the default sub-tab when opening a record by going to setup, navigating to Custom Settings, and editing the Default Subtab setting. This setting allows you to specify which sub-tab should be displayed by default when opening a record in Health Cloud – Console. The other options are not relevant for changing the default sub-tab.

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.

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.

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.

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.

Health Cloud helps HLS organizations achieve HIPAA compliance (A), Health Cloud is HITRUST certified ©, and Health Cloud is GDPR certified (D) are three ways that Health Cloud meets compliance and regulatory requirements. Health Cloud is not HIPAA certified (B), as HIPAA certification does not exist. Health Cloud is not HL-7 compliant (E), as HL-7 is a standard for exchanging health information, not a compliance requirement.

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

The three key considerations when complying with HIPAA regulations using Salesforce Shield in conjunction with Bloomington Caregivers’ data strategy are ensuring that sensitive data is encrypted both in transit and at rest, configuring data retention policies to ensure that records are retained for the appropriate length of time, and implementing audit trails and regularly reviewing them to detect unauthorized access attempts. Salesforce Shield provides these features as part of its platform encryption, event monitoring, and field audit trail capabilities.

• 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

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.

According to the Salesforce documentation1, the Health Cloud Provider data model is an optional data model that can be used to represent providers and their relationships in Health Cloud. It is not required for all Service Cloud to Health Cloud migrations, and it can coexist with the existing data model. The Custom Provider Search Lightning component is a custom component that can be used to search for providers using any data model, including the Health Cloud Provider data model or a custom provider data model. The Health Cloud Provider Search component is a standard component that can be used to search for providers using the Health Cloud Provider data model only. It can be extended or customized, but not replaced by a custom component1.

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.

• A is correct because barcode scanning is a capability that can be leveraged with Health Cloud out-of-the-box using Intelligent Document Automation (IDA). IDA can scan and extract data from barcodes on documents, such as patient wristbands, lab reports, or medication labels.
• B is correct because record type association is a capability that can be leveraged with Health Cloud out-of-the-box using IDA. IDA can associate a document with a specific record type based on the document type, such as consent form, referral letter, or discharge summary.
• C is incorrect because eFax connection is not a capability that can be leveraged with Health Cloud out-of-the-box using IDA. IDA does not support receiving or sending documents via eFax. However, it is possible to integrate IDA with third-party eFax services using custom code or connectors.
• D is correct because automated document checklist item creation is a capability that can be leveraged with Health Cloud out-of-the-box using IDA. IDA can create document checklist items for documents that are received and processed, and update their status based on the document processing stage.

References: : Intelligent Document Automation : Intelligent Document Automation for Healthcare

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.

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 website, Health Cloud solves for some of the common challenges that healthcare companies face from various sources. Some of these challenges are:

• The need to drive sales while reducing cost: Health Cloud helps healthcare companies increase their revenue and efficiency by streamlining their processes, automating their workflows, and optimizing their resources.
• Growing customer expectations for delivery of care everywhere: Health Cloud helps healthcare companies deliver personalized and collaborative care across every touchpoint, whether it is in person, online, or on mobile devices.
• Growing demand for a more personalized care experience: Health Cloud helps healthcare companies provide tailored and holistic care for each customer by leveraging data insights, artificial intelligence, and digital engagement tools.

 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.

Einstein Analytics Predictions is an add-on license that enhances Health Cloud to allow you to highlight times when a patient is most likely to attend an appointment. It uses machine learning to analyze historical data and generate predictions based on various factors2. Einstein Vision, Einstein Bots, and Einstein Activity Capture are not related to this use case.

• B is correct because integrating using the FHIR Clinical API is the appropriate method for Bedrock to access the information leveraging Health Cloud functionality. The FHIR Clinical API is a RESTful API that allows external systems to access and exchange clinical data stored in Health Cloud, such as AllergyIntolerance, Condition, MedicationOrder, and Procedure. The FHIR Clinical API uses the FHIR standard, which is a widely adopted interoperability standard for healthcare data.

References: : FHIR Clinical API : FHIR Overview

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.

• C is correct because Provider Relationship Management is a Health Cloud add-on that helps payers to recruit, credential, and onboard providers into their network. Provider Relationship Management provides features and tools that allow payers to manage provider contracts, track provider performance, monitor provider satisfaction, and streamline provider communication.

References: : Provider Relationship Management : Provider Relationship Management Implementation Guide

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.

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.

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.

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.

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.

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.

To implement a robust appointment management system for a provider that uses an external system, a consultant should use a package created by ISV (Independent Software Vendor) for Health Cloud. This would allow the provider to leverage existing solutions that are integrated with Health Cloud and offer features such as scheduling, reminders, cancellations, rescheduling, and confirmations. Using an EHR routing system, creating a custom FHIR Adapter, or creating an Apex class are not viable options for this requirement3.

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.

Shield © is the Salesforce product that allows encryption of Protected Health Information (PHI) data at rest to enhance Health Cloud. Tableau CRM (A), Service Cloud (B), and Health Cloud (D) are not products that provide encryption capabilities.

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

• 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 Implementation Guide, two statements that are true about Care Teams are:

• Care Team Members are optional on a Care Plan. This statement is true because a care plan can be created without any care team members assigned to it. However, adding care team members can help with collaboration and coordination of care.
• A Care Plan must have a Coordinator as a member of the Care Team before a Care Plan Template can be applied. This statement is true because a coordinator is required to manage the tasks and goals of a care plan template. A coordinator can be either an internal or external user who has access to Health Cloud. If the Problem and Goal objects use Private Sharing, Care Team Membership provides access to these objects is not a true statement, as care team membership does not grant access to objects that use private sharing. Communities must be enabled before External Care Team members can be added is not a true statement, as external care team members can be added without enabling communities.

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.

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

Reference and details below.

Reference and details below.

To implement Home Health scheduling with Health Cloud, a consultant should assign Healthcare Visit Manager permission set license to users who need to schedule visits. This permission set license grants users access to objects and fields related to home health visits, such as Service Appointment, Service Resource, Service Territory, Service Report Template, etc7. This permission set license also enables users to use Salesforce Scheduler for Health Cloud feature, which allows users to schedule home health visits based on various criteria, such as availability, location, skills, etc8. Field Dispatch Scheduler, Manage Home Health, or Execute Health Scheduling are not permission set licenses that can fulfill this scenario.

To show end users highlighted information about providers that work at specific facilities, a consultant should implement the Provider Relationship Card feature. This feature allows end users to view information such as provider name, contact details, specialty, role, facility name, and relationship status on a card-like interface on the Facility record page. Provider Network Management, Facility Relationship Center, or HCProvider360 FlexCard are not features that can fulfill this requirement.

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.

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.

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 view medication data from Health Cloud leveraging FHIR standards, a consultant should use the clinical data model. This data model is built to align with HL7’s FHIR R4 and provides objects and fields to store and access clinical information such as medications, conditions, encounters, observations, and more6. The clinical data model also supports FHIR APIs to enable interoperability between Health Cloud and external systems that use FHIR standards7. Integrated Care Management data model, Electronic health record (EHR) data model, or Virtual Care data model are not data models that can fulfill this requirement.

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.

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.