A configured operational environment, not an off-the-shelf product.
PulseArc is configured to the administrative workflows an organisation already runs. Nothing is switched on until it has been scoped, agreed and validated with that organisation.
Platform status: Implementation-led delivery
PulseArc is delivered as a configured implementation for healthcare organisations. Modules, integrations and scope are agreed with each organisation in writing, and every environment is configured for that organisation alone. PulseArc supports administrative and operational work only — it does not provide medical advice, diagnosis, treatment or emergency response.
An administrative setting of the kind PulseArc supports. No patient data is shown.
Modules
Module scope and status
Module names describe the operational problem they support. Where an area is planned, it is labelled as planned and carries no commitment.
Patient communication support
Available by approved implementation
Configured outbound messaging templates and message logs for administrative contact with the people an organisation already has a relationship with.
Intended organisational user
Front-desk and patient-administration teams
Workflow result
Sending agreed administrative messages and keeping a record of what was sent, when and by which user.
Customer input or system dependency
The organisation supplies its own contact lists, message wording and consent basis, and provides the messaging account used for delivery.
Important boundary
Administrative messaging only. PulseArc does not author clinical content and does not decide who may be contacted.
Appointment and follow-up workflow support
Available by approved implementation
Configured queues, statuses and reminders that mirror an organisation's existing booking and follow-up steps.
Intended organisational user
Scheduling coordinators and service managers
Workflow result
Tracking which appointments and follow-up tasks are open, assigned or overdue against the organisation's own rules.
Customer input or system dependency
The organisation defines its appointment types, service rules and who is authorised to act on each queue.
Important boundary
Workflow tracking only. It does not triage, prioritise clinically, or determine clinical urgency.
Operational reporting
Available by approved implementation
Reports built from the activity recorded inside the configured environment — volumes, task ageing, completion and user activity.
Intended organisational user
Operations leads and organisation administrators
Workflow result
Producing recurring operational reports for internal management review.
Customer input or system dependency
Report definitions, comparison periods and distribution lists are agreed with the organisation during configuration.
Important boundary
Reports describe recorded platform activity only. They are not clinical, financial or regulatory reporting.
Organisation-level service coordination
Available by staged rollout
Shared task and hand-off views across more than one site or team within the same organisation.
Intended organisational user
Multi-site operations and administration teams
Workflow result
Coordinating administrative hand-offs between locations or departments under one organisation account.
Customer input or system dependency
The organisation confirms its site structure, user roles and which information may be visible across sites.
Important boundary
Available to a small number of organisations while the configuration model is validated.
Approved integration support
Available by approved implementation
Assessed, contracted connections to systems an organisation already operates.
Intended organisational user
Organisation IT and system owners
Workflow result
Exchanging agreed operational data with a named source system.
Customer input or system dependency
The organisation must own or be authorised to access the target system and its interfaces.
Important boundary
No integration is offered or implied until it has been assessed and confirmed in writing for that organisation.
Availability
Capability and availability matrix
PulseArc capabilities, their intended users, current availability, customer dependencies and limitations.
Capability
What it supports
Intended organisation
Current availability
Customer dependency
Important limitation
Configured operational environment
A workspace configured to an organisation's agreed administrative workflows.
Healthcare organisations with in-house administration teams
Available by approved implementation
Agreed scope and named organisational owners.
Configuration scope is fixed in the applicable agreement.
User accounts and access management
Creating, changing and removing access for authorised users.
Organisation administrators
Available by approved implementation
The organisation nominates administrators and maintains its own user list.
PulseArc does not decide who inside an organisation should have access.
Administrative messaging support
Agreed outbound administrative messages and message records.
Patient-administration teams
Available by approved implementation
Organisation-owned messaging account and message wording.
Not for clinical communication or emergency contact.
Operational reporting
Recurring reports on recorded platform activity.
Operations and service management
Available by approved implementation
Agreed report definitions and recipients.
Covers platform-recorded activity only.
Multi-site coordination
Shared administrative task views across sites in one organisation.
Multi-location organisations
Available by staged rollout
Confirmed site structure and visibility rules.
Limited number of organisations while the model is validated.
System integrations
Agreed data exchange with a named organisational system.
Organisations with an internal system owner
Available by approved implementation
Documented access to the target system.
Assessed case by case. No compatibility is implied in advance.
Payment and receipt workflows
Not offered on the platform at this time.
—
Available on scoped request
—
PulseArc does not currently provide payment processing, receipting or merchant services.
Configured operational environment
Available by approved implementation
What it supports
A workspace configured to an organisation's agreed administrative workflows.
Intended organisation
Healthcare organisations with in-house administration teams
Customer dependency
Agreed scope and named organisational owners.
Important limitation
Configuration scope is fixed in the applicable agreement.
User accounts and access management
Available by approved implementation
What it supports
Creating, changing and removing access for authorised users.
Intended organisation
Organisation administrators
Customer dependency
The organisation nominates administrators and maintains its own user list.
Important limitation
PulseArc does not decide who inside an organisation should have access.
Administrative messaging support
Available by approved implementation
What it supports
Agreed outbound administrative messages and message records.
Intended organisation
Patient-administration teams
Customer dependency
Organisation-owned messaging account and message wording.
Important limitation
Not for clinical communication or emergency contact.
Operational reporting
Available by approved implementation
What it supports
Recurring reports on recorded platform activity.
Intended organisation
Operations and service management
Customer dependency
Agreed report definitions and recipients.
Important limitation
Covers platform-recorded activity only.
Multi-site coordination
Available by staged rollout
What it supports
Shared administrative task views across sites in one organisation.
Intended organisation
Multi-location organisations
Customer dependency
Confirmed site structure and visibility rules.
Important limitation
Limited number of organisations while the model is validated.
System integrations
Available by approved implementation
What it supports
Agreed data exchange with a named organisational system.
Intended organisation
Organisations with an internal system owner
Customer dependency
Documented access to the target system.
Important limitation
Assessed case by case. No compatibility is implied in advance.
Payment and receipt workflows
Available on scoped request
What it supports
Not offered on the platform at this time.
Intended organisation
—
Customer dependency
—
Important limitation
PulseArc does not currently provide payment processing, receipting or merchant services.
Product visuals
Why there are no product screenshots here.
Screens from a configured environment contain an organisation's own operational data. PulseArc does not publish them, and does not publish invented substitutes dressed up as evidence. Where a visual helps explain the platform, it is a labelled diagram.
PulseArc is a technology provider. It does not provide medical advice, diagnosis, treatment, emergency response or clinical decision-making.
Workflow diagram — no patient data or customer records are shown.
1
Organisation account
One account per contracted organisation, with its configuration kept separate from any other.
2
Sites and teams
The organisation's own structure, as it confirms it during implementation.
3
Named user accounts
Created, changed and removed by the organisation's nominated administrators.
4
Workflow records
Administrative records created by those users, retained on terms agreed with the organisation.
5
Operational reports
Built only from activity recorded inside that same environment.
The structure of a configured environment: how access, records and reporting are arranged for a single organisation.
Integrations
No integration, compatibility, partnership or connection is promised before technical, commercial, security and legal assessment is completed and confirmed in writing.
Ask whether a specific workflow is in scope.
Describe the coordination problem you are trying to solve and we will tell you whether the current platform supports it.
