Master the Salesforce Health Cloud Accredited Professional (WI24) Health-Cloud-Accredited-Professional Exam with Confidence!

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.

The steps required to display a custom field from the HealthCondition object that categorizes High Risk Conditions on the Patient Card are:

• Create a custom formula field on the Custom HealthCondition object. This field can use logic to determine whether a health condition is high risk or not based on certain criteria.
• Add the newly created custom formula field on the Patient Card referencing the HealthCondition object. This can be done by creating or editing a patient card configuration record and adding the field API name in the Field Name column.

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.

• 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

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

Health Cloud Foundation

Assigns read access to additional Health Cloud platform capabilities, including the Provider Management data model.

TheHealth Cloud Provider Network Management permission set grants access to provider management objects so users can manage

credentialing and recruiting.

To use the Provider Network Management features of Health Cloud, assign both the Provider Network Management permission set and

the Health Cloud permission set to your users

 Users can access Provider Management standard objects by using Health Cloud, by assigning Health Cloud Platform Permission set licenses, and by assigning Health Cloud Foundation Permission set. Health Cloud is the industry-specific solution that includes Provider Management features such as provider search, provider network management, and provider credentialing3. Health Cloud Platform Permission set licenses grant access to the Health Cloud platform objects and features, including the Provider Management data model4. Health CloudFoundation Permission set assigns read access to additional Health Cloud platform capabilities, including the Provider Management data model5. Service Cloud is not required to access Provider Management standard objects, and the Provider Permission set is not a standard permission set in Health Cloud.

To get a patient’s allergy information from Bloomington Caregivers’ Health Cloud system, anexternal 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.

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 coordinationof 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 beeither 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 objectsthat 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.

To implement a robust appointment management system for a provider that uses an external system, a consultant should use a package created by ISV (Independent Software Vendor) for Health Cloud. This would allow the provider to leverageexisting solutions that are integrated with Health Cloud and offer features such as scheduling, reminders, cancellations, rescheduling, and confirmations. Using an EHR routing system, creating a custom FHIR Adapter, or creating an Apex class are not viable options for this requirement3.

The best way to conduct discovery to define a workflow for the call center users is to identify personas and ask them to walk through a day in their life, taking notes and identifying opportunities for optimization. This approach will help the consultant understandthe current state of the process, the pain points and challenges, the goals and expectations, and the potential solutions.