All templates

Automated Medical Necessity Packets

Every morning, WebRun finds oral appliance cases ready for submission in DentalWriter, generates or pulls the SOAP medical-necessity narrative, gathers the sleep study, physician order, and chart notes into a single packet in Google Drive, and drafts the payer or physician submission email in Gmail for your team to review and send.

Runs on WebRun · Strict Lockdown policy
Every day at 9:00 AM WebRunorchestrates each step
1 DentalWriter generate the SOAP narrative
2 Google Drive assemble the packet
3 Gmail draft the submission
In short

How do I assemble a medical-necessity packet for oral appliance claims?

WebRun finds ready oral appliance cases in DentalWriter each morning, generates the SOAP medical-necessity narrative, and assembles the sleep study, physician order, and notes into one packet in Google Drive. It then drafts the payer submission in Gmail for your team to review and send, so every claim goes out complete and approved.

  • Every submission goes out with a complete SOAP narrative and supporting records
  • Packets are assembled and drafted the same morning a case is ready
  • Incomplete cases are held back instead of submitted and denied

Built for dental sleep medicine practices · DSM billing coordinators · medical billing dentists · TMD and sleep teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens niermanpm.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    DentalWriter - generate the SOAP narrative
    niermanpm.com
    WebRun in DentalWriter: generate the SOAP narrative
    WebRun opens DentalWriter to generate the SOAP medical-necessity narrative.
    • Open DentalWriter and find oral appliance patients whose documentation is complete and ready to submit
    • Generate or pull the SOAP medical-necessity narrative report for each case
    • Confirm the diagnosis, AHI, appliance and E0486 code, and referring physician are present
    • List which supporting documents belong in the packet: the sleep study, physician order, and exam notes

    Done when Each ready case has a SOAP narrative and a checklist of supporting documents.

  3. 2
    Google Drive - assemble the packet
    drive.google.com
    WebRun in Google Drive: assemble the packet
    WebRun opens Google Drive to assemble the medical-necessity packet.
    • Open Google Drive and create or open the submission folder for the patient
    • Assemble the SOAP narrative, sleep study, signed physician order, and exam notes into one ordered packet
    • Name each file clearly with patient, date, and document type
    • Flag any case still missing a document so it is held back rather than submitted incomplete

    Done when Every ready case has a single complete medical-necessity packet in Drive.

  4. 3
    Gmail - draft the submission
    gmail.com
    WebRun in Gmail: draft the submission
    WebRun opens Gmail to draft the payer submission for review.
    • Draft the submission email in Gmail to the payer or referring physician with the packet referenced
    • Include only the minimum patient detail the recipient needs to process the request
    • Leave every submission as a draft for a team member to review and send, so no protected health information goes out unapproved
    • Queue the drafts together so your coordinator can review and release the day's submissions in one pass

    Done when A submission is drafted and waiting for review for every complete packet.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
niermanpm.com
ScheduleRuns automatically on this cadence
Every day at 9:00 AM
DeliveryHow each run's result reaches you
Necessity packets · Gmail
OutputWhat each run produces - A complete medical-necessity packet per case in Google Drive and a drafted payer or physician submission in Gmail, each waiting for a human to review and send.
Document + drafts
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it submit the packet to the payer automatically?

No. WebRun assembles the packet and drafts the submission email, then leaves it unsent for a team member to review and send. Because the packet contains protected health information, a human always releases it.

What goes into the medical-necessity packet?

The SOAP medical-necessity narrative from DentalWriter plus the supporting records a payer expects: the diagnostic sleep study, the signed physician order, and the relevant exam notes, all assembled in one Drive folder.

What happens if a document is still missing?

It holds that case back rather than assembling an incomplete packet, and flags the missing document so your team can obtain it before the packet is drafted for submission.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.