AI medical coding

Every suggested code,linked to the record.

Rhazes retrieves code identifiers from real code lists and never invents them. See the record evidence behind each suggestion.

Clinic noteAlex Morgan · 23 Sep 2026 · Fictional record

Presenting complaint

Right knee ache after running for two weeks.ME82Pain in joint

No injury, swelling, locking or fever.

Background

Type 2 diabetes.5A11Type 2 diabetes mellitus

Metformin 500 mg twice daily.

Amlodipine 5 mg once daily for hypertension.BA00Essential hypertension

Examination and plan

Full range of movement. No swelling. Normal gait. BP 138/84.MC80.0Elevated blood-pressure reading

Reduce running for now. Gentle exercises. Review in two weeks.

Illustrative example with a fictional patient. Codes shown for demonstration only.

Try the review

Open a suggestion. Check the evidence. Make the call.

You have reviewed 0 of 4 suggestions

Clinic noteFictional record

Alex Morgan · DEMO-UI-001 · 23 Sep 2026

Presenting complaint

Right knee ache after running for two weeks.

No injury, swelling, locking or fever.

Background

Type 2 diabetes.

Metformin 500 mg twice daily.

Amlodipine 5 mg once daily for hypertension.

Examination

Full range of movement. No swelling. Normal gait.

BP 138/84.

Plan

Reduce running for now. Gentle exercises.

Review in two weeks if symptoms persist.

ICD-11
Pain in right knee EvidenceRight knee ache after running for two weeks. ME82Pain in jointReviewed
Choose a code for pain in right knee

Uncertainty: no structural diagnosis is supported by the record.

Type 2 diabetes EvidenceType 2 diabetes. 5A11Type 2 diabetes mellitusReviewed
Choose a code for type 2 diabetes
Hypertension EvidenceAmlodipine 5 mg once daily for hypertension. BA00Essential hypertensionReviewed
Choose a code for hypertension
Blood pressure reading EvidenceBP 138/84. MC80.0Elevated blood-pressure reading, without diagnosis of hypertensionReviewed
Choose a code for the blood pressure reading

Generated by Rhazes AI. Please review all codes before using in practice and verify against current coding guidelines.

Illustrative example with a fictional patient. Choices here are not saved.

How it works

From clinical record to reviewed codes.

  1. 01

    Bring in the record

    Start with patient notes, context and your chosen coding standard.

  2. 02

    Review suggested codes

    See real code identifiers and their supporting record evidence.

  3. 03

    Confirm the result

    Compare alternatives, add clinical detail and confirm your chosen codes.

Illustrative example with a fictional patient. Codes shown for demonstration only.

Specialties and local rules

Your organisation’s rules, built in.

Upload your own code list. Rhazes retrieves matching identifiers from it, linked to the clinical evidence.

  • Comorbidities coded alongside the main complaint
  • Multiple specialties in one workspace
  • Local code lists uploaded as a simple CSV

Familiar coding systems

One record. The coding system you work in.

Use ICD-11, SNOMED CT, CPT or your own code list, with supporting evidence in the same workspace.

Evidence in the record“Right knee ache after running for two weeks. No injury.”

Suggested code

ICD-11: ME82, Pain in joint

Also supported: CPT and other widely used coding systems.

Questions from clinicians.

Which coding systems are supported?

Rhazes supports ICD-11, SNOMED CT, CPT and your own code list, with supporting evidence in the same workspace.

Can I see why a code was suggested?

Yes. Each suggested code links to the words in the record that support it.

Are codes submitted automatically?

Final decisions stay with your clinical or coding team. Review and approve each code before use.

More time for your patients.

Start with the free plan, or contact us about Rhazes for your hospital or clinic.

Rhazes, wherever you work.

Use Rhazes in your browser today. Apps for iPhone and Android are coming soon.

Trusted with patient data

  • ISO 27001
  • EU Class I SaMD
  • HIPAA
  • GDPR
  • Cyber Essentials
Visit the Trust centre