Applied Judgment Assessment
Applied skill assessment · medical coders, clinical documentation specialists, health information and revenue-cycle teams, coding trainers · browse the full catalogue

Medical Coding and Clinical Documentation Accuracy Assessment for Health Information and Revenue Cycle TeamsThe note said one side. The claim said both. How far would that have travelled before anybody caught it?

Ten clinical notes, each with six coding lines: three the note supports and three it does not. Twenty-eight more exercises on what a record supports when a side is missing, a cause is only likely, or a query has gone unanswered. Scored in two directions that are never added, and reported as an escape ladder: five downstream controls with declared multipliers, and each of your errors pinned to the rung where it would first have been caught.

30 minutes38 scored exercisesEvidence-keyed scoringGlobal · INR & USD

A coding test that prices where an error would have been caught, not how many you made

The Medical Coding and Clinical Documentation Accuracy Assessment is a thirty-minute check of whether a person can read a clinical note and tell which coding the documentation actually supports, across ten invented notes and twenty-eight further exercises, with no code number anywhere, reported as two figures that are never combined and an escape ladder of five downstream controls.

Most coding tests hand you a note and a code book and count matches. This one never asks for a number. Every line is a coding decision described in words: a diagnosis coded as bilateral where the note records one side, a procedure coded as an excision where the note describes a shave, a heart attack coded as confirmed where the note says cardiac cause not found. Three of every six lines are supported and three are not, so marking everything and marking nothing both land in the same place, and the only way through is to read.

Two figures are computed and never averaged. Coded beyond the note is the direction the payer and the audit find: a line the clinician never wrote. Left out of the record is the direction the organisation pays for: a monitored condition, a documented procedure or a treated complication that never reached the coded record. Each is corrected against a coder marking every line at its declared prior, so zero on either is the ordinary coder, not half marks, and the weakest note is printed beside the mean rather than averaged away.

The report is an escape ladder. Five real controls in a coding department, the coder's own second read, the internal audit sample, the claim edit, the payer query and the external documentation audit, drawn as a spine with their declared multipliers printed above it: one, three, eight, twenty, forty. Every line in the instrument carries the rung of the first control whose job is to catch an error of that kind, and your errors are pinned there. Errors clustered at the top are a fluency problem; errors clustered at the bottom are a checking problem; those are different pieces of advice, and the page names which one you need.

The escape index is normalised against every exercise's worst reachable rung, never against your own error count, so a clean sitting is 1.00, a sitting that escapes everywhere is 0.00, and a reader who answered three exercises is refused rather than flattered. The multipliers are printed because a cost ladder is a value judgement, and the panel opens by saying that nothing in this sitting reached anybody, because a sitting is not a working day.

Every rule is stated in the exercise that applies it, as the guideline your organisation follows: the principal diagnosis as the condition established after study, diagnoses taken from the treating clinician, an uncertain outpatient diagnosis coded to the symptom, the compliant documentation query with its indicators and its open options. Nothing depends on one country's programme rules or one payer's policy. The report says in plain words what it did not measure: any code set, any code number, clinical judgement, speed, or how you code under a production target. It is not a credential and it audits no real record.

Two figures, never added, an escape ladder, and four areas each corrected against the ordinary coder:
Documented supportSpecificity and lateralitySequencing and the principal diagnosisQuery and escalation

What you walk away with

Coded beyond the note

Lines the note does not support that you marked: a diagnosis from an uncertain word, a side the note never stated, a procedure the note says did not happen. Corrected against the ordinary coder, with its 68 and 95 per cent bands, and the direction the payer finds.

Left out of the record

Lines the note supports that you did not mark: the monitored diabetes, the documented tube, the treated wound infection. The same arithmetic, printed beside the first figure and never averaged with it, because one is fixed by deleting and the other by adding.

The escape ladder

Five controls with declared multipliers, each of your errors pinned to the rung where it would first have been caught, the rung carrying the largest share of your index named, and the shape of the ladder read as fluency or checking. A rung with none of your errors is drawn empty, not left out.

Documented support

What the treating clinician wrote against what the results tab, the nursing note, the template and the history section imply: a potassium the laboratory flagged and nobody addressed, a blood pressure the clinician deferred in writing, a template line unchanged since admission.

Specificity and laterality

The side, the site and the type at the specificity the record gives: a fracture with no side, a right knee diagnosed beside a left knee imaged, a consent form that disagrees with the operation note, and where a query is due before any of them is coded.

Sequencing, the principal diagnosis, and the query

The condition established after study against the one that presented first; a planned operation cancelled after an arrhythmia was found; a compliant query in the right order; and what the policy supports when the deadline is tomorrow and the clinician has not replied.

Inside your report

Illustrative sample — your report is generated from your own responses.

The escape ladder: five controls, multipliers above the spine, your errors pinned where each would have been caught
0.93
Spreadescape index, 1.00 is a clean sitting · prior-drawing coder 0.64
Declared multipliers, above the spine:x1x3x8x20x40A value judgement, not a measurement. Each rung names the control, never the consequence.1x1 · The coder's own second read● 1 pinned · 1 of 12 escaped2x3 · The internal coding audit sample● 5 pinned · 15 of 120 escaped3x8 · The claim edit before submission○ empty: none of your errors here4x20 · The payer query or denial● 2 pinned · 40 of 380 escaped5x40 · The external documentation audit● 1 pinned · 40 of 840 escaped

How to read it: the hollow bar is what could have escaped at that rung on the exercises you answered; the filled part is what did. Errors clustered at the top are a fluency problem, at the bottom a checking problem. The two on rung 4 and the one on rung 5 carry 80 of the 96 that escaped, so the page names the payer rung as the one to read first. Nothing in a sitting reaches anybody; the ladder prices detection position, not outcome.

RungMultiplierYour errorsEscapedCould have
● 1. The coder's own second readx11112
● 2. The internal coding audit samplex3515120
○ 3. The claim edit before submissionx8empty064
● 4. The payer query or denialx20240380
● 5. The external documentation auditx40140840
● you: index 1 − 96 / 14160.93
◇ a coder answering at the declared priors, same form0.64
Two figures, never added: each with its own count, its own bands, its cost, its fix, and the one line worth a sentence
Coded beyond the note
Not coded beyond the note: 3 of 30 lines
56
▲ Above the ordinary coder
0 = ordinary coder−100100● you 56

Two chances in three between 45 and 67; nineteen in twenty between 34 and 78.

What it costs: The direction the payer or the audit finds: a diagnosis the note never confirmed, a side the note never stated.

How it is fixed: Fixed by deleting, or by asking first: find the clinician's own sentence that states the line as current and confirmed.

The one worth a sentence: On the chest-pain note, the line musculoskeletal pain coded as a confirmed cause. The note says likely.

Left out of the record
Nothing supported left out: 6 of 30 lines
12
▬ Near the ordinary coder
0 = ordinary coder−100100● you 12

Two chances in three between 1 and 23; nineteen in twenty between -10 and 34.

What it costs: The direction the organisation pays for: a monitored condition or a documented procedure that never reached the coded record.

How it is fixed: Fixed by adding: read the plan, the results and the nursing record for care that happened, not only the assessment line for names.

The one worth a sentence: On the pneumonia note, the line type 2 diabetes, monitored during the admission. Daily glucose checks are care.

The weakest note, printed beside the mean

Note 7: Primary care review for tiredness. 3 of 6 lines right, corrected score −100. 1 coded beyond the note, 2 left out. A coded record is only as good as the note it gets wrong.

The two directions are never averaged: one is fixed by deleting a line or asking first, the other by adding a line from the note, and a single accuracy figure would tell you to do neither.

Built for

  • Medical coders and clinical coding officers who want to know which of their errors would travel furthest before being caught
  • Clinical documentation specialists and query writers who sit between the note and the code and want the two error directions separated
  • Health information and revenue-cycle managers hiring or auditing coders, who need a check that does not test a code book
  • Coding trainers and educators who want a report that says fluency problem or checking problem rather than a percentage

Find out how far your errors would have travelled

38 exercises across six formats · about 30 minutes · two figures never added, an escape ladder with declared multipliers, and the note you read least accurately printed beside the mean.

₹699 (incl. GST) · assessment and full report, nothing further to pay

Buy this assessment

No account needed to buy. Your name and email identify the purchase and your receipt is sent to that address.

Secure Razorpay payment · ₹699 includes 18% GST

Bought this already and lost the tab? Sign in and enter your purchase code under Claim a purchase on your dashboard.

Secure checkout · INR & USDFull report immediately after submission

Frequently asked questions

Does the test use real diagnosis or procedure codes?

No. No code number from any code set appears anywhere, and none is asked for. Every line is a coding decision described in words: a diagnosis coded as bilateral where the note records one side, a procedure coded as an excision where the note describes a shave. The question is always whether the documentation supports the decision, so the test works whichever code set and whichever national guideline your organisation uses.

What is the escape ladder?

Five downstream controls in a coding department, drawn as a spine: the coder's own second read, the internal coding audit sample, the claim edit before submission, the payer query or denial, and the external documentation audit. Each carries a declared multiplier, one, three, eight, twenty and forty, printed above the ladder because it is a value judgement. Every line in the test carries the rung of the first control whose job is to catch an error of that kind, and your errors are pinned there, so the report shows where each would have been caught rather than only how many there were.

Why are the two error directions never averaged?

Because they need opposite corrections. Coding a line the note does not support is fixed by deleting it, or by querying before it goes in. Leaving out a line the note supports is fixed by adding it. An average would tell you to do neither. Each figure is corrected against a coder marking every line at its declared prior, so zero on either is the ordinary coder, and each carries its own band.

Is this a coding credential or a certification?

No. It is not a credential, it does not qualify anybody to code for submission, and it audits no real record. Every note was invented for the instrument, and no real patient, clinician, hospital or payer is described. It is not affiliated with any coding authority, professional association, certifying body, payer or software vendor. The report says this in the reader's own language, in a refusal block, never in a footer.

How long is it, what does it cost, and what happens if I leave exercises unanswered?

About thirty minutes for thirty-eight exercises across six formats. The sitting is free to take; the report is the product, priced at ₹699 in India, inclusive of GST, or US$6.99 elsewhere, one time. An unanswered exercise leaves the denominator rather than scoring zero. A sitting with fewer than twenty-three of the thirty-eight answered is not reported at all: the refusal is printed where the ladder would have been, because an escape index over a handful of answers would reward the short sitting.

One of the AssessAll applied-judgment assessments

Each one takes a single capability, puts you inside the situations where it is actually tested, and scores your choices against published evidence — with a report designed for that capability alone, not a template. They span hiring, compliance, education, operations and personal skill.

Browse the catalogue →

Methodology: Thirty-eight original exercises across six formats: ten clinical-note sweeps, each a short note with six coding lines of which three are supported by the note and three are not, delivered as select-every-line-the-note-supports; ten single-choice exercises about what a record supports; seven true-or-false claims about documentation rules; four match-the-following exercises; four ordering exercises on the query, escalation, principal-diagnosis and support-check procedures; and three numeric estimates on a slider. One response instruction is declared for the whole instrument and it is a KNOWLEDGE instruction: which coding the documentation supports, never what the respondent would do or feel. Construct statement: this measures whether a person can read a clinical note and tell which coding the documentation actually supports, in two directions that are never netted, coding what the note does not support and missing what the note does support, together with knowing when a documentation query is raised instead of a guess; it does not measure knowledge of any code set, any code number, any national programme's rules, any payer's policy, clinical judgement, typing speed, or how a person codes under a production target, and it is not a coding credential. Scoring is two-sided coverage against a declared selection prior (C19). On every sweep the keyed set is the SUPPORTED class and the complement is what the note leaves unsupported; content.option_classes states the class of every line beside the key so the two can be checked against each other across the bank. Every line carries option_base_rate, the declared share of working coders expected to mark it. Two figures are computed from the sweeps and never combined: not coded beyond the note, the share of unsupported lines left unmarked, and nothing supported left out, the share of supported lines marked. Each is corrected against a coder marking every line at its declared prior, so zero on either figure is the ordinary coder, and each carries its own n, its own assumed omega printed unrounded and its own standard-error band. A figure is printed only when at least eight sweeps were answered and omega is at or above .70; otherwise a three-way placement is printed in the figure's place. The weakest sweep is printed beside the mean. The report is an escape ladder (D23): five downstream controls in a coding department, the coder's own second read, the internal coding audit sample, the claim edit before submission, the payer query or denial, and the external documentation audit, each carrying a declared multiplier of 1, 3, 8, 20 and 40 printed above the ladder. Every coding line, option, pair, ordering and estimate in the seed carries the rung of the first control whose job is to catch an error of that kind, and the respondent's errors are pinned to those rungs. The escape index is one minus the sum of the multipliers at the rungs the respondent's errors reached, divided by the sum over every answered exercise of its worst reachable rung; it is normalised against the form and never against the respondent's own error count, is 1.00 for a clean sitting, and is printed beside what a coder answering at the declared priors would score on the same form. The multipliers are a value judgement and not a measurement, and are printed so they can be disagreed with. The ladder prices where an error would have been detected, not whether anything went wrong, and the panel says so in its first sentence. The single-choice, true-or-false, matching, ordering and estimation exercises are corrected against the declared prior on every option, pair, position or value and feed four competency areas together with the sweeps: documented support, specificity and laterality, sequencing and the principal diagnosis, and query and escalation. An area with fewer than eight answered exercises or an omega under .70 carries a three-way placement and no number. No true-or-false prior in the file is .50/.50. Refusal rules: an unanswered exercise leaves the numerator, the denominator and the chance term together; an empty sitting scores exactly zero on every figure; a sitting with fewer than twenty-three of the thirty-eight exercises answered is not reported, and the refusal is printed where the ladder and the figures would have been. A careless-responding count is computed for the operator and never shown to the respondent as a judgement. Legal: no code number from any code set appears anywhere in this instrument, no code list is printed, and every exercise describes a coding decision in words. This instrument is not affiliated with, endorsed by or derived from the World Health Organization, any national coding authority, any professional association, any certifying body, any payer or any software vendor, and it names none of them except the one attribution in the sources below. It is jurisdiction-neutral: every exercise states the rule it applies as the guideline your organisation follows, and no exercise depends on one country's programme rules. It is not a coding credential, does not qualify anybody to code for submission, and audits no real record; every note is invented, and no real patient, clinician, hospital or payer is described. Sources drawn on: the World Health Organization's instruction manual to the International Statistical Classification of Diseases and Related Health Problems, for the conventions and the definition of the main condition (the classification and its name belong to the World Health Organization; no affiliation or endorsement is implied); the public definition of the principal diagnosis as the condition established after study to be chiefly responsible for the admission, as used in hospital statistical reporting since the Uniform Hospital Discharge Data Set (1985); the public compliant-query practice of listing clinical indicators and offering an open set of options, as described in professional guidance on documentation queries (2008 onward, revised 2013, 2019 and 2022); Cheng, Gilchrist, Robinson and Paul, The risk and consequences of clinical miscoding due to inadequate medical documentation (2009); Campbell, Campbell, Grimshaw and Walker, A systematic review of discharge coding accuracy (2001); Burns, Rigby, Mamidanna and others, Systematic review of discharge coding accuracy (2012), for the size and direction of coding error; O'Malley, Cook, Price and others, Measuring diagnoses (2005), for the sources of error along the documentation-to-code path; Dixon, Sanderson, Elliott and others, Assessment of the reproducibility of clinical coding in routinely collected hospital activity data (1998); Nouraei, Hudovsky, Frampton and others, A multidisciplinary audit of clinical coding accuracy (2015), for the internal audit as a control; Reason, Human Error (1990), and Hollnagel, Barriers and Accident Prevention (2004), for the layered-defence model behind the escape ladder; Macmillan and Creelman, Detection Theory: A User's Guide (2005), for the two-error framing; Gollwitzer and Sheeran, Implementation intentions and goal achievement, a meta-analysis (2006), for the if-then action; and Haladyna, Downing and Rodriguez (2002) for the item-writing rules. All exercises are original works written for this instrument. No commercial instrument's items or name are used or implied, and no code set's numbers are reproduced.