# Integrations

Architecture, appointment sync, requirements and compatibility for IT teams

For IT teams assessing Diarybook as an **integration layer**: running alongside an existing patient
management system (PMS) or hospital information system (HIS), and adding automated reminders
without replacing it.

Your source system stays the master record, and appointments continue to be booked in it. Your
side runs a scheduled export that writes upcoming appointments to a flat file and uploads it to
Diarybook's SFTP endpoint. Diarybook reads the file, syncs the clients and appointments into your
account, and sends reminders according to the rules set for each clinic code.

Data flows outbound from your network only. Diarybook has no inbound access, no VPN into your
network and no credentials for your database, so the integration stays under your own change
control.

## The pages

- [Integration Overview](/docs/integrations/integration-overview/): what connects to what, the
  daily file and its format, and how records are matched.
- [Appointment Sync Service](/docs/integrations/appointment-sync-service/): the messaging side of
  an integrated service, including two-way replies.
- [Requirements and Compatibility](/docs/integrations/requirements-and-compatibility/): which
  source systems feed Diarybook today, what network access each side needs, and the optional route
  for sending replies back.

<!-- Add as it publishes — linking now would 404:
- [Security and Data Protection](/docs/integrations/security-and-data-protection/) -->

Certifications and supplier documentation for security questionnaires are in the
[Trust section](/trust/). For how an integrated account looks to the staff using it, see
[Standalone or Synced](/docs/start-here/standalone-or-synced/).

## Pages in this section

- [Appointment Sync Service](https://diarybook.com/docs/integrations/appointment-sync-service/): syncing appointments to leverage diarybooks advanced messaging platform
- [Integration Overview](https://diarybook.com/docs/integrations/integration-overview/): How appointment data reaches Diarybook from an existing system — clinic codes, the daily file, its format, and how records are matched.
- [Requirements and Compatibility](https://diarybook.com/docs/integrations/requirements-and-compatibility/): Which source systems feed Diarybook today, what network access each side needs, and the optional route for sending replies back.

---
Source: https://diarybook.com/docs/integrations/