A summary independent of the video, organized by chapter. Each part explains what was tested in the interface and what depends on configuration or permission.
What will you see in the tour?
00:00
A tour of Nasaq Care with synthetic data that starts with the dental chart, then follows one patient from the appointment to the invoice, payment and follow-up. The goal is to prove the current interface and its boundaries, not to show marketing promises.
How are tooth condition, periodontal data and the plan recorded?
00:50
The chart uses FDI numbering and shows conditions on teeth 16, 17, 26 and 36. The periodontal section records mobility, pocket values, bleeding and notes per tooth, and the treatment plan shows procedures, priority and estimated price. These sections are saved inside the visit.
How does the clinic organize appointments and booking?
01:53
The demo clinic has two branches, two doctors and dental services, and reception shows the day schedule with doctor, date and status filters. We created a new appointment, reopened the date and confirmed it appeared in the schedule.
How does a patient book from outside the clinic?
02:47
The public booking page lets the patient choose a branch, service and day, view available arrival windows, enter patient data and submit the request. A test request arrived in the reception online bookings list.
What happens from arrival to calling the patient?
03:31
Reception checks the patient in, the patient appears in the queue, and the doctor sees the list and presses the call patient button. The status changes at reception after the call, showing the handoff between the two roles.
How does the doctor review previous visits?
04:16
The patient record brings data, visits and documents together. The demo patient has two previous visits on different dates, and the doctor can open either before the current visit.
How is the examination saved and verified?
05:03
We changed the symptom duration inside the visit, pressed save draft, then reopened the visit. The value was still saved, which proves the save is tied to the correct visit and template.
How are chart, periodontal data and plan edited and saved?
05:48
We added tooth 17 to the chart, a periodontal row for tooth 36 and a new treatment plan item. After saving and reloading, all three additions appeared again.
What appears in the report and attachments?
06:40
The visit contains a synthetic panoramic X-ray linked to the patient and visit. The print report shows patient data, the chart, periodontal rows, the plan, completed procedures and attachments.
How are invoice, payment and receipt linked to the patient?
07:24
The invoice is linked to the patient and visit. In the example the total is 600 pounds with a previous 200 payment. We recorded a 250 payment from the billing account, the balance updated to 450 paid and 150 remaining, and a receipt was issued.
How do follow-up, multiple doctors and branches work?
08:13
The follow-up is linked to the patient with a reason and date, and we created a future appointment for the same patient. We tested the second doctor on the Maadi branch and their patient appeared in the queue, while official doctor and branch limits appear in the plan source.
What is proven from the interface and what remains API-only?
09:06
Appointments, public booking, reception, queue, record, visit, chart, periodontal data, plan, attachments, report, invoice, payment, follow-up and multiple doctors and branches are proven in the interface. The longitudinal chart and performing and billing a plan item were verified through the API and tests, not through a web interface in this release.