Skip to main content

X12 Generate

Category: Healthcare Standards
Node id: x12-generate

Standards: HIPAA, SOC2

Generates X12 EDI text from structured claim data with proper envelope segments

What it does​

  • X12 EDI generation from structured claim data
  • Proper ISA/GS/ST envelope wrapping
  • Support for multiple transaction types (837P, 837I, 270, 276, 278)
  • Configurable sender/receiver identifiers
  • Control number generation and tracking

Use cases​

  • Generate 837 professional/institutional claims for submission
  • Create 270 eligibility inquiry transactions
  • Produce 276 claim status inquiry messages
  • Build X12 transactions from internal data models

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
claim_datajsonNoStructured claim data for X12 generation
segmentsjsonNoRaw segment strings to include in the transaction

Output ports​

NameTypeRequiredDescription
resultjsonNoGeneration result (x12_text, segment_count, control_numbers, transaction_type)
successbooleanNoWhether the generation succeeded

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Transaction Typetransaction_typestringYes837PX12 transaction type to generate (e.g. 837P, 837I, 270, 276, 278)
Sender IDsender_idstringYesISA sender identifier
Receiver IDreceiver_idstringYesISA receiver identifier

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
VersionversionstringNo005010X222A1X12 implementation guide version

Errors​

CodeDescription
SENDER_ID_REQUIREDISA sender identifier is required
RECEIVER_ID_REQUIREDISA receiver identifier is required
CLAIM_DATA_REQUIREDClaim data or segments required for generation

Runtime notes​

  • claim_data takes priority over segments — if both are provided, claim_data is used for content generation
  • ISA/GS/ST envelope and SE/GE/IEA trailer are always auto-generated; only provide content segments
  • Control numbers are auto-generated from the current timestamp
  • For 837P/837I, claim_data supports sub-keys: bht, provider (last_name, first_name, npi), patient (last_name, first_name, member_id)

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

Something unclear? Send documentation feedback by email.