Integrations overview
Miraa connects to other tools your clinic uses — practice management systems, calendars, secure messaging, and email. Integrations vary in maturity, so this section is careful to show real status.
Never assume an integration is live. An integration only exchanges real data when it’s genuinely connected and confirmed. Miraa’s UI is designed to reflect the true status — if something isn’t connected, don’t rely on it.
How to read status
Available now — works today, end to end.
In development — being built or requires vendor/partner approval before it can operate.
Planned — on the roadmap, not yet built.
Needs confirmation — check with your Miraa contact before relying on it.
Status of the integrations in these docs
| Integration | What it’s for | Status |
|---|---|---|
| Transactional email to patients and clinicians | Available now | |
| Calendar (Google, Microsoft) | Connect clinic calendars | Available now (OAuth) |
| Cliniko (PMS) | Practice management connector | In development (verification pending) |
| HealthLink | Secure messaging for referrals | In development (vendor-gated) |
| Best Practice | PMS connector | Planned (partner access) |
| Genie | PMS connector | Needs confirmation |
Release is gated by VERIFIED_INTEGRATION_IDS in
miraa-app/src/lib/integrations/availability.ts — a connector is only “Available
now” once its id is uncommented there.
Miraa also connects to other practice management, EMR, calendar, and secure messaging systems at varying stages of maturity. This section documents the ones most commonly asked about. For the current status of any specific connector, check your Integrations area in the app or ask your Miraa contact.
Setting up an integration
Check the status
Confirm the integration is available for your clinic and plan.
Connect it
Follow the connection flow in your Integrations area. Connecting usually requires admin access and credentials or an authorisation step.
Confirm it’s working
Verify the connection succeeds and behaves as expected before relying on it.
Admin only. Connecting integrations is typically an admin task and may require specific permissions.
Operational cautions
- Data leaves your clinic when an integration transmits — make sure the recipient and content are correct.
- Approval still applies. Clinical content sent through an integration must be clinician-approved first. See Clinician approval.
- Credentials are sensitive. Integration credentials are stored securely and never displayed in full.