X12 Claim Submit
Category: Healthcare Standards
Node id: x12-claim-submit
Standards: HIPAA, SOC2
Submits 837P/837I claims to a clearinghouse endpoint via HTTP
What it does
- 837P/837I claim submission to clearinghouse via HTTP
- Pre-built X12 text or structured claim data input
- Automatic X12 generation from claim data
- Clearinghouse acknowledgment parsing
- Configurable authentication and timeout
Use cases
- Submit professional claims (837P) to payer clearinghouses
- Submit institutional claims (837I) for hospital billing
- Automated batch claim submission workflows
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
x12_text | text | No | Pre-built X12 837 claim text |
claim_data | json | No | Structured claim data (used if x12_text not provided) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Submission result (submission_id, status, claim_type, acknowledgment, http_status) |
success | boolean | No | Whether the submission succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Clearinghouse URL | clearinghouse_url | string | Yes | Base URL of the clearinghouse endpoint | ||
| Claim Type | claim_type | enum | No | professional | professional, institutional | Type of claim to submit |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Auth Token | auth_token | secret | No | Bearer token for clearinghouse authentication |
Errors
| Code | Description |
|---|---|
CLEARINGHOUSE_URL_REQUIRED | Clearinghouse URL must be configured |
NO_CLAIM_DATA | Neither x12_text nor claim_data provided |
SUBMISSION_FAILED | HTTP request to clearinghouse failed |
CLEARINGHOUSE_REJECTED | Clearinghouse returned non-success status |
Runtime notes
- x12_text takes priority over claim_data — if x12_text is provided, claim_data is ignored
- When claim_data is used instead of x12_text, the data is JSON-serialized as the transaction payload (not converted to X12 format)
- submission_id is a UUID generated per invocation for tracking the claim through the clearinghouse
- HTTP 4xx/5xx from the clearinghouse causes the node to error, not return success=false
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..