MEDICAL CODING SERVICES
Clinical Detail, Translated Into Defensible Codes
Accurate coding begins with the medical record, not a claim scrubber. Billing Horizon combines specialty-aligned coding professionals, AI-assisted review, and current code-set guidance to help practices resolve documentation gaps, select supported codes and modifiers, and submit claims with clearer clinical context.
ICD-10-CM · CPT · HCPCS Level II
Specialty-specific review
Human decisions, assisted by technology
Encounter evidence
Reason for visit · Assessment · Procedure note · Time and units
The operating principle: A code should describe the documented service, satisfy the code set’s instructions, and withstand the applicable payer’s review. If those three do not align, the right next step may be a provider query, not a faster submission.
WHERE CODING ACCURACY IS DECIDED
Four Questions Before the Claim Leaves
Each review point answers a different operational question. Together they help reduce avoidable rework without allowing a rule engine to override the record.
01 / DOCUMENTATION
What happened in the encounter?
We compare the assessment, procedure note, time, units, medical necessity, and clinician intent. When a key element is unclear, the coding team routes a specific, nonleading query to the provider.
02 / CODE SET
Which code actually describes it?
ICD-10-CM specificity, CPT descriptors and instructions, HCPCS Level II options, sequencing, and effective dates all matter. A familiar code is not automatically the right code for a new date of service.
03 / MODIFIER
Is the distinction documented?
Modifier use depends on the circumstances of the service and the payer’s rules. A modifier does not make a bundled service separately payable merely because a claim edit permits an override.
04 / PAYER
What will be evaluated downstream?
Coverage policies, NCCI procedure-to-procedure edits, medically unlikely edits, authorization conditions, and contract rules can change how an otherwise correct code is adjudicated.
AI-ASSISTED CODING REVIEW
Use AI to Surface the Pattern. Use People to Interpret It.
AI-assisted checks can highlight inconsistent diagnosis and procedure combinations, missing specificity, modifier patterns, unusual units, and documentation that appears incomplete. A qualified coding professional then reviews the actual record and current guidance before changing the code, querying a clinician, or clearing the exception.
The boundary matters.
The system does not infer an undocumented diagnosis or recommend upcoding to increase payment. Its role is to prioritize review, preserve an audit trail, and help teams learn from recurring exceptions.
EXCEPTION REVIEW
Human review queue
01
Diagnosis specificity
Clinical note has a more detailed finding
Query / review
02
Modifier support
Separate procedural service needs evidence
Review note
03
Unit variance
Claim quantity differs from documented units
Reconcile
04
Repeated edit
Same service line across one payer
Investigate
Illustrative workflow, not live patient data.
One coding framework
60+
specialties supported
Behavioral Health
time · telehealth · service type
Oncology
drug units · administration
Urgent Care
E/M · procedures · site of service
Physical Therapy
timed units · plan of care
Cardiology
diagnostics · interventions
Gastroenterology
endoscopy · pathology
Orthopedics
procedures · laterality
Dermatology
lesions · excisions
Radiology
modality · supervision
Primary Care
E/M · chronic care
SPECIALTY-ALIGNED CODING TEAMS
The Same Code Set Does Not Mean the Same Coding Work
The operational risk changes with the service mix. An infusion claim may turn on drug units and administration sequencing. Therapy billing can hinge on timed-service documentation and discipline-specific rules. Behavioral health has its own time, provider, and telehealth distinctions. We align reviewers with the relevant specialty and escalation path so those details receive attention before submission.
Specialty-specific work instructions and case review
Clear ownership for provider queries and disputed codes
Feedback from denials and audits returned to the coding team
Cross-coverage designed to preserve coding consistency
Tell us about your specialty
CODING PROFESSIONALS & GOVERNANCE
Credentials Matter. Review Discipline Matters More.
Professional credentials such as CPC and CCS indicate formal coding knowledge. In day-to-day operations, that knowledge must be supported by specialty training, code-book access, documented escalation, second-level review, and measured feedback. Verify the specific credentials and staffing assigned to your account during implementation.
01
Case assignment
Route encounters by specialty, complexity, and reviewer scope rather than sending all work into a single undifferentiated queue.
02
Independent checks
Sample coded work for documentation support, code selection, sequencing, and modifier rationale; track findings by category.
03
Provider queries
Use clear, nonleading questions when the record cannot support a coding decision. Record the response and its effect.
04
Closed-loop education
Turn recurring audit and denial findings into work-instruction updates and targeted coaching, then recheck the result.
CONTINUOUS COMPLIANCE MONITORING
A Coding Rule Is Only Useful When It Is Current
Code sets and payment edits do not all change on one calendar. FY 2026 ICD-10-CM guidelines cover October 2025 through September 2026; CPT 2026 Category I additions took effect January 2026; HCPCS Level II and Medicare NCCI edits have quarterly updates. We translate relevant changes into effective-date checks, specialty instructions, and audit criteria.
Our review also distinguishes code validity from coverage and payment. A valid CPT or HCPCS code may still need documentation, medical necessity, authorization, or payer-specific conditions to support reimbursement.
2026 coding calendar
Different sources. Different effective dates.
OCT
ICD-10-CM
FY 2026 guidelines and diagnosis code set
JAN
CPT
2026 Category I code changes effective
QTR
HCPCS Level II
Monitor applicable quarterly files
QTR
NCCI
Procedure-to-procedure and unit edit updates
Sources: CMS FY 2026 ICD-10-CM guidelines · AMA CPT 2026 release · CMS HCPCS updates · CMS NCCI edits. Content is operational, not legal or payer-specific advice.
YOUR EXISTING EMR / EHR
→
CODING WORKFLOW
Encounter note
Documentation review
Charge capture
Code and modifier checks
Provider query
Resolution recorded
Claim status
Denial feedback returned
Configuration depends on your system access and practice workflow.
EMR / EHR TECHNOLOGY INTEGRATION
Work Where the Clinical Evidence Already Lives
During onboarding, we map how notes, orders, charge tickets, diagnoses, and claims move through your existing system. Review queues and access permissions are defined with the practice, not assumed from a product name. The coding team should be able to locate the evidence behind a code and return a clear query without disrupting the clinician’s documentation process.
Where the platform supports it, reconciliation can compare completed encounters with coded charges, submitted claims, and unresolved queries. We validate the exact integration method with your EHR and practice before promising an automated connection.
EMR / EHR systems we can discuss in your workflow
Access and data exchange are assessed for your specific configuration.
Epic
eClinicalWorks
athenahealth
NextGen Healthcare
Oracle Health
ModMed
AdvancedMD
Practice Fusion
Veradigm
MEDITECH
50+ More Platforms
CODING PROFESSIONALS & GOVERNANCE
Credentials Matter. Review Discipline Matters More.
Professional credentials such as CPC and CCS indicate formal coding knowledge. In day-to-day operations, that knowledge must be supported by specialty training, code-book access, documented escalation, second-level review, and measured feedback. Verify the specific credentials and staffing assigned to your account during implementation.
Documentation gaps
Which service lines and providers generate queries, and are the same missing elements recurring?
Audit findings
What proportion of sampled encounters need correction, by code family, specialty, and error type?
Edit & denial trends
Are payer and clearinghouse responses pointing to coding logic, eligibility, authorization, or another cause?
Turnaround visibility
How long do encounters wait for coding, clarification, secondary review, and release to billing?
Issue → Owner → Correction → Recheck
A reporting loop that makes improvement traceable.
A CONTROLLED START
Change Your Coding Support Without Losing Context
We start with a sample of the work the practice actually performs: specialties, encounter types, payer mix, EHR configuration, current query process, aging uncoded charts, and known denial patterns. The implementation plan defines who reviews which encounters, how disagreements are resolved, what gets audited, and how output is released to billing.
Before volume moves, the practice and coding lead agree on documentation standards, review thresholds, turnaround expectations, and escalation contacts. That baseline makes the first weeks measurable rather than a guessing period.
01
Scope the work
Sample encounters, specialties, locations, and current backlog.
02
Map the system
Access, documentation locations, queues, and billing handoffs.
03
Validate decisions
Compare sample coding, resolve differences, and set query rules.
04
Monitor the launch
Review volume, exceptions, audit findings, and claim feedback.
Client Perspective
A Clearer Coding Decision Has Effects Downstream
Coding support earns trust when questions are specific, decisions are documented, and recurring issues lead to clearer guidance for the practice.
A PRACTICE-SPECIFIC CONVERSATION
Where Does Coding Slow Down Your Revenue Cycle?
Tell us your specialty, EHR, service mix, and current concern. We can discuss the right review model, whether your issue begins in documentation or code selection, and what the first implementation checks would look like.
- No patient information needed
- Focused on your actual encounters
- Clear next steps after the discussion
Discuss Your Coding Operation
No obligation. No pressure. Just a practical conversation about your revenue cycle.