Intake and scrub
Practice context, provider setup, payer rules, and claim readiness sit in front of the work, not behind it. Held lines surface before submission, with the reason in plain English.
Operations
Billing-company operations.
Medi is built for the billing company that runs revenue cycle work as its core product. Practice context, cross-practice queues, permissions, payment workflows, and audit logging are organized around the billing company as the tenant, not bolted onto a practice-management system.
Operating model
One workspace across client practices.
One workspace, every client, one queue. Owners, managers, billers, posters, denial leads, and follow-up staff work from shared queues. Practice context controls access and reporting automatically, so cross-practice visibility never costs you record-level control.
Practice context never blocks cross-practice workQueues route work by action, not by which login is openPermissions match billing-company staffing patterns
Operating proof
Claim-to-cash operating map.
From scrub to posting to reporting. Each step references the specific surfaces that handle it inside Medi, including the clearinghouse handoff, ERA exception queue, and audit-log retention.
Submit and acknowledge
Claims hit Stedi as the clearinghouse. 277CA acknowledgments and payer rejections route back to the same queue, so follow-up ownership is one click from the original submission.
Post, deny, or recover
ERA review queues hold lines that need a decision: write-off variance, recoupment, secondary not posted, PLB adjustment. Denials, appeals, underpayment review, and recovery work share the same workflow surface as posting.
Report and control
Owners see A/R aging, staffing throughput, practice-level activity, and client reporting from one workspace. Audit logs cover seven years per HIPAA Security Rule §164.312(b).
Surfaces
The day-to-day surfaces Medi is designed around.
Billing-company control across practices requires four things at once: easy practice switching, shared queues, role-based permissions, and migration tooling that does not lose open A/R.
Practice context without the login dance
Switch client practices with one keystroke. Permissions, reporting, and audit logs stay scoped to the practice automatically, so a poster working five clients does not log in and out of five accounts.
Cross-practice work queues
One queue routes submissions, payer follow-up, ERAs, denials, aging, and enrollment work by what needs action, not by which Tebra-style instance is open. The denial lead sees every client's denials; the poster sees every client's payment exceptions.
Permissions that match how billing companies hire
Restrict a biller to specific practices and providers. Onboard an offshore poster against four clients without exposing the other four. Roles map to billing-company staffing, not to a practice's user model.
Migration tooling that protects open balances
Plan each client cutover against open A/R, payer enrollment status, reporting needs, and parallel-run reconciliation. The Tebra migration guide walks the playbook for the most common move.
Workflow coverage
The workstreams that share one operating picture.
837P and 837I claim scrub review before submission
277CA acknowledgment tracking and payer response follow-up
835 ERA review, line matching, and posting decisions on one screen
Denials, appeals, recovery work, and underpayment flags routed by payer and value
A/R aging, client reporting, and owner-level visibility across the full book
FAQ
Common operator questions.
How is this different from a practice-management product that supports billing companies?
A practice-management product treats the practice as the tenant and bolts billing-company workflows on top. Medi treats the billing company as the workspace and treats practices as scoped tenants inside it. The differences show up in permissioning, cross-practice queues, pricing structure, and what gets duplicated when you add the eleventh client.
Does Medi replace an EHR or scheduling system?
No. Medi is the billing layer. Most billing-company clients already use an EHR (Athena, eClinicalWorks, Epic, or a specialty system) and want a billing platform that does not duplicate their clinical workflow. Medi connects to clinical data through HL7 and FHIR where the integration is needed for billing context.
What does the workspace look like for an offshore biller?
The same workspace as the US-based team, scoped to the practices and providers their role allows. Practice-level access restriction is native, so an offshore poster handling four clients does not see the other four. Audit logging captures every PHI access for compliance review.