Bulk Claims Data Ingestion Into Data Cloud

Prerequisites:

1. To set up Data Cloud:

   • Log in to your Salesforce Data Cloud instance.
   • Go to Setup and click Data Cloud Setup.
   • Click Ingestion API, and then click New.
   • Name the ingestion API BCDA.
   • Click SAVE.
   • Upload the schema and save it.
   • Click App Launcher and select Data cloud.
   • Click Data Streams and click NEW.
   • Select the Ingestion API box and click Next.
   • Select the Ingestion API name from the dropdown (the source API name you created in the previous steps), and then select the object names and click Next.
   • For each object, select the appropriate category and primary key.
   • After all the objects and their fields are selected, click Next.
   • On the next page, verify the details, like the Data stream name and object, and then click Deploy.

   • To set up a connected app:

     • See Create a Connected App for Data Cloud Ingestion API.

     • Enable the Username-Password Flow in Setup > OAuth and OpenID Connect Settings > Allow OAuth Username-Password Flows > Enable.

     • Note: OAuth 2.0 JWT is not supported.

Setup:

• Log in to Salesforce and navigate to the Setup page.
• Search for the ‘Integrations Setup’ page.
• Select the Bulk Claims Data Ingestion Into Data Cloud application and click the Enable button.
• Enter the application display name, target business group, and environment for deployment, then click Next.
• Select Bulk Claims Data Ingestion Into Data Cloud tab and enter the following details to configure the application properties.

• Select the Generic FHIR Client tab and select the Authorization protocol as appropriate.
• Here’s an example of client credentials grant type with CMS sandbox for a generic FHIR client application:

• Click Proceed to deploy the application

Post-Deployment Steps:

• MuleSoft endpoints can be triggered as mentioned in the API documentation.

Troubleshooting

• If the application crashes and Bulk jobs are stuck in the “InProgress” state, abort the job by using the Abort functionality.

  • URL: https://{hostname}/{basePath}/job/{jobID}

    • Note: The base path for the URL is: /bcda-integration/v1/

  • Method: DELETE

• The BCDA app requires a minimum of 0.2 vCores and an additional 0.1 vCore for the Generic FHIR Client app.
• For large loads with EOBs more than 1 million records, the BCDA app requires a minimum of 1vCore and an additional 0.1 vCore for the Generic FHIR Client app.