X12 Eligibility
Category: Healthcare Standards
Node id: x12-eligibility
Standards: HIPAA, SOC2
Handles 270/271 eligibility inquiry and response processing for insurance verification
What it does
- 270 eligibility inquiry generation and submission
- 271 eligibility response parsing
- Insurance coverage verification via clearinghouse
- Structured benefit and eligibility extraction
Use cases
- Real-time insurance eligibility verification at registration
- Automated patient coverage checks before appointments
- Parse 271 responses for benefit details display
Runtime
- Performance tier:
variable
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
x12_text | text | No | Pre-built X12 270/271 text (used directly, skips patient_data) |
patient_data | json | No | Patient data for building a 270 inquiry. Must be a flat object with top-level keys. |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the eligibility operation |
eligible | boolean | No | Whether the patient is eligible |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | inquiry | inquiry, generate_270, parse_271 | Eligibility operation to perform |
| Clearinghouse URL | clearinghouse_url | string | No | Base URL of the clearinghouse endpoint (required for inquiry) |
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 270 generation | |
| Receiver ID | receiver_id | string | No | RECEIVER | ISA receiver identifier for 270 generation | |
| Service Type Code | service_type_code | string | No | 30 | Service type code for eligibility inquiry (e.g. 30 for health benefit plan coverage) |
Errors
| Code | Description |
|---|---|
PATIENT_DATA_REQUIRED | Patient data required for eligibility inquiry |
X12_TEXT_REQUIRED | X12 text required for parse_271 operation |
CLEARINGHOUSE_URL_REQUIRED | Clearinghouse URL required for inquiry operation |
INQUIRY_FAILED | HTTP request to clearinghouse failed |
Runtime notes
- Requires EITHER x12_text OR patient_data — if both are missing, throws 'x12_text or patient_data is required'.
- x12_text is checked first. If present and non-empty, patient_data is ignored entirely.
- patient_data MUST be a flat JSON object with top-level keys: last_name, first_name, member_id (required), date_of_birth (optional). Nested objects like {data:{last_name:...}} will NOT work — the node reads patient_data['last_name'] directly.
- Do NOT wire a validator result directly to patient_data — validator outputs {valid,errors,data:{...}} which is not the flat structure this node expects. Use a transform/extract node to flatten it first.
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..