Infinitus API - Implementation Template

Prerequisites

Before implementing this integration, please ensure the following requirements are met.

Authentication and Access

• Valid API credentials (API key) from your Infinitus organization
• Configured webhooks in your Infinitus organization's settings

System Requirements

• FHIR-compatible system that supports:

  • RTPBC (Real-Time Pharmacy Benefit Check) Claim bundle requests
  • RTPBC Claim response endpoints
  • CoverageEligibility requests and responses

• For Salesforce PSP Benefits Verification integration: Understanding and proper configuration of Salesforce PSP Benefits Verification system

• For Agentforce for Eligibility and Benefits Verification: Understanding and proper configuration of Agentforce for Contact Center (https://help.salesforce.com/s/articleView?id=ind.hc_admin_contact_center_agent_topic_eligibility_and_benefit_verf.htm&type=5)

Implementation Steps

1. API Manager Integration

   • If you are using MuleSoft API Manager, you must first set up your API in API Manager before deploying the Mule application.
   • Follow these guides to create an API and obtain the Auto Discovery ID:
     • Set up an API in API Manager
     • Create and Apply API Policies
   • After creating the API, obtain the Auto Discovery ID from API Manager.
   • You will also need to add your anypoint.platform.client_id and anypoint.platform.client_secret to your Mule App's Runtime Properties. To generate these:
     • How to create Connected Apps and get Client ID/Secret
   • If you are not using MuleSoft API Manager, remove the API Autodiscovery global-configuration from global.xml.

2. Consume the MuleSoft Template Application

   • Download the Infinitus MuleSoft template application from the provided repository or distribution source.
   • Import the project into Anypoint Studio.
   • Update the implementation or add required properties in the property files as needed.
   • Build the project in Anypoint Studio to generate the deployable JAR file for your environment.

3. Deploy Infinitus Mule Application

   • Deploy the built Infinitus Mule application JAR to your Mule runtime environment.

   • Configure the following mandatory environment variables and properties:

     • programId: Specifies the target program within your Infinitus organization. If not set, the default program will be used.
     • infinitus.apiKey: The Infinitus API key obtained from your Infinitus Customer Portal.
     • sfdcMulesoft.app.host: The Salesforce host URL (e.g., https://your-salesforce-instance.salesforce.com).
     • secure::sfdcMulesoft.app.username: The Salesforce username for integration (e.g., integration.user@yourdomain.com).
     • secure::sfdcMulesoft.app.password: The Salesforce password (and security token, if required) for the integration user.
     • env: Specifies the deployment environment. Supported values: dev, qa, prod. Please consult your deployment documentation or environment administrator to determine the correct value.
     • secure.key: Used for encrypting/decrypting secure properties. This property is referenced in secure property files such as secure.properties or secure.<env>.properties. These files should be placed in the src/main/resources directory. For more details, see MuleSoft Secure Properties documentation.

   • Sample property values:

     programId=default
     infinitus.apiKey=YOUR_API_KEY
     sfdcMulesoft.app.host=https://your-salesforce-instance.salesforce.com
     secure::sfdcMulesoft.app.username=integration.user@yourdomain.com
     secure::sfdcMulesoft.app.password=YOUR_PASSWORD_AND_TOKEN
     env=dev
     secure.key=YOUR_SECURE_KEY

4. Configure Infinitus Webhook

   • Access the Infinitus Customer Portal.
   • Navigate to Settings → API Keys → Webhooks.
   • To form the webhook URL, append /api/getTaskResults to your Infinitus Mule application deployment URL. For example: https://your-mule-app-url.com/api/getTaskResults
   • When configuring the webhook, you will be prompted to provide credentials. Use the same Salesforce integration username and password configured in your Mule application (secure::sfdcMulesoft.app.username and secure::sfdcMulesoft.app.password).