Patient-centered operating control system
Trace one defined period from care delivered to bank-cleared cash, classify the gap, expose payer and administrative friction, pay clinical labor before ownership return, and preserve the operating reserve that protects judgment.
Use only aggregate, coded, permitted information. No account, upload, or server storage is used.
Before you enter numbers
You are deciding where one period’s care became cash, where it became delayed or disputed, and what must be protected before owner distributions or process changes.
Start here if you are learning the decision or do not have every record yet.
Use this after the first result, or with advisers and stronger records.
The care-to-cash reconciliation
Production, receivable movement, service-period attribution, receipt channels, bank timing, and operating cash answer different questions. Reconcile each bridge before interpreting distributions, cash available to distribute, or reserve adequacy.
Documented charges for the defined period—not cash and not value.
Contract-controlled reductions kept separate from other write-offs.
Every noncontractual adjustment or write-off needs a reason and owner.
The calculated clinical-to-financial starting point.
Net production plus opening receivables minus closing receivables estimates receipts attributable to service periods.
Current-period and prior-period receipts are identified separately; neither is inferred from a payment channel.
Insurance, patient, membership, and other receipts must reconcile to the service-period attribution.
Refunds reduce receipts; opening and closing deposits in transit explain legitimate bank timing.
Receipt channels, refunds, deposits in transit, processor records, and the bank must reconcile.
Operating payments, debt, capital, tax, clinical pay, distributions, reserves, and outside funding complete the cash roll-forward.
Complete fictional aggregate example
The loaded example uses opening and closing receivables to estimate attributable receipts, separates current- and prior-period cash, reconciles receipt channels and deposits in transit, pays owner clinical labor, and preserves a separate operating-reserve test.
Separated from receipts for earlier service
Timing, error, dispute, patient, and clearing
After operations, debt, capital, tax, clinical compensation, and outside funding
Documentation and reconciliation limits reviewed separately
Every value and payer segment is fictional. This is not a benchmark, accounting policy, coding rule, contract interpretation, payer recommendation, collection target, or clinical-performance score.
Local operating control file · Model v2.0.0
The workbench does not code, submit, appeal, collect, post, reconcile, approve a payer, or set an accounting policy. It separates the cash journey, exceptions, payer burden, clinical compensation, reserves, and safety checks.
Data boundary
Use aggregate periods, coded payer segments, and short local record locators. Nothing is uploaded or saved by DenQAI. Inputs remain in this browser tab until you export a file you control.
No common direct-identifier pattern detected. Pattern screening cannot certify confidentiality, de-identification, contract permission, or security.
01 · Patient-centered operating mandate
Production, reimbursement, and overhead are constraints. They do not authorize overtreatment, unsupported coding, unsafe staffing, hidden balances, or reserve depletion.
Decision Summary · 02 · Event and cash bridges
Declare the unit and event period for every line. Claim counts never enter dollar arithmetic. Current receipts can include older care, while current production can remain in receivables; deposits in transit then explain why receipts and bank-cleared cash differ.
Period warning: this is a reconciliation model, not accrual accounting or a universal practice benchmark. A dental CPA should define the actual chart of accounts, cutoffs, owner compensation, taxes, debt classification, capital treatment, and reconciliation policy.
03 · Exception ownership
Timing, error, dispute, patient balance, and clearing are separate failure modes. Staff cuts do not repair rejected claims, and old-AR calls do not repair an unprofitable contract.
Patient-level work belongs in the practice’s governed systems—not in this public browser tool or exported aggregate file.
04 · Payer performance
These are coded segments, not a shared fee database. Keep exact contract terms and patient-level records out of DenQAI, and do not use this workbench to coordinate prices or market conduct with competitors.
Contract, state, privacy, and antitrust review control any later aggregation or shared service.
05 · Eight safety checks that cannot be averaged away
A safety check is supported only when you identify the document or report behind the answer, record its limits, and name the person responsible for reviewing it.
06 · Save or share your review
Print or save a PDF for a readable discussion. Save the DenQAI project file only if you want to reopen these exact inputs here. The tool does not create patient work queues, submit claims, retain files, or send data to DenQAI.
These CSV files are raw row-and-column data for advisers or analysts. They are not the recommended reading format.
Downloads are disabled when common private-data patterns are detected. A technically safe file does not establish permission to share its contents.
Source-controlled boundaries
ADA claims guidance covers common rejection and appeal categories, while HealthCare.gov states that preauthorization is not a promise of payment. Payment-card security, state law, payer contracts, patient authorization, privacy duties, and accounting treatment remain separate reviews.