Skip to main content

Clinic integrations

Your clinic’s tools, working together.

Keep the clinic’s email, diary and payments connected to its day-to-day work. Start with the accounts your team uses, check the setup, and agree what is included before switching.

Start with email, calendar and payments

These connections need your clinic’s account, permissions and setup checks. Confirm the scope in your plan and signed order; listing a provider here does not switch it on for your clinic.

Clinic setup required

Gmail or Outlook email

Connect your clinic’s Gmail or Outlook mailbox to the shared inbox. Your clinic approves the account and access; staff check recipients and approve outgoing messages. A mailbox connection does not enable organisation-wide single sign-on.

Clinic setup required

Stripe

Payment links are available only after the clinic, signed order and live Stripe configuration are approved. Automatic receipts, card-on-file and financing are not universally claimed.

Clinic setup required

Google Calendar or Outlook

Connect Google Calendar or Outlook through your clinic’s approved account. Calendar sync requires connection, permission checks and a successful setup check for the clinic.

Check the fit before you connect

  1. Name the account. Bring the provider names and the work you need connected. Keep passwords and patient details out of your enquiry.
  2. Agree the scope. Confirm the plan, permissions, provider charges and what will remain in your existing system.
  3. Check it with your team. Verify the connection and who can use it before relying on it for clinic work.
Discuss your setup in a demo

Connections that are not available

Keep using your clinic’s approved channels for these services. No launch date or future connection is promised here. Email and calendar connections above are separate from organisation-wide sign-in below.

Communication · Not available

Healthmail — disabled

Not launch-authorised. Clinicians use the clinic’s approved referral channel until account, contract, recipient and production evidence is accepted.

Billing · Not available

PCRS — submission disabled

Not launch-authorised: clinics continue to use their normal PCRS claim channel.

Clinical · Not available

HSE Referrals

Not launch-authorised: clinicians verify recipients and use the clinic’s approved referral channel.

Telehealth · Not available

Zoom

Video is off; clinicians author notes and recording/Generative summaries are disabled.

Insurance · Not available

VHI — submission disabled

Not launch-authorised: no automated eligibility, prefill or submission.

Insurance · Not available

Laya — submission disabled

Not launch-authorised: no automated eligibility, prefill or submission.

Insurance · Not available

Irish Life Health — submission disabled

Not launch-authorised: no automated member verification or claim submission.

Identity · Not available

Microsoft 365 — not yet enabled

Not launch-authorised until the agreement, tenant configuration, roles and production authentication evidence are approved.

Identity · Not available

Google Workspace — not yet enabled

Not launch-authorised until the agreement, least-privilege IAM, key restrictions, logging and production authentication evidence are approved.

Identity · Not available

Okta — disabled

No launch-authorised SSO or SCIM route is claimed.

Internal · Not available

Slack

Not launch-authorised pending an approved vendor route, purpose and data-minimisation review.

Where your clinic’s records are hosted

Primary records are hosted in AWS Dublin (eu-west-1). Hosting providers support the service; they are not extra clinic accounts you need to connect.

Review security, hosting and provider disclosures
Hosting provider details

Supabase: Primary record storage is in AWS Dublin (eu-west-1). The database is backed up daily, eight backups are kept in the EU, and a restore was tested on 1 October 2026; point-in-time recovery is not on. RLS/security-lint, access, encryption and logging evidence is still outstanding.

AWS: Primary records are hosted in AWS Dublin (eu-west-1); other disclosed provider routes require separate transfer evidence.

Need another connection? Send an integration request. We assess the purpose, provider terms and data flow. A request is not a commitment to build or enable it.