For practices waiting on insurance money

Dental revenue cycle management that checks every claim before it goes out.

Benefits verified before the visit, each claim checked before it is sent, and every denial worked with the appeal drafted for your team to approve.

Connects to your practice software, directly or through Dion’s bridge · Sign in →

Illustrative preview · sample data

MedicalDentalRCM is dental revenue cycle management software for dental and medical practices and multi-location groups that verifies benefits before each visit, checks claims before they go out, and works denials and aged A/R, with the AI doing the legwork inside limits you set and your team approving.

Dental · Medical
both books, one system
AI works · you approve
your limits, your queue
One office or many
per-office queues, one roll-up

The problem

The work was done. The claim is what slipped.

“We found out about the denial at ninety days.”
Denials come in overnight and are read before the morning huddle — why the payer said no, what it wanted, and a drafted appeal.
“Benefits get checked at the desk, with the patient standing there.”
Everyone booked in the coming week is verified before they arrive, dental and medical, primary through tertiary.
“The claim went out without the x-ray.”
Claims are checked before they are filed; one missing what the payer requires waits in Document Pending instead of going out.
“Nobody owns the 120-day bucket.”
Aged A/R is a list of claims, each with an owner and a next action — not a total on a report.

The film

See it work — in under 3 minutes.

Claims checked and sent, a denial appealed, aged A/R with an owner on every claim, and what the patient sees along the way.

Recorded on synthetic data — every name and number is illustrative.

What MedicalDentalRCM does

The whole revenue cycle, in one queue.

Denials, worked every day.

Denials are pulled in daily. Each one gets a root-cause read and a drafted appeal. You set the limits the AI may act within; everything else waits in an approval queue for your team.

Denied claim · appeal drafted

Benefits checked before the visit.

Every day, coverage is verified for patients booked in the coming week — dental and medical, primary through tertiary — and the results land in a verification queue.

Claims checked before they go out.

Each claim is checked for what gets claims rejected before it is filed — dental and medical, one system.

Aging A/R, on a worklist.

Unpaid claims past your follow-up window open a follow-up automatically and escalate as they age; they close themselves when the payer pays.

Patient balances and payments in one place.

Insurance payments recorded in your practice system come across with their claims, and patient balances become collection cases your team reviews before anything is sent.

15+automations that run without anyone starting them
3coverages checked per patient — primary, secondary, tertiary
2books in one system — dental and medical
13exportable reports, from A/R by age to coverage gaps
7other Dion apps it works with
1sign-in across Dion

A working day

The work arrives done. Your people decide.

Most of the revenue cycle is checking, reading and chasing. That part runs before your office opens; what is left for your team is the part that needs judgment.

  1. Overnight

    Your practice system syncs

    Patients, coverages and claims come across from your practice software.

  2. Overnight

    New denials are read

    Each denial is read and an appeal is drafted from what is already on the claim. Inside the limits you set, the AI may act; everything else is queued for a person.

  3. Before the office opens

    The week’s benefits are verified

    Coverage is checked electronically for every patient booked in the next seven days. Anything inactive, missing or unclear lands on the verification queue.

  4. Before the office opens

    Aging claims get an owner

    Unpaid claims past your follow-up window open a follow-up, escalate as they age, and close themselves when the payer pays.

  5. Morning

    The daily digest arrives

    What the platform and your staff did yesterday — counts, amounts and claim numbers. No patient names leave in the email.

  6. Morning huddle

    Your office manager decides

    One approval queue: appeals waiting for sign-off, ledger cases that do not add up, and verifications the payer answered incompletely.

  7. After each visit

    The clinical packet is already there

    From Dion Clinical, the visit’s statement of charges, letter of medical necessity and imaging report arrive as one PDF, with the codes as the clinician accepted them. Your biller builds the claim from it.

What runs on its own

15+ jobs, nobody has to start.

They run office by office, for every practice on the account. The last three are built and start switched off, because they reach patients or patient records — you turn them on.

Your practice system, kept in sync

Overnight and through the day

Patients, coverage, appointments, claims and payments come across without anyone exporting anything.

Payer responses matched to claims

Continuously

Acknowledgements and rejections land on the claim they answer.

Claim status followed

Every day

Claims in flight are checked with the payer, so nobody has to ask.

Denials collected and sorted

Every day

New denials, grouped by why they happened, each with a recommended next step.

Denials read and appeals drafted

Overnight

A drafted appeal for every denial; acted on inside your limits, queued for a person above them.

Appeals sent

Every day

Approved appeals go out, and any that fail to send are tried again.

Benefits verified

Before the office opens

The week ahead verified, dental and medical, primary through tertiary.

Aging claims followed up

Every day

Follow-ups opened, escalated as claims age, and closed on payment.

A/R history kept

Overnight

A dated record of A/R by age, so you can see the trend, not just today.

Chart documents ready for claims

Continuously

Each patient’s documents, perio charts and narratives on hand, so a missing attachment is found at once.

Provider credentials watched

Every day

Expired and soon-to-expire credentials flagged, with an email to your team.

One patient across Dion

Every day

New patients linked to their Dion record, so every Dion app means the same person.

Balances kept in step with Dion Pay

Every day

The balance a patient pays matches the one your team works.

The daily digest

Every morning

Yesterday’s work by the platform and your staff — no patient names in the email.

Claim status shared across Dion

Within minutes

The rest of Dion knows where each claim stands.

Clinical claims received

As soon as they are sent

Claims and insurance packets from Dion Clinical land in the biller’s worklist.

Records retained

Automatically

The audit trail kept for the full retention period, and no longer.

Claim packages prepared ahead

Switch it on

Documentation assembled in advance for claims waiting on records.

Patient statements

Switch it on

Statements drafted for review, or sent automatically for balances that pass your rules.

Insurance requests to new patients

Switch it on

Requests for missing insurance queued for a person to release. Nothing is sent on its own.

AI-assisted or fully autonomous

You choose how far the AI goes.

Each workflow runs in assist mode, where the AI prepares and a person approves, or autonomously, inside limits you set. Where a step always stays with a person, it says so.

The AI completes the work inside limits you set, and escalates the rest.

Denial appealsAutonomous — on, inside your limits

Inside your limits, the appeal goes out to the payer ahead of the filing deadline. Anything above them waits for a person.

Limits you set · approval queue

Correct & resubmitAutonomous — built, switch it on

For the low-risk denial categories you allow, the claim goes back to Ready with the correction notes, under tighter limits. Sending it stays a person’s step.

Only the denial types you allow · stricter limits

Write-offsAssist only

Stays with a person. The agent recommends a write-off and says why; a person decides.

Always a person’s call

Benefits verificationAutonomous — on, inside your limits

Every day, the coming week’s schedule is verified, dental and medical, primary through tertiary; problems land on the queue.

Runs on its own every day

Aging A/R follow-upsAutonomous — on, inside your limits

Follow-ups open for unpaid claims past your window, escalate as they age and close themselves when the payer pays.

Follow-up window · escalation by age

Claim documentationAutonomous — built, switch it on

Claims visibly waiting on records get their documentation package assembled ahead of time.

On / off for your account

Claim submissionAssist only

Stays with a person. Claims are checked and prepared; your biller reviews what the check found and submits.

A person submits

Patient statementsAutonomous — built, switch it on

Automatic mode sends statements for balances that pass your collection rules.

Off · review · automatic — starts off · held while a ledger case is open

New-patient insurance requestsAssist only

Stays with a person. Requests for missing dental and medical insurance are queued; a person releases each one.

Queue only — nothing is sent on its own

How it works

From your practice system to paid claims.

01

Connect your practice system

Supported practice software connects directly or through Dion’s own bridge, set up practice by practice. Your patients, coverages and claims come across.

02

The AI works the queues

Benefits are checked ahead of each visit, claims are checked before they go out, aging claims are opened for follow-up, and every denial gets a read and a drafted appeal.

03

Your team approves

You set the limits. Anything outside them waits in an approval queue for a person on your team — and every action the AI takes is written to the audit log.

In detail

Who does what, line by line.

Benefits verification

Know what is covered before the patient sits down.

Each day, coverage is verified electronically for the coming week’s schedule — every checkable plan in both the dental and the medical book. The result is one verification record, the same one that appears on the patient’s Dion chart.

The AI
Runs the checks, skips anyone verified recently, and flags inactive coverage and answers the payer left incomplete.
Your team
Your front desk works only the flagged patients, and decides what to tell them.

Claims

Checked before it goes out — dental and medical in one system.

Dental and medical claims from one system. The supporting documents a payer asks for are gathered from the chart, and a claim that is missing one waits instead of going out incomplete.

The AI
Checks each claim for what gets claims rejected, assembles the attachment package, and checks the status of claims in flight through the clearinghouse.
Your team
Your biller reviews what the check found and submits.

Denials & appeals

Every denial read the day it lands.

Every denial is read and gets a recommendation — appeal, correct and resubmit, or write off — and a drafted appeal letter built from what is already on the claim, signed electronically by the treating provider.

The AI
Drafts the appeal and, only inside the limits you set, acts on it.
Your team
Everything above those limits waits for a person to approve, edit or reject.

A/R follow-up

Aged A/R as a worklist, not a bucket.

A/R by payer and by age, the same on every screen and every export. Each unpaid claim past your follow-up window carries an owner and a next action, and escalates as it ages.

The AI
Opens, escalates and closes follow-ups on its own as claims age and get paid.
Your team
Your team works the list, and chooses which claims are worth the time.

Patient balances & ledger cases

The office manager’s list of what does not add up.

Patient ledgers are analysed for credits, stale balances and entries that do not reconcile, and each finding becomes a case with a full narrative. A patient with an open case has statements held until it is resolved. Statements can carry a Dion Pay link, turned on per practice.

The AI
Finds the cases, writes up what it found, and holds statements where the balance is in doubt.
Your team
Your office manager investigates, notes the outcome, and releases what may be sent.

Practices and groups

Built for one office or fifty.

The same system runs a single practice and a multi-location group, because every queue, job and permission is per office from the start.

A queue per office
Verification, denials, follow-ups and ledger cases are worked per practice; every nightly job runs practice by practice.
One view across all of them
Switch between offices, or to an all-practices view that aggregates what you are allowed to see.
A group roll-up
A DSO roll-up shows per-office figures and group totals side by side — read-only, because billing stays per office.
Staff scoped to their offices
Billers and account managers are assigned to offices and see only those.
Remittances kept apart
Insurance payments are matched to the office they belong to, so one office never sees another’s money.
Per-office billing identity
Each office keeps its own billing entity, enrolments and payer set-up.

What it takes off your team

Hours back, across every location.

Estimate — change the assumptions to match your practice.

2,035tasks a month handled or prepared by the AI, across 3 locations
186staff hours a month returned
2,228staff hours a year
The assumptions — change them to match your practice.
TaskMinutes by handShare the AI completesHours a month
Benefits checksOne check per visit. The rest are flagged for a person, so they are not counted. %105
Claim checks and documentationChecking a claim and gathering its attachments by hand. %56
Denials read and appeals draftedA person still reviews every draft; only the reading and drafting are counted. %17
Aging follow-ups opened and closedOpening, escalating and closing the follow-up — not the conversation with the payer. %8

Estimate — change the assumptions to match your practice. These are conservative starting points, not measured results: there is no published time-saved figure for MedicalDentalRCM yet.

Works with the rest of Dion

The claim starts in the chart, and the answer goes back to it.

MedicalDentalRCM trades data with seven other Dion apps. Here is what moves in each direction, and what your team sees because of it.

Dion Clinical → MedicalDentalRCM

Claims and post-visit insurance packets — charges, letter of medical necessity and imaging report — arrive with the codes the clinician accepted.

What you seeYour biller opens a packet in the worklist and builds the claim from it — nothing re-typed.

MedicalDentalRCM → Dion Clinical

Eligibility checks on request from the chart, verified benefits, and the list of insurance carriers.

What you seeThe doctor sees the verified plan on the chart; the front desk picks carriers from a list instead of typing them.

MedicalDentalRCM → Dion Pay

The patient’s share once the insurance has paid, and every change to a patient’s balance.

What you seeThe balance a patient pays in Dion Pay matches the ledger your biller works.

Dion Pay → MedicalDentalRCM

Patient payments come back as payment events, recorded against the patient.

What you seeThe biller sees what the patient has already paid before chasing anything.

Dion Membership → MedicalDentalRCM

Membership coverage in force — never treated as an insurance payer. Where the practice has connected Dion Membership, staff can create a single-use invite link that pre-fills the patient’s signup.

What you seePatient responsibility is worked out against the plan the patient actually holds.

Desk, Patient Engagement, Clinical → MedicalDentalRCM

Appointment events from the Dion schedule.

What you seeVerification and follow-up work from the same appointment book everyone else uses.

MedicalDentalRCM → Patient Engagement

A patient-safe view of coverage and benefits for the patient portal.

What you seePatients can check their own insurance without calling the office.

MedicalDentalRCM → Dion Insights

Insurance A/R by age, and adjudicated claims — billed, allowed, paid, written off, and why claims were denied.

What you seeThe owner’s dashboard shows the same A/R the billing team works from.

MedicalDentalRCM → the rest of Dion

Where each claim stands — submitted, paid or denied — shared within minutes, without clinical notes or patient names.

What you seeEvery other Dion app knows where a claim stands without reading anyone’s notes.

Dion console ↔ MedicalDentalRCM

One sign-in: the console hands you into MedicalDentalRCM already signed in. Pending approvals can be run from the console under the same limits.

What you seeOne login, one patient record across Dion, and one place to clear approvals.

Who it is for

One system, five desks.

Practice owner
A/R by payer and by age, denials by reason, and a daily digest of what was done — from your own data, for one office or the whole group.
Office manager
One approval queue and one list of ledger cases, each with the full story attached.
Billing team
Verifications, claims, denials, follow-ups, prior authorizations and provider credentials in one place, with the draft already waiting.
Front desk
Benefits already verified for the week, and a short list of the patients who need a conversation.
Doctors
Claims built from the notes and imaging you already signed in Dion Clinical — and credentials flagged ninety days before they lapse.

Trust & control

The AI escalates. You stay in charge.

Limits you set
The AI acts on its own only inside the limits you choose. Above them, it drafts and waits.
An autonomy plan you can read
One screen shows what is running on its own, what is blocked by a gate, what needs a person and what needs your decision.
Nothing to a patient unreviewed
Patient collections run off, review-only or automatic — they start off, and statements are held for any balance under investigation.
A tamper-evident audit log
Access to patient information and every AI action are logged in a record that cannot be quietly edited, with a screen to review it.
Scoped to your practice
People see only the practices they are assigned to; a multi-office group sees each office and the roll-up.

Read the full picture, including what is still in progress, on the security page.

Questions

Asked plainly.

Something not here? Ask us.

What is MedicalDentalRCM?

MedicalDentalRCM is dental and medical revenue cycle management software. It verifies benefits before the visit, checks each claim before it goes out, reads every denial and drafts the appeal, and turns aged A/R into a worklist with an owner on every claim. The AI does the legwork inside limits the practice sets, and the practice’s team approves everything above them.

Who is MedicalDentalRCM for?

It is for dental and medical practices, and for groups with several locations, that bill insurance. Owners see A/R by payer and by age, office managers get one approval queue, billers get worklists with the draft already waiting, and front desks see benefits verified for the week. Clinical decisions stay with the doctor; the software works on the billing around them.

What does MedicalDentalRCM replace?

It takes the place of the separate lists, manual benefit checks and follow-up spreadsheets a billing team keeps for dental insurance verification, claims, denials and aged A/R, and puts the dental book and the medical book in one system. It is dental billing software, not a billing service: your team keeps the payer relationships and the calls that need judgment.

Does it work with our practice management software?

Supported practice software connects directly or through Dion’s own bridge, installed and set up with each practice, and once connected your patients, coverages and claims come across. It also trades data with other Dion apps, including Dion Clinical, Dion Pay and Dion Insights. Tell us which system you run and we will confirm how it connects before you rely on it.

How do the AI and our team split the work?

The AI does the checking, drafting and chasing, and your people make the decisions. It verifies benefits, checks claims, reads denials, drafts appeals and opens follow-ups. Inside limits you set it may act; above them it drafts and waits for approval. Write-offs and claim submission always stay with a person, and every AI action is written to an audit log.

How does it handle HIPAA and patient data?

It is built for HIPAA-regulated workflows. A Business Associate Agreement is signed with every practice, traffic is encrypted in transit and stored data is encrypted at rest by the managed platforms it runs on, people see only the practices they are assigned to, and every AI action and access to patient information is logged. The security page lists what is in place and what is still in progress.

Does it work across several locations?

Yes. Each office keeps its own queues, billing entity and remittances, and every automated job runs practice by practice. Staff see only the offices they are assigned to, and owners switch to an all-practices view or a DSO roll-up with per-office figures and group totals side by side. The roll-up is read-only, because billing stays per office.

How do we get started?

Run an insurance check on a test patient, then we scope it with you. Connecting your practice system comes first, and the verification and denial queues start filling from the first sync. You can begin with the AI only drafting, then switch the autonomous modes on one at a time, inside limits you set. Setup time depends on your system and your number of offices, so we do not quote a number.

Hand the checking to the AI. Keep the decisions.

For one practice or a whole group — run an insurance check on a made-up test patient and see what comes back before the visit.

Guardrails, built in.

A BAA signed with every practice
Encrypted in transit and at rest
Role-based access
Audit log of every AI action