The operating layer between your client practices and the payers.
Medi’s queues, posting rules, and deadline math come from billers working live claims against real payers, not from a product spec. Where a module is still in controlled rollout, this site says so instead of listing it next to the parts that run every day.
Turn auto-posting on and clean remits post themselves. Anything that doesn’t match lands in a review queue with the reason attached, so your team spends the day on the money that’s actually missing instead of keying EOBs.
See how it runs →Your appeals lead sees the denials. Your posters see the payments. Your follow-up team sees the aged claims. Same screen, different lens.
Tour the queue →In our experience denials die of neglect more often than merit. Every one lands in a worklist with its appeal deadline attached, most urgent first, so the ones worth fighting get fought in time.
See the denial lifecycle →A claim nobody noticed. A short-pay nobody caught. A check that won’t balance. Medi flags each one and brings the paperwork.
No acknowledgment in seven days? It surfaces for resubmission. Payer says they have no record of it? You find out now, not at day 89.
Payers short-pay quietly. With underpayment detection turned on and your fee schedules loaded, each posted line is compared against what your contract says they owe, and anything short gets flagged with the proof attached. Underpayment detection is in controlled rollout, turned on during onboarding rather than by default.
No more hunting for the missing $14 at five o’clock. Every dollar on the check has to land somewhere before it posts, and any line snaps back to exactly what the payer said with one click.
Switching shouldn’t strand your history in the old system. Migration guides: Tebra · AdvancedMD · CollaborateMD
Walk through practices, users, permissions, claims, ERAs, and operational queues before your team depends on a live workspace.
Open the guide → EDI / X12Medi starts at $1.00 per claim and moves to $0.90 and then $0.80 at the volume marks published on the pricing page, with the full schedule at /pricing. There is no monthly fee, no per-practice fee, and no per-provider fee, and ERA posting is included in the claim price. Usage add-ons are priced separately: eligibility is $0.25 and claim status is $0.20. COB inquiry, insurance discovery, and claim attachments are $1.50 each and are in controlled rollout, switched on per billing company at onboarding. 277CA acknowledgments and PDF generation cost nothing extra.
Medi is built for third-party billing companies that bill for more than one practice. Every client practice lives in one workspace, so a biller moves between clients from a single switcher instead of logging in and out of separate systems. A practice billing in-house can run on Medi, but the multi-practice parts (cross-client work queues, per-practice access limits) are why it exists.
No. Medi is the operating layer between your client practices and the clearinghouse and payer rails, not a replacement for the rails. Claims are built and scrubbed in Medi, then transmitted as 837P professional claims through your clearinghouse. The 277CA acknowledgments and 835 remits come back into Medi, where clean remits post automatically once you turn auto-posting on, exceptions land in a review queue, and follow-up work surfaces when a payer goes quiet or short-pays.
Migration is a concierge service the Medi team runs for you, not self-serve tooling. It is free with a 12-month commitment. Without one it is $100 per practice, capped at $3,000 no matter how many practices you move. Your history and open balances do come across, as a read-only historical ledger preserved to the cent and visible beside live work. Those records stay out of active A/R, aging, and statements until you deliberately promote a claim on a dated action, so nothing is stranded in the old system and nothing pollutes the new book. Payer enrollment is re-enrollment through the clearinghouse rather than an import. Plan on about one business day per practice once exports and enrollment inputs are ready. There is no early-termination fee.
Medi operates as a HIPAA business associate, which is a program posture rather than a certification. PHI sits behind authenticated sessions and server-side permission checks, every access is written to a user-attributable audit log retained seven years (beyond the six-year documentation retention minimum in 45 CFR 164.316(b)(2)(i)), and SSNs are encrypted at rest. A BAA is signed before any PHI workflow goes live, and subprocessors are documented during implementation review. Medi does not claim a HITRUST or SOC 2 certification.
Join the Medi waitlist. When your spot opens we’ll walk through your billing team’s daily workflows and show how client practices, queues, claims, ERAs, denials, and follow-up fit in Medi.
