Dentally Platform Reference¶

Public Information Compilation — Foundation for Middleware Integration

Prepared for: Supreme Dental Clinics Middleware Project Source: Publicly available information as of May 2025 Purpose: Serve as the foundation document for understanding Dentally's capabilities before vendor engagement

1. Platform Overview¶

Dentally is a cloud-based dental practice management software (PMS) developed by Henry Schein One. It brings together clinical, practice admin, and patient experience features in a single platform.

Key Characteristics: - Cloud-based — No on-premise installation required - Multi-site support — Group visibility and consistency across locations - NHS integrated — Fully integrated with NHS in England, Wales, Scotland and HSC in Northern Ireland - API-first — REST API available for integration (v1) - Partner ecosystem — Marketplace of third-party integrations

Target Markets: - Multi-site practices (group visibility and consistency) - New practices (intuitive, fast, flexible) - NHS and HSC practices

2. Feature Modules¶

2.1 Clinical Features¶

Efficient dental charting
AI-powered clinical notes
Treatment planning
Advanced imaging with AI-powered detection (Dentally Vision)
Clinically compliant AI tools

2.2 Practice Admin Features¶

Automated messaging — Appointment reminders, confirmations
Real-time reporting — Practice performance dashboards
Short notice appointment filler — Waitlist management
Scheduling & diary management — Chair time utilisation
Recall automation — Patient recall management
Monthly accounts — Practitioner and associate pay tracking
Outstanding Treatment report — Identifies patients with incomplete care

2.3 Patient Experience Features (Dentally Portal)¶

Online appointment booking
Digital form filling (medical histories, consent forms)
Seamless arrivals (kiosk/tablet check-in)
Patient self-service portal

2.4 Dentally Vision (Imaging)¶

Cloud-based imaging workspace
AI-powered condition detection
Integrated with clinical workflow

2.5 Key Reports Available¶

Report	Purpose
Patients report	Build targeted patient lists
Recall Effectiveness report	Past and future recall performance
Monthly Accounts report	Practitioner and associate pay
Outstanding Treatment report	Patients with incomplete care
Custom reporting via MPC	Advanced analytics (partner integration)

3. API Capabilities¶

Based on the official Dentally Developer Hub (https://developer.dentally.co/):

3.1 API Overview¶

Protocol: REST API
Format: JSON
Version: v1 (default, optional in URL)
Authentication: Not publicly documented (requires vendor engagement)
CORS: Supported for AJAX requests from any origin
User Agent: Required header for all requests
Pagination: 25 items default, up to 100 per page
Sorting: Supported via sort_by and sort_direction parameters
Metadata: Custom key-value data (up to 3 keys, 40 char keys, 500 char values)

3.2 Documented API Endpoints¶

Resource	Endpoint	Operations	Key Data
Accounts	`/v1/accounts`	GET (single, list)	Balance, patient ID, planned treatment values
Acquisition Sources	`/v1/acquisition_sources`	GET (list)	Source name, active status
Appointment Cancellation Reasons	`/v1/appointment_cancellation_reasons`	GET (list)	Reason, type, archived status
Appointments	`/v1/appointments`	GET, POST	Start/finish time, practitioner, patient, state, reason, duration, notes, metadata, room
Patients	`/v1/patients`	(Likely GET/POST — needs confirmation)	Patient demographics, contact info
Practitioners	`/v1/practitioners`	(Likely GET — needs confirmation)	Practitioner details
Rooms	`/v1/rooms`	(Likely GET — needs confirmation)	Room configuration
Treatment Plans	`/v1/treatment_plans`	(Likely GET/POST — needs confirmation)	Treatment plan details

3.3 Appointment States¶

The appointment lifecycle includes these states: - Pending - Confirmed - Arrived - In surgery - Completed - Cancelled - Did not attend

Each state has a corresponding timestamp field (e.g., confirmed_at, arrived_at, completed_at).

3.4 Appointment Reasons¶

Exam
Scale & Polish
Exam + Scale & Polish
Continuing Treatment
Emergency
Review
Other

3.5 Metadata Feature¶

Custom key-value data can be attached to Patients and Appointments. This is a critical integration point — middleware can store its own references on Dentally objects.

3.6 Webhooks¶

Not confirmed from public docs. This is a key question for vendor engagement. Webhooks would enable real-time event-driven integration (e.g., notify middleware when an appointment is created or modified).

4. Integration Ecosystem¶

4.1 Partner Categories¶

Category	Examples
Imaging & Infrastructure	Dental imaging software, connectivity tools
Patient Communication	Boxly, Working Feedback
Payments & Finance	Dojo, Worldpay
Practice Growth	Marketing, patient acquisition tools
Reporting, Workflows & Compliance	My Practice Cloud (MPC), Chairsyde, Dent Compliance

4.2 Notable Partners¶

Boxly — Patient communication and marketing
My Practice Cloud (MPC) — Advanced reporting and analytics
Chairsyde — Treatment plan presentation
Working Feedback — Patient feedback and reputation management
Dojo — Payment processing
Worldpay — Payment processing
Dent Compliance — Compliance management

4.3 Integration Pattern¶

Dentally's integration approach appears to be API-based with a partner marketplace model. Third-party applications connect via the REST API to read/write Dentally data.

5. Security & Compliance¶

Based on public information: - Cloud-based — Data stored in the cloud (specific region TBC with vendor) - Encrypted databases — Data encryption at rest - User permissions — Role-based access control - IP restrictions — Network-level security controls - Compliance certification — Formal compliance certifications (specific frameworks TBC) - Unlimited cloud storage — Included as standard - Offline capability — Can run over 3G/4G/5G mobile data if internet goes down

Key questions for vendor: - What specific compliance certifications? (ISO 27001, SOC2, HIPAA?) - Where is data stored geographically? - What is the backup and disaster recovery policy? - Is there audit logging of all data access?

6. Multi-Site Capabilities¶

Dentally explicitly supports multi-site practices with: - Group visibility across every location - Consistency across sites - Central management capabilities (extent TBC with vendor)

This is critical for Supreme Dental Clinics which operates multiple locations.

7. Data Model & Key Objects¶

Based on API documentation, the core data objects are:

Patient
  ├── id, name, contact info, image
  ├── Account (financial)
  │     ├── current_balance
  │     ├── opening_balance
  │     ├── planned_nhs_treatment_value
  │     └── planned_private_treatment_value
  ├── Appointments
  │     ├── start_time, finish_time, duration
  │     ├── practitioner_id, patient_id
  │     ├── state (Pending → Confirmed → Arrived → In surgery → Completed)
  │     ├── reason, notes
  │     ├── room_id
  │     ├── metadata (custom key-value)
  │     └── cancellation_reason_id
  ├── Treatment Plans
  └── Metadata (custom key-value)

8. Integration Points for Middleware¶

8.1 Data Flow: Dentally → Middleware¶

Data	Method	Real-time?	Priority
Appointment created/updated	API poll or webhook	Preferred	High
Patient demographics	API pull	Batch OK	High
Appointment status changes	API poll or webhook	Preferred	High
Recall due patients	API pull	Batch OK	Medium
Outstanding treatment	API pull	Batch OK	Medium
Account/balance changes	API pull	Batch OK	Low

8.2 Data Flow: Middleware → Dentally¶

Data	Method	Real-time?	Priority
Appointment creation (from phone/online)	API POST	Yes	High
Patient updates	API PUT	Yes	High
Metadata enrichment	API PUT	Batch OK	Medium
Treatment plan updates	API POST/PUT	Batch OK	Medium

8.3 Key Integration Requirements¶

Authentication — API key or OAuth (TBC with vendor)
Webhooks — For real-time event notifications (TBC with vendor)
Rate limits — API usage limits (TBC with vendor)
Data mapping — Dentally data model → Middleware schema
Error handling — Retry logic, idempotency, conflict resolution

9. Gap Analysis Template¶

To be completed after vendor engagement and client validation

Capability	Public Info	Vendor Confirmation	Supreme Usage	Gap
API - Appointments	✅ Documented
API - Patients	Likely available
API - Webhooks	❌ Not confirmed
Multi-site management	✅ Supported
NHS integration	✅ Supported
Custom reporting	Via MPC partner
Audit logging	TBC
Real-time events	TBC

10. Reference Links¶

Resource	URL
Dentally Homepage	https://www.dentally.com/en-gb
Platform Features	https://www.dentally.com/en-gb/dental-software-features
Clinical Features	https://www.dentally.com/en-gb/dental-software-features/clinical
Practice Admin Features	https://www.dentally.com/en-gb/dental-software-features/practice-admin
Patient Portal	https://www.dentally.com/en-gb/product/dentally-portal
Dentally Vision	https://www.dentally.com/en-gb/product/dentally-vision
Integrations	https://www.dentally.com/en-gb/integrations
Security	https://www.dentally.com/en-gb/security
Cloud Benefits	https://www.dentally.com/en-gb/cloud-based-dental-software
Pricing	https://www.dentally.com/en-gb/pricing
Customer Stories	https://www.dentally.com/en-gb/stories
FAQs	https://www.dentally.com/en-gb/resources/faqs
Developer Hub (API Docs)	https://developer.dentally.co/
Community	https://community.dentally.com/
Academy (Training)	https://academy.dentally.com/
Help Centre	https://help.dentally.com/en/
Onboarding	https://www.dentally.com/en-gb/resources/easy-onboarding

This document is a compilation of publicly available information. It serves as the foundation for understanding Dentally's capabilities. Gaps identified will be addressed through vendor engagement (Issue #1) and client validation with Grace Tan.

Next step: Assign a staff member to review this document and the linked resources, then update the Gap Analysis section with findings.