Enterprise DNA

Instead of Core Practice

Stop renting Core Practice. Own your dental practice system.

We build your version around how your practice books, recalls and follows up. We map the Core Practice records available to you, check the migration with your team and run the agreed system for you.

Core Practice quotes the base subscription. Provider additions and optional SMS bundles affect the bill. Compare your actual invoice with the version your practice needs.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the subscription covers

Separate the practice records from the services around them

Core Practice’s pricing page lists provider allowances and SMS bundles, but no base subscription amount. Ask for a current quote, then compare the work your practice actually needs.

paid

A base subscription to quote

Clinical and Communicator plans are listed without a base amount. We use your actual quote to compare costs.

groups

Provider allowances

Both listed plans include two providers and show an additional-seat charge. That is separate from the number of devices you use.

sms

Optional SMS bundles

The pricing page offers pay-as-you-go messaging and monthly bundles. Message delivery remains a separate running cost in your own version.

event

Booking and recall screens

Appointments, online booking and recall marketing are listed features. The free base here holds appointment history and recall worklists; we scope patient booking screens with you.

description

Clinical records and charting

Core Practice lists charting and treatment planning. Your own version starts with recorded plans and notes; visual charting and imaging are custom work to validate with your practice.

support_agent

Setup and support

The vendor says setup or migration fees can apply and offers an optional response-time service. Our managed version has one setup fee, then a retainer.

What you own

The records behind the next practice decision

Recalls

Find the patients who still need a booking

Read the recall due date beside the next appointment and missed-visit count.

  • check Overdue recalls with no future booking
  • check The reason and last contact date on each recall
  • check Recorded missed visits beside the recall
  • check A draft recall letter for staff to check

Treatment plans

Follow up the plan already recorded

See which plans are waiting, how long they have waited and whether the next visit exists.

  • check Proposed and accepted plans ordered by age
  • check Plans without a future appointment
  • check Recorded items, tooth, surface and fees
  • check A draft treatment plan in your practice name

Record quality

See missing evidence before the weekly review

Check completed visits, accepted plans and upcoming appointments for gaps in the records.

  • check Completed visits without a linked note
  • check Accepted plans without recorded consent evidence
  • check Upcoming patients without a recorded history review
  • check Corrections linked to earlier notes so the original remains

Practice ownership

Change the question as your practice changes

Your records support appointment, recall and balance reviews in one place. Add the question your team needs next.

  • check Booked minutes by provider and location
  • check Overdue balances after recorded receipts, separated by currency
  • check A weekly report built from current practice records
  • check A complete export of every record held in the free version

Make it yours

Design your own Core Practice replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Core Practice. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Core Practice replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Core Practice data across and run it for you.

What it looks like

Ask it like you would ask a colleague

Real answers from the demo data that ships with Dental Practice for Claude Code. It runs in Claude Code inside the Claude app, so it feels like any chat you already use.

forum

Dental Practice for Claude Code

Connected to your own database

Which overdue recalls have no appointment booked?

Alex Morgan

Patient no
CP001
Due on
2026-08-31
Days overdue
35
Reason
Recall examination
Last contact on
2026-08-26
Missed visits
1

Alex Murray

Patient no
CP003
Due on
2026-09-25
Days overdue
10
Reason
Plan review
Missed visits
0

Ask it anything

Ten questions your own records can answer

These are working questions in the free version. Core Practice also offers reporting; we do not claim these questions are exclusive.

chat_bubble Which overdue recalls have no future booking?
chat_bubble Which recall patients also have missed visits?
chat_bubble Which proposed plans have been waiting longest?
chat_bubble Which plans have no next appointment?
chat_bubble Which providers carry the booked minutes this week?
chat_bubble Which completed visits have no recorded note?
chat_bubble Which accepted plans lack recorded consent evidence?
chat_bubble Which upcoming patients have no medical history review recorded?
chat_bubble Which overdue accounts still have a balance after recorded receipts?
chat_bubble What was originally written before a patient note was corrected?

Switching

How to switch from Core Practice

A move involves exporting the records you need, mapping them and checking the results before you stop relying on Core Practice.

  1. 1

    Export your records

    Start with Core Practice’s documented Appointment Details report, which exports to Excel. The free import accepts that workbook or a spreadsheet saved from it, including patient numbers, attendance and cancellation notes. For anything else, export what your account allows, usually CSV or Excel, and check with Core Practice. Clinical notes, PDFs, images, treatment plans and balances need separate mapping.

  2. 2

    Run a test import

    Use the import’s dry run first, with the exported Appointment Details data and the practice location it belongs to. The test checks the data and rolls back rather than keeping imported rows. This lets you see whether the spreadsheet can be read before loading it for real. Keep the source files private and preserve PDFs and other documents separately.

  3. 3

    Check flagged records

    Review the headings and counts reported by the import, then compare them with the export. Resolve missing or mismatched information rather than guessing. Ambiguous patient matches are listed for you to check, and conflicting patient names or changed source appointments stop the batch. Reconcile appointment history and patient and provider identifiers, then handle any separately mapped records on their own.

  4. 4

    Run both systems together

    Keep Core Practice available for a short period while you check that the imported records support your practice’s day-to-day work. Compare appointment history and patient and provider details with the source. Check separately mapped clinical records, plans and balances against their original records too. Keep using Core Practice as your reference until you have resolved discrepancies and your team is ready to rely on the new database.

  5. 5

    Switch off Core Practice

    Once you have reconciled the records you chose to bring over and your team is ready, follow Core Practice’s process for ending the service. Keep the exports and any documents you need to retain in your practice’s backup location. Confirm that your team knows where the new records are held and who is responsible for operating the system before you stop using Core Practice.

construction

Where the real effort goes

The main work is usually mapping your own fields and practice rules, then deciding how much history to bring. Appointment Details covers appointment history and basic identifiers, but clinical notes, images, plans and balances need separate mapping and reconciliation. Enterprise DNA does this mapping and scope work with you when you have them run the move.

Not ready for a call?

Get your Core Practice switch plan by email

We will send you the step-by-step plan for moving your business off Core Practice, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Three ways to own it

Choose how much you want us to handle

Open source

Do it yourself

Free, MIT licence

  1. 1 Clone the repo and run npm install, then npm run demo
  2. 2 Open it in Claude Code, Codex, OpenCode or Cursor
  3. 3 Import the Core Practice appointment export after a dry run
  4. 4 Set up your database access, backups and practice checks before live use
Get it on GitHub

Built around your business

We customise it

A setup fee for your agreed version

  • check Your patient fields, recall rules and document wording
  • check Your Core Practice exports mapped and reconciled
  • check Booking screens or visual charts scoped with your team
  • check A different technical foundation if your practice needs it
Get your version built

Omni by Enterprise DNA

We run it for you

One setup fee, then a retainer

  • check Installed and operated through Omni by Enterprise DNA
  • check Migration checked with your practice before cutover
  • check Connections, access and backup arrangements agreed with you
  • check Someone responsible for keeping your version working
Book a discovery call

Questions

Instead of Core Practice, answered

What will this cost compared with Core Practice? expand_more

The free code has no provider licence fee. Hosting, message delivery, implementation and support still have costs. Core Practice does not list a base subscription amount on its pricing page, so bring your actual invoice. For a managed version, Enterprise DNA agrees one setup fee and then a retainer.

Will all our patient history come across? expand_more

The free import reads the Core Practice Appointment Details Excel export, or a spreadsheet saved from it, including patient numbers, attendance and cancellation notes. Clinical notes exported as PDFs, images, plans and balances need separate mapping. We reconcile the full record scope with your practice before any cutover.

Can reception keep a booking screen and dentists a tooth chart? expand_more

Yes, we can scope those into your custom version. The free base records appointments and plan items by tooth and surface and produces read-only reports. Your team defines the screens, imaging connections and chairside workflow that must be built and validated.

Does it make clinical decisions or submit health fund claims? expand_more

No. It records the treating practitioner's decisions and checks for missing evidence. Consent remains a clinical process. Health fund claiming, payment terminals and clinical integrations need separately agreed work and validation; they are not switched on by installing the free version.

Who controls the data and who supports the system? expand_more

You control the database and can export the records held in it. If you run the free version, you own its operation and access arrangements. If we run it, Omni by Enterprise DNA handles the agreed hosting, backups, connections and ongoing support. Your practice retains control of clinical decisions and record policies.

Bring your Core Practice bill and your recall list

Spend 30 minutes with Sam. We look at the software bill, the work your team repeats and the records you need to retain. You leave with the scope of an owned version and the migration checks it needs.

Book a discovery call Get the free version

Dental Practice for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Core Practice?

Get your version built