PMS Sync DSN

Kubo + DSN One chart. No double entry.

DSN keeps the schedule, the ledger, and the chart. Kubo takes the documentation off the end of the day — reading the case list from DSN and writing the finished note, letter, and consent back into it.

DSN
  • Out of DSN Today's schedule, patients, providers
  • Back into DSN Signed notes, letters, consent forms
Vendor
DSN Software
Deployment
On-premise server
Two-way sync Nothing to migrate

Trusted chair-side by

What syncs

Your schedule comes in.
Your charting goes back.

Kubo pulls in today's schedule and files approved documents back.

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.
Out of Kubo

Back into DSN

  • Clinical & operative notes Approved notes file to the chart before the patient reaches the front desk. See Kubo Scribe
  • Referral letters Sent to the referring office and saved to the patient chart. See Kubo Letters
  • Signed consent forms Signed on the patient's phone and filed as a PDF — no printing or scanning. See Kubo Consents

Only approved documents write back. Drafts never reach the chart.

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

In the practice

Four workflows.
No manual work.

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

Save time. Keep one record.

The front office stays in DSN. The clinical team works in Kubo. Everything syncs to one chart.

Front office DSN
Clinical team

Getting connected

How the DSN connection
actually gets made.

A service account on your existing DSN database, plus a small agent on the practice server that files finished documents back to the chart.

  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 — and where each kind of document should land in the chart.

  3. 03

    You open Kubo to a full day

    No import, no parallel run. The schedule is there, and the first signed note syncs back.

The connection
System
DSN · DSN Software
Deployment
On-premise server
Direction
Two-way — read schedule, write documents
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 file a finished note back into the chart.