X12 EDI
Category: Healthcare Standards
Node id: x12-edi
Standards: HIPAA, SOC2
Processes X12 EDI transactions with parse, validate, generate, transform, and extract operations
What it does
- X12 EDI parsing with auto-detection of transaction types
- HIPAA 5010 validation with configurable strictness
- X12 transaction generation from structured data
- X12-to-JSON/FHIR/XML format transformation
- Targeted data extraction (claim, patient, provider, diagnoses, procedures)
Use cases
- Healthcare claims processing and EDI gateway operations
- EDI document validation before clearinghouse submission
- X12 to FHIR transformation for interoperability
- Automated claim data extraction for analytics
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
content | text | No | Raw X12 EDI content |
transaction_type | text | No | Transaction type for generate operation (e.g. 837) |
data | json | No | Structured data for generate operation |
targets | json | No | Array of extraction targets (claim, patient, provider, diagnoses, procedures) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Main result data from the X12 EDI operation |
validation | json | No | Validation information including errors, warnings, and validity status |
success | boolean | No | Whether the operation succeeded |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | Yes | parse | parse, validate, generate, transform, extract | X12 EDI operation to perform |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Target Format | target_format | enum | No | json | json, fhir, xml | Target format for transform operation |
Errors
| Code | Description |
|---|---|
CONTENT_REQUIRED | X12 EDI content is required for parse/validate/transform/extract |
DATA_REQUIRED | Structured data required for generate operation |
INVALID_X12 | Content is not valid X12 EDI format |
UNSUPPORTED_OPERATION | Operation not recognized |
Runtime notes
- Result shape varies by operation: parse includes transaction+claim_info+patient_info, validate has transaction_type, generate has content+segment_count, transform has data+data_type, extract has extracted_data
- validation output is always present but may be empty ({}) for generate/transform/extract operations
- Parse requires ISA, GS, and ST segments minimum — missing segments cause a parse error
- Transform to 'fhir' produces a FHIR Claim resource; 'json' produces a flat representation of the transaction
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..