Coding sits between the visit and the claim. If it is slow, cash is slow. If it is wrong, the claim is denied or, worse, paid and later recouped. Most practices feel this as a backlog that never quite clears and a steady trickle of coding-related denials that nobody has time to analyze.
Revelrex coding works from your documentation, inside your EMR where possible. Each encounter is coded by a certified coder, a sample is reviewed for quality, and anything the documentation does not support goes back to the provider as a clear question rather than a guess.
Practices that benefit
- Practices whose providers code their own visits and want an independent review before claims go out.
- Practices with a coding backlog or a coder on leave.
- Specialty groups with procedure-heavy encounters that need modifier accuracy.
- Organizations that want coding quality measured, not assumed.
What usually goes wrong
Encounters waiting to be coded
A visit that is not coded within a few days is a claim that goes out late. Backlogs push charges across months and distort your reporting.
Coding that the note does not support
Evaluation and management levels chosen by habit, procedures billed without the documentation to match, and diagnoses that never reached the note create denials and audit risk.
Missed modifiers and bundling rules
Same-day procedures with E/M visits, bilateral procedures and NCCI edits are where clean claims quietly become rejections.
No feedback loop
Providers rarely learn which of their patterns cause denials, so the same issue repeats every month.
The actual work
Documentation review
We read the signed note, the orders and any procedure report for the encounter, not just the superbill.
Diagnosis and procedure coding
ICD-10-CM codes to the highest specificity the documentation supports, CPT and HCPCS codes for services performed, with modifiers, units and place of service applied correctly.
E/M level selection
Levels are selected under the current medical decision making or time rules, and the reason is recorded so it can be defended.
Provider queries
When the note is missing something the code needs (laterality, acuity, a signature), we send a short, specific query. We do not code what is not documented.
Coding quality review
A second coder reviews a defined sample of each coder's work every month. Accuracy is reported to you.
Completion tracking
Every encounter has a status: received, coded, queried, complete. You can see how many encounters are waiting and how old they are.
Escalation
Repeated documentation gaps or unusual patterns are escalated to the practice with examples, so they can be fixed at the source.
What is included
- Coding of professional encounters (office, telehealth, procedures, preventive visits) from documentation.
- Provider queries and re-coding after the provider responds.
- Monthly coding accuracy report from the quality review sample.
- Coding-related denial feedback when Revelrex also handles billing.
Not included
- Retrospective audits of previously submitted claims (see RCM Audit).
- Provider education workshops (available separately).
- Facility or inpatient coding.
- Coding audits of historical claims, education sessions for providers and chart abstraction for risk adjustment programs are quoted separately.
What your practice needs to provide
- The date of service from which Revelrex becomes responsible for coding.
- Read access to the EMR or a secure export of encounter documentation.
- A provider contact who answers queries, ideally within two business days.
- Your fee schedule and any payer-specific coding policies you already follow.
Step by step
- 1
Onboarding
We agree the start date of service, the encounter types in scope and how documentation will reach us.
- 2
Daily coding
Encounters signed by the provider are coded, normally within two business days.
- 3
Queries
Encounters needing clarification are queried. The encounter stays in "queried" until the provider responds.
- 4
Quality review
A sample is reviewed by a second coder. Corrections are made before the claim goes out.
- 5
Reporting
Monthly report: encounters coded, turnaround, query rate, accuracy, and patterns worth fixing.
What you receive
Coded encounters ready for claim submission, inside your system.
Query log with provider responses.
Monthly coding volume, turnaround and accuracy report.
A short list of documentation improvements with examples from your own charts.
Add Coding to your Service Cart
A written proposal follows within two business days.
Frequently asked
Do your coders work inside our EMR?
Whenever the practice can create a delegated user for Revelrex, yes. Coding inside the EMR avoids exports and keeps the audit trail in one place. If access is not possible, we work from a secure document export.
How fast are encounters coded?
Our standard is two business days from provider signature. Encounters that require a query wait for the provider's answer; the query rate is reported so you can see where documentation slows things down.
What if a provider disagrees with a code?
We explain the guideline behind the code. If the provider documents additional detail that supports a different code, we update it. The final code is always tied to what is in the note.
Are your coders certified?
Coding is performed by certified professional coders. Specialty encounters are assigned to coders with experience in that specialty.
Can you start with a backlog?
Yes. Backlog encounters are coded at the same per-encounter rate and tracked separately so you can see the backlog shrink.