According to the Salesforce documentation2, Remote Patient Monitoring is a feature in Health Cloud that enables healthcare organizations to use the data generated by connected devices used by patients to monitor their health and provide personalized care. Remote Patient Monitoring allows healthcare organizations to:

Use a meaningful subset of the data generated by connected devices to drive patient engagement and intervention. Remote Patient Monitoring helps healthcare organizations filter and prioritize the device data based on predefined rules and thresholds, and trigger actions such as alerts, tasks, or messages when certain conditions are met2.

Use the data generated by connected devices used by patients to monitor their health. Remote Patient Monitoring helps healthcare organizations collect and store the device data in Health Cloud, and display it in various views such as charts, dashboards, or reports. This helps healthcare professionals gain insights into the patients’ health status, trends, and outcomes2.

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.

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.

According to the Health Cloud Implementation Guide, a Health Cloud administrator can change the default sub-tab when opening a record by going to setup, navigating to Custom Settings, and editing the Default Subtab setting. This setting allows you to specify which sub-tab should be displayed by default when opening a record in Health Cloud – Console. The other options are not relevant for changing the default sub-tab.

Shield is a Salesforce product that allows encryption of protected health information (PHI) data at rest to enhance Health Cloud2. Shield Platform Encryption encrypts sensitive data at rest without compromising critical platform functionality. It helps you address privacy policies, regulatory requirements, and contractual obligations for data protection2.

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.

To modify the out-of-the-box Advanced Patient Card to display the Category, SubjectID, and Date for active Clinical Alerts, a developer should take the following steps:

Create and activate a new child card: This step allows the developer to create a custom card that inherits the properties of the parent card and displays additional information from Clinical Alerts object4.

Create a DataRaptor to extract necessary data: This step allows the developer to create a DataRaptor Extract that queries the Clinical Alerts object and returns the Category, SubjectID, and Date fields for active records5.

Change the child card state to show active: This step allows the developer to change the state of the child card from inactive to active, so that it is visible on the Advanced Patient Card component6. Cloning the parent card, defining session variables, or creating an Integration Procedure are not required steps for this task.

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

According to the Salesforce documentation1, there are two ways to request a rep-to-rep transfer in Health Cloud:

When creating an order authorization for a visit, you can request a transfer from another rep’s inventory location by selecting the Transfer option in the Product Selection screen1.

To request a transfer from a specific inventory location, you can navigate to Products, select the product you want to transfer, and then click Request Transfer in the Related list1.

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.

 To migrate from the legacy Health Cloud EHR data model to the FHIR R4 clinical data model, a consultant needs to leverage the Health Cloud FHIR API and map objects and fields to the target objects. The Health Cloud FHIR API enables interoperability between Health Cloud and external systems that use FHIR standards. The mapping process ensures that the data is transformed and loaded into the correct objects and fields in Health Cloud. Using the Health Cloud Clinical Transition tool, using Data Loader to load the respective data, or creating an Apex class and leveraging Intelligent Appointment Management are not recommended steps for this migration2.

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

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 two best practice recommendations to upload information to support Provider Search and Provider Relationship Card are using Composite API Request and Data Loader. Composite API Request is a REST API resource that allows the administrator to execute multiple requests in a single call, which reduces the number of API calls and improves performance. Data Loader is a tool that allows the administrator to insert, update, delete, or export data from Salesforce objects in bulk.

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

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

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.

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.

Salesforce Shield is the encryption solution that supports the encryption of files in this scenario. Salesforce Shield provides platform encryption, which allows the administrator to encrypt files and attachments stored in Salesforce. Platform encryption supports full sandbox instances and complies with data protection regulations

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

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.

Reference and details below.

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

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 Salesforce documentation1, the Timeline View Configuration is a custom metadata type that defines the appearance and behavior of a timeline in Health Cloud. Each timeline has its own Timeline View Configuration record, which can be accessed and edited from the Health Cloud - Lightning Admin app2. One of the settings that can be changed in the Timeline View Configuration is the Orientation, which controls whether the timeline is displayed horizontally or vertically1. Therefore, to alter the appearance of the timeline so that it displays vertically instead of horizontally, the administrator should find the Timeline View Configuration for each relevant timeline in the Health Cloud - Lightning Admin app and change the Orientation to vertical.

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.

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.

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.

According to the Health Cloud Implementation Guide, Contact Tracing is a feature in Health Cloud that allows providers to perform contact tracing of their internal employees or their patients during an infectious disease outbreak or pandemic. Contact Tracing helps providers identify and monitor people who have been exposed to an infected person and provide them with guidance and resources. With the help of Contact Tracing, providers can perform the following three actions:

Perform contact tracing of their internal employees during an infectious disease outbreak or pandemic. This action allows providers to track and manage the health status of their employees who may have been exposed to an infection at work or in the community.

Perform contact tracing of their patients during an infectious disease outbreak or pandemic. This action allows providers to track and manage the health status of their patients who may have been exposed to an infection during a visit or in the community.

Track the location, duration, and number of participants in each contact encounter that the infected person was involved in. This action allows providers to collect and analyze data about the exposure risk and transmission patterns of an infection. Performing an audit of the Contact Record to keep track of the changes made to the Contact record by users is not an action that providers can take with the help of Contact Tracing. Tracking their patients as contacts by using Contact entity in Salesforce is not an action that providers can take with the help of Contact Tracing.

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

 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.

Salesforce Surveys is the best solution for moving existing PROMs surveys to Health Cloud. It allows for question banks and version control for this standardized survey.

A is correct because Remote Device Monitoring can help the MedTech company to manage its run rate business by enabling them to monitor the performance and usage of their devices remotely, and alert them of any issues or anomalies that may affect contract compliance.

B is incorrect because MedTech Accelerator is not a feature of Health Cloud, but a program that provides funding and mentorship for early-stage medical device and health technology companies.

C is incorrect because Advanced Account Forecasting is not a feature of Health Cloud, but a feature of Sales Cloud that helps sales teams to predict their revenue and quota attainment.

D is correct because Sales Agreements can help the MedTech company to manage its run rate business by allowing them to create contracts that commit the customer to buy products in a specific quantity or for a specific amount over time, and track the fulfillment and invoicing of those contracts.

References: : Remote Device Monitoring : Sales Agreements

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.

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.

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

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.

B is correct because Health Cloud Reports for Patient Referral Management is an unmanaged package that delivers a prebuilt dashboard and reports for analyzing patient referrals. The dashboard shows metrics such as referral volume, referral status, referral source, and referral outcome. The reports provide more details on each metric and allow users to filter by various criteria.

References: : Health Cloud Reports for Patient Referral Management

According to the Salesforce documentation1, the Health Cloud Provider data model is an optional data model that can be used to represent providers and their relationships in Health Cloud. It is not required for all Service Cloud to Health Cloud migrations, and it can coexist with the existing data model. The Custom Provider Search Lightning component is a custom component that can be used to search for providers using any data model, including the Health Cloud Provider data model or a custom provider data model. The Health Cloud Provider Search component is a standard component that can be used to search for providers using the Health Cloud Provider data model only. It can be extended or customized, but not replaced by a custom component1.

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

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.

To create Visit records for a Field Sales Agent using Intelligent Sales, the administrator must create Contacts, Locations, and Assets records for the agent. Contacts are the people that the agent visits or interacts with during their sales cycle. Locations are the places where the agent conducts their visits or activities. Assets are the products or devices that the agent sells or services during their visits. Opportunities and Accounts are not required for creating Visit records using Intelligent Sales.

Expression Set Templates are the prebuilt feature that the payer should leverage to implement predefined rules for its prior authorization request review process. Expression Set Templates are reusable sets of expressions that can be used to evaluate business logic and trigger actions based on the results.

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.

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

 FHIRR4 is the industry data standard that a consultant should use with Health Cloud. FHIRR4 stands for Fast Healthcare Interoperability Resources Release 4, and it is a standard for exchanging healthcare information electronically. FHIRR4 enables interoperability between different systems and applications, and supports a variety of use cases, such as clinical, administrative, and financial.

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

List of Patient/Member Conditions (B), Gender ©, and Date of Birth and Age (E) are three types of basic Patient or Member information that are displayed on the Patient info component. Primary Care Coordinator (A) and Thumbnail of Chatter Photo (D) are not displayed on the Patient info component.

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

To identify pain points and define project requirements for setting up a Contact Center leveraging Health Cloud, a consultant should work with the following group of people:

(Persona) Contact Center agent: This is the end user who interacts with patients through phone calls, emails, chats, or other channels. The Contact Center agent needs to have access to patient information, appointment scheduling, billing inquiries, plan updates, and other tasks in Health Cloud. The consultant should work with the Contact Center agent to understand their needs, challenges, and expectations from the system.

(Stakeholder) Salesforce administrator: This is the person who configures and maintains the Health Cloud system for the Contact Center. The Salesforce administrator needs to set up user profiles, permissions, page layouts, workflows, reports, dashboards, and other features in Health Cloud. The consultant should work with the Salesforce administrator to understand the technical requirements, limitations, and best practices for setting up the system.

(Stakeholder) Integration architect: This is the person who designs and implements the integration between Health Cloud and other external systems, such as EHRs, billing systems, or third-party applications. The integration architect needs to ensure that data is exchanged securely and accurately between Health Cloud and other systems. The consultant should work with the integration architect to understand the integration requirements, challenges, and solutions for the system. General physician, Marketing Cloud administrator, Care coordinator, Tableau developer or MuleSoft developer are not relevant people for this use case.

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.

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.

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

Health Cloud does not support native HL7 messages out of the box, so option A is incorrect. Option B is also incorrect, because Salesforce Connect is not designed to handle HL7 messages. Option C is possible, but it would require a lot of custom code and maintenance, and it is not recommended by Salesforce. Option D is the best option, because it uses an external HL7 broker/engine to convert the HL7 message into JSON, which can be easily consumed by Health Cloud using the standard REST API or the Health Cloud Data Loader12.

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.

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 .

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.

 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.