Aller au contenu principal

X12 Validate

Category: Healthcare Standards
Node id: x12-validate

Standards: HIPAA, SOC2

Validates X12 EDI documents against HIPAA 5010 rules at basic, standard, or strict levels

What it does​

  • HIPAA 5010 compliance validation
  • Three-tier validation levels (basic, standard, strict)
  • Segment-level error reporting in strict mode
  • Separate error and warning classification

Use cases​

  • Pre-submission claim validation for clearinghouses
  • EDI compliance auditing for healthcare organizations
  • Incoming transaction quality checks

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
x12_texttextYesRaw X12 EDI text to validate

Output ports​

NameTypeRequiredDescription
resultjsonNoValidation result (errors, warnings, segment_errors, error_count, warning_count)
is_validbooleanNoWhether the X12 document passed validation
successbooleanNoWhether the validation operation completed

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Validation Levelvalidation_levelenumNostandardbasic, standard, strictLevel of validation strictness

Errors​

CodeDescription
X12_TEXT_REQUIREDRaw X12 EDI text input is required
INVALID_VALIDATION_LEVELValidation level must be basic, standard, or strict

Runtime notes​

  • is_valid is a top-level boolean output (not inside result). It is true only when result.errors is empty.
  • result.errors are structural issues (missing ISA/IEA/GS/GE/ST/SE, wrong element counts); result.warnings are advisory.
  • result.segment_errors only appear in strict mode — they flag whitespace and formatting issues within individual elements.
  • success means the validation ran to completion; a document can be invalid (is_valid=false) while success is still true.

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

Quelque chose n'est pas clair ? Envoyez vos commentaires sur la documentation par courriel.