Skip to main content

Validate Diagnosis

Category: Healthcare Standards
Node id: validate-dx

Standards: HIPAA, GDPR, SOC2

Validates diagnosis codes (ICD-10/ICD-9) for format, specificity, billing eligibility, and medical necessity

What it does​

  • ICD-10 and ICD-9 code format validation
  • Diagnosis code specificity analysis
  • Billing alignment checking (diagnosis vs. procedure codes)
  • Medical necessity evaluation for services
  • Code normalization and formatting

Use cases​

  • Claims submission pre-validation
  • Diagnosis code quality checks during EHR data entry
  • Medical necessity documentation for prior authorization
  • Revenue cycle management code auditing

Runtime​

  • Performance tier: fast

Input ports​

NameTypeRequiredDescription
codetextNoDiagnosis code to validate
proceduretextNoProcedure code for billing alignment
diagnosesjsonNoList of diagnosis codes (for necessity check)
servicetextNoService/procedure for medical necessity check

Output ports​

NameTypeRequiredDescription
resultjsonNoDiagnosis validation data (code details, errors, warnings, billing, specificity, necessity)
is_validbooleanNoWhether the validation passed
successbooleanNoOperation success flag

Settings​

Basic​

SettingNameTypeRequiredDefaultAllowed valuesDescription
OperationoperationenumNovalidatevalidate, format, specificity, billing, necessityValidation operation to perform
Code SystemsystemenumNoicd-10icd-10, icd-9Diagnosis code system

Advanced​

SettingNameTypeRequiredDefaultAllowed valuesDescription
Min Specificitymin_specificitynumberNo3min 1; max 7Minimum specificity level required

Errors​

CodeDescription
CODE_REQUIREDDiagnosis code is required
INVALID_FORMATCode does not match expected ICD format
INSUFFICIENT_SPECIFICITYCode lacks required specificity level
UNSUPPORTED_OPERATIONOperation not recognized

Runtime notes​

  • Result shape varies by operation: validate returns errors/warnings, format returns formatted_code, specificity returns is_specific_enough, billing returns is_billable, necessity returns supporting/non_supporting arrays
  • Input ports are operation-specific: 'code' for validate/format/specificity/billing, 'diagnoses'+'service' for necessity
  • is_valid semantics change per operation: format validity, specificity pass, billing eligibility, or medical necessity
  • Code lookup uses an in-memory database — only a small set of codes (E11.9, E11, I10, Z23, 250.00) are recognized

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.