Get Ready for Multifactor Authentication
Multifactor authentication will be required for all users starting February 1st, 2022. This requirement adds an additional layer of security that ensures only valid users have access to sensitive information, like PHI or other data that is regulated by HIPAA. Fortunately, it’s a painless workflow for most users and does not impact their productivity. Users access their Salesforce environment in the same way as before, with one minor difference. Upon logging in, they’ll receive a notification through the Salesforce Authenticator App on their mobile device. By confirming that they attempted to log in, they’ll be credentialed and allowed access.
Provide More Personalized User Experiences with Data Prototyping…but think about HIPAA
Einstein services will be given the ability to find patterns in the ways your users search within your Salesforce environment. As a result, Einstein can adapt and personalize the content they see, allowing them to work smarter. The Einstein Data Prototyping program is currently a pilot, so it will require an administrator’s consent. Pay attention to which apps and data are accessible to be prototyped, as it may impact Salesforce HIPAA compliance.
Support Larger and more Diverse Populations in Your Patient or Member Portals
Customer community licenses now allow six times as many members. This means that insurance companies and healthcare providers can support growing healthcare populations without worrying about exceeding user thresholds.
Additionally, the new Build Your Own (LWR) templates allow you to deliver content to patients in up to 20 languages. This means that your portal can be translated into any language that Experience Cloud supports.
Be Aware of new Health Cloud Features
New security measures that verify patient identity make Health Cloud more secure than ever. For example, when a patient or member discussion will involve PHI, agents are able to verify by asking for an address, date of birth, or other personal identifiers.
Retiring the Candidate Patient Object
Users will no longer be able to create new records as a “candidate patient.” Salesforce recommends that the lead object be used in its place. In cases where a candidate is not supported by the lead object, a custom field can be used instead.
Users now have more visibility into the inventory levels of disposables, parts, and more by using the “Cycle count” feature. This can significantly reduce the write-off costs caused by inventory discrepancies, allowing reps to identify low inventory before it impacts customers. Cycle Count can be used in the browser or via the mobile app, allowing even remote field agents clear access to inventory levels.
Better Prescription Management
An enhanced patient medication management lighting component improves care transitions by ensuring that care coordinators have access to a detailed report of a patient’s medication history. This enables providers to avoid dangerous drug interactions, identify potential gaps, and reduce the chance of medicinal errors.
Seamless Contracting Workflows
Provider Network Management in Salesforce Health Cloud now allows more robust contracting support. This enables your users to thoroughly manage payment agreements, create custom payment types, manage network participation records, and enable site users’ access.
New and Updated Objects
There are a variety of changes to the object model. Salesforce provides a comprehensive list of these updates here.
We’re incredibly excited about the new features in the Spring ’22 release. Do you have questions about how any of the updates will affect your organization? We’d love to hear from you!