The visit is a routine follow-up for knee pain. Halfway down the note, the problem list carries a chronic kidney disease entry carried forward from last year. The exam covers the knee. The plan covers the knee. No lab is reviewed, no medication is adjusted, and nobody writes a word about kidney function. The coder captured the CKD code anyway. Deciding whether it stands, chart after chart and with a reason you can defend, is what remote HCC coding auditor jobs are about. This one is full-time, work from home, and pays $78,000 per year (USD). Residence anywhere is fine; the charts themselves follow US Medicare risk adjustment rules, and a few clients add residency terms of their own.
MEAT stands for Monitored, Evaluated, Assessed or Treated. A diagnosis coded from a face-to-face encounter needs at least one of those elements documented by an acceptable provider in that note.
In the knee visit above, none of the four appears for CKD, so the code fails. If the provider had written "CKD stage 3, will recheck kidney panel next visit," it would pass. Some organizations add internal criteria, such as TAMPER. You audit to the client's written policy and note which standard you applied.
Medicare Advantage plans receive payments adjusted for how sick their members are expected to be. Diagnoses map to Hierarchical Condition Categories, and the model uses those categories, along with demographic factors, to estimate expected cost. Within a hierarchy the more severe condition outranks the milder one, so one wrong specificity choice can move a member's category.
CMS revises the model over time. Categories get added, dropped or remapped, and a code that counted under one version may not count under the next. Auditors keep track of which version applies to which service year and read the annual updates and coding guidance closely. Expert command of ICD-10-CM sits underneath all of it.
Strip any HCC coding auditor job description down and this is what is left. Work usually arrives as a sample: a random pull from a coder's recent output, a targeted set for one condition such as vascular disease or major depression, or a pre-submission review before a plan sends data. You open each chart in the risk adjustment software, read the full encounter note, and compare every submitted code against the documentation. An encoder helps you confirm code selection, check Excludes notes and settle specificity questions.
Each finding gets recorded against the coder's result: agree, delete, add, or change. The tool or a scoring sheet then calculates accuracy, often split between code-level and HCC-level results. A hurried auditor who misses an error does more damage than a slow coder.
An overcoded diagnosis creates compliance exposure, because an unsupported HCC can inflate a risk score. An undercoded one leaves a real, documented condition out of the record. Both count as errors, and both go in your findings with a citation to the note.
Gray cases need the most care. A diagnosis in the history section with a current medication listed elsewhere. A "history of" cancer that the coder treated as active. A signature missing credentials. When documentation is ambiguous, you follow the written guidelines and, where a provider query process exists, you recommend one instead of guessing in either direction.
Being fair to coders means showing your work. Every error you mark should carry the page reference, the rule behind it and the correct code. Coders should have a way to rebut, and good auditors welcome it, because sometimes the auditor missed a line in an addendum.
When the same mistake shows up across several charts, the fix is education rather than another round of deductions. You might write a short tip sheet on coding diabetes with complications, or join a call to walk through three anonymized examples. Coders who feel ambushed hide uncertainty; coders who trust the process ask questions early.
At the end of a cycle you prepare summaries for the risk adjustment quality and compliance teams. These pull together accuracy by coder, the categories with the most deletions, recurring documentation gaps by provider group, and any finding that may need escalation. Write them plainly. A compliance reader needs to know what was reviewed, which standard was applied, what was found and what you recommend. Protected health information stays inside approved systems, under HIPAA and the client's own access rules.
Expect to provide dual monitors, since a chart on one screen and the coding tool on the other is the only practical way to audit. You will need encoder access, either supplied through the client's platform or arranged per the employer's instructions, plus a secure, stable internet connection. Many clients also require a room to yourself while charts are open, a VPN or virtual desktop login, and a computer that meets their security settings. Get the split of who supplies what in writing before your start date.
For HCC coding auditor certification, a CRC, CPC or CCS is required. The AAPC Certified Risk Adjustment Coder credential is the most direct fit, since its exam centers on risk adjustment documentation and HCC rules, but CPC and CCS holders are also eligible. An HCC coding auditor course or CRC prep class can help, though the credential matters more than which course you took.
Experience is the bigger gate. This role calls for 3 to 5 years of risk adjustment HCC coding plus prior audit or QA experience. The usual route into auditing is coding at volume, posting consistently high accuracy scores, then taking on peer reviews or second-level QA before applying. Employers almost never fill HCC coding auditor jobs with no experience behind the applicant, and entry level auditor openings are scarce; a new coder should start in production coding and build the record.
For an HCC coding auditor resume, list your credential, the service years and models you coded under, your audit volume, and your accuracy history. Typical HCC coding auditor interview questions include a mock chart and how you would handle a coder who disputes your finding.
This position's HCC coding auditor salary per year is $78,000 USD, full-time. Auditing roles like this exist at risk adjustment vendors, Medicare Advantage health plans, provider groups and value-based care organizations, coding service companies, and consulting firms that perform pre-submission or retrospective reviews. Postings for HCC coding auditor work from home jobs differ on productivity targets and hours, so ask about both before accepting an offer.
An HCC coder reads a chart and asks what can be captured. An auditor reads the same chart and asks whether what was captured holds up, and whether anything supported was left out. The coder works for volume and accuracy. The auditor works for accuracy and defensibility, and also carries responsibility for teaching, scoring and reporting. The core HCC coding auditor skills are guideline recall, careful reading and the ability to explain a deduction without making it personal.
Natural language processing and AI coding tools increasingly pre-read charts and suggest diagnoses before a person sees them. That shifts some work from first-pass coding toward validation. Software can flag a term, but it often struggles to judge whether a condition was actually addressed in that encounter, and plans remain accountable for what they submit. Human review of MEAT support stays important, and an auditor who understands how these tools make mistakes is well placed to check their output. Expect the tools and the rules around them to keep changing.