Salesforce Certified Health Cloud Accredited Professional Practice Test - Questions Answers, Page 13

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.

Risk scores are recalculated only for patients that are affiliated with a Care Program is the most likely reason why the recalculation score for the patient is not displaying. CMS risk scores can be recalculated in Health Cloud (A), so this is not a reason for the score not displaying. CMS risk scores can be recalculated using both third party APIs and Salesforce APIs (B), so this is not a reason for the score not displaying. Risk scores can be calculated using both the CMS recalculation API and other methods (D), so this is not a reason for the score not displaying.

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.

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.

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.

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.

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.

The users need both the Health Cloud permission set license and the Health Cloud Standard permission set license to access Health Cloud features.The Health Cloud Foundation permission set license is for users who only need access to the Health Cloud data model, and the Health Cloud Platform permission set license is for users who need access to the Health Cloud Lightning components3.

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.