Claims
X12 Delivery: Webhooks
Setup
To enable Optimizer output or EDI delivery through webhooks, you will need to navigate to your admin panel, and setup webhooks with a credentials set. You must have a webhook registered for each event you want to receive. You will receive the following responses for the claim optimization APIs:
Output
X12 Claim Denials
The output of the Optimizer X12 Denials API will be a body like so:
Field | Description |
---|---|
claim_id | A unique identifier for the claim. |
patient_control_number | The control number assigned to the patient. |
edits | A list of differences identified by the AI between the uploaded claim and the AI-generated claim. Each difference includes: |
- difference : A description of the specific discrepancy found in the claim. | |
- rationale : The reasoning provided by the Cair AI for the identified discrepancy. | |
ai_generated_claim | The claim generated by the Cair Health Claims Optimizer AI, including corrected or updated information. |
ai_generated_encounter_summary | A natural language summary of the patient’s encounter, providing context and details about the patient’s visit and treatment. |
Draft Claim From Notes PDF
The output for the Draft Claim From Notes API will look similar the above, but slightly different. Notably the inclusion of the ai_generated_x12_837
field with the submission-ready 837.
Field | Description |
---|---|
claim_id | A unique identifier for the claim. |
patient_control_number | The control number assigned to the patient. |
ai_generated_x12_837 | The X12 837 formatted claim generated by the Cair Health Claims Optimizer AI. |
ai_generated_encounter_summary | A natural language summary of the patient’s encounter, providing context and details about the patient’s visit and treatment. |