Medical billing
Day-to-day claim work with the upstream conditions that create denials kept in view.
Medical billing at OneSource is a visible, accountable workflow. We run the claim lifecycle while paying attention to enrollment status, EHR defaults, authorization pathways, clearinghouse edits, and payer behavior that can create repeat failures.
Photo: Unsplash
How billing works here
Claim work with the upstream conditions kept in view
What the work typically includes
Claim creation, review, scrubbing, and submission; payment posting and reconciliation; ERA/EFT enrollment and workflow support; denial analysis and resolution; appeals; patient financial workflows; payer follow-up; and reporting subject to system capabilities. When credentialing is included in the engagement, enrollment work stays tied to claim readiness rather than living in a separate silo.
Clean-claim setup and submission
Still fixing the same edits? Useful billing work often includes rebuilding charge templates, place-of-service and modifier defaults, taxonomy mapping, and authorization capture so fewer problems are inherited by the claim queue. Vendors that only submit charges leave practices in rework. OneSource treats configuration and denial prevention as part of revenue cycle execution.
A/R recovery without disrupting care
Behind on collections or cleaning up aging claims? We identify bottlenecks, resubmit denied claims, and pursue unresolved balances to bring revenue current — without turning the clinic into a forever fire drill. Modest onboarding cleanup is often part of the relationship; large forensic backlogs can be scoped when needed.
Billing capabilities in scope
Core claim, remittance, denial, and patient-financial work as part of connected revenue cycle support.
Claims management
Accurate coding support, timely submissions, denial follow-up, and day-to-day claim work with the precision of an internal department — without building that department from scratch.
Denial management & appeals
Review, correct, and resubmit rejected claims. Custom appeal work when a denial needs more than a quick fix, so payable work stays visible and active.
A/R recovery & cleanup
Identify bottlenecks, resubmit denied claims, and pursue unresolved balances. Onboarding cleanup may be included for modest scopes or scoped separately when the backlog is large.
Patient statements & support
Patient billing communication with clarity, understandable statements, and professional handling of billing questions so front-desk staff have support.
Prior authorization support
Payer back-and-forth for coverage and pre-approvals, plus help configuring capture pathways so authorizations are captured before they become a denial pattern.
Analytics & reporting
Reporting subject to system capabilities — collections, aging, payer mix, denial trends, and related operational views that help you see what to do next rather than stare at noise.
Complex & specialty billing contexts
Where operationally relevant, work may involve high-complexity treatment workflows, group or intensive outpatient coding contexts, elective or cash-pay situations, and other specialized billing patterns. These are areas of experience, with scope confirmed for each engagement.
Root cause
Root-cause analysis is the core workflow
When the same rejection pattern returns, we ask both how to resolve the claim and what setup is producing the pattern. That can mean taxonomy or rendering-provider linkage, place-of-service and modifier defaults, missing authorization capture, stale CAQH details, plan mapping, or an unowned clearinghouse edit. Root-cause analysis turns recurring denials into prevention rules where the system allows it.
Specialty contexts
Same root-cause posture across behavioral health depth and selective outpatient specialties.
Specialty and high-complexity contexts
Behavioral health depth is a major area of experience — including telehealth modifiers, Medicaid ASO quirks, medication management add-ons, Spravato, and group/IOP-style workflows when they are in scope. Other outpatient specialties get the same root-cause approach: procedures, pathology, therapy utilization, and cash-pay adjacent pathways are handled with clear attention to payer reality.
EHR configuration stays attached to billing
If your friction is a charge template, telehealth default, or authorization capture problem, it belongs in the main workflow discussion. See Practice operations for the full systems section (Tebra/Kareo, TherapyNotes, eClinicalWorks, and more) and how configuration, training, and consulting connect to cash.
Claim ownership
What direct claim ownership means here
We work inside EHR claim settings, payer portals, clearinghouse tools, and denial queues you authorize. Core PHI work stays in our controlled environment. Standard RCM agreements are month-to-month with 30 days’ written notice. Most practices do not pay an onboarding fee; implementation fees apply only when specifically established for the engagement.
- Work inside the EHR, payer portals, and clearinghouse tools you authorize
- No offshore handling of PHI
- Month-to-month agreements; most practices do not pay an onboarding fee
Connected chain
How billing connects to credentialing and practice operations
Billing execution is central. Credentialing and practice-operations support help prevent panel timing, ERA/EFT setup, charge-template, eligibility, and workflow failures from reaching the claim queue. If you are evaluating fit, read those pages next. If behavioral health is your specialty, the mental health billing page goes deeper on that context.
- Credentialing stays tied to claim readiness
- Practice operations keeps templates and auth capture accurate
- OneSource OS keeps related work together while people retain accountability
Software
How this relates to OneSource OS
OneSource RCM is the people doing and advising on this work today. OneSource OS is software being shaped around the same connected operating reality, so enrollment status, configuration, and follow-through do not have to live in fragmented trackers. The product is designed to support accountable RCM work.
Claim lifecycle
Acceptance is not the same as paid.
Submission, remittance, posting, and denial resolution stay owned as one sequence — with root-cause work when the same failure repeats.
Recurring denials
When the same denial returns, fix the source.
Templates, modifiers, enrollment gaps, and auth capture produce the pattern. Resubmits without diagnosis refill the queue.
Photo: Unsplash
Follow-through
Remittance and AR with ownership — not polite neglect.
Open balances are worked with clear ownership, progress notes, and explicit practice decisions when needed.
Describe the billing problem behind the balance
Include the specialty, systems, payer mix, denial pattern, and where follow-through is breaking down.