In your office
Chartwright OS server
Runs behind your firewall, next to your practice-management system. Never leaves the building.
- Patient names, birthdates, addresses
- Clinical notes and treatment history
- Radiographs and photos
- The chart itself
How it works
One verification. The whole visit.
Chartwright doesn't try to be the whole record. It handles the two things practice software usually gets wrong: knowing the plan, and moving the patient through the visit.
- 01
Verify the plan, once.
Anyone at any office calls the payer, pulls benefits into Chartwright Cloud, and marks the plan verified. It is now the single answer every workstation reads — until it changes, and you re-verify.
- 02
Route the visit.
Chartwright OS pulls the patient from your PMS, drops them on the routing board, and moves them through front desk → operatory → billing. Every screen reads from the same verified plan.
- 03
Quote and check out.
Estimates use the plan's actual rules — downgrades, missing-tooth clauses, frequencies, remaining maximum. The number at the counter is the number the payer will honor.
Where your data lives
Plan facts in the cloud. Patient charts on your server.
Chartwright is deliberately split. What benefits from being shared across the industry — the insurance plans themselves — lives in the cloud. What must never leave your office — the patient chart — never does.
In the cloud
Chartwright Cloud — plan facts only
The shared library of insurance plans. No patient identifiers, no chart data — ever.
- Payer, group, plan identifiers
- Per-CDT-code benefits and downgrades
- Frequencies, waiting periods, missing-tooth clauses
- Verification attribution: who, when, from which call
Put plainly: if Chartwright Cloud were breached tomorrow, no patient information would be in it to lose. The plan library would need to be re-secured. Your patients would not need to be notified, because nothing about them lives there.