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.
To set up a connected app:
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 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 | Data Cloud instance Url | https://test-instance.salesforce.com | Data Cloud instance URL. |
| 4 | 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}
- Note: The base path for the URL is:
/bcda-integration/v1/
- Note: The base path for the URL is:
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.
Note: This application connects to the FHIR System Integration in Real Time Using Generic FHIR Client (GFC) and checks the GFC's TLS certificate by default. If your GFC uses its bundled self-signed certificate, the connection fails.
For non-production environments only, you can allow the connection by adding genericapi.tls.insecure=true to Additional Properties. This setting turns off certificate validation. Don't use it in production.
For production, install a certificate signed by a trusted certificate authority (CA) on the GFC.
Security notice: Configure TLS and the keystore for production
This application includes a sample Java KeyStore (bulk-claims-data-ingestion-api-impl-keystore.jks) to help you deploy quickly and test locally. Don't use this keystore in production.
You're responsible for provisioning your production keys. Before you send production traffic to the application, replace the sample keystore with your organization's own private key and certificate.
Follow the steps for your deployment model.
If you deploy to CloudHub 2.0 Private Spaces.
You can manage your certificates at the platform level, without changing the application.
1. In Anypoint Platform, go to Runtime Manager > Private Spaces.
2. Select your private space, and then click Domains & TLS tab.
3. In the TLS context configuration, upload your organization's PEM or JKS file.
4. Enter the passwords and aliases that your organization's certificate requires.
For more information, see CloudHub 2.0 Private Space TLS Documentation.
If you deploy to CloudHub 1.0, Runtime Fabric, or a standalone runtime.
Before you deploy, add your own keystore to the application artifact.
1. Generate a new, organization-specific JKS using your own PKI or the Java keytool.
2. Open the application artifact (or import it into Anypoint Studio), and go to src/main/resources/tls/.
3. Delete the default bulk-claims-data-ingestion-api-impl-keystore.jks file, and then add your new .jks file.
4. Update the application's configuration properties to match your new keystore. You can do this on the Properties tab in Runtime Manager or in your YAML configuration file.
tls.keyStoreAlias: tls.keyStoreSecret: * tls.keySecret: 5. Deploy the updated application artifact.
For more information, see MuleSoft TLS Configuration Guide.