What ICD10Insighter actually does
ICD10Insighter is a text reader, not a coding authority. It takes free-text documentation and returns candidate ICD-10-CM codes, each with a short rationale that quotes the supporting part of the note.
- It reads narrative documentation and identifies documented diagnoses.
- It suggests codes with an explanation of why each one was chosen.
- It does not invent codes. Every suggestion is checked against the official FY 2027 dataset, and anything that cannot be matched is flagged as unverified rather than presented as a valid code.
- It does not decide what to bill, and it never replaces the tabular list.
Step 1 — De-identify the note
This is the step people skip, and it is the one that matters most. Work through the text and strip out anything that could identify a person:
- Names of the patient, relatives, clinicians and staff.
- Record numbers, account numbers and insurance identifiers.
- Dates of birth, admission dates and specific visit dates.
- Addresses, phone numbers, email addresses and employer names.
- Any rare detail that could identify someone in a small community.
Keep the clinical substance: symptoms, findings, duration, laterality, encounter type and the assessment. Those are what drive code selection.
Step 2 — Extract the candidate codes
Open ICD10Insighter, paste the de-identified note into the text area and run the extraction. The result is a list of codes, each with a description and a rationale.
Step 3 — Read the rationale, not just the code
The rationale is the most useful part of the output. For every suggestion, ask one question: does the documentation actually support this? If the rationale quotes something vague, or the diagnosis was considered but ruled out, discard the code. A code you cannot defend from the record is a code you should not report.
Step 4 — Verify each code against the official dataset
Click any suggested code to open its full detail page. Four checks catch most problems:
- Billable or header. Category headers cannot be reported on their own. If the code is not billable, choose a more specific code from the sub-code list.
- Specificity. Where the note supports it, code to the most specific level available, including laterality and encounter type.
- Seventh character. Injury, poisoning and external-cause categories need a 7th character (for example initial encounter, subsequent encounter or sequela). The detail page tells you when one is required.
- Excludes notes. Read the Excludes 1 and Excludes 2 sections before you finalise anything. Understanding Excludes 1 and 2 explains what each note means.
Step 5 — Check that the codes work together
Individually valid codes can still conflict. Run the shortlist through the Claim Validator, which checks a set of codes for Excludes 1 conflicts. Fixing a conflict before submission is far cheaper than an appeal.
Where ICD10Insighter earns its keep
- Long, multi-problem notes where it is easy to miss a documented diagnosis.
- Producing a first-pass candidate list to review, rather than starting from a blank screen.
- Spotting a diagnosis in the narrative that was not carried into the assessment.
- Learning ICD-10 phrasing quickly when you are new to a specialty.
Where it should not be used
- As a substitute for the official tabular list or the coding guidelines.
- As the sole basis for a billing decision.
- On identifiable patient information.
- To generate coding data. The Excludes notes, guidelines and coverage content on this site come from official CMS sources, never from AI.
Quick checklist
- Note de-identified before it is pasted.
- Every suggestion traced back to a rationale in the record.
- Every code checked for billable status and specificity.
- 7th character requirements satisfied.
- Excludes 1 and Excludes 2 notes read.
- Code set validated with the Claim Validator.