Our Software
TMJ Journey
Practice software for TMJ and dental sleep medicine — built, hosted and supported by Vault Data Servers.
Less admin. More treatment.
One system for the clinical, front-desk and financial sides of a TMJ and sleep practice — with documentation that writes itself while you talk. It is purpose-built for the specialty rather than a general dental system with the fields renamed, and it is ours end to end: Vault writes it, runs it and answers the phone about it.
What It Covers
The whole practice, not a module
Clinical
Range of motion, joint findings, staging and imaging on the visit they belong to. Signed notes lock and corrections amend the record. CBCT and sleep studies attach to the encounter.
Operations
A TMJ case has a dozen chances to stall. Stages you name with callback cadences behind them, operatories and split-day hours, a waitlist that fills the cancellation, and calls that match to the chart as they arrive.
Financial
Long treatment, usually paid out of pocket. Phases priced from your own fee schedule, signed on screen before they leave, and CPT, HCPCS and CDT on one superbill. Cash-pay by design — keep your biller.
Patients
Forms at home instead of a clipboard, reminders at a sensible hour, and a text they can reply to and get a real answer. Digital intake, e-signed consents, and a portal for appointments, forms and documents.
Referrals
ENTs, sleep physicians and general dentists treated as part of the product rather than an inbox. A portal they will actually use, outbound referrals tracked to where they landed, and case review without emailing records around.
Reporting
Which referrers send cases that start, not just cases that call. Where cases stall, what the schedule is really doing, and what the practice collected — on the practice's own clock, not a server's.
Ambient Documentation
The note is done before you stand up.
It listens to the visit and drafts the note in your specialty's language — findings, assessment, plan. You read it, change what you want, and sign. Structured exam findings become readable narrative automatically, so what you enter as numbers doesn't get written out twice.
Nothing is filed without a clinician reading it first, and it is off unless you turn it on — a per-practice choice, not a default.
See it write a noteDrafted while you talk
The visit is documented as it happens, in the language of the specialty.
A clinician signs it
You read and change the draft before anything is filed. Nothing signs itself.
Off unless you turn it on
Ambient documentation is a per-practice choice, enabled deliberately.
HIPAA-aligned, BAA provided
Signed as part of onboarding, before your first patient record exists. Access is role-scoped; changes and views of patient data are logged.
Why Vault
We built it. So we know how to fix it.
One company, not a vendor chain
The servers, the network and the practice software are ours end to end. When something breaks, nobody opens a ticket with a vendor who has never seen your setup.
You talk to the people who build it
There is no tier-one queue between you and someone who can actually change the software — the upside of buying from a small team rather than a large one.
Your data is yours
Export your records whenever you want — clearly labelled PDFs and spreadsheets, readable without any proprietary software and simple to load into whatever you use next.
Switching
Coming from another system
TMJ Journey replaces the system you're on rather than sitting beside it. That sounds like the bigger change — it's the smaller one, because there's no second place to look and nothing to keep in sync.
Your history comes with you
Patients, appointment history and documents. What that takes depends on the system you're leaving, so we scope it with you on the call.
Nothing switches off on day one
Keep your old system read-only as long as you want it.
Your team is trained separately
Front desk and clinical learn the parts each of them actually touches.
Leaving stays as easy as arriving
Your records stay yours and stay exportable for as long as you're with us.
FAQ
The things practices actually ask
Does this work alongside my current practice management system?
No — it replaces it. TMJ Journey is the system your practice runs on, not a companion that mirrors a second one. Practices that tried running both ended up doing everything twice, and a sync that drifts is worse than no sync at all.
Can I bring my existing patients across?
Yes — patients, appointment history and documents. How that works depends on what your current system will give us, so it's scoped on the demo call. Anything ambiguous gets flagged for you to decide rather than quietly guessed at.
What about insurance billing?
We don't file claims, and that's deliberate. TMJ Journey produces superbills carrying CPT, HCPCS and CDT codes priced from your fee schedule, and your biller takes it from there. You keep the biller who already knows your cases.
How long does it take to get going?
The practice itself is ready quickly — the variable is how much history you're bringing and what shape it's in, which we scope with you before you commit. Text messaging is the one thing nobody can rush: carrier registration runs to weeks, so we start it immediately.
Is patient data safe?
A BAA is signed as part of onboarding, before your first patient record exists. Access is role-scoped, and both changes and views of patient data are logged. The software runs on hardware Vault owns and operates.
Am I locked in?
Month to month. Your records stay yours and stay exportable, so leaving is a decision rather than a project.
Do I have to be a Vault managed IT client to buy it?
No. TMJ Journey is sold on its own and plenty of practices will only ever buy the software. If you also want the network, the workstations and the phones handled by the same people, that's the other half of what we do.
Can it connect to the form on my existing website?
Yes. Keep the form you have and post it to the Lead Intake API — enquiries land in the same inbox as everything else, and nobody rebuilds a page that already works. If you would rather we hosted the form instead, you can build one in the app and embed it. Both are covered in the developer documentation.
See it on one of your own cases
Thirty minutes with the people who build it. Bring the case that's most awkward in your current system and we'll do that one.