Free and Premium Salesforce Health-Cloud-Accredited-Professional Dumps Questions Answers

B is correct because OmniStudio Document Generation is the tool that can provide the necessary functionality to send patients information documenting their visit and care plan. OmniStudio Document Generation allows users to generate documents from Microsoft Word or PowerPoint templates that can include data from any Salesforce object or external data source. Users can select from predefined templates or create their own, and personalize the documents with conditional logic, data tokens, and tabulation. Users can also convert the documents to PDF format and send them via email or other channels.

References: : OmniStudio Document Generation : Intelligent Document Automation for Healthcare

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.

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.

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.

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.

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

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

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

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

Reference and details below.

nder Custom Metadata Types, Update the Health cloud ‘HCFeature’… © and Under Custom Metadata Types, Create a mapping records for Person accounts (E) are two Health Cloud specific settings that must be configured in a Health Cloud org that has Lightning Experience enabled person account. Under Custom Metadata Types, enable the Health cloud Setting (A) and Disable “Use Individual Data Model” in custom setting (B) are not required settings for Health Cloud. Enable “Use Person Accounts” custom setting (D) is not a valid setting in Health Cloud.

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.

The main considerations when transforming the individual data model to person accounts are:

Transforming the individual data model to person accounts in production orgs is irreversible.

Organization-wide default sharing settings for accounts and contacts.

Integration between Salesforce and third-party systems.

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

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

References:

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

According to the Health Cloud Implementation Guide, Householding Map is the visual representation in Health Cloud that enables a care coordinator to see all the relationships between a patient and the people and organizations participating in the patient’s care, including those across multiple care plans. Householding Map shows a graphical view of the patient’s household members, care team members, providers, and other related entities. Timeline View, Care Team, Lightning Empower Components, and Patient Card are not visual representations that show all the relationships between a patient and their care participants.

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, Health Cloud uses Business APIs that should be used instead of object level APIs when creating records in Health Cloud objects. Business APIs are custom REST APIs that perform complex business logic and validations on Health Cloud objects. Object level APIs are standard REST or SOAP APIs that perform CRUD operations on individual objects. Business APIs ensure data integrity and consistency across Health Cloud objects, while object level APIs may result in data errors or inconsistencies2.

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

A is correct because enabling data protection details for fields is the entity that the administrator should enable within Data Protection and Privacy for Health Cloud to work in this scenario. Data protection details for fields allow users to specify the data protection level and data classification for each field on leads, contacts, and person accounts. This helps to identify and protect sensitive data, such as protected health information (PHI), and comply with privacy regulations, such as General Data Protection Regulation (GDPR).

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.

FHIR (Fast Healthcare Interoperability Resources) is a standard for exchanging healthcare information electronically. FHIR V4 is the latest version of FHIR, and it is aligned with Health Cloud3. Option A is incorrect, because there is no FHIR V5 yet. Option C is incorrect, because FHIR V3 is an older version of FHIR that is not aligned with Health Cloud. Option D is incorrect, because FHIR V1 is also an older version of FHIR that is not aligned with Health Cloud.

According to the Salesforce documentation1, the following types of electronic health record data transmitted via HL7 can be stored in Salesforce objects:

Observation Results (ORU): ORU messages contain clinical observations and results, such as lab tests, vital signs, or imaging reports. ORU messages can be stored in the DiagnosticReport object in Health Cloud1.

Admission, Discharge, Transfer Data (ADT): ADT messages contain information about patient admissions, discharges, transfers, or updates, such as demographics, insurance, or diagnosis. ADT messages can be stored in the EhrPatient object in Health Cloud1.

Clinical Document Architecture (CDA): CDA is a standard for exchanging clinical documents, such as discharge summaries, progress notes, or referrals. CDA documents can be stored in the Document object in Health Cloud1.

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

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 documentation3, Practitioner Relationship is an object in Health Cloud that is used to track the relationship between a provider and another provider or a facility. Practitioner Relationship includes information such as the relationship type, start date, end date, and status. Practitioner Relationship can be used to help sales teams view all providers related to a specific facility3.

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.

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.

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

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

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

The Advanced Patient Card is a Health Cloud capability that allows users to view and navigate to critical information on a patient’s profile, such as insurance, clinical, and primary care physician information1. The Advanced Patient Card is a customizable component that can be added to the Health Cloud console or the Contact Center app2. It can also display data from external sources, such as EHR systems or medical devices3.

References:

1: Use the Advanced Patient Card - Salesforce 2: Configure the Person Account Page Layout for Contact Center - Salesforce 3: Display Data from External Sources in the Advanced Patient Card - Salesforce

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

According to the Health Cloud Data Model Developer Guide, Program Management is a feature in Health Cloud that allows life science companies to track and manage care programs that offer products and services to patients and providers. With Program Management, life science companies can track the following three items about a care program:

The multiple marketing campaigns that enrollees are subjected to as part of the care program. This item can be tracked by using the CareProgramEnrolleeCampaign object, which represents a marketing campaign that targets a specific care program enrollee.

The products that are associated with a given care program. This item can be tracked by using the CareProgramEnrolleeProduct object, which represents a product or service that is offered to a care program enrollee.

The plans that enrollees have been engaged in as part of the care program. This item can be tracked by using the CareProgramEnrolleePlan object, which represents a plan or package that contains one or more products or services for a care program enrollee. The budget and expenses of the company’s associated care program is not an item that can be tracked by using Program Management. The clinical indicators that need to be monitored in the care programs is not an item that can be tracked by using Program Management.

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.

After deploying a care plan template from a sandbox to a final environment using Data Loader, the consultant should recommend the following two steps to enable users to successfully leverage the new template:

Confirm User access to Care plan objects: The consultant should ensure that the users have the appropriate permissions and sharing settings to access the care plan objects, such as Care Plan Template, Care Plan Template Problem, Care Plan Template Goal, and Care Plan Template Task1. The users should also have access to the parent records of the care plan objects, such as Account or Contact2.

Activate the new care plan template: The consultant should activate the new care plan template by changing its status from Draft to Active3. This will make the template available for users to apply to their patients. The consultant does not need to activate the problems, goals, and tasks associated with the template separately, as they are automatically activated when the template is activated3.

References:

1: Permissions Required for Care Plans - Salesforce 2: Give Caseworkers Access to Goal Assignments and Benefit Assignments Related to Care Plans - Salesforce 3: Create a Care Plan Template - Salesforce

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

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.

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

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

According to the Salesforce documentation2, to display device information on a patient card, you need to create an asset record and a care registered device record that look up to the patient. An asset record represents the device that is used by the patient, such as a blood pressure monitor, a glucose meter, or a pulse oximeter. A care registered device record represents the relationship between the patient and the device, such as the device name, serial number, status, and start and end dates2.

Reference and details below.

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 administrator should add the respiratory therapist to the patient’s Care Team and grant Read or Read/Write access as needed. This is the out-of-the-box Health Cloud feature that allows the administrator to share patient data with other users who are involved in the patient’s care. The Care Team is a group of users who can collaborate and communicate on a patient’s health record.

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

Mulesoft Accelerator for Healthcare (A) is the solution that includes pre-built APIs, connectors, implementation templates, and a prescriptive end-to-end reference architecture to enable EHR connectivity and power a patient 360 from any EHR into Health Cloud using HL7 V2 or FHIR standards. Shield (B) is a solution that provides encryption and auditing capabilities for data security. Specialty vendors © are not a solution, but a type of external partners that can provide integration services. Tableau CRM for Healthcare (D) is a solution that provides analytics and insights for healthcare data.

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.

Reference and details below.

Graphical user interface, text, application Description automatically generated

Reference and details below.

 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.

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

Patients should be modeled as Person Accounts. Providers and non-clinical staff should be modeled as Contacts (D) is the correct answer. Patients, physicians and non-clinical staff should not be modeled as Person Accounts (B), as Person Accounts are only for patients. The individual Data Model is not recommended for HC, as it does not support all the features of HC ©. Providers and non-clinical staff can be modeled as Person Accounts or Contacts (A) is not a valid answer, as it does not specify which group should be modeled as Person Accounts.

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.

The three steps that the administrator should take as part of the org setup to enable Assessments are enabling Discovery Framework in Setup, adding the Assessment component to the Patient page, and enabling users to view and complete Assessments. Discovery Framework is a feature that allows the administrator to create and manage assessments in Health Cloud. The Assessment component is a Lightning component that displays the assessments assigned to a patient on their record page. Enabling users to view and complete Assessments requires assigning them the appropriate permission sets and page layouts.

To identify pain points and define project requirements for setting up a Contact Center leveraging Health Cloud, a consultant should work with the following group of people:

(Persona) Contact Center agent: This is the end user who interacts with patients through phone calls, emails, chats, or other channels. The Contact Center agent needs to have access to patient information, appointment scheduling, billing inquiries, plan updates, and other tasks in Health Cloud. The consultant should work with the Contact Center agent to understand their needs, challenges, and expectations from the system.

(Stakeholder) Salesforce administrator: This is the person who configures and maintains the Health Cloud system for the Contact Center. The Salesforce administrator needs to set up user profiles, permissions, page layouts, workflows, reports, dashboards, and other features in Health Cloud. The consultant should work with the Salesforce administrator to understand the technical requirements, limitations, and best practices for setting up the system.

(Stakeholder) Integration architect: This is the person who designs and implements the integration between Health Cloud and other external systems, such as EHRs, billing systems, or third-party applications. The integration architect needs to ensure that data is exchanged securely and accurately between Health Cloud and other systems. The consultant should work with the integration architect to understand the integration requirements, challenges, and solutions for the system. General physician, Marketing Cloud administrator, Care coordinator, Tableau developer or MuleSoft developer are not relevant people for this use case.

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

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.

The steps required to display a custom field from the HealthCondition object that categorizes High Risk Conditions on the Patient Card are:

Create a custom formula field on the Custom HealthCondition object. This field can use logic to determine whether a health condition is high risk or not based on certain criteria.

Add the newly created custom formula field on the Patient Card referencing the HealthCondition object. This can be done by creating or editing a patient card configuration record and adding the field API name in the Field Name column.

The set of objects that the consultant should implement to meet the pharma company’s requirements are Account, Purchaser Plan, Plan Benefit, and Member Plan. These objects are part of the Health Cloud data model and allow the company to track payer organizations, plans, benefits, and patient enrollments.

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

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

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.

Reference and details below.

According to the Salesforce documentation3, there are two ways to support the health department so that the team can efficiently assess the individual, enroll them in a program, and monitor them during emergency:

Install Emergency Response Management unmanaged package, which provides prebuilt objects, fields, apps, tabs, reports, dashboards, and more to help health organizations manage emergency response3.

Leverage pre-configured flows provided with Health Cloud, such as Assess Individual Risk Level flow and Enroll in Program flow, which help health workers quickly assess and enroll individuals in emergency programs3. Therefore, options B and C are correct. Option A is incorrect, because there is no such thing as a healthcare provider enrollment flow in Health Cloud. Option D is incorrect, because there is no such thing as a patient enrollment console in Health Cloud.