Patient status and authorization mismatches
Inpatient, observation, and outpatient services have different coverage rules. Verify eligibility and authorization requirements, document payer responses, and flag status issues before submission.

Hospital billing & revenue cycle management
A hospital claim passes through many hands before it gets paid. We connect patient access, charge capture, coding, claim submission, denials, and payment follow-up into one accountable workflow.
Support for inpatient, outpatient, observation, emergency, surgical, and ancillary services. Built around your hospital's systems, payer mix, and approval process.
Beyond claim submission
Hospital billing depends on accurate patient status, complete clinical documentation, coordinated charge capture, and claims built for the correct payment system. A missing handoff can become a denial, underpayment, patient balance, or delayed cash.
We verify the information behind each claim, track denials and underpayments to their root cause, and show what is pending, paid, or at risk. Front-end errors are corrected before they reach coding. Denial trends go back to the department that can prevent them.

Where revenue leaks
Each leak has a different owner and next action. These are the gaps our hospital billing workflows are designed to surface.
Inpatient, observation, and outpatient services have different coverage rules. Verify eligibility and authorization requirements, document payer responses, and flag status issues before submission.
Review diagnoses, procedures, POA indicators, discharge status, CPT or HCPCS, modifiers, revenue codes, and medical-necessity support against the record before final coding.
Reconcile documented drugs, supplies, implants, imaging, and procedures with departmental charge activity. Trace recurring gaps to chargemaster mappings or interfaces.
Validate applicable edits and modifier support before submission. Categorize denials by root cause so repeated issues reach the department that can fix them.
Compare remittances with expected reimbursement. Prioritize high-value and time-sensitive accounts, then document follow-up through resolution.
Reconcile payer responsibility before transferring balances to patients, particularly after eligibility, deductible, or coordination-of-benefits changes.
Full service coverage
Select the functions your hospital needs. Scope, ownership, and approvals are documented before implementation.
Verify demographics, benefits, coordination of benefits, referrals, and prior authorization requirements.
Align billing with documented inpatient, outpatient, or observation status and the hospital's approved utilization process.
Reconcile departmental activity with documented services, revenue codes, billable items, and interface handoffs.
Review ICD-10-CM, ICD-10-PCS, POA, discharge status, and documentation supporting the assigned MS-DRG when applicable.
Review ICD-10-CM, CPT, HCPCS, modifiers, revenue codes, medical necessity, and applicable payer edits.
Prepare 837I institutional claims and CMS-1450 data. Keep 837P and CMS-1500 professional workflows distinct when in scope.
Check subscriber details, authorization references, codes, modifiers, and payer-specific edits before release.
Post remittances, apply approved adjustments, and investigate payment variances before balances are closed.
Confirm denial causes, gather support, and submit corrected claims or appeals within payer deadlines.
Segment accounts by payer, age, value, status, and filing risk to focus follow-up where it matters.
Confirm payer processing before patient billing; support clear statements and approved payment options.
Report acceptance, denials, A/R aging, variances, write-offs, and follow-up with documented definitions.
Billing pathways
The examples below describe common Medicare facility billing patterns. Commercial, Medicaid, critical access, specialty facility, and contract rules may differ.
| Element | Inpatient facility billing | Outpatient facility billing |
|---|---|---|
| Patient classification | Formal inpatient admission supported by the record and applicable requirements | Outpatient services, including observation when the patient has not been admitted |
| Institutional transaction | 837I electronically; CMS-1450 (UB-04) when paper billing is permitted | 837I electronically; CMS-1450 (UB-04) when paper billing is permitted |
| Common code sets | ICD-10-CM diagnoses and ICD-10-PCS inpatient procedures | ICD-10-CM diagnoses plus CPT and HCPCS services, with applicable modifiers and revenue codes |
| Common Medicare payment method | IPPS payment by MS-DRG for many acute-care hospitals | OPPS payment using APC groupings for many hospital outpatient services |
| Frequent claim risks | Unsupported DRG, missing POA indicator, discharge-status error, documentation gap, or level-of-care denial | Status mismatch, authorization issue, modifier or code edit, medical-necessity denial, charge or revenue-code mismatch |
| Primary review focus | Documentation, principal diagnosis, procedures, POA reporting, DRG assignment, and discharge data | Status, coverage, charge capture, CPT or HCPCS coding, modifiers, revenue codes, and applicable edits |
Professional billing, when included, runs through a separate 837P or CMS-1500 workflow.
Implementation
We establish the baseline, responsibilities, safeguards, and cutover plan before work moves between teams.
Review agreed samples of denials, payer responses, A/R aging, payment variances, and workflow documentation.
Document responsibilities, service levels, escalation paths, system access, reporting definitions, and the BAA before PHI is exchanged.
Map registration through remittance, test claim and report outputs, and confirm approval points with your team.
Move new claims and existing A/R under an agreed cutover plan. Log, assign, and track exceptions.
Review recurring denial causes, payer behavior, documentation needs, and handoffs. Assign and measure corrective actions.
Operations leaders can review
The work must be visible, fit the hospital's environment, and protect patient information throughout the engagement.
Separate claim rejections from payer denials. Define the measurement point for first-pass performance, show aging by payer and account class, and link each number to the accounts and work queues behind it.
Map the engagement to your EHR, patient accounting, clearinghouse, and payer workflows. Confirm access, interfaces, formats, testing responsibilities, and integrations during implementation.
Execute a Business Associate Agreement before PHI access. Document role-based access, protection in transit and at rest, workforce training, audit controls, incident procedures, and access removal during due diligence.
Why Medbilling RCM
A scoped plan covers your service lines, systems, payer mix, volume, and internal approval requirements.
Common questions
They may cover patient access, eligibility and authorization, charge capture, inpatient and outpatient coding, institutional claims, payment posting, denials, A/R, underpayments, patient billing, and reporting. The final scope should state what stays with the hospital.
Facility services usually use the 837I electronic transaction or CMS-1450 (UB-04) paper form. Professional services use 837P or CMS-1500. The claims, code sets, payment rules, and denial risks differ.
Yes, when both are included in scope. Inpatient work may involve ICD-10-CM, ICD-10-PCS, POA, discharge data, and DRGs. Outpatient work may involve CPT, HCPCS, modifiers, revenue codes, observation status, and outpatient edits.
We confirm the payer reason, account history, and filing window. The next step may be a corrected claim, supporting documentation, reconsideration, appeal, or payer follow-up. Root-cause reporting guides upstream fixes.
We compare remittances with expected reimbursement based on approved contract terms, payment methodology, and claim data. Variances are reviewed before an adjustment is accepted.
Pricing depends on facility type, service lines, volume, payer mix, existing A/R, systems, and the functions included. We scope pricing after the revenue assessment.
Timing depends on access, data quality, payer enrollment, clearinghouse setup, security review, interface testing, and A/R transfer. The plan sets milestones for validation, parallel work, cutover, and first reporting.
The engagement is designed around existing hospital technology where practical. We confirm supported systems, access methods, file formats, clearinghouse connections, and interface requirements during scoping.
A Business Associate Agreement is executed before PHI is received. Due diligence should confirm role-based access, encryption, audit controls, training, incident response, and access removal.
Use defined measures such as first-pass acceptance, initial denial rate, denial overturns, days in A/R, A/R over 90 days, net collection rate, underpayment variance, unbilled accounts, write-offs, and patient-balance aging.
Your next step
A hospital revenue assessment can show whether the immediate problem is front-end data, patient status, charge capture, coding, denials, payment variance, or aging follow-up. We review agreed data, explain the findings, and scope support around the work your team needs.
Get a Free Hospital Revenue AssessmentYour next step
A hospital revenue assessment can show whether the problem is front-end data, patient status, charge capture, coding, denials, payment variance, or aging follow-up.