Resources
Everything needed for a first review, in one place.
There is no gated content here and no download form. Each page states what is in scope and what is not.
Evaluating the platform
Platform scope and module availability
What each area supports, who it is for, and where the boundary sits.
Capability and service catalogue
Six quote-only services with prerequisites, inclusions, exclusions and boundaries.
Operational scenarios
Concrete coordination problems and what stays with the organisation.
Organisation types
Where the platform fits and the limitations for each type.
Due diligence
Delivery and support
Site content last reviewed: 31 July 2026. Questions about anything on these pages can be sent to management@pulsearc.online.
Evidence
Implementation evidence, shared appropriately
PulseArc does not publish customer names, patient data, unverified outcomes or screenshots from customer environments. Where an organisation has approved disclosure, relevant implementation material may be shared during a suitable organisation-level discussion.
Implementation approach
A documented process for defining scope, responsibilities, access and acceptance before configuration.
Due-diligence discussion
A structured conversation about operational needs, exclusions, data responsibilities and implementation dependencies.
Approved reference material
Shared only where it is genuine, authorised and appropriate to the requested discussion.
Before you enquire
A short internal checklist
Organisations that work through these points first get a far more useful first conversation, because the answers shape the scope.
- Confirm the platform scope covers the administrative problem you actually have.
- Read the boundary statement and check it against your internal governance expectations.
- Review the security and data-roles page with whoever owns privacy in your organisation.
- Identify your executive sponsor, operations owner and nominated administrator before discovery.
- Decide internally which cross-site visibility you are willing to allow.
- Agree who signs the scope and responsibility statement on your side.
Glossary
Terms as we use them
- Configured environment
- A workspace set up to one organisation's agreed administrative workflows, separate from every other organisation's.
- Administrative workflow
- A non-clinical coordination step — booking admin, follow-up chasing, hand-offs, access changes and routine messages.
- Boundary
- A written statement of what the platform does not do, kept alongside what it does so neither is assumed.
- Availability status
- The published position of a capability: live, available by approved implementation, available by staged rollout, planned, or available on scoped request.
- Quote-only service
- A service whose fee depends on sites, volume and configuration effort, and is issued in writing in AED against an agreed scope.
- Nominated administrator
- The person inside the customer organisation authorised to manage user access and raise change requests.
Something you need that isn't published?
Ask for it directly. If we can evidence it, we will send it in writing; if we cannot, we will say so.