X12 Prior Auth
Category: Healthcare Standards
Node id: x12-prior-auth
Standards: HIPAA, SOC2
Handles 278 prior authorization request and response processing
What it does
- 278 prior authorization request generation and submission
- 278 prior authorization response parsing
- Clearinghouse integration for authorization workflows
- Structured authorization decision extraction
Use cases
- Submit prior authorization requests to payers electronically
- Automate prior auth workflows for scheduled procedures
- Parse authorization responses for approval/denial status
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
x12_text | text | No | Pre-built X12 278 text |
auth_data | json | No | Authorization request data (payer, provider, patient, diagnosis, procedure info) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the prior authorization operation |
status | text | No | Authorization or submission status |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | request | request, generate_278, parse_response | Prior authorization operation to perform |
| Clearinghouse URL | clearinghouse_url | string | No | Base URL of the clearinghouse endpoint (required for request) |
Auth
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Auth Token | auth_token | secret | No | Bearer token for clearinghouse authentication |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Sender ID | sender_id | string | No | SENDER | ISA sender identifier for 278 generation | |
| Receiver ID | receiver_id | string | No | RECEIVER | ISA receiver identifier for 278 generation |
Errors
| Code | Description |
|---|---|
AUTH_DATA_REQUIRED | Authorization request data required |
X12_TEXT_REQUIRED | X12 text required for parse_response operation |
CLEARINGHOUSE_URL_REQUIRED | Clearinghouse URL required for request operation |
REQUEST_FAILED | HTTP request to clearinghouse failed |
Runtime notes
- Result shape varies: request returns trace_number+response, generate_278 returns x12_text, parse_response returns auth_number+status_description+certification_type
- For request, either x12_text or auth_data must be provided — auth_data auto-builds the 278 transaction
- parse_response extracts HCR segment for auth status (A1=certified, A3=not certified, A4=pended) and UM for review actions
- Status output is 'submitted' for request, 'generated' for generate_278, or the HCR status code for parse_response
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..