FEZA innovation – Home
← All products

Development on request

Dental Clinic Operations

Dental Clinic Software

Follow the treatment plan, sessions and payment schedule through one patient record. We will define the scope of the dental clinic software we will build for you around your dentists' working methods and reception's daily needs.

  • Scope shaped around your workflow
  • Roles and record design
  • Integrations subject to conditions
Dental chair and examination lamp beside a tooth model, tooth cross-section and appointment calendar
  1. Discovery
  2. Scope and quote
  3. Development

When a dental treatment plan spans several sessions

When treatment stretches across several days, the dentist's plan, reception calendar and payment list can become disconnected. It may be unclear which tooth will be treated next, while an image brought by the patient sits in another folder. As you explain a plan change to the team, the calendar may still show the previous appointment duration.

In the software we will build, the patient record will connect these elements. Clinical decisions will remain with the dentist; planned procedures, reserved chairs and payments will be linked. Reception will be able to follow the purpose and preparation of the next session without opening clinical details.

Your current process

  • Treatment notes, appointments and payment lists remain in separate places.
  • After a plan change, the duration of the next session has to be checked again.

In the software we will build

  • Tooth-specific plans, sessions and follow-up needs will be scoped together.
  • Operational information for reception will be separated from clinical records.

Dental treatment from examination to follow-up

Consider a treatment that begins with an examination and requires several sessions. We will ask for blank forms used in this process and a breakdown of team responsibilities. The steps below illustrate how we can discuss development scope; they do not replace clinical decisions or treatment advice. We will also examine longer sessions, a change of dentist and a patient's reconsideration of the plan within the same example.

  1. 01

    Examination and planning

    The dentist's tooth-specific findings, proposed procedures and plan discussed with the patient will be scoped as separate fields. Planned and completed procedures will have distinct statuses.

  2. 02

    Session preparation

    Reception will be able to reserve the dentist and chair together according to the duration specified by the dentist. Materials or images needed by the assistant will be considered in a preparation list with appropriate access rights.

  3. 03

    Procedure and follow-up

    The procedure performed will be linked to the relevant tooth and plan. Remaining treatment, follow-up appointments and payments will be tracked separately; a postponed procedure will not be marked as completed.

Patient records, dental chair scheduling and payments

Choose the first version around your daily patient flow. Documents, equipment and team structures differ between clinics. Rather than including every option at the start, we will establish which records each task needs.

Storing an image file and receiving data from imaging equipment are separate tasks. Image interpretation, diagnostic suggestions and unconditional submissions to official health systems fall outside this proposed initial scope. Data sources and responsibility for additional work you request will be assessed during discovery.

  1. For the first version

    Patients and treatment plans
    Patient records, tooth-specific plans, session links and procedure statuses entered by dentists can form the initial scope.
    Scheduling and payments
    Dentist and chair availability, agreed instalment schedules and payment records will be defined together.
  2. Added as needed

    Images and documents
    An X-ray archive, files linked to individual teeth, consent versions and a limited patient view can be added as needed.
  3. Dependent on external systems

    Notifications and invoicing
    SMS and connections to Turkey's e-invoice and e-archive invoice systems will be reviewed separately if your provider offers API access.

From a single dentist to shared dental chairs

The number of dentists affects more than user accounts. Shared chairs, sessions handed to another dentist and image access rules also change. Once you describe your current division of work, we will design scheduling and permissions accordingly. Defining which records two dentists treating the same patient can edit, who can change the plan and whom reception should contact makes the daily workflow easier to understand.

Scheduling

Single-dentist clinic
Dentist and chair availability will be considered together.
Multiple dentists
Shared chairs, dentists' working hours and leave will be defined separately.

Sharing treatment plans

Single-dentist clinic
The same dentist may own the plan and follow-up.
Multiple dentists
Session handovers and permission to change plans will have separate rules.

Management

Single-dentist clinic
A daily appointment and payment summary can be selected.
Multiple dentists
Authorised summaries by dentist and chair can be included in scope.

Access for dentists, assistants and dental reception

Share patient records according to team responsibilities. Booking an appointment does not require access to X-rays. In the software we will build, viewing, editing and export permissions will be considered separately. Discovery will also define account closure when staff leave and record rules for tracing their earlier actions.

Dentists and assistants

Clinical editing by dentists, preparation information for assistants and image access will be scoped separately. Actions linked to individual users are recommended instead of shared accounts.

Reception and management

The design will give reception the fields needed for appointments and payments. Access to management reports will not imply permission to read all clinical notes.

Health data and permissions

KVKK, Turkey's personal data protection law, health data processing conditions, consent documents, retention and access logs will be assessed in scope. Your clinic is the data controller; document wording will be clarified with your authorised adviser.

Postponed sessions and revised dental treatment

Dividing treatment into sessions means that each appointment may represent a different procedure. If a patient postpones one stage, the dentist may need to reassess the conditions for the next session.

Instead of silently overwriting the old plan, the software we will build will include the reason for a change and its link to the relevant session in scope. How previous payments relate to the new plan will be defined around your working methods. A cancelled appointment and an abandoned treatment will be treated as different record statuses.

What makes the decision difficult

  • Cancelling one session can be mistaken for cancelling the entire plan.
  • A revised procedure can become confused with the previous payment agreement.

Workflow to define in the project

  • Postponed sessions and remaining treatment will be tracked with distinct statuses.
  • The revision reason and authorised approval will be linked to the record.

Matching treatment plans, sessions and images

The export format of historical tooth charts matters as much as the patient list. We will map fields using a sample file containing no personal data. Image naming and patient links will be examined separately. Connections to official health systems will be assessed against technical requirements and your clinic's needs.

  1. 01

    Review the source records

    We will review treatment plans, session statuses and image filenames in a sample with patient identities removed. Where links between an old plan, session and image are unclear, we will clarify the mapping with your clinical team.

  2. 02

    Trial transfer and review

    The trial transfer will be scoped to let the clinic review how treatment plans relate to completed and postponed sessions. Images that cannot be matched to a patient and duplicate patient cards will be addressed separately before migration.

  3. 03

    Establish the connection requirements

    If API access is available for imaging or health records, patient matching, file formats and access errors will be examined. Otherwise, image file transfers or record entry by authorised clinical staff will be considered.

Proposal scope around treatment and imaging boundaries

Prepare a blank treatment plan, session schedule and payment example. Mark the information dentists, assistants and reception need. Together, we will define the boundaries of the first version using examples containing no personal data.

  • Identify the dentist changing treatment plans and the role recording sessions.
  • Prioritise treatment, session and image relationships in the initial scope.
  • Prepare image naming examples with patient identifiers removed.

Treatment plan fields, postponed sessions and image matching will define the proposal boundaries. The usage model, support and access requirements reviewed for health connections will be discussed in writing.

How we work

We do not sell an off-the-shelf package: we design the software around your workflow, build the first version in short steps and keep running it after launch.

  1. 01

    Discovery

    We listen to how your business works, your team and the tools you use today.

  2. 02

    Scope and quote

    Modules, priorities and price are set out in a written quote.

  3. 03

    Development

    We show working versions at short intervals and move on with your feedback.

  4. 04

    Setup and migration

    We move your existing records across and help your team get started.

  5. 05

    Support

    We run the software on a subscription and keep it up to date and secure.

Frequently asked questions

Can we bring our existing patient records across?

Patient details, phone numbers and a summary of treatment history can be imported from Excel. A complete transfer of dental chart history from other software depends on what that software can export and is scoped per project.

We work with several dentists and chairs. How would the diary be set up?

We design it so that each dentist and each chair has its own diary. A procedure appointment books the dentist and the chair together, so if either is taken, no second appointment can go into the same slot. Durations for each type of procedure are defined with you.

Will reception be able to see clinical notes?

Not unless you allow it. In the setup we recommend, reception books appointments and takes payments but cannot open clinical records or X-rays. Because health data is special-category personal data, this separation is one of the foundations of lawful processing, and every time someone opens a record it is logged.

Will dentists be able to record treatment on a tablet at the chair?

That is one of the main design criteria. Our aim is that a completed procedure can be marked on the dental chart with a few taps, because writing long notes mid-treatment is not realistic. The screens are designed for both tablet and desktop.

Can patients see their own treatment plan?

A limited patient view showing planned treatments, completed work and the payment schedule can be included in the scope. When patients can see their own plan and payments, it helps cut down the questions at the desk and on the phone.

Could the software connect to official health information systems?

Sending data to official health systems depends on the obligations your clinic is subject to and on the technical requirements of those systems. If such a connection is needed, it is examined in the discovery meeting and scoped separately. We do not commit to an integration like this before the technical requirements and the official process are clear.

How will an earlier treatment plan be handled after a change?

In the software we will build, linking a plan revision to its date, reason and authorised user can be included in scope. Completed procedures, postponed sessions and new proposals will be defined together as separate statuses.

Must instalments follow the same sequence as treatment sessions?

Payment schedules and clinical progress can be designed as separate processes. During discovery, we will define which payment belongs to which plan; clinical decisions will remain with your dentist.

How is the price set?

After a discovery meeting we prepare a written quote covering the scope, the modules and the setup work. The software is provided on a monthly or annual subscription.

Do we receive the source code?

In our standard model the software is provided on a subscription and the source code is not transferred. If you need a different model, it is agreed in a separate written contract.

Who is responsible for what is done with the software?

We build and operate the software. The business using it is responsible for how it is used, the data entered and the content published; the details are set out in the service agreement.

Related products

Let us clarify your clinical record links

Share treatment plan and session samples with patient details removed so we can examine their links to image files and define the clinic's initial scope.

  • Scope shaped around your workflow
  • Roles and record design
  • Integrations subject to conditions