Salesforce Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional Exam (SU24) Exam Practice Test

 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.

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.

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.

Reference and details below.

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

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.

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.

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]

Custom label (A), Patient Card ©, and Timeline (D) are components that are customizable within Health Cloud. EHR data (B) is not a component, but a type of data that can be integrated with Health Cloud. Life Events (E) is not a customizable component, but a standard object in Health Cloud.

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.

Claims data model leverages external objects to support the use case of integrating claims data from external systems into Health Cloud. External objects are similar to custom objects, except that they map to data that’s stored outside your Salesforce org1.

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

According to the Health Cloud Implementation Guide, the recommended best practice for modeling members in Health Cloud for a payer service cloud org that uses accounts and contacts to model health insurance members is to model them as person accounts, whether they are using Health Cloud capabilities or not. Person accounts are a type of account that combines account and contact information in a single record. They are suitable for representing individual consumers in healthcare and life sciences. Using person accounts for all members can simplify data management and avoid data duplication. Only groups needing Health Cloud capabilities need to use person accounts is not a recommended best practice, as it can create inconsistency and complexity in data modeling. Account record types for existing members can remain as-is is not a recommended best practice, as it can limit the functionality and integration of Health Cloud features. Using the individual model with Health Cloud is not a valid option, as the individual model is not supported by Health Cloud.

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.

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

To meet the requirements of the call center manager for identity verification, a consultant should do the following:

Add two new Identity Verification Process Field records for ‘Bloomington ID’; one with Field Type set to Result Field and one with Field Type set to Required Verifier: This step allows the consultant to add ‘Bloomington ID’ as a custom field on Account to the identity verification process. The Result Field record type makes the field appear in the search results, while the Required Verifier record type makes the field mandatory for verification purposes5.

Change the Birth Date record with Field Type value Required Verifier to Optional Verifier: This step allows the consultant to change the status of Birth Date from a required field to an optional field for verification purposes. The Optional Verifier record type makes the field appear in the verification screen, but does not require a match for verification6. Adding ‘Bloomington ID’ to the picklist choices within the Identity Verification flow, removing Birth Date from the required fields picklist, adding Birth Date to the optional verifiers picklist, deleting Birth Date record, or adding new record to Lightning component parameters are not valid steps for this task.

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.

D is correct because Patient Provider Relationship is the standard object in Health Cloud that is used to track patient relationships to healthcare practitioners, such as cardiologist, primary care physician, and oncologist. Patient Provider Relationship represents the association between a patient and a healthcare practitioner who provides care for the patient. This object can store information such as the practitioner’s specialty, role, contact details, and relationship status.

References: : Patient Provider Relationship : Healthcare Practitioner Data Model

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

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

Utilization Management is the capability in Health Cloud that helps the payer accomplish its goal of balancing quality care and managing the cost of care effectively. It enables the payer to streamline its approval processes for care requests using predefined rules and workflows.

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.

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.

According to the Health Cloud Data Model Developer Guide, two ways that a data architect can ensure PHI/PII data visibility is minimized during the migration of patient data from an existing Service Cloud org to a new Health Cloud org are:

Use Salesforce Data Masking when moving data to a sandbox. Data Masking is a tool that helps you protect sensitive data in sandboxes by masking it with anonymized values.

Use Data Templates to exclude PHI/PII data from being added to partial copy sandboxes. Data Templates are files that specify which objects and fields to include or exclude when creating a partial copy sandbox. Exporting data to a spreadsheet to remove PHI before importing it into a sandbox is not a recommended way, as it can introduce errors and security risks. Ensuring sandboxes have Platform Shield enabled is not a valid way, as Platform Shield is not a feature of sandboxes. Platform Shield is a product that allows encryption of data at rest in production orgs.

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.

According to the Health Cloud Implementation Guide, Program Enrollee Settings is the place within Health Cloud Settings where a Health Cloud administrator can make changes to accomplish the requirement of enabling the members to enroll in and out of Care Program multiple times. Program Enrollee Settings allow the administrator to configure how members can be enrolled in or removed from care programs, such as allowing multiple enrollments, setting enrollment statuses, and defining enrollment criteria. Care Program Settings, Health Cloud Settings, and Care Request Settings are not places where the administrator can make changes to enable multiple enrollments.

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.

 To display device information on a patient card, an administrator can create an Asset record and create a Care Registered Device record that looks up to the Asset record and then looks up to the Account record for the Patient. Asset records represent devices that are owned by patients or members. Care Registered Device records link assets to patients or members and store information such as device type, status, serial number, and manufacturer5. Creating custom fields on other objects such as EHR_Patient, EHR_DeviceRequest, FilterCondition_c, or EHR_MedicalDevices will not display device information on a patient card.

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

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

According to the Salesforce documentation1, consent documents are files that capture the enrollee’s consent to participate in a care program. Consent documents can be uploaded as PDF, DOC, DOCX, or JPG files in secure folders of Health Cloud for a care program. The file size limit for consent documents is 2 MB1. Therefore, options C and D are correct. Option A is incorrect, because copy-protected PDF files cannot be uploaded as consent documents. Option B is incorrect, because opt out consent documents are not used to enroll in a care program, but to withdraw from it. Option E is incorrect, because password protected files cannot be uploaded as consent documents.

To migrate from the individual model to person accounts, you need to do the following steps:

Enable person accounts on your org.

Configure your person account record type in the Individual Record Type Migration custom setting.

Use a CSV file and map PersonRecordTypeId to the person account record type.

To enable care providers to conduct video visits with patients and capture socioeconomic factors that impact their care, a consultant should recommend the Telehealth capability in Health Cloud. Telehealth allows care providers to connect with patients through video calls, chat messages, and surveys within Health Cloud. Telehealth also enables care providers to collect and analyze social determinants of health (SDOH) data from patients using assessments and surveys3. Telehealth helps improve patient engagement, satisfaction, and outcomes by providing convenient and personalized care. Integrated Care Management, Intelligent Appointment Management, or Virtual Care are not capabilities that can fulfill this use case.

The feature that the consultant should configure to leverage dependent intervention tasks as part of their care coordination solution using Integrated Care Management is Action Plan Templates. Action Plan Templates are reusable sets of tasks that can be assigned to patients or members based on their care needs. Action Plan Templates can include dependent tasks that are triggered by the completion of other tasks.

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

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

 To use the Enhanced Timeline functionality, a consultant needs to create a new Timeline View Configuration record and specify the object, fields, and filters for the timeline view. This allows the customer to view a patient’s health conditions and clinical encounters as a sequence on the patient’s Person Account page. Cloning the HCTimeline FlexCard, adding a record to the HealthCloudTimelineConfig custom setting, or creating a new Timeline record within Setup are not required for this functionality1.

B is correct because if a user cannot access a field used in a filter on a patient or member list, they will not be able to see the list. This is because the filter criteria are applied to the user’s query, and if the user does not have permission to view the field, the query will return no results. To avoid this issue, the administrator should ensure that the user has the appropriate field-level security settings for the fields used in the filter.

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

According to the Salesforce documentation2, the following standard objects are used in the workflow to manage utilization data:

Care Request Plan: A care request plan is an object that stores information about the plan of care for a member. It includes details such as the diagnosis, the service type, the start and end dates, and the status of the plan2.

Care Authorization: A care authorization is an object that stores information about the approval or denial of a service or payment by a payer. It includes details such as the authorization number, the decision date, the decision reason, and the status of the authorization2.

Care Request: A care request is an object that stores information about the request for a service or payment by a provider or a member. It includes details such as the request type, the request date, the priority, and the status of the request2.

The two integration patterns that a consultant should recommend to share patient medication information with an external pharmacy are Platform Event and Apex HTTP Callout. Platform Event allows Bloomington Caregivers to publish events when medication records are updated in Health Cloud, and the external pharmacy can subscribe to those events and receive notifications in near real time. Apex HTTP Callout allows the external pharmacy to send an HTTP request to Health Cloud with the medication interaction information, and Health Cloud can process the response and display it to the users.

To leverage Utilization Management features in Health Cloud, users need to have Health Cloud Permission Set License, Health Cloud Utilization Management Permission Set, and Health Cloud Foundation Permission Set. Health Cloud Permission Set License grants access to the Health Cloud platform objects and features. Health Cloud Utilization Management Permission Set grants access to utilization management objects so users can manage care requests and reviews. Health Cloud Foundation Permission Set assigns read access to additional Health Cloud platform capabilities4. Health Cloud Analytics Permission Set and Health Cloud Platform Permission Set License are not required for Utilization Management.

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 two capabilities that a consultant should customize to implement Utilization Management in Health Cloud and submit and track prior authorizations are creating a new Support Process to match the customer’s process steps and customizing the Service Request object. A Support Process defines the picklist values available for the Status field on a Service Request record, which represents a prior authorization request. The consultant can create a new Support Process to match the customer’s process steps, such as Submitted, Approved, Denied, or Pending. The Service Request object stores information about the prior authorization request, such as the patient, the provider, the service type, and the outcome. The consultant can customize this object by adding or removing fields, creating validation rules, or defining page layouts.

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 three steps that are required as part of the setup of Virtual Care in Health Cloud are setting up and configuring Salesforce Scheduler, assigning Health Cloud Video Calls permission set, and installing the Virtual Care unmanaged package. Salesforce Scheduler allows Bloomington Caregivers to schedule video appointments with patients or members. Health Cloud Video Calls permission set allows users to access the video call features in Health Cloud. Virtual Care unmanaged package provides out-of-the-box components and flows for enabling video calls in Health Cloud.

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

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

According to the [Health Cloud Integration and Interoperability Guide], the new clinical data model in Health Cloud is aligned with FHIR R4 standards, which is the latest version of the FHIR specification. Health Cloud supports data exchange with both HL7 and FHIR enabled systems, using different methods such as MuleSoft connectors, Salesforce APIs, or third-party integrations. Most EHR data exchange today is still done via legacy HL7 v2 – simple application interface, which is a widely adopted standard for exchanging clinical and administrative data. Health Cloud does not have a FHIR server, but it can connect to external FHIR servers using APIs or MuleSoft connectors. The new clinical data model in Health Cloud is not aligned with HL7 v2-simple application standard, which is a different standard from FHIR.

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.

To help the payer organization electronically receive requests for services from Bloomington Caregivers, a consultant should recommend the following business level APIs:

Prior Authorization API: This API allows Bloomington Caregivers to create requests for prior authorization for services that require approval from the payer organization. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests9.

Care Services API: This API allows Bloomington Caregivers to create requests for care services that are covered by the payer organization’s benefit plans. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests10.

Referral Request API: This API allows Bloomington Caregivers to create requests for referrals to other providers that are part of the payer organization’s network. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests11. Admission, Discharge, and Transfer (ADT) API or Benefit Verification API are not business level APIs that can fulfill this requirement.

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

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.

Advanced Therapy Management assists the healthcare organization with its complex scheduling requirements by allowing them to reschedule part of the appointment chain and book multi-step appointments. Rescheduling part of the appointment chain enables the organization to adjust the dates and times of individual appointments within a chain without affecting the rest of the chain. Booking multi-step appointments enables the organization to create a series of related appointments that follow a predefined sequence and duration.

 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.

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

Reference and details below.

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

According to the Salesforce documentation3, to leverage the health cloud utilization management capabilities, you need to install the health cloud managed package and the health cloud care request extensions managed package. 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 care request extensions managed package contains additional objects, fields, tabs, apps, components, and more that are specific to utilization management3.

Reference and details below.

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.

 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.