Files and third-party payers
Referral, missing documents, forms and administrative follow-up on a payer request: collection stops by itself once a document arrives, and the file reaches the consultation complete.
Between consultation and start of treatment, an accepted plan can die quietly. The follow-up is written into Zenvox; at ABELDent, external access is not established.
7 days, 20 answered calls, no card
The follow-up is written into Zenvox: the request or referral received, missing documents against your list, the specialty concerned, the administrative terms you approved. ABELDent keeps the truth of the chart and of the treatment plan. External access is not established: nothing is written there, and the online booking link is the explicit fallback.
On external access, the research is clear: it is not established, and documentation has to be requested per version and per region. Nothing is asked of you meanwhile. One point of method belongs here too: this software’s real footprint in Quebec practices has to be measured, not presumed.
The practice targeted here is sequenced treatment — orthodontics, implantology, oral surgery — where treatment starts long after the consultation: missing documents, a preparatory appointment left unbooked, a cost question unanswered, and the file goes quiet.
The status below reflects an access qualification that was not established. It moves only on documentation obtained from the vendor.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | The required operations are known: patient, appointment type, resources, approved plan, status and documents. Reading the acceptance status of a plan would be the most useful operation, and it is also the most sensitive; access is not established. |
| Create | Zenvox native mode | The appointment sequence of a treatment commits resources, preparation and confirmations. The receptionist prepares the request and the clinic enters the sequence into its own software. |
| Update | Zenvox native mode | When a plan is revised after an exam, chasing on the old version is suspended and any booking depending on it is too, until the new pathway is approved. That suspension is decided by the clinic, and Zenvox applies it to its own follow-ups. |
| Cancel | Zenvox native mode | Dropping or pausing a treatment is a decision of patient and professional. It is taken, recorded and passed on; Zenvox follow-ups stop at the same moment, with no orphan chase left running. |
Answering, receiving a referral, telling a consultation apart from treatment follow-up, applying the emergency protocol and passing everything on sit inside your healthcare base. Document follow-up on a case and coordinating a multi-session pathway are named add-ons.
On a long treatment, the authorisation that matters is the one freezing a follow-up at the right moment.
A patient seen in consultation last month calls back. The clinic is in surgery. Nothing is written into the software.
PatientHi, I saw the surgeon about my implant and I think I want to go ahead. What do I do now?
ReceptionistLet me confirm your name and date of birth. I can see your file is waiting on two items before the next step; I will name them and log them as expected.
ReceptionistFor the plan itself and the terms, the team walks you through it — I do not weigh in on that. I am passing on your intent to start and your availability.
The clinic gets a clear signal: this patient wants to start, and two named items are missing. Collection stops by itself when they arrive. The gap between consultation and start of treatment stops being a black hole.
That is today status. The online booking link is the explicit fallback, and case follow-up happens inside Zenvox.
No. The sequence commits resources, preparation and confirmations: the receptionist prepares the request, and the clinic enters the sequence into its own software.
It is suspended, and so is any booking depending on it, until the new pathway is approved. That suspension is decided by the clinic, and Zenvox applies it to its own follow-ups.
Dropping or pausing is taken, recorded and passed on, and Zenvox follow-ups stop at the same moment. No orphan chase is left running behind a closed file.
No. It would be the most useful operation, and it is also the most sensitive; external access is not established, and documentation has to be requested from the vendor, for your version and your region.
Its real footprint in Quebec practices has to be measured, not presumed, and this page claims nothing beyond that. The practice targeted is sequenced treatment — orthodontics, implantology, oral surgery.
To name the real gap: between consultation and the start of treatment, an accepted plan can die quietly. Document follow-up happens inside Zenvox, collection stops by itself once a document arrives, and the file reaches the consultation complete.
See the practice concerned, or the full list of software studied.
ABELDent