Essential tips for a successful Salesforce health cloud implementation
Posted by Jaya on July 4th, 2022
The sheer amount of information and power available to those new to the platform, on the other hand, can be overwhelming. Don't be concerned! We can provide you with a comprehensive overview of the Salesforce Health Cloud.
You can even develop professional and personal healthcare networks with Salesforce Health Cloud so that everyone on the care team, including patients and caregivers, can take ownership of health goals. Overall, Salesforce Health Cloud allows you to easily manage your whole patient population, personalize every interaction, and enhance outcomes.
SP Tech suggests the following guidelines to any company considering a migration to Health Cloud:
Person Accounts should be enabled.
"Person Accounts are awful!" has been pounded into the skulls of nearly every Salesforce administrator. We see this on a regular basis in the many places we frequent, and generally agree. Person Accounts can add a lot of extra complexity to an organization, and once you enable them, you'll never be able to turn them off. Isn't it a little frightening?
Person Accounts, on the other hand, can be quite useful when used in the proper data model. They enable you to handle patients and members as both Contacts and Accounts, giving you a lot of freedom when it comes to building relationships with them. Is there a clinician on the patient's care team that works in two locations?
Whereas ordinary accounts and contacts would necessitate a bewildering amount of customization to show this, activating Person Accounts in Health Cloud allows you to not only use standard objects and fields for these relationships, but also to visualize them graphically.
Are members of the patient's family actively involved in their care? At this point, the Health Cloud admin and developer manuals do a fantastic job of addressing this setup phase, but just to reiterate: the Individual model should not be used for patients. Person Accounts should be enabled at the start of your development.
Health Cloud provides a variety of data models and features tailored to specific use cases in the healthcare business, such as pre-authorization of insurance claims, participation in life sciences programmes, patient specialty referrals, and more. It's doubtful that your company will require all of these features, and implementing them will clog up your database with hundreds of fields, objects, record kinds, metadata, and other items. Later on, getting rid of these becomes a nightmare.
Before you install, make a list of the features you want.
Every Salesforce administrator has been in this situation: your organization has purchased a new product, management is pressuring you to produce results quickly, and you've been provided an installation guide that reads like a novel. So, how do you go about it? You install all of the packages recommended in the guide, then go over them to see which ones your team wants to use.
Spend some time with your stakeholders to figure out their use cases and requirements. Then have a look at the different managed and unmanaged packages to see what features are offered. You may then figure out what has to be installed (in a sandbox, of course!). When in doubt, hold off on installing – it's always easier to add more features than it is to clean up a cluttered org!
Wherever possible, use standard components.
As previously said, Health Cloud's packages include a lot of value. A lot of the UX in Health Cloud is driven by sample flows, Apex triggers, custom metadata types, and other elements. Even if you read the admin guide from cover to cover, the purpose of each of these components will not be immediately evident until you've spent some time behind the hood. Fortunately, the Salesforce product team has spent a significant amount of time and effort ensuring that Health Cloud is compatible with and easily interfaces with popular healthcare workflows and systems. They are continually launching enhancements and devising innovative ways to reduce their clients' time to value.
Take into account your patient communication options Early!
Yes, Health Cloud complies with HIPAA regulations, at least when it comes to data in transit. But what if you need to send PHI to a patient or another provider who isn't part of your Salesforce organization?
First and foremost, ordinary email is not going to suffice. CMS has severe requirements for secure patient messaging that Outlook and Gmail aren't designed to meet. Will patients be required to submit attachments? Do you have any health questionnaires or consent documents on hand? Are you getting faxed referrals?
Although Health Cloud comes with numerous tools to help with some of these use cases, you may discover that a third-party solution is a better fit for your business based on your needs. Sending and receiving secure email can be made easier with tools like Zix or Paubox. Tools like Formstack or Form Assembly can help handle patient forms and consent, and eFax has a HIPAA-compliant fax product that can interface with Health Cloud. All of these tools have additional license charges and take time to obtain, so it's ideal to look into them early in the project discovery phase so that your implementation doesn't come to a standstill while you wait for vendor contracts to be finalized.
Like it? Share it!
About the AuthorJaya
Joined: June 27th, 2022
Articles Posted: 3
More by this author