cpt_code validator

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

function validCpt(value) {
  return /^\d{5}$/.test(value)
    ? OK
    : fail('cpt_format', 'expected 5 digits')
}

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: cpt_code
    type: string
    validators:
      - type: cpt_code

• HCPCS Level II codes (one letter + 4 digits, e.g. `J3490`) are rejected. Use a separate validator if you mix CPT and HCPCS.
• CPT Category II (4 digits + `F`) and Category III (4 digits + `T`) codes also fail the shape — they are not pure 5-digit.
• No AMA registry lookup. `00000` and `99999` both pass the format check.

• Claims line itemsclaims_line_items_v1

  CPT/ICD-10-coded claim line items.

  Fields: cpt_code

Validators add no AI cost — they are pure functions. Every map bills a small flat per-map fee from your prepaid token wallet ($10 minimum, shared across our suite); only columns that reach the metered LLM layer, plus any-to-any convert and reshape, bill real AI tokens. See pricing →

Back to the documentation index or browse the template catalogue.