Implementation
An implementation begins with scope and responsibility, not with software.
Implementations are opened by discussion with the organisation. There is no self-serve onboarding.
Process
Six stages, in order
- 1
Organisation discovery
Confirm the operating context, the workflows in question, the stakeholders involved and the boundaries of what technology should and should not touch.
- 2
Scope and responsibility review
Define in writing what PulseArc will configure and what remains with the organisation, including clinical, consent and regulatory ownership.
- 3
Data and integration assessment
Confirm which data sources are approved, what access is required, which technical dependencies exist and which privacy roles apply.
- 4
Configuration and validation
Configure the agreed environment and validate it with the organisation's own authorised users before it is relied upon.
- 5
Training and handover
Provide the agreed operational guidance, administrator instructions and the named support contacts.
- 6
Ongoing support and change management
Handle issues, configuration changes and any future modules through the approved support route.
Implementation timing, available modules, integration support, training and any service levels are confirmed in the applicable agreement. This page does not state a delivery timeline.
Before we start
What your organisation needs to have
- A named internal owner for the workflows in question
- Agreement internally on which administrative steps are actually in scope
- A nominated administrator who will manage user access
- Clarity on your own consent, privacy and regulatory position
- For any data source or system: its internal owner and your authority to use it
Afterwards
Support and change management
A single documented support route by email to the organisation's named PulseArc contact. Configuration changes, issues and any future modules are handled through that same route so there is one record of what was requested and agreed.
Support hours and response times are not published on this website. Where an organisation requires a specific commitment, it is agreed in the applicable agreement.
Start with a scope conversation.
The first discussion is about your operating context and where the boundaries sit — not a product walkthrough.