How the Platform Works
One Mid-Revenue Cycle Operating Platform. Every Department. Real Time.
Not a suite of modules that happen to share a login. A single platform where every module continuously communicates with every other module — covering the mid-revenue cycle end to end, while the patient is still admitted.
In plain language
MGear is the real-time mid-revenue cycle operating platform for hospitals. It connects utilization management, authorization, peer-to-peer reviews, denials, payer communication and analytics into one process — and automates the routine steps in them, so every department sees where each case stands while the patient is still admitted. It works the same way for an academic medical center, a community hospital or a critical access hospital: the hospital gains live visibility into processes that today run department by department, out of view.
Product Tour
MGear in 54 seconds
How a case moves through the platform: utilization review, payer communication, denials and appeals, and analytics.
Chapters
One Stay
From the review to the resolution
Each stage is one module handing the case to the next, while the patient is still admitted and the outcome can still change.
The patient is still admitted
1.Reviewed
Utilization Management
2.Authorized
Authorization Management
3.Payer notified
Payer Communication
4.Escalated
P2P and Denial Management
5.Resolved before discharge
Analytics
Illustrative — sample data.
The Flagship Chain
The chain, in full
This is the flagship example, run start to finish — from the review that starts it to the resolution before discharge.
- 1
Utilization Management completes the review and the authorization request starts automatically, with no second data-entry step.
- 2
The authorization is delayed: it has not come back and the stay is still running.
- 3
Payer Communication is notified the moment the delay is detected — not at the next status meeting.
- 4
Payor Grid verifies that specific payer's requirements automatically: notification windows, documentation format, submission endpoints.
- 5
Analytics updates its dashboards in real time, so the delay is visible to anyone watching, not buried until month-end.
- 6
Quality identifies this as a workflow delay, not just a missed authorization — the pattern gets tracked, not just the instance.
- 7
MGear works out what is holding it up — for example, medical records that were never sent to the payer — then recommends the fix, or applies it automatically where it can.
- 8
The manager is alerted to anything MGear cannot resolve on its own.
- 9
The team resolves it before discharge — because the patient is still in the building, the outcome can still change.
What it earns: increased authorization efficiency, fewer preventable denials, and fewer avoidable days. The delay is caught and fixed while the stay is still open — instead of surfacing at a payer meeting weeks later, when the outcome can no longer change.
And if the payer denies
The same chain carries on without anyone re-keying the case.
- 1
The denial is recorded in Authorizations while the patient is still in-house.
- 2
MGear checks whether the case is appealable, and whether this payer allows a concurrent peer-to-peer.
- 3
A P2P case is created and scheduled with the physician advisor, and the appeal process starts alongside it.
- 4
The advisor works the call and the outcome is captured. Overturned: the stay is authorized and no appeal is needed. Upheld: an appeal is drafted automatically, deep-linked back into the case that produced it.
- 5
If the payer is right and the case does not meet criteria, MGear recommends a lower level of care — a change of admission status, or billing at a lower level. The physician makes the call.
- 6
Overturn rates and advisor performance update in Analytics.
What it earns: denial prevention, fewer avoidable days, and faster appeal turnaround.
ROI Estimator
Estimate Your Opportunity Today
Enter your own denial write-off figures and targets below to estimate the financial impact for your organization.
Enter your own annual write-off figures — MGear doesn't supply those numbers here. This just does the arithmetic on the amounts and targets you provide.
Lack of Clinicals
No Authorization
Level of Care (Inpatient)
Estimated Improvement
Monthly improvement
$0
Annual improvement
$0
This is a planning estimate based on the figures and targets you enter — not a guarantee of results. *On average, MGear's workflow has been able to decrease denials by 30–40% in year one.
Eight Real Chains
Eight chains. Pick one.
The authorization delay above is one real chain out of eight. Every one of them is actual behavior in the working product, not an illustration built to look good. Pick a trigger and watch it move.
Trigger: An authorization has not come back and the stay is still running.
What it earns: Increased authorization efficiency, fewer preventable denials, and fewer avoidable days — the delay is caught and fixed while the stay is still open, instead of surfacing at a payer meeting weeks later, when the outcome can no longer change.
The Whole System
The whole system, one picture
Extend that same chain across every department that touches revenue, and this is the platform. One frame holds all of it: the patient is still admitted. A tool that shows you this after discharge is a dashboard. This shows it while the outcome can still change. Click any box to see exactly what it receives and sends.
Productivity and Alerts each receive from across the platform rather than one specific box — click either one to see exactly what feeds it.
Click any box to see what it receives and sends.
Why MGear
Why MGear, if you already have something
“We already have Epic” (or Cerner, or another EHR).
Your EHR is the system of record — documentation, scheduling, the clinical chart. Coordinating authorizations, denials and payer communication across departments is a different job. You can export reports and reconcile them yourself in a BI tool, but that typically takes months to build, and it still only tells you what already happened. MGear doesn't replace your EHR; it integrates with it via FHIR and HL7 and sits on top as the operational coordination layer. It automates the workflows — not just the analytics — noticing that an authorization is stalling and getting the right department moving on it in real time, while your EHR keeps the chart.
“We already outsource this.”
An outsourced UM or denials vendor does the same work described above — but usually alone, disconnected from the other nine departments. You get a report back after the fact instead of a live alert while the stay is still open, and typically only the summary the vendor chooses to report — not live, case-level analytics you can look into yourself. The problem was never that this work wasn't getting done somewhere. It's that nowhere was it connected to everything else protecting the same revenue.
Financial Impact
This chain earns authorization efficiency and fewer preventable denials.
At the platform level, the same coordination pattern is what produces the outcome on the Results page — not a different mechanism, this same chain, run continuously, across a whole program.
ED program additional annual revenue
$5.26MED program net annual impact
$4.87MFrequently asked
See how each module works.
Eleven connected modules, each opening with what it receives and what it sends before anything else.