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

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.

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.

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.

The three requirements for implementing patients or members in Health Cloud are ensuring the Person Account object is used, ensuring 1-to-1 Account to Contact relationship, and ensuring the Parent Account field is blank. These requirements are part of the Health Cloud data model and allow the consultant to model patients or members as individuals with personal and health information.

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

Reference and details below.

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

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

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

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

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

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.

Reference and details below.

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

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

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

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

References:

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

According to the 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.

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.

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

According to the Health Cloud Implementation Guide, leveraging Person Accounts is the recommended approach to represent Members and Patients during the basic set-up of Health Cloud console for Care Coordinators and Managers. Person Accounts are a type of account that combines account and contact information in a single record. They are suitable for representing individual consumers in healthcare and life sciences. The other options are not recommended approaches to represent Members and Patients.

According to the 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.

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.

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.

Reference and details below.

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

According to the Health Cloud Implementation Guide, Life Events are a feature in Health Cloud that allow clinicians to see an overview of the patient’s life, such as Starting a New Job, Birth of a Baby, Divorce, etc. Life Events help clinicians understand the patient better and help them with a personalized care plan. Life Events can be added to the patient’s timeline or life map. Life Goals, Household Map, Milestones, and Life Map are not features that show the patient’s life events.

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.

Add NPI for associated provider (A) and create a care program health care provider with an associated care program provider (E) are two steps required to create health care providers for health program. Choose associated facility for care program (B) is not a valid step, as facilities are not related to health care providers. Add the UPIN © is not a required step, as UPIN is an optional field for health care providers. Create care program providers from the app launcher (D) is not a valid step, as care program providers are created from the related list on the care program record.

Medication Management is a Health Cloud add-on product that helps providers and care coordinators manage the medication regimen of their patients, helping to improve patient safety and reduce healthcare costs1. One of the features of Medication Management is the ability to perform medication reconciliation of patients’ medication list and detect potential drug-to-drug interactions1. This feature can help Bloomington Caregivers to view and address any medication issues for their patients and make recommendations based on the data within Health Cloud.

References:

1: Medication Management | Health Cloud Administration | Salesforce Developers

Reference and details below.

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

References:

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

B is correct because creating a new record for the HCBenVerConnect custom setting is required to access the Benefit Verification component in Health Cloud. The HCBenVerConnect custom setting stores the configuration details for the connection to the external benefit service that provides the patient’s insurance coverage information.

D is correct because creating a named credential to support authenticated callouts is required to access the Benefit Verification component in Health Cloud. A named credential specifies the URL of the external benefit service and the authentication protocol and credentials to use for callouts to that service.

References: : Set Up Data for Benefit Verification : [Named Credentials]

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

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

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

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.

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.

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.

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

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.

 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.

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.

Health Cloud Foundation

Assigns read access to additional Health Cloud platform capabilities, including the Provider Management data model.

The Health Cloud Provider Network Management permission set grants access to provider management objects so users can manage

credentialing and recruiting.

To use the Provider Network Management features of Health Cloud, assign both the Provider Network Management permission set and

the Health Cloud permission set to your users

 Users can access Provider Management standard objects by using Health Cloud, by assigning Health Cloud Platform Permission set licenses, and by assigning Health Cloud Foundation Permission set. Health Cloud is the industry-specific solution that includes Provider Management features such as provider search, provider network management, and provider credentialing3. Health Cloud Platform Permission set licenses grant access to the Health Cloud platform objects and features, including the Provider Management data model4. Health Cloud Foundation Permission set assigns read access to additional Health Cloud platform capabilities, including the Provider Management data model5. Service Cloud is not required to access Provider Management standard objects, and the Provider Permission set is not a standard permission set in Health Cloud.

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

Health Cloud meets compliance and regulatory requirements in the following ways2:

Health Cloud helps healthcare organizations achieve HIPAA compliance. HIPAA is a US law that protects the privacy and security of patient health information. Health Cloud offers various features and tools to help customers comply with HIPAA, such as encryption, audit trails, data masking, and consent management. Customers who want to use Health Cloud for HIPAA purposes can sign a Business Associate Addendum (BAA) with Salesforce.

Health Cloud is HL7 compliant. HL7 is a set of standards for exchanging health information electronically. Health Cloud supports HL7 FHIR (Fast Healthcare Interoperability Resources), which is a modern specification for representing and sharing health data. Health Cloud allows customers to integrate with external systems that use FHIR APIs and access FHIR resources within Salesforce.

Health Cloud is HITRUST certified. HITRUST is a framework that provides a comprehensive and flexible approach to security and privacy in the healthcare industry. HITRUST certification demonstrates that an organization meets the highest standards of data protection and compliance. Health Cloud has achieved HITRUST CSF certification for its core services and features.

Health Cloud is not HIPAA certified or GDPR certified. HIPAA certification does not exist as a formal process or accreditation. HIPAA compliance is a shared responsibility between Salesforce and its customers, and each party must implement appropriate safeguards and policies to protect patient data3. GDPR is a European law that regulates the processing of personal data of individuals in the EU. GDPR compliance depends on various factors, such as the type and purpose of data processing, the location of data subjects and processors, and the rights and obligations of data controllers4. Salesforce provides various tools and resources to help customers comply with GDPR, but it does not certify Health Cloud as GDPR compliant.

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

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.

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 Health Cloud Implementation Guide, the two steps that need to be taken during the set-up process for Utilization Management are:

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

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

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

Reference and details below.

According to the Health Cloud Data Model Developer Guide, Risk scores are only recalculated for patients who are affiliated with a care program is the most likely reason why recalculation score for the patient is not displaying. Risk scores are calculated based on CMS-HCC (Centers for Medicare & Medicaid Services - Hierarchical Condition Categories) model, which assigns risk factors to patients based on their diagnoses and demographic factors. Risk scores are used to adjust payments for health plans and providers. Risk scores are only recalculated when the recalculate flag is set to TRUE and the patient is affiliated with a care program. Using CMS recalculation API is not a valid reason, as CMS recalculation API is not a feature of Health Cloud. CMS scores cannot be recalculated in health cloud is not a valid reason, as CMS scores can be recalculated in health cloud by setting the recalculate flag to TRUE. Using a third party API to recalculate CMS risk score is not a valid reason, as it has nothing to do with displaying the recalculation score.

Reference and details below.

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

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.

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

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

The two objects that support Salesforce’s recommended approach to model the doctors in the clinic’s Health Cloud org are Contact and Healthcare Practitioner. Contact is used to store the personal information of the doctor, such as name, phone, and email. Healthcare Practitioner is used to store the professional information of the doctor, such as specialty, license, and credentials.

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.

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

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

Reference and details below.

Graphical user interface, text, application Description automatically generated

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.

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.

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

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

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