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
| Name | Type | Required | Description |
|---|---|---|---|
code | text | No | Diagnosis code to validate |
procedure | text | No | Procedure code for billing alignment |
diagnoses | json | No | List of diagnosis codes (for necessity check) |
service | text | No | Service/procedure for medical necessity check |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
result | json | No | Diagnosis validation data (code details, errors, warnings, billing, specificity, necessity) |
is_valid | boolean | No | Whether the validation passed |
success | boolean | No | Operation success flag |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Operation | operation | enum | No | validate | validate, format, specificity, billing, necessity | Validation operation to perform |
| Code System | system | enum | No | icd-10 | icd-10, icd-9 | Diagnosis code system |
Advanced
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Min Specificity | min_specificity | number | No | 3 | min 1; max 7 | Minimum specificity level required |
Errors
| Code | Description |
|---|---|
CODE_REQUIRED | Diagnosis code is required |
INVALID_FORMAT | Code does not match expected ICD format |
INSUFFICIENT_SPECIFICITY | Code lacks required specificity level |
UNSUPPORTED_OPERATION | Operation 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.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..