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

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 documentation, Patient Immunization is an object in Health Cloud that is used to store the details of a vaccine being administered. It includes information such as the vaccine name, lot number, manufacturer, route of administration, site of administration, dose quantity, dose unit, expiration date, and adverse reaction.

 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.

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.

Reference and details below.

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.

To implement Home Health scheduling with Health Cloud, a consultant should assign Healthcare Visit Manager permission set license to users who need to schedule visits. This permission set license grants users access to objects and fields related to home health visits, such as Service Appointment, Service Resource, Service Territory, Service Report Template, etc7. This permission set license also enables users to use Salesforce Scheduler for Health Cloud feature, which allows users to schedule home health visits based on various criteria, such as availability, location, skills, etc8. Field Dispatch Scheduler, Manage Home Health, or Execute Health Scheduling are not permission set licenses that can fulfill this scenario.

 Health Cloud Consent Management provides features such as email for signature and e-signature. Email for signature allows users to send consent documents to participants via email and track their status. E-signature allows participants to electronically sign consent documents using a third-party service such as DocuSign1. Capture Data Use Purpose, Delegated Signing, and Capture IP Address during completion are not features of Health Cloud Consent Management.

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

According to the Health Cloud Implementation Guide, Lead is the object that is leveraged to track patient referrals. Lead is a standard object that represents a potential customer or patient who has expressed interest in a product or service. Leads can be converted into person accounts or contacts when they are qualified. Care Request, Care Program Enrollee, and Cases are not objects that are used to track patient referrals.

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.

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

According to the Salesforce documentation2, Health Cloud uses Business APIs that should be used instead of object level APIs when creating records in Health Cloud objects. Business APIs are custom REST APIs that perform complex business logic and validations on Health Cloud objects. Object level APIs are standard REST or SOAP APIs that perform CRUD operations on individual objects. Business APIs ensure data integrity and consistency across Health Cloud objects, while object level APIs may result in data errors or inconsistencies2.

B is correct because enabling person accounts from Setup is a prerequisite to install the Health Cloud managed package. Person accounts are a special type of account that combines the attributes of an account and a contact. 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.

C is correct because enabling Chatter settings from Setup is a prerequisite to install the Health Cloud managed package. Chatter is a collaboration tool that allows users to communicate and share information with each other. Health Cloud uses Chatter to enable features such as care team collaboration, patient engagement, and social determinants of health.

D is correct because enabling contacts to relate to multiple accounts is a prerequisite to install the Health Cloud managed package. This feature allows users to create relationships between a contact and multiple accounts, and specify the role and status of each relationship. Health Cloud uses this feature to enable features such as actionable relationship center, patient provider relationship, and referral management.

A is incorrect because making data protection details available in records is not a prerequisite to install the Health Cloud managed package, but an optional step that can be done after the installation. Data protection details for records allow users to view and edit the data protection level and data classification for each record on leads, contacts, and person accounts.

E is incorrect because logging a support case to have person accounts enabled is not a prerequisite to install the Health Cloud managed package, but an alternative way to enable person accounts if they are not available in Setup. However, this method requires contacting Salesforce Customer Support and waiting for their response, which may take longer than enabling person accounts from Setup.

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 admin must configure all Lead field mappings including Medical Record Number, Source System and Source System ID (A), some Lead field mappings including Medical Record Number, Source System ID can be handled automatically by HC ©, and duplicate checks on Medical Record Number, Source System and Source System ID can be handled automatically by HC (E) are true statements about the steps the admin can take. The custom Convert to Patient button should be added to the Lead detail page, not the list view (B). The Lead to Individual Conversion apex class will not create a new Opportunity for the patient (D).

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

 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.

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.

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.

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.

According to the Salesforce website, The Social Determinants feature in Health Cloud helps providers perform the following activities:

Integrate services such as transportation and meal delivery into their patient care plans and programs. The Social Determinants feature allows providers to connect patients with community resources that can help them overcome nonclinical barriers to care, such as lack of transportation, food insecurity, or social isolation.

Track determinants and barriers to care across their patient populations. The Social Determinants feature allows providers to collect and analyze data on various social factors that affect patients’ health outcomes, such as income, education, housing, or environment.

Plan interventions to help address the barriers to care within their patient populations. The Social Determinants feature allows providers to create and manage action plans that target specific social needs of patients and measure their impact on health indicators.

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.

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

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

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

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

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.

Goal © and Problem (D) are optional fields when creating a new Care plan task. Status (A) and Task Owner (E) are required fields when creating a new Care plan task. Due Date (B) is not a field on Care plan task, but rather on Task object.

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.

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

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.

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.

The design considerations that the administrator has to be aware of when creating the application for utilization management are:

Each care request has to have an associated case. A case is the standard Salesforce object that represents a care request in Health Cloud4.

New care requests can be created using the ‘Create Care Request’ component. This component allows users to create a new care request from any page in the Health Cloud console5.

Path can be used to visually represent the status of a care request. Path is a standard Salesforce feature that displays the stages of a process, such as a care request, and guides users along the steps in Salesforce Lightning Experience6.

Care request functionality is not included in the Health Cloud managed package. It requires installing the Utilization Management unmanaged package for Health Cloud and assigning the Health Cloud Utilization Management permission set to users along with Health Cloud permission set licenses.

Care requests do not have empower components that can be exposed within Communities. Empower components are custom Lightning components that allow patients or members to view and manage their health information in Communities. Care requests are not part of the empower components.

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

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

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.

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.

Reference and details below.

The three features in Health Cloud that the consultant should recommend to the health plan provider are Business Rules Engine, Utilization Management data model, and Out-of-the-box Process libraries. These features enable the provider to manage prior authorizations with predefined approval criteria, store and track care requests, and leverage best practices and templates for common scenarios .

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

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

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

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.

Concurrent review is a type of care request review that ensures that a member is getting the right care in a timely and cost-effective way. It involves reviewing the medical necessity and appropriateness of an ongoing service or admission3. Disposition review, care review, preauthorization review, and retrospective review are not the correct terms for this type of review.

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.

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

 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.

Reference and details below.

According to the Salesforce documentation3, the following Salesforce and Health Cloud objects can be used to represent providers and their relationships in a provider management data model:

Contact: A contact is a standard object in Salesforce that stores information about an individual person, such as name, phone, email, address, etc. A contact can be used to represent a provider who is a person, such as a physician, nurse, or therapist3.

Healthcare Practitioner Facility: A healthcare practitioner facility is a custom object in Health Cloud that stores information about the relationship between a provider and a facility where they practice, such as hospital, clinic, or pharmacy. A healthcare practitioner facility can be used to track each of the different locations where a provider practices3.

Healthcare Provider: A healthcare provider is a custom object in Health Cloud that stores information about a provider who is an organization or a group of providers, such as hospital system, clinic network, or physician group3.

According to the Health Cloud Implementation Guide, two statements that are true about Care Teams are:

Care Team Members are optional on a Care Plan. This statement is true because a care plan can be created without any care team members assigned to it. However, adding care team members can help with collaboration and coordination of care.

A Care Plan must have a Coordinator as a member of the Care Team before a Care Plan Template can be applied. This statement is true because a coordinator is required to manage the tasks and goals of a care plan template. A coordinator can be either an internal or external user who has access to Health Cloud. If the Problem and Goal objects use Private Sharing, Care Team Membership provides access to these objects is not a true statement, as care team membership does not grant access to objects that use private sharing. Communities must be enabled before External Care Team members can be added is not a true statement, as external care team members can be added without enabling communities.

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

Medication Review and Medication Reconciliation are two Health Cloud solutions that can help a company based in the United States to track medications that patients take in a standardized format and detect potential drug-to-drug interactions.

Medication Review is a Health Cloud feature that allows users to capture standardized information related to medication, such as drug name, dosage, frequency, route, and indication1. Users can also add notes and recommendations for each medication, and view the medication history of a patient1. Medication Review supports the RxNorm standard, which is a normalized naming system for generic and branded drugs in the US2.

Medication Reconciliation is a Health Cloud feature that allows users to efficiently manage and reconcile a patient’s medications list using the Patient Medication Manager lightning component3. Users can easily review the patient’s medication information, identify errors and adverse drug interactions, and add recommendations and notes, all from one place3. Medication Reconciliation also supports the RxNorm standard, and uses the National Library of Medicine API to check for drug-to-drug interactions4.

References:

1: Medication Management and Medication Review - Salesforce

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 Data Model Developer Guide, Insurance Benefit, MemberPlan, and Insurance Coverage are three standard objects available for Insurance Management. Insurance Benefit represents a specific benefit or service covered by an insurance plan. MemberPlan represents an insurance plan that a member is enrolled in. Insurance Coverage represents an insurance policy that covers one or more members. PurchaserPlan and Coverage Benefit are not standard objects available for Insurance Management.

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.

B is correct because integrating using the FHIR Clinical API is the appropriate method for Bedrock to access the information leveraging Health Cloud functionality. The FHIR Clinical API is a RESTful API that allows external systems to access and exchange clinical data stored in Health Cloud, such as AllergyIntolerance, Condition, MedicationOrder, and Procedure. The FHIR Clinical API uses the FHIR standard, which is a widely adopted interoperability standard for healthcare data.

References: : FHIR Clinical API : FHIR Overview

Reference and details below.

Graphical user interface, text, application Description automatically generated

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.

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

Health Cloud does not have a built-in HL7 integration engine, so option A is incorrect. Option B is also incorrect, because Health Cloud does not have prebuilt connections for any EMRs. Option C is incorrect, because there is no such lightning component button automatically configured to export to EMR. Option D is correct, because Health Cloud provides data mappings from commonly used HL7 messages (such as ADT, ORU, and RDE) to the Health Cloud data model, which can help developers and integrators map the data from external systems to Health Cloud objects and fields12.