From discovery to first site —
then scale.
PULSE implementation begins with a controlled understanding of the patient journey, the operating model and the systems around it. The first site proves the operating pattern. Later sites reuse the platform, evidence and deployment approach.
The implementation path.
Seven controlled phases take PULSE from discovery to a repeatable rollout factory. Select a phase to see what is understood and what it produces.
Discover
Understand & define
Output
Controlled client evidence and scope baseline.
Indicative first-site timeline.
A staged view of how a first-site programme typically progresses from discovery to pilot hypercare.
Discovery and mobilisation
Solution and detailed design
Core platform and foundational module build
Integration and validation
Site readiness and deployment
Pilot and hypercare
Indicative planning timeline. The actual programme depends on selected modules, integrations, client readiness, evidence and pilot scope. This is not a contractual schedule.
What a first-site pilot may include.
A reference pilot is deliberately bounded — one facility, a small set of approved services, and a clear evidence baseline before any expansion.
- A selected facility and approved service boundary
- One to three approved services or patient journeys
- PULSE Core
- Agreed foundational modules
- Relevant role-based workspaces
- Priority integrations or a controlled interim data route
- Journey and Work Item configuration
- Accepted operational baseline
- Pilot success measures
- Role-based testing and training
- Go-live readiness and rollback controls
- Hypercare
- Evidence and scale review
Illustrative pilot composition. Final scope requires client evidence, governance and approval. This is not a contractual scope.
What the pilot seeks to measure.
Measures are defined against an accepted baseline. The pilot does not promise a guaranteed result — it builds evidence for decision-making.
| Measure | Potential evidence source | Decision use |
|---|---|---|
| Wait to first action | Journey and Work Item timestamps | Identify where demand is building |
| Work Item age | Work Item state history | Flag ageing or stalled work |
| Unowned work | Work Item ownership state | Reassign or escalate unowned items |
| Hand-off acceptance | Hand-off and acceptance events | Detect unaccepted transfers |
| Patient-status visibility | Journey state availability | Reduce status enquiries |
| Repeat status enquiries | Communication and contact logs | Target communication gaps |
| Staff interruption | Work Item interruption events | Improve work ownership |
| Journey-completion evidence | Completion and hand-off records | Confirm closed-loop outcomes |
| Escalation response | Escalation timestamps and resolution | Assess escalation effectiveness |
| Adoption | Workspace and Work Item usage | Guide training and change |
| Safety exceptions | Safety exception and incident log | Strengthen safety controls |
| Privacy exceptions | Privacy exception log | Reinforce data governance |
| Operational exceptions | Operational exception events | Tune workflows and capacity |
Wait to first action
Evidence: Journey and Work Item timestamps
Decision use: Identify where demand is building
Work Item age
Evidence: Work Item state history
Decision use: Flag ageing or stalled work
Unowned work
Evidence: Work Item ownership state
Decision use: Reassign or escalate unowned items
Hand-off acceptance
Evidence: Hand-off and acceptance events
Decision use: Detect unaccepted transfers
Patient-status visibility
Evidence: Journey state availability
Decision use: Reduce status enquiries
Repeat status enquiries
Evidence: Communication and contact logs
Decision use: Target communication gaps
Staff interruption
Evidence: Work Item interruption events
Decision use: Improve work ownership
Journey-completion evidence
Evidence: Completion and hand-off records
Decision use: Confirm closed-loop outcomes
Escalation response
Evidence: Escalation timestamps and resolution
Decision use: Assess escalation effectiveness
Adoption
Evidence: Workspace and Work Item usage
Decision use: Guide training and change
Safety exceptions
Evidence: Safety exception and incident log
Decision use: Strengthen safety controls
Privacy exceptions
Evidence: Privacy exception log
Decision use: Reinforce data governance
Operational exceptions
Evidence: Operational exception events
Decision use: Tune workflows and capacity
Measures are evidence-led. No guaranteed improvement, target percentage, customer baseline, contractual threshold or invented result is implied.
Staged module rollout.
A recommended sequence that establishes the foundation, adds engagement and control, then activates optional extensions.
Foundation
- PULSE Core
- PULSE Access
- PULSE Flow
- Basic operational evidence
- Initial role workspaces
Engagement and Control
- PULSE Engage
- PULSE Command
- Expanded worklists
- Operational governance
- Patient communication
Optional Extensions
- PULSE Verify
- PULSE Resource
- PULSE Navigate
- PULSE Insight
- PULSE Edge
Final sequencing depends on the client problem, site readiness, providers and intended use.
Client and PULSE responsibilities.
A balanced operating model. Roles, not named people, define who is accountable across the programme.
Client team
- Executive Sponsor
- Product Owner
- Clinical Safety Officer
- Design Authority
- Privacy and Security
- Operations Lead
- Site Leadership
- Integration and Data Owners
- Commercial Authority
- Service Owner
PULSE team
- Programme Leadership
- Product and Journey Design
- Solution Architecture
- Engineering
- Integration
- Data and Migration
- Clinical-Safety Support
- Privacy and Security Support
- Testing and Evidence
- Training and Change
- Deployment
- Hypercare and Service Transition
One site first.
Rollout factory next.
What is proven at the first site becomes the reusable foundation for every site that follows.
What becomes reusable
How PULSE is delivered safely.
Evidence before approval.
Safety before activation.
One primary deployment architecture.
Feature flags for controlled rollout.
Rollback before go-live.
Competency, not attendance.
Hypercare with exit criteria.
Benefits measured against accepted baselines.
What a PULSE discovery discussion covers.
The initial discussion is intended to understand the operational problem and determine whether a structured discovery or first-site pilot is appropriate.
- Selected facility or service
- Current patient journey
- Common delay and hand-off points
- Staff roles and operational ownership
- Existing systems
- Integration boundaries
- Devices and connectivity
- Potential pilot scope
- Candidate success measures
- Next-step options
