Pre-requisites
To use this integration:
The clearinghouse or payer system must be FHIR compatible and must support Rtpbc Claim request and response endpoints.
The clearinghouse or payer system must have the appropriate OAuth 2.0 protocol support for authentication and authorization.
You must understand the FHIR server’s connection policies.
Connect to the clearinghouse or payer system and generate the credentials before enabling the integration. Follow the specific clearinghouse or payer system’s instructions to understand their OAuth 2.0 protocol support and steps to generate the client credentials.
Set up a Salesforce Life Sciences or Health Cloud Local External Client App for this application to integrate with Salesforce Life Sciences or Health Cloud.
Use the credentials during setup of the Integration from Life Sciences or Health Cloud MuleSoft Direct setup.
Setup
- Log in to Salesforce and navigate to the Setup page.
- Search for the ‘Integrations Setup’ page.
- Select the PSP Benefits Verification application and click Enable.
- Enter the application display name, target business group, and environment for deployment, then click Next.
- Select the
Benefits Verification tab and enter ‌these details to configure the application properties:
| Key name | Sample value | Description |
|---|
| 1 | Salesforce Life Sciences Instance URL | https://test-instance.salesforce.com | Salesforce Life Sciences instance URL |
| 2 | Salesforce Life Sciences Token URL | https://login.salesforce.com/services/oauth2/token | URL for generating the Salesforce access token |
| 3 | Salesforce Life Sciences Consumer Key | - | Client ID to use for generating a Salesforce access token |
| 4 | Salesforce Life Sciences Consumer Secret | - | Client Secret to use for generating a Salesforce access token |
| 5 | Pharmacy Benefits Verification Request Path | /submitPBMClaim | Pharmacy Benefit Verification endpoint URL of the clearinghouse or payer system |
- To add any optional configuration, click Add Additional Parameters and enter the required details.
- Select the
Generic FHIR Client tab and select the Authorization protocol. - Here’s an example of client credentials grant type with a clearinghouse or payer system for a generic FHIR client application:
- Click Proceed to deploy the application
Post Deployment
Customizations
- This application supports CareLimitTypes, including CoPay, CoInsurance, Deductibles_Applied, and Total. To add mapping to any additional care limit types, add the appropriate mapping in the adapter code.
- The currency symbol supported by the application is dollar ($) for USD. You can add more currency symbols in the code to support this.