Configuring Provider Credentialing in Salesforce
When built on Salesforce, the provider credentialing use case creates a single source of truth across enrollment, contracting, credentialing, marketing, and sales.
Read Full Use Case
When built on Salesforce, the provider credentialing use case creates a single source of truth across enrollment, contracting, credentialing, marketing, and sales.
Read Full Use Case
Provider credentialing delays lead to revenue loss for hospitals daily, hindering the ability of valuable resources to attend to an increasing patient load. Traditionally, this process relies on manual coordination among staff services, HR, and physicians, prone to inefficiencies and delays that worsen the situation. Providers may also rely on credentials verification organizations (CVOs) to outsource the process, but these carry their own pitfalls, like long turn around times and added overhead.
In the face of healthcare staffing shortages, intense talent competition, and expanding patient populations, automation becomes essential for financial sustainability. That's where Salesforce comes in.
Quickly credentialing physicians to avoid revenue leakage in an environment rife with manual effort and staffing shortages
A scalable credentialing platform with digital physician applications, paperless workflows, and unified data
Significantly faster time-to-revenue from newly onboarded physicians and less manual work
There are a variety of requirements needed to solve the credentialing use case with Salesforce. At the highest level, credentialing platforms need to:
Additionally, we generally configure two basic permission sets in Salesforce to achieve this use case. They are:
Now, let's run through how we solve each requirement in Salesforce.
Penrod utilizes a third-party form component for gathering CAQH data and other pre-employment specifics crucial for jumpstarting the credentialing process. One of our top HIPAA-compliant form tools is Titan, known for its remarkably user-friendly form creation process, empowering us to link fields to any object or field within Salesforce.
Field mapping plays a pivotal role in ensuring data accessibility throughout the credentialing journey, typically encompassing details related to a provider's background, licenses, and education. With the exchange of sensitive information like social security numbers, email addresses, names, and physical addresses, the entire process is secured with a digital certificate for TLS/SSL encryption over an HTTP protocol. Other information we collect could include:
Clearly, forms can get complicated. The time-to-revenue clock starts when a provider begins filling out the application. Faster form completion means faster credentialing. As a result, it's important to implement time saving features that remove road blocks to prompt completion. Penrod expedites form submission by customizing URLs to auto-fill data from primary sourced data, like CAQH. We also prevent providers from losing progress and enabling them to pick up where they left off later on.
Declarative workflows kick in right after an application is sent. When we talk about declarative workflows, we're referring to processes tailored to a specific use case. This setup allows us the freedom to execute automations, set off alerts, and tweak processes in real-time.
This is where Salesforce excels, and why its customization makes it an ideal platform for the credentialing use case. We activate Salesforce workflows at various points during the credentialing process. Through the lightning interface, these points can trigger specific layouts, user alerts, tasks, and more to expedite the process. So, once an application is submitted, an applicant is generated under the lead object. This object houses all the necessary info a medical staff manager needs to evaluate applicants, validate their credentials, and kickstart contracting without manual data entry. The high level lightning flow includes stages for application submitted, verification, contracting, and credentialed.
The entire credentialing process involves accessing multiple data sources for verification. Manually checking each one leads to significant delays in the process. By consolidating them within the Salesforce interface under one dashboard, we offer an instantaneous view to the care manager specialist or whoever is verifying an application.
Here are some common data sources Penrod integrates into the care manager dashboard to solve this use case:
By uniting all these sources into a single credentialing platform, staff no longer need to switch between multiple sources to verify providers.
Eliminate delays caused by manual data entry
Eliminate gaps from verification to onboarding
Get physicians earning revenue faster