How to Pass Salesforce Health Cloud Accredited Professional Exam
1. About the Salesforce Health Cloud Accredited Professional Exam
The Salesforce Health Cloud Accredited Professional exam is intended for an individual who has broad knowledge of the Health Cloud platform and its capabilities, understands Health Cloud terminology, and can troubleshoot and solve basic platform issues.
 | Content | 60 multiple-choice/multiple-select questions |
 | Time allotted | 75 minutes |
 | Passing score | 65% (39 out of 60 questions) |
 | Exam Fee | USD 150 plus applicable taxes |
 | Retake Fee | USD 155 plus applicable taxes |
 | Prerequisite | None |
2. Exam Outline
| Topics | Weighting |
|---|---|
| Discovery 1. Given customer use cases, define the personas and stakeholders. 2. Given customer requirements, define the capabilities that need to be analyzed for a successful project. 3. Given a customer’s desired outcomes, gather functional and technical requirements to meet customer outcomes. | 11% |
| Design 1. Given customer requirements, determine how to create the solution for Health Cloud features according to best practices. 2. Given customer requirements, understand how to model patients, providers, healthcare facilities, etc., using the appropriate Health Cloud objects. 3. Given customer requirements, determine how to create the proper application solution design leveraging Health Cloud best practices. 4. Given customer requirements, determine when to use specific Health Cloud capabilities. 5. Given customer requirements, determine how to create the design solution for a specific Health Cloud vertical to meet those customer requirements. 6. Given the business processes/requirements for Health Cloud, determine how to create the solution design utilizing Health Cloud Industry best practices and Health Cloud modules. 7. Given information about a customer’s business objectives and goals for the program, define success metrics/key performance indicators (KPIs) and configure Salesforce to enable reporting on these metrics. 8. Given a customer’s security and compliance requirements, design and implement the appropriate organizational security and data access considerations. 9. Given information about a customer’s external systems and data requirements, determine the optimal integration strategy for the customer’s Salesforce org. 10. Given a customer’s business requirements, design the future state business processes. 11. Given a customer’s data requirements, create a data migration strategy considering the legacy and future state system landscape to ensure accuracy and referential integrity in data loads (intricacy of data load, order of operations). | 42% |
| Implement 1. Given a finalized design, determine how to install Health Cloud according to best practices. 2. Given a scenario, determine how to configure Health Cloud applications or solutions to meet customer needs. 3. Given a customer design, determine how to configure OmniStudio components for Health Cloud to meet customer requirements. 4. Given a customer design, determine how to customize Health Cloud to meet customer needs. 5. Given a scenario, determine when to use Salesforce Integration capabilities, including standard APIs, related to Health Cloud. 6. Given a scenario, determine how to configure security, sharing, and visibility rules to meet customer needs. 7. Given a list of success criteria, determine how to configure Salesforce to provide agreed-upon reports. | 42% |
| Deploy 1. Given a scenario, determine the pre-deployment steps for a specific use case. 2. Given a scenario, determine the post-deployment steps for a specific use case/capability within Health Cloud. 3. Given a use case, provision users with the right permission sets and permission set licenses to provide the right access to users. | 5% |
3. Salesforce Health Cloud Accredited Professional Exam Study Course
Accredited Professional Exam curriculum is available on Salesforce Partner Learning Camp. Please refer to Accredited Professional Partner Community Page for details.
4. Health Cloud Superbadge
5. Important Topics for Salesforce Health Cloud Accredited Professional Exam
- Social Determinants of Health Data Model
- Provider Data Model: Provider Network Management allows health insurance companies to bring providers into their network and helps members or patients find care that fits their needs. It provides objects for managing provider networks and contract payment agreement terms.
- Utilization Management Data Model: Utilization Management (UM) is a health insurance plan’s process of interfacing with plan members and contracted medical providers to interpret, administer, and explain the medical policies of the health plan. Health Cloud provides objects you can use to review and evaluate medical care services, communicate about clinical policies, and help health plan members ensure they receive the right care in the right setting at the right time.
- Intelligent Sales: Maximize productivity for your sales teams by giving them the tools required to efficiently plan and execute their surgical case visits and cycle counts. Give your teams valuable insight into field inventory and impacted revenue, with visits-based product availability projections. If someone has a product shortfall, they can request a product transfer from a nearby inventory. Reps can also blaze through cycle counts with fewer errors using their mobile devices.
- Intelligent Appointment Management: Health Cloud integrates with a customer’s appointment management system to provide a patient appointment booking experience in Salesforce for call center agents and care coordinators. The Health Cloud data model for appointments enables you to work with multiple source systems operating on different electronic health record platforms.
- Steps to Setup Health Cloud
- Step 1: Go to Account Settings and verify that the Contacts to Multiple Accounts option is enabled in your Salesforce org.
- It’s not possible to install the Health Cloud package without enabling the Shared Contacts feature.
- Step 2: Install the Health Cloud package.
- Install Managed Package
- Step 3: Set up your organzation.
- Set up My Domain (wait for the domain to register) and deploy to Users.
- Assign default record types, page layouts, and permission sets to your system administrator profile. And make sure you’re a Service Cloud User, so you can access the Health Cloud Console.
- Step 4: Configure Health Cloud profiles, permission sets, and roles.
- Get ready to manage the different Users who make up Health Cloud: Health Cloud admins, internal Salesforce Users, patients, care coordinators, and care community members.
- Step 5: Customize the Health Cloud console.
- Salesforce has given you the ability to edit the key components and attributes that you’ll need to make your instance of Health Cloud fit your company’s needs.
- Step 6: Migrate your patient data.
- Patient creation includes two processes: a job flow that creates the patients, and then a mapping group that maps data from the Candidate Patient object to other patient objects. The settings that control these processes are available for customization so that you can control how patient creating and data mapping occur in your org.
- Step 1: Go to Account Settings and verify that the Contacts to Multiple Accounts option is enabled in your Salesforce org.
- To be able to access Health Cloud, every user must have two Permission Set License (PSL).
- Health Cloud Permission Set License (PSL)
- Health Cloud Platform Permission Set License (PSL)
- Optionally, you can assign the Analytics Platform PSL if you plan to use CRM Analytics for Healthcare.
- The Lightning Console app for Health Cloud allows you to view multiple records and their related records on the same screen.
- To access and use a Lightning console app, users must have the Lightning Console User permission, and their profile must be added to the Lightning console app.
 |  |  |  |  |  |
- Care plans are practical, actionable steps to support the health of a patient. Care plans consist of problems, goals, tasks, and care teams.
- Problem: A problem is a clinical or nonclinical health issue identified as a priority for the patient. It can be a specific diagnosis identified by a care professional or a lab test.
- Goal: A health goal represents a targeted outcome to be achieved by the patient in order to overcome the problem. A patient can have more than one goal associated with a problem.
- Task: A task is the primary driver of a care plan. Tasks denote a measurable action toward a goal. They help track the progress of the activities associated with a problem.
- Care team: A care team is the support hub of a patient’s community. It consists of individuals and professionals who work together to improve the patient’s health.
- Care plan templates are standardized care plans with a list of actions tailored to a patient’s specific health needs.
- Care plan template are useful because:
- They standardize the workflow and ensure integrated care.
- They save time and minimize effort.
- They personalize the experience for the patient.
- They increase patient engagement, thus leading to stronger relationships with the patient.
- Care programs offer guidance and support for a patient to proactively manage their health.
- Health Cloud care programs help patients manage their health:
- By providing education around how to make the most of a medication.
- By sharing resources and providing training to ensure that medication is taken properly.
- By arranging follow-up procedures to monitor progress.
- By extending financial support and benefits investigation.
- By sending adherence reminders through connected devices.
- By conducting predictive analysis (through Einstein Analytics) to help detect adherence risks.
- Care Request Review Types
- Prior authorization is a way to review non-emergency hospitalizations, outpatient surgery, skilled nursing and rehabilitation services, home care services, and some medical equipment. It’s also referred to as prospective review, precertification, or preauthorization.
- Concurrent Review takes place while care is happening. It often takes the form of a decision on whether to continue a hospital stay. The focus of concurrent review is to ensure that the member is getting the right care in a timely and cost-effective way.
- Retrospective Review is conducted after the service has been completed. Emergency room care is often subject to retrospective review because there isn’t time for prior authorization review.
Types of Provider Relationship Cards: You can set up two types of provider relationship cards to see the association between provider organizations and practitioners.
| What | Where | Why |
|---|---|---|
| Provider cards for a facility | Account page | To see all the providers (contacts) that are associated with the account. |
| Relationship cards for a practitioner | Contact page | To see all the hospitals (accounts) that the practitioner is associated with. |
- CareProviderSearchableField object holds a variety of information from certain fields in the provider data model, ensures faster provider searches.
- HL7 (Health Level Seven) refers to a set of international standards for transfer of clinical and administrative data between software applications used by various healthcare providers.
- FHIR (Fast Healthcare Interoperability Resources) is a standard describing data formats and elements and an application programming interface for exchanging electronic health records.
- HL7 V2 is referred simply as HL7 is the most popular mechanism for accessing EHR data
- HL7 FHIR API referred simply as FHIR. Most significant release is the current one, FHIR R4. Health Cloud supports R4 as of Spring ’21 release
- Salesforce provides an HL7v2 ADT connector in Health Cloud
- Health Cloud supports data exchange with EHRs that have HL7 interfaces like CorePoint and Cloverleaf that work on top of EHRs.
- Health Cloud supports data exchange with FHIR enabled systems.
- The Health Cloud does not contains a native FHIR interface for integration
- Health Cloud needs to have data model to ingest FHIR data – which it has. With the FHIR-HC mappings published, Health Cloud can serve data as per FHIR specs using a middleware.
- Packages leveraging the Claims data model (part of Payer functionality) require Salesforce Connect Licenses
- The HL7 ADT Connector in Health Cloud is appropriate for less than 1,000 messages per hour.
 |  |  |  |  |
- Health Cloud Utilization Management helps payer organizations connect utilization management and care management.
- Providers can submit preauthorization requests to health insurance plans.
- UM clinicians at the payer organization can review, evaluate, and escalate requests.
- Medical directors can approve or deny requests.
- With Health Cloud utilization management, you can:
- Automate decisions based on medical policy, monitor service-level agreements (SLAs), improve decision making, and reduce manual intervention.
- Reduce costs by delivering more appropriate care to members.
- Transparently submit, process, review, and communicate authorizations by connecting providers, payers, and members.
- Achieve optimal patient outcomes and contain medical costs through comprehensive support.
- Improve the member experience and earn trust.
- Health Cloud Utilization Management Permission Set needs to be assigned to the users for them to use UM.
- The UM data model enables customers to streamline care requests. Agents, clinical professionals, and medical directors get guided workflows for UM processes, including:
- Drug requests
- Service requests
- Admissions
- Concurrent (continued stay) reviews
- Appeals
- Complaints and grievances
- Intelligent sales helps med tech sales teams ensure they’ve got the right products and the right reps at the right locations.
- Sales agreements assist businesses and sales reps by providing them with insights into products, prices, discounts, and quantities based on a contract made with a customer agreeing to a price or quantity of products over a certain time.
- Account forecasting in Health Cloud provides a clear picture of new and run-rate business based on orders, opportunities, sales agreements, contracts, and custom metrics.
- The surgical case management visit is an operationally oriented visit. It helps sales reps manage all aspects of the surgical case including inventory availability, ordering, billing, patient registration, provider education, and consent among others.
- How does Health Cloud intelligent sales for med tech help sales reps?
- It ensures that products are available for surgical cases.
- It allows sales reps to view surgical case visit details on the go from any device.
- It helps reps execute visits with predefined tasks and out-of-the box flows that can be customized for each business.
- It captures key notes and authorizes orders onsite (e-signature).
- The serial inventory support in Health Cloud provides capability to accept product transfers for serial tracked products, ensure that the stock is tracked at serial number level, and capture serial number details for order authorization.
- Steps to enable Intelligent Sales
- Assign the ActionPlans, Health Cloud Foundation, and Industries Visits permission sets to your users so that they can use Intelligent Sales.
 |  |  |  |  |
- Traditional Account-Contact model cannot be used to model Patients/Members in Health Cloud
- While the Individual Data Model continues to be supported by Health Cloud, the Person Account Model is the recommended Data Model for new implementations going forward
- Moving From Service Cloud to Health Cloud
- Step 1: How do you represent Patients or Members in your org today?
- As Person Accounts: Proceed to the next question!
- As traditional Contacts: Start evaluating how you’ll migrate these records to Person
- Accounts. (Found a blocker? Use the Individual model as your backup plan.)
- Step 2: Which parts of the Health Cloud data model you will leverage?
- Compare your current custom objects against Health Cloud objects. Consider level of effort, and migrate data to Health Cloud objects as required/appropriate.
- Step 3: Which parts of the Health Cloud User Interface you will leverage?
- Nearly all of Health Cloud is modularized, making it straightforward to add these components most anywhere in Salesforce.
- Step 1: How do you represent Patients or Members in your org today?
- Identifier records map provider, patient, facility, and asset records in Health Cloud to corresponding records in an external scheduling system, such as an electronic health record (EHR) system.
- Health Cloud Assessments use the power of Discovery Framework and OmniStudio to build more complex questionnaire paths. You can complete assessments in two different formats. A healthcare professional administers assessments such as screeners or questionnaires over the phone or in person. Send an email notification to a patient with a link to access assessments as a guest user on an Experience Cloud site. To enable Assessments, you must install OmniStudio, enable Discovery Framework, and update sharing settings.
- Centers for Medicare and Medicaid Services (CMS) risk scores:
- You can recalculate patient risk scores in Health Cloud with a batch Apex job using the
HcCMSRiskScoringScheduledJobclass. - You can either run the job manually as needed or schedule it. The patient risk scores are updated based on the recalculation results.
- Risk scores are recalculated for patient records that are affiliated with a care program and have the Recalculate flag set to
true. The flag resets totruewhenever a patient’s information changes.
- You can recalculate patient risk scores in Health Cloud with a batch Apex job using the
- Set Up Remote Monitoring in Health Cloud:
- Create code sets, units of measure, and care metric targets to set up remote monitoring.
- Enable care coordinators to remotely monitor health metrics by displaying care observations and remote monitoring charts on the patient’s account page.
- Provider Search:
- Provider Search helps your users find healthcare providers based on criteria such as location, specialty, and whether the provider is accepting new patients. You can even see the location of each provider right in Health Cloud.
- Provider Search uses data stored in various records, such as Contact, Account, Healthcare Provider, and Healthcare Practitioner Facility to name a few. However, some of this data isn’t searchable on its own.
- Provider Search includes automation that maps the source data to a searchable object called Care Provider Searchable Field. Automation keeps the data from the source records in sync so that your users always have the most recent information.
- Set Up Permissions for Utilization Management:
- Ensure system admins have these permission sets and permission set licenses:
- Health Cloud permission set license
- Health Cloud Platform permission set license
- OmniStudio Admin permission set
- OmniStudio User permission set
- RuleEngine Designer permission set
- RuleEngine Runtime permission set
- Assign these permission sets to your users:
- Health Cloud Foundation
- Health Cloud Utilization Management
- OmniStudio User permission set
- RuleEngine Runtime permission set
- Ensure system admins have these permission sets and permission set licenses:
- Display Information on the Patient Info Component: The Patient Info component, which is part of the patient or member information section of the Health Cloud Console, shows essential identification information about the person, including a thumbnail photo when one is available. This component isn’t customizable.
6. Additional Resources
Recommended Articles
