How Dentavector works
A read-only reader of your Dentally account, built for one contract and hosted in London.
How it works
01 Integration model
A read-only reader
The integration never changes anything in a practice's Dentally account and it reads only what the dashboard needs:
- Practice & sites
- Contracts
- Practitioners
- Appointments
- Treatment plans
- NHS claims
- Treatment catalogue
- Practitioner diaries
- Invoices and payment plans
- Patients (names and contact details never stored)
If a practice turns them on, Dentally also tells us when an appointment changes. The practice sets this up in its own Dentally account; we still never write anything to it.
02 Sync behaviour
Light on Dentally's platform
One full sync, then a weekly check
Your history loads once; a Sunday check catches anything missed.
Incremental only
Per-entity watermarks fetch just what changed since the last run.
Rate-limit aware
Back-off and retry when Dentally asks us to slow down.
Twice a day
Scheduled syncs at 06:00 and 19:00 and when you open the app.
03 Architecture
One schema per practice
Each practice's data lives in its own PostgreSQL schema.
Stack. Node.js 22 / Express 5 · Next.js · PostgreSQL · Docker and nginx on AWS in London (eu-west-2).
04 The hard part
The composer — care packages before the claim
The NHS only records care packages once a claim is sent. The composer learns from your claims how your treatments add up to care packages, so work in open courses is valued before it's claimed.
05 Security & data protection
Kept safe, kept to a minimum
- Data residency in the UK
- Data encryption
- TLS on every connection
- Logs without patient identifiers
- Every rejected request logged
- Data minimisation