Practice management and scheduling systems
Assessed only where the organisation owns the licence and the vendor exposes a supported interface.
Most common blockerNo documented interface, or vendor authorisation the organisation does not hold.
Integrations
No integration is claimed before it has been confirmed.
Integration availability is assessed during implementation planning. PulseArc does not imply compatibility with a system until it has been confirmed for that organisation.
Current position
There are no publicly listed integrations.
PulseArc has no contracted, publicly disclosable integration to list at this time. Rather than display logos or system names that suggest a relationship that does not exist, this page states the position directly.
How an integration would be assessed
- 1You identify the system, its owner inside your organisation, and the exact data or workflow you need exchanged.
- 2We confirm whether the system exposes a supported interface and whether your organisation is authorised to use it.
- 3Privacy roles, access requirements and technical dependencies are documented before any build work is considered.
- 4If it proceeds, the scope, prerequisites and limitations are fixed in writing in the applicable agreement.
No integration, compatibility, partnership or connection is promised before technical, commercial, security and legal assessment is completed and confirmed in writing.
No partner, API, clinical-system, payment-provider, insurance or government connection is offered or implied anywhere on this website.
Assessment categories
The kinds of system we are asked about
Listing a category is not a claim of compatibility. It records the questions an assessment starts from and the obstacle that most often ends it.
Messaging and notification providers
The organisation supplies and owns the provider account; PulseArc does not resell messaging.
Most common blockerSender registration, consent basis or template approval not yet in place.
Identity and staff directory
Considered where an organisation wants access administration to follow its existing joiner and leaver process.
Most common blockerNo single authoritative staff directory across sites.
Reporting and data export destinations
Scheduled export of platform-recorded activity to a destination the organisation controls.
Most common blockerUndefined report definitions, or a destination with no named internal owner.
Clinical record systems
Treated as out of scope unless a separate assessment, privacy review and written agreement are completed for that organisation.
Most common blockerClinical data governance requirements the organisation has not yet resolved internally.
None of the categories above represents an existing connection, a partnership or a vendor relationship. Each is assessed for one organisation at a time and is only offered once it is confirmed in writing.
Discuss a specific system.
Tell us which system you operate and who owns it internally, and we will tell you whether an integration is realistic.