Salesforce Health-Cloud-Accredited-Professional Dumps

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

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.

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.

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.

 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.

Case, Problems, Goals, Tasks, Care Plan Templates (D) are the standard objects that are included in the Care Plan Data Model. Care programs, Product, Patients (A), Life Events (B), and Benefits, Barriers, Provider Education © are not standard objects in the Care Plan Data Model.

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

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

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.

Reference and details below.

According to the Health Cloud Implementation Guide, the best practice when transitioning an org from Service Cloud to Health Cloud is to approach it depending on how each customer uses their org. There is no one-size-fits-all solution for migrating from Service Cloud to Health Cloud, as each customer may have different requirements, use cases, and data models. Therefore, any of the other options may be used depending on the customer’s needs and preferences.

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

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.

According to the Salesforce documentation, there are three steps that should be followed when setting up Intelligent Sales in Health Cloud:

Enable Intelligent Sales: This step allows you to turn on the Intelligent Sales feature in Health Cloud and configure some settings such as default visit duration, visit report template, and visit report email template.

Set up permission set for Intelligent Sales: This step allows you to assign the appropriate permission sets to users who need access to Intelligent Sales features such as visit management, product catalog, order authorization, and inventory management.

Set Visit Inventory Management to enabled: This step allows you to enable the inventory management feature in Health Cloud and configure some settings such as default inventory location, default inventory transfer status, and default order authorization status.

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

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

A is correct because administrators can restrict access to patient or member lists using standard Salesforce sharing settings on the list. The Patient List object has an organization-wide default sharing setting that determines the baseline access level for all users in the org. Administrators can also use sharing rules, manual sharing, or Apex managed sharing to grant additional access to specific users or groups.

B is correct because users with profile or permission sets that restrict access to an object cannot create a list using that object. Users need to have at least read access to the objects and fields that they want to use as filters or display columns in their lists. Administrators can check and modify the user’s object and field permissions from their profile or permission set.

C is incorrect because administrators cannot restrict access using HCPatientListSecurity custom setting. This custom setting is used to control the visibility of patient or member lists in the Patient List tab, not the access to the lists. Administrators can use this custom setting to specify which lists are visible to which profiles or permission sets, or hide all lists from a profile or permission set.

D is correct because when a user’s field-level security restricts access to a field used as a display column, the column does not appear in the list. This is because the field-level security settings override the list settings and prevent the user from viewing the field value. Administrators can check and modify the user’s field-level security settings from their profile or permission set.

References: : Manage Your Patient or Member Lists : Control Access to Patient or Member Lists

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.

 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.

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.

The developer should add a Conditional Block to the existing Create Appointment Integration Procedure to solve the request. A Conditional Block is a component in OmniStudio that allows the developer to define conditional logic based on input values or variables. A Conditional Block can be used to check if the provider has moved to a new location, and if so, send an email with the new address to the patient.

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

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.

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

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.

Reference and details below.

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.

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

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.

According to the Salesforce documentation, the following capabilities of the provider search would a customer service agent use to help payers find the right provider:

Control the list of fields displayed in the search panel and search results. The provider search allows customer service agents to customize which fields are displayed in the search panel and search results for different types of providers or facilities. This helps them find the most relevant information quickly and easily.

Use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of the search provider. The provider search allows customer service agents to use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of the search criteria or filters. This helps them narrow down their search results based on specific attributes or preferences.

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.

To solve the use case of creating a new order and displaying available products for purchase, a developer should leverage the following OmniStudio capabilities:

OmniScript: This is a capability that allows developers to create guided flows that capture user inputs and execute business logic. OmniScript can be used to create a process that builds a new order based on customer data and product selection9.

FlexCards: This is a capability that allows developers to create reusable UI components that display data from various sources. FlexCards can be used to create a component that shows customer data and contains a link to start the OmniScript flow10.

Document Generation: This is a capability that allows developers to create documents based on templates and data from various sources. Document Generation can be used to create an order confirmation document that shows the details of the order and products purchased11. DataRaptors or Integration Procedures are not required capabilities for this use case.

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.

Reference and details below.

 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.

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.

According to the Health Cloud Implementation Guide, the way to change the label ‘Patient Card’ to ‘Member Card’ to be more aligned with their specific business terminology and use case is to go to setup, navigate to Custom Labels, select the ‘Patient_Card_Header’ label, click the ‘New Local Translation/Overrides’ button, select the language and enter the new label. This method allows you to override the default label for a specific language. The other options are not valid ways to change the label.

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.

According to the Health Cloud Data Model Developer Guide, CarePlan Template Task, TimelineViewConfiguration, and CarePlanGoal are three Health Cloud objects that are part of the standard Care Management data model. CarePlan Template Task is a custom object that represents a task that is part of a care plan template. TimelineViewConfiguration is a custom object that defines how to display timeline events for a care plan. CarePlanGoal is a custom object that represents a goal that is part of a care plan. CareSpeciality and CareProgramGoal are not Health Cloud objects that are part of the standard Care Management data model.

The Healthcare Practitioner Facility object is used to model a physician’s locations of service, such as clinics or hospitals. It stores information about the facility name, address, phone number, and type.

 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.

To enable agents to answer questions from members regarding their benefits coverage, a consultant should recommend the Benefits Coverage component for the Member record page. This component displays information such as plan name, effective date, termination date, deductible amount, coinsurance percentage, copay amount, and out-of-pocket maximum for each benefit plan that the member is enrolled in. Benefits Verification, Eligibility Validation, or Coverage Confirmation are not components that exist in Health Cloud.

According to the [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 approach that a consultant should use to set up this integration is a middleware integration solution that can handle data transformation if necessary. A middleware integration solution is a software layer that connects different systems and applications and facilitates data exchange between them. A middleware integration solution can also perform data transformation, which is the process of converting data from one format or structure to another. This is useful when the source system and the target system have different data models or standards.

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

C is correct because Integration Procedures are components that can be used to update an existing field on a custom SObject. Integration Procedures are reusable processes that can perform various actions on data, such as reading, writing, transforming, or validating. Integration Procedures can be invoked from an OmniScript or a DataRaptor, and can accept input parameters and return output values.

D is correct because DataRaptors are components that can be used to update an existing field on a custom SObject. DataRaptors are data transformation tools that can extract, load, or transform data from any Salesforce object or external data source. DataRaptors can be invoked from an OmniScript or an Integration Procedure, and can accept input parameters and return output values.

References: : Integration Procedure : DataRaptor

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

References: : Social Determinants of Health at CDC

To get a patient’s allergy information from Bloomington Caregivers’ Health Cloud system, an external provider should use the Interoperability API. This API allows external systems to access and exchange clinical data with Health Cloud using FHIR standards. The Interoperability API supports various FHIR resources, including AllergyIntolerance, which represents a patient’s allergic or intolerant reaction to a substance1. AllergyMedication API, Patient Healthcare API, or Clinical Summary Healthcare API are not APIs that exist in Health Cloud.

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.

B is correct because Program Enrollment Flow is the out-of-the-box Health Cloud feature that helps users to register patients to care programs while capturing their consent. Program Enrollment Flow is a prebuilt flow template that guides users through the steps of selecting a program, adding related records, and obtaining consent from the patient. The flow also creates a care plan for the patient based on the program template.

References: : Care Programs in Health Cloud : Configure the Program Enrollment Flow

Customizing the out of box enrollment flow to match requirements (A) and identifying the patient as approved candidate in the flow (D) are two steps that an administrator can take to configure the care program enrollment flow. Using the provider enrollment flow out of box (B) is not applicable, as it is for providers, not patients. Customizing the provider site flow © and customizing the care coordinator flow for patient (E) are not related to the care program enrollment flow.

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.

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.

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 [Intelligent Sales for Medical Devices Implementation Guide], to set up a warehouse that serves as a product fulfillment location to salesforce representatives in a specific region, irrespective of the account, a salesforce administrator should complete the following steps:

Create Inventory Location and add Visitor Address as Location Address. This step creates a record for the warehouse location and associates it with a visitor address.

Create Record in Product Fulfillment Location. This step defines the product fulfillment location for the inventory location and assigns it to a specific region.

Create a product item entry inventory, a single entry for each product that will be replenished from industry. This step adds the products that will be available in the warehouse location and specifies their quantity and expiration date. Setting up Product Transfer and Product Request are not required steps for setting up a warehouse location. Selecting inventory location while creating visit is not a step for setting up a warehouse location, but for creating a visit record.

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

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

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 Health Cloud Implementation Guide, the three steps that an administrator should take to ensure all tasks identify the role ‘Care Consultant’ are:

Update/Add the organization roles in the CarePlan_Role_Patient key:value pair in Health Cloud Setting. This step allows the administrator to define or modify the roles that are available for assigning tasks to patients.

Update the organization roles in the CarePlan_Role_Care_Coordinator key:value pair in Health Cloud Setting. This step allows the administrator to define or modify the roles that are available for assigning tasks to care coordinators.

Update the corresponding roles in the Assigned To picklist for the Care Plan Template Task object. This step allows the administrator to update the values in the picklist field that determines who is responsible for completing a task in a care plan template. Creating an ETL script to update the previously assigned To picklist values of Tasks created in the past is not a recommended step, as it can introduce errors and data loss. Updating the Care Plan Record Type custom metadata type to reflect the care coordination processes specific to the Care Coordinators is not a relevant step for changing the role name.

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

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

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.

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.

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

According to the Salesforce documentation, PurchasePlan is an object in Health Cloud that stores information about a plan purchased by an employer or an individual from a payer. PurchasePlan is to be used as a template for creating MemberPlan records for each member enrolled in the plan. MemberPlan is an object in Health Cloud that stores information about a member’s enrollment in a plan, such as effective date, termination date, coverage type, and benefits.