Scope for each practice is confirmed in the engagement agreement, including systems, payers, and queues.
Unsupported codes create both lost revenue and audit risk
Undercoding leaves allowed money unbilled. Overcoding and copied review-of-systems language create refund and audit exposure. Many practices rely on a superbills favorite code because the schedule is full. Coding support reads the note that was actually written, applies current code definitions, and sends a short query instead of guessing a level of service.
What the work includes
- Diagnosis coding in ICD-10-CM from the documented condition
- CPT and HCPCS assignment for visits, procedures, and supplies the note supports
- Modifier review, including laterality, distinct service, and professional-component questions
- NCCI and medically unlikely edit awareness before the claim is released
- Provider queries when a level of service or a procedure is not supported
- Feedback on documentation patterns that repeatedly block a code
How the work moves
Step 1
Read the encounter, not the favorite code
The coder starts from the signed note, the order, and the captured charge. A superbill is a clue, not an instruction to ignore the record.
Step 2
Assign codes and modifiers
Diagnoses are specific to the level the note supports. Procedures include the approach and laterality the document describes. Unspecified codes are used when the note is unspecified, then queried if specificity would change payment or medical necessity.
Step 3
Query once, clearly
A query asks for the missing fact. It does not suggest a diagnosis the clinician did not assess. The response is dated and stored with the encounter.
Step 4
Release or hold
Supported encounters move to claim edits. Held encounters are visible so they do not age as unbilled mystery charges.
Operational benefits
- Charges that match the record a reviewer would read
- Fewer downcodes and medical-necessity denials caused by vague diagnosis codes
- A query habit instead of a silent guess
- Specialty-specific edit focus rather than one generic code list
Common challenges
- E/M level selection depends on the guideline the payer expects and on the note's actual content
- Copied templates make notes look complete when the exam was narrow
- Add-on codes and bundling edits change by code pair
- Coders cannot invent documentation that was never created
Technology
Coding can happen in the EHR's encoder or a standalone tool the practice already licenses. Suggestions from an encoder are reviewed by a person. We do not describe an automated code assignment as final.
Where specialty changes the work
Family medicine coding turns on E/M, prevention, and small procedures. Orthopedics turns on globals and fracture care. Behavioral health turns on time. The specialty pages hold those differences. This service is the coding discipline underneath them.
Questions
Will you code higher to increase payment?
No. The code has to match the documentation and the definition. If the note supports a higher level than the clinician selected, we query. We do not change the level without support.
Do you offer a certified coding credential as a company badge?
Individual coders may hold credentials. This website does not claim an organizational certification. Staffing is described by role during an engagement, not by invented biographies.
Can you code from a superbill only?
A superbill can start the charge. Final codes for anything beyond a straightforward encounter need the note. Procedure coding without the procedure note is a hold, not a guess.