Bulk Claims Data Ingestion Into Data Cloud
Setup
Prerequisites:
- 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.
- Follow this link for setting up a connected app.
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 Cloudtab and enter the following details to configure the application properties.
| Key name | Sample value | Description | |
|---|---|---|---|
| 1 | Client ID for Data Cloud instance | - | Client ID for Data Cloud instance. |
| 2 | Client secret for Data Cloud instance | - | Client secret for Data Cloud instance. |
| 3 | Username for Data Cloud instance | - | Username for Data Cloud instance. |
| 4 | Password for Data Cloud instance | - | Password for Data Cloud instance. |
| 5 | Data Cloud instance Url | https://test-instance.salesforce.com | Data Cloud instance URL. |
| 6 | Data Cloud source API name | BCDA | Source API Name for Data Cloud Objects. |
- Select the
Generic FHIR Clienttab 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:
| Key name | Sample value | Description | |
|---|---|---|---|
| 1 | Base URL | https://sandbox.bcda.cms.gov/api/v2 | Base URL of the end system. |
| 2 | Token URL | https://sandbox.bcda.cms.gov/auth/token | Token URL of the end system. |
| 3 | Client ID | - | Client ID for the end system. |
| 4 | Client Secret | - | Client Secret for the end system. |
- 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}
- 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.