Saltar al contenido principal

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​

NameTypeRequiredDescription
contenttextNoRaw X12 EDI content
transaction_typetextNoTransaction type for generate operation (e.g. 837)
datajsonNoStructured data for generate operation
targetsjsonNoArray of extraction targets (claim, patient, provider, diagnoses, procedures)

Output ports​

NameTypeRequiredDescription
resultjsonNoMain result data from the X12 EDI operation
validationjsonNoValidation information including errors, warnings, and validity status
successbooleanNoWhether the operation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
OperationoperationenumYesparseparse, validate, generate, transform, extractX12 EDI operation to perform

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Target Formattarget_formatenumNojsonjson, fhir, xmlTarget format for transform operation

Errors​

CodeDescription
CONTENT_REQUIREDX12 EDI content is required for parse/validate/transform/extract
DATA_REQUIREDStructured data required for generate operation
INVALID_X12Content is not valid X12 EDI format
UNSUPPORTED_OPERATIONOperation 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..