icd10_code validator

Format

Matches `/^[A-Z]\d{2}(\.\d{1,3})?$/` after uppercasing. One uppercase letter, two digits, optional dot + 1–3 more digits.

Examples

• E11.9 (Type 2 diabetes without complications)
• I10 (Essential hypertension)
• "asthma" → resolved to J45.909

Implementation

Faithful summary of lib/validators.ts. Validators are pure functions and run identically in the worker, the Workbench, and the MCP server.

function validIcd10(value) {
  return /^[A-Z]\d{2}(\.\d{1,3})?$/.test(value.toUpperCase())
    ? OK
    : fail('icd10_format', 'expected A00 or A00.0')
}
// Plus the resolver wrapper.

Use in a template

Validators attach to a field on a custom template. The cascade runs them after mapping but before commit; failures surface in the per-row validation report.

fields:
  - column: icd10_code
    type: string
    validators:
      - type: icd10_code

Common gotchas

• We accept ICD-10-CM (US/CH variant). WHO ICD-10 codes that overlap will pass; codes that are CM-only (e.g. `O80`) and codes that are WHO-only behave differently downstream.
• Decimal point is optional, but a trailing dot with no digits (`I10.`) is rejected. The regex requires 1–3 digits after the dot when the dot is present.
• Lowercase input is uppercased before matching. `e11.9` passes.

Related templates

• Claims line itemsclaims_line_items_v1

  CPT/ICD-10-coded claim line items.

  Fields: icd10_code

Pricing

Validators run on every committed row

Schema-only mode (headers + ≤3 sample rows) is free and unlimited; full-data commits are metered. See plans →