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, 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.
Operating proof
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.
Practice context, provider setup, and claim readiness sit in front of the work, not behind it. A global pre-submission scrubber holds lines before they file, with the reason in plain English, and authorization and referral requirements can be authored per payer.
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.
ERA review queues hold lines that need a decision: write-off variance, recoupment, secondary not posted, provider adjustment. Denials and appeals share the same workflow surface as posting. Underpayment review and the recovery workspace sit on that surface too, and are turned on book by book during onboarding.
Owners see A/R aging, provider production, practice-level activity, and client reporting from one workspace. Audit logs are retained seven years, beyond the six-year documentation retention minimum in 45 CFR §164.316(b)(2)(i).
Surfaces
Billing-company control across practices requires four things at once: easy practice switching, shared queues, role-based permissions, and a migration that does not lose your history.
Switch client practices from the workspace switcher, in the same session. 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.
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.
Restrict a biller to specific practices and providers. Onboard an offshore poster against four clients without exposing the other four.
The Medi team runs each client cutover: exports, re-enrollment through the clearinghouse, reporting needs, and a plan for open A/R. History and open balances land as a read-only historical ledger, preserved to the cent and visible beside live work, and stay out of active A/R, aging, and statements until you promote a claim on a dated action. Plan on about one business day per practice once inputs are ready.
Read the Tebra migration guideFAQ
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.
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 does not connect to clinical systems. Charges reach Medi through the claim wizard or a file import of patients, charges, and payments.
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.
