PMS Sync DSN

Kubo + DSN One chart. No double entry.

DSN keeps the schedule, the ledger, and the chart. Kubo reads the case list from DSN and drafts the note, letter, and consent around each visit — the finished documents live in Kubo for your team to review, download, and file. Nothing is written back to DSN.

DSN
  • Out of DSN Today's schedule, patients, providers
  • Ready in Kubo Notes, letters, consent forms — ready to file
Vendor
DSN Software
Deployment
On-premise server
Read-only sync Nothing to migrate

Trusted chair-side by

What syncs

Your schedule comes in.
Your paperwork lands in Kubo.

Kubo pulls today's schedule from DSN and drafts the documentation around it — notes, letters, and consents, finished and ready in Kubo.

Out of DSN

Into Kubo

  • Patient demographics Name, chart number, date of birth, and referring dentist.
  • Today's appointments Times, procedures, and status — kept current as the day changes.
  • Providers & locations Mapped once so each surgeon sees the right schedule at the right office.
In Kubo

Ready in Kubo

  • Clinical & operative notes Drafted during the visit and approved in Kubo — polished and ready to file.
  • Referral letters Written from the note and sent from Kubo, with a copy kept for your records.
  • Signed consent forms Signed on the patient's phone and saved as a clean PDF, ready to download anytime.

DSN stays exactly as it is — every document Kubo produces is finished and waiting in one place.

No historical data is moved or converted. Disconnect Kubo and your chart stays untouched.

In the practice

Four workflows.
Done in Kubo.

DSN stays the same. Kubo removes the paper shuffling around it.

Save time.

The front office stays in DSN. The clinical team works in Kubo, with every finished document ready in one place.

Front office DSN
Clinical team

Getting connected

How the DSN connection
actually gets made.

A read-only service account on your existing DSN database. Kubo reads the schedule and patient details and never writes to the chart, so there is no write-back agent to install.

  1. 01

    We connect to your DSN

    On-premise server, exactly as you run it today. Your database stays where it is and keeps doing the job it already does.

  2. 02

    We map your practice once

    Providers, locations and appointment types — so each surgeon opens to the right schedule at the right office.

  3. 03

    You open Kubo to a full day

    No import, no parallel run. The schedule is there, and Kubo drafts the documentation around it.

The connection
System
DSN · DSN Software
Deployment
On-premise server
Direction
One-way — read schedule only
In transit
Encrypted end to end
At rest
Encrypted, access logged

Running DSN alongside another system? Tell us everything that's in the practice — most groups are on more than one.

Ask about your setup

Keep DSN.
Lose the paperwork.

See Kubo pull a real schedule out of DSN and turn the visit into a finished note.