How to Automate DentalWriter

Oral appliance therapy gets billed to the medical plan

A dental practice that treats sleep apnea bills a medical plan rather than a dental one, and DentalWriter exists to make that possible. Nierman Practice Management sells it today as DentalWriter Plus+, built around dental sleep medicine, temporomandibular disorder and oral surgery.

A medical insurer does not want a dental note. It wants a history, an examination, a diagnosis, a reason for this treatment rather than another, and a physician somewhere in the story. Patients complete online intake questionnaires before they arrive, the exam goes onto forms written for sleep and TMD rather than for fillings, and the software turns the two into a SOAP report of medical necessity.

So it sits at the front of everything a sleep programme does. A referral arrives from a physician, the questionnaire goes out, the exam happens, the narrative is generated, the case is cross-coded from dental to medical, and the appliance is authorised, delivered and billed against the same chart.

The sleep study and the physician order come from somewhere else

A medical claim for an oral appliance is not paid on the dentist's say-so. It is paid on a stack of documents, most of them produced by people who do not work at the practice.

The diagnosis of obstructive sleep apnea comes from a sleep study the practice did not run, and the order behind it from a physician it does not employ. The prior authorisation sits on a payer's website and changes status quietly. Bill Medicare for the appliance and a supplier enrolment sits underneath that too, with an accreditation and a surety bond expiring on dates held elsewhere again.

So the coordinator's morning goes on other people's logins. Has the authorisation come back. Did the sleep lab send the report. Was that claim paid, denied, or simply sitting there. Which patient was fitted seven weeks ago and has never been billed, because a record never arrived.

Each is two minutes of work, which is why none gets fixed. Together they are why an appliance delivered in March is paid for in September.

DentalWriter

Authorisations checked before the appliance is ordered Every pending request read on the payer's own portal overnight, so a delivery visit is booked against an approval that came back rather than one assumed.

Deliveries matched against claims Appliances fitted with no medical claim behind them, listed each week while the filing window is still open.

Enrolment dates watched for you Medicare supplier enrolment, accreditation and surety bond expiry followed on the sites that hold them, not on a note pinned to a wall.

Intelligent Cross-Coding writes the claim it cannot then go and chase

The software already does more of this than most practices use, and the licence is worth exhausting first.

Online patient intake questionnaires collect the history before the patient sits down. Automated SOAP reports of medical necessity build the narrative from the questionnaire and the exam form. Intelligent Cross-Coding turns the dental case into the medical codes a claim needs, a real-time claim tracker shows what went out and what came back, and Quickletters produces the physician correspondence a referral relationship runs on.

All of it works on what DentalWriter already holds, and the ceiling is the one every practice system meets. It cannot open a website belonging to somebody else.

The reason a claim stalled, the wording of a denial, whether an appeal was received and how long is left to file one: those live on the payer's provider portal. The sleep study lives with the sleep lab, the signed order in a referring physician's system, the accreditation date with the accrediting body. Every one needs a person with a password.

The appliance is delivered against an approval that actually exists

What changes is when the practice finds out. Read those portals every day and the surprises arrive early enough to do something about.

Every pending prior authorisation read on the payer's portal before the office opens, oldest first, so an appliance is ordered against an approval that came back rather than one assumed. Denials pulled with their reason codes and appeal deadlines attached.

Delivered appliances checked against claims actually submitted, so the handful fitted and never billed is a short list on a Monday rather than a discovery at year end. Sleep studies and physician orders matched against the patients waiting on them, with the request to the referring office drafted. Medicare enrolment, accreditation and surety bond dates watched where they live, because a lapse stops payment on everything at once.

Then the patients who fell out of the middle. Titration finished with no efficacy retest booked. An appliance delivered with no follow-up on the calendar. A referral that arrived and was never called.

One line in a clinical practice does not move. The gathering runs unattended. Anything that changes a chart, submits a claim or reaches a patient is prepared and waits for a qualified person.

An agent signs in at seven so nobody else has to

The chasing is not clinical work, and yet it decides whether an appliance the practice has already made gets paid for. It needs somebody signed into six websites before the first patient of the day, which is why it happens on quiet mornings and not busy ones.

WebRun is an AI agent that works a real Chrome browser, signed in the way your team signs in. It opens DentalWriter, the payer portal and the referring physician's site, reads what each says, and brings back the authorisation list or the unbilled deliveries already assembled.

It runs on your schedule inside your own private environment, sessions are not shared between the sites in a workflow, and a run can be locked to a named list of domains.

The workflows below are already built, and each one names exactly what it opens.