> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/integrations/billing-candid/candid-setup-and-configuration.md).

# Candid Setup and Configuration

Welkin Health offers centralized billing through its integration with Candid Health. This allows organizations to automate the entire RCM and billing process.

## Setup overview

| Deliverable / Step                 | Responsible party |
| ---------------------------------- | ----------------- |
| Contracting                        | Both              |
| Enable integration                 | Welkin            |
| Enable and permission API/Webhook  | Customer          |
| Add User Attributes                | Customer          |
| Create Automation in Designer      | Customer          |
| Create Encounter Disposition Field | Welkin            |
| Create Profile Fields for Billing  | Welkin            |
| Create CDTs for Billing            | Welkin            |
| Testing                            | Both              |

## Step 1: Contracting

Complete the contracting process with the Welkin Sales or CSM team.

## Step 2: Enable integration

Welkin's CSM and integration team will enable the integration internally.

## Step 3: Enter credentials in Admin

1. Obtain your **API Client** and **API Secret** from Candid Health
2. Log in to the Welkin Admin portal
3. Navigate to **Integrations → Candid** tab
4. Enter the API Client and API Secret
5. Save

## Step 4: Add User Attributes

Enable and add the following User Attributes for each user in Admin:

* Billing Zip
* Billing Zip4
* Billing Address
* Billing City
* Billing State
* Zip
* NPI
* Self-Pay Billing Organization NPI
* Insurance Billing Organization NPI
* Billing Tax Code

## Step 5: Create Profiles, CDTs, Encounter Dispositions, and Billing Form Assessment in Designer

Welkin will create the required Profile fields, CDTs, and the Encounter Disposition field. The customer is responsible for:

1. **Create an Automation** with:

   * Trigger Event Type: **Encounter Finalized**
   * Action: **Create Candid Claim**

   This sends encounter data to Candid when an encounter is finalized. You can optionally target a specific Encounter Template in the trigger if claims should only be sent for certain encounter types.

   Optionally, create a second automation with Trigger Event: **Encounter Cancelled** and Action: **Create Candid Claim** if needed.
2. **Create a "Submit to Candid" Encounter Disposition Field:**
   * Field Name: Submit to Candid
   * Type: Boolean
   * Display Type: Checkbox
3. **Create a Billing Form Assessment** (optional) — a form completed with each encounter to send claim information to Candid. If not used, information will be taken directly from User Attributes, CDTs, and Encounter Disposition fields.

> **Important:** Candid requires fields to be named in a specific format. Element names must exactly match the field names listed in [Candid Integration Required Fields](/integrations/billing-candid/candid-integration-required-fields.md).

## Step 6: Testing

Coordinate testing with your Integration or CSM Manager to verify your workflows are working as expected.

***

More Questions? Contact <csm@welkinhealth.com> or your Implementation/CSM directly.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/integrations/billing-candid/candid-setup-and-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.