Zum Hauptinhalt springen

X12 Parse

Category: Healthcare Standards
Node id: x12-parse

Standards: HIPAA, SOC2

Parses raw X12 EDI text into structured segment data with auto-detection of transaction types

What it does​

  • Raw X12 EDI text parsing into structured segments
  • Auto-detection of transaction type (837, 835, 270, 276, 278, etc.)
  • Configurable segment, element, and sub-element separators
  • ISA interchange control number extraction

Use cases​

  • Ingest and parse incoming EDI transactions
  • Pre-processing step before X12 validation or transformation
  • EDI document analysis and debugging

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
x12_texttextYesRaw X12 EDI text to parse

Output ports​

NameTypeRequiredDescription
resultjsonNoParse result (segments, segment_count, transaction_type, transaction_name, interchange_control_number)
successbooleanNoWhether the parse succeeded

Settings​

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Segment Separatorsegment_separatorstringNo~Character used to separate segments
Element Separatorelement_separatorstringNo*Character used to separate data elements
Sub-Element Separatorsub_element_separatorstringNo:Character used to separate sub-elements

Errors​

CodeDescription
X12_TEXT_REQUIREDRaw X12 EDI text input is required
PARSE_ERRORFailed to parse X12 text (malformed content)

Runtime notes​

  • Each segment in the output includes both raw 'elements' array and 'parsed_elements' with sub-element splitting
  • ISA segment gets extra keys: sender_id, receiver_id, date, control_number
  • transaction_type is extracted from the ST segment; transaction_name is a human-readable label (e.g., 'Health Care Claim')
  • Separators are configurable — override defaults if parsing non-standard EDI with different delimiters

See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.

Etwas unklar? Senden Sie Feedback zur Dokumentation per E-Mail..