Private Preview

Human Experience Intelligence Platform

From fragmented signals to confident, governed action

proHX is the intelligence engine between your data and your decisions — connecting patient, workforce, and operational signals into the clarity healthcare leaders need.

Patient signals
Workforce signals
Operational data
Public feedback
Survey streams
EHR events

Built by people who've seen this problem from both sides.

Oliver Sear

Oliver Sear

Founder

Ten years building the case for experience as a system-level driver, from IBM and PwC boardrooms into healthcare.

Why proHX
  • Visited 20 clinics across Dubai. Found the same gap in every one: leaders who could feel what was going wrong but had no way to bring it to a decision.
  • The gap between signal and decision is the problem. Not dashboards. Not surveys.
  • A decade translating experience into boardroom evidence, now applied where the stakes are highest.
Anushka Patchava

Anushka Patchava MD, MBA

Co-Founder

Physician and healthcare executive working across clinical care, insurance, pharma, and health tech. Advisor to the UN and WEF.

Why proHX
  • Saw the same structural problem from every angle: as a clinician, as an executive, as a policy advisor.
  • Healthcare doesn't lack information. It lacks the means to translate intelligence into action.
  • Operational intelligence will define resilience, performance, and outcomes this decade. proHX is built for that.
The problem

Healthcare has more data than ever. Confidence in decisions is declining.

The core problem is not a lack of data — it's the inability to translate it into aligned action. Experience does not fail suddenly. It erodes, quietly, across journeys and segments, weeks before outcomes fail.

Fragmented signals

Patient, workforce, and operational data live in disconnected dashboards, reviewed in separate forums by separate teams.

📉

Survey fatigue

Systems run 10–20+ surveys annually but response rates fall to 20–30%, with declining trust that feedback leads to action.

🔀

Conflicting dashboards

Different teams use different metrics, creating competing narratives about the same underlying problem.

🔁

No prioritisation layer

Without a clear intelligence layer, leaders default to the loudest problems — not the most important ones.

This is where proHX was born

Patient experience and workforce experience are two sides of the same system. Layer operational data over both, patient flow, length of stay, readmissions, turnover, and the business case for change writes itself. Experience isn't the soft metric. It's the leading indicator.

The platform

One intelligence engine. A governable human system.

This isn't another point solution. proHX starts at the signal and lands in the boardroom, a single intelligence layer between the systems you already run and the decisions your leadership has to make.

67% reduction in length of stay when systemic patterns are acted on at the right tier, not incident by incident Emes et al., 2019 (Health Systems)
>60% of hospital costs are labour, making workforce signal the highest-leverage source of experience intelligence Zinouri et al., 2018
12–20% typical patient survey response rate. Survey-led models are running on a fifth of the signal they think they have NHS England, 2023
4–8wks lead time between correlated workforce and patient signals forming, and a complaint or incident becoming reportable proHX pattern analysis
Intelligence Engine

Platform Core

Ingests signals continuously, constructs journeys automatically, overlays patient, workforce, and operational data — then prioritises what matters now.

  • Signal ingestion — read-only, API-based, event-driven
  • Normalisation and signal structuring at scale
  • Journey and segment engine — no manual mapping
  • Cross-signal correlation and leading indicator detection
  • Eight-domain Experience Framework
  • Prioritisation logic: impact × risk × repeatability
  • Learning loop — auditable, adaptive, continuous

Patient Module Capture

Contextual outreach and feedback capture across the patient journey — embedded, QR, and multi-channel. Right signal, right moment.

Workforce Reach Engage

Safe, flexible, and anonymous staff channels — capturing frontline pressure, barriers, and improvement signals before they become incidents.

CX Copilot Activate

Embedded AI agent that turns intelligence into reports, journeys, personas, stakeholder materials, and business cases. Makes the platform actionable.

Workforce Reach

Your staff already have the answers. We help them share.

proHX detects pressure signals from operational and clinical data, then opens a safe, anonymous channel for frontline staff to respond — in 30 seconds, on their own device.

Signal-triggered outreach
Reach-outs aren't scheduled — they fire when the platform detects elevated risk: readmission clusters, staffing pressure, complaint spikes.
🔒
Genuinely anonymous
No names, no device IDs, no shift-linking. Responses are federated and anonymised at source before they reach any analyst view.
💬
30-second interactions
Designed for clinical environments. Staff respond between tasks — one rating, one sentence, done. No login, no survey fatigue.
📊
Feeds directly into the platform
Every response is enriched, correlated, and surfaced in the intelligence layer — connecting frontline voice to operational and patient signals.
9:41 ●●●
proHX Reach Anonymous
⚡ Signal detected · Ward 7
Hi — we've noticed some pressure on Ward 7 this week. How are you feeling about your current workload?
😊
😐
😟
🔴
It's been a tough few shifts — short-staffed and the bay handovers are taking too long.
Received and logged — thank you. Your response is completely anonymous and will help improve resourcing decisions this week.
🏅 Contribution recognised — 3 colleagues also flagged handover pressure this week. Your voice shaped this week's action brief.
🔒 Your identity has never been visible to anyone — not your manager, not your team.
Patient Experience

Every patient has a journey. We help you see it, and hear it.

proHX reconstructs each patient's visit from signals your systems already hold, then opens a simple, personal channel for feedback at any point along the way. No generic surveys. No guesswork. Just the right question, at the right moment.

Reconstructed from your data
proHX rebuilds each patient's visit from signals your systems already hold. No new infrastructure, no manual mapping.
Asked at the right moment
Feedback prompts fire at meaningful touchpoints inside the journey, not weeks after. The question knows where the patient is and what just happened.
Context-aware questions
If the EHR shows a 54-minute wait, the question isn't generic. It's specific to that wait. No survey fatigue, no boilerplate.
Feeds directly into the platform
Every response is enriched, journey-anchored, and surfaced in the intelligence layer alongside workforce and operational signals.
11:02 ●●●
Your visit · City General
Today · 8 touchpoints
📱
Pre-visit
Appointment
📋
Check-in
Reception · 09:14
👩‍⚕️
Triage
Nursing · 09:31
Waiting
54 min · Waiting area
🔬
Diagnostics
Pathology · 10:41
🩺
Consultation
Dr. Ahmed · 11:02
How was your consultation experience?
👏 Send a shoutout
💊
Pharmacy
Pharmacy · 11:48
🏠
Discharge
Discharge · 12:15
📝
Review your whole visit 2-min survey · all 8 touchpoints
How It Works

From signal to impact, one connected loop

One worked example, Ward 4B, threading through seven beats of the proHX loop. From signal arriving, through investigation and decision, to the loop closing.

01 · Signal
Three streams. One unified signal.
Patient Engagement signals, Workforce Reach responses, and existing systems data flow in continuously, normalised and time-aligned into one schema. Read-only. No disruption to source systems.
Patient Engagement
2,847 signals
Workforce Reach
891 responses
Existing systems
47,214 records
02 · Journey Intelligence
Patient and workforce journeys, overlaid.
Journeys are inferred automatically from signal patterns. No workshops, no manual mapping. Patient friction and workforce pressure plotted on the same timeline. Where they converge, something real is happening.
Check-in
Triage
Waiting
Consult
Pharmacy
Discharge
Patient
Workforce
Positive
Moderate
High friction
⚡ 2 convergence points, Waiting and Discharge
03 · Forming Patterns
Where signals converge, a pattern forms.
The Core surfaces convergence as named, evidenced patterns. Not raw alerts. Each pattern carries its evidence: which signals, how many patients, how long it has been building.
High Ward 4B · Discharge Communication Friction
Patient signal x 23 Workforce signal x 4 Readmission +1.8pp 89 patients affected Building since W46
Medium Outpatient Clinic A · Wait Experience
Wait sentiment declining Short-staffed Tue to Thu 312 patients affected
04 · Investigations
When a pattern is forming, the Core asks better questions.
Patterns don't get promoted on signal volume alone. When confidence sits below threshold, the Core opens an Investigation. It dispatches targeted Workforce Reach prompts, frames context-aware patient questions, gathers the evidence it needs. The system asks. It doesn't wait.
01 Ward 4B discharge pattern, hypothesis being tested Investigating 76% to 87% confidence
02 Outpatient Clinic A wait sentiment, evidence gathering Investigating 58% confidence
03 Pharmacy counselling consistency, closed inconclusive Closed Insufficient evidence
05 · Prioritised Decisions
Confirmed patterns become briefs, scoped to authority.
When a pattern crosses confidence threshold, it becomes a governance brief. Each brief is scoped to the right authority tier, evidence-cited, and routed to a named owner. Decisions are signed. Nothing is assigned automatically.
Pattern
Ward 4B
89 patients · 87% confidence
Owner
Sarah Mahmoud
Head of Patient Experience
Option
People · 3w
Targeted clinician comms training
Status
Signed
Project opened W4
06 · Projects
Every accepted decision becomes a Project the Core watches.
Once a brief is signed, a Project opens. proHX continues listening for signal decay against the original pattern. The intervention is working, or it isn't, and the system tells you which. The loop is not optional. It is the product.
Project · Discharge friction · Ward 4B
Week 4 of 6
Intervention working: signals decaying as expected. Review scheduled W6.
07 · Outcome
The loop closes, or it routes back.
When signals decay, the Project closes and the pattern goes into history. When they don't, the Core routes back into a new Investigation, and the cycle starts again with what it learned. Every loop adds to the evidence base.
Closed
Ward 4B · Discharge friction
Signed Jan 8 Closed Feb 12 89 patients
Watching
What forms next
47 3 forming
Active signal streams across the network
The decision layer

Where intelligence becomes a signed decision.

CX Copilot turns a confirmed pattern into a governance-ready brief, drafted in seconds, scoped to the right authority tier, routed to a named owner. Not a chatbot. A governance instrument.

How it works
CX Copilot opens in context, never from scratch.
When the Core confirms a pattern, CX Copilot loads it in focus and suggests the next best actions, scoped to the user's authority tier. It's not a blank chatbot waiting for a prompt. It's a governance assistant with an opinion about what should happen next.

Try it: tap Build governance brief in the panel. Watch CX Copilot draft, then sign the brief and watch the loop close.
Tap an action to start
CX Copilot
Pattern-layer intelligence · Strategic tier
×
Pattern in focus
Discharge communication friction · Ward 4B
89 patients 6-week window 87% confidence
Next best actions
Build governance brief
Compose for the right authority tier
Compare to prior quarter
Pattern history & recurrence
Question this read
Push back on the system's interpretation
Ask anything about this pattern…
Authority-tier aware
Every brief scopes options to what the owner can actually decide. Ward-level briefs look different from directorate briefs.
Evidence-cited
Every claim links back to its source signal, patient, workforce, or operational. Nothing asserted without provenance.
Audit-grade
Every brief is logged, signed, and traceable. The Project that follows is auditable through to outcome.
Non-exhaustive

Seven enterprise priorities proHX accelerates.

By turning fragmented signals into ranked, routed action, proHX shortens the distance between insight and impact across the operating priorities health systems already measure.

01
Homecare & Continuity of Care
The pain

Transitions between acute, community and home are where signal, and patients, get lost.

What proHX does

Detects discharge-to-readmission patterns across post-discharge surveys, EHR events, and community handover signals.

02
Value-Based Care
The pain

Outcome and cost data sit in separate dashboards from the experience signals that explain them.

What proHX does

Correlates cost-per-patient, LOS, and readmission with workforce and patient experience signals on the same chain.

03
Digital Adoption
The pain

Portal, EHR, and app investments are evaluated on usage, not on whether they reduce friction in care.

What proHX does

Reads adoption signals against experience and workforce outcomes to surface where digital actually moves the needle.

04
Utilisation
The pain

Capacity, throughput, and bed turnover are managed reactively, in operational silos.

What proHX does

Joins throughput, bed-event, and workforce-pressure signals to flag utilisation drift before it becomes failure.

05
Referral & Acquisition
The pain

Why referrals stall, and why patients leave, is rarely traceable to a system cause.

What proHX does

Connects referral funnel data with patient experience, access, and clinician engagement signals.

06
Governance & Regulatory Readiness
The pain

Regulators want evidence-led, cross-domain accountability. Most systems still assemble it from scratch each cycle.

What proHX does

Maintains a continuous, audit-grade chain of signal, decision, and outcome, ready for the next CQC, JCI, or board cycle.

07
Innovation & Piloting
The pain

Pilots of ambient AI, telemedicine, and new care models run without a baseline for what actually changed in the human system.

What proHX does

Provides the before/after signal layer that lets innovation teams measure impact across patient and workforce experience, not just adoption metrics.

Who it's for

The people proHX is built for

Three users. Three different relationships with the system. One platform that changes what each of them can do.

S
Sarah
Head of Patient Experience · NHS acute trust · Reports to CNO
Core frustration

Spends most of her time producing reports, not acting on them

Biggest blocker

Can't connect what patients say to what operations teams see

What keeps her up

Knowing something is wrong before she can prove it clearly enough to act

Without proHX
"I know what the problems are. I've known for months. What I can't do is show the system why they matter."
  • Manually compiles data from 6+ sources for every board report
  • Wednesday spent deciding which version of the data to present
  • Complaints arrive weeks after the incident window has closed
  • Board asks why the same issue appeared last quarter
With proHX
"For the first time, the ops lead and I are working from the same picture."
  • Prioritised discharge risk surfaced automatically — no searching
  • CX Copilot drafts board report section in minutes, not days
  • Patient and workforce signals connected for the first time
  • Time saved redirected to designing the intervention itself
J
James
Director of Operations · Regional hospital group · 4 sites
Core frustration

KPIs tell him what broke. Nothing tells him what's about to break.

Biggest blocker

Experience data and operational data reviewed in completely separate meetings

What keeps him up

Making resource decisions that look rational on paper but feel wrong in practice

Without proHX
"My dashboards are full of data about what happened last month. What I need is something that tells me where we are heading."
  • Calls three people to diagnose an ED wait time spike
  • Governance meetings reviewing last quarter — window for action closed
  • Resource decisions made without workforce experience context
  • Complaint arrives Friday — the signals were there all week
With proHX
"The governance meeting now runs from current intelligence. The conversation shifts from history to what we do this week."
  • ED rise and workforce strain signal connected before first call
  • Governance runs on current intelligence — two risks tabled before it starts
  • Site 3 reallocation changed because workforce data is visible
  • No complaint — handoff gap addressed the day before
P
Priya
Inpatient Service Manager · General Medicine · 3 wards, 87 beds
Core frustration

Finds out about patient experience problems through complaints — always too late

Biggest blocker

Staff tell her everything face to face. None of it makes it into any system.

What she can't see

Whether declining staff morale on Ward B is connected to rising patient dissatisfaction on the same ward

Without proHX
"My staff tell me everything — but only face to face. As far as the organisation is concerned, it doesn't exist."
  • 07:45 — verbal handover flag about pain meds. Nothing written down.
  • 40 minutes filling a rota gap — managing nothing else in that time
  • Complaint arrives about an incident three weeks old
  • Ward B skill mix concern stays in her notebook all month
With proHX
"I know. And it's already in front of the general manager." — said to a ward HCA for the first time.
  • 07:30 — Ward B pattern visible before she reaches the ward
  • Rota escalation includes patient impact evidence — prioritised differently
  • Complaint becomes input to systemic fix, not just a document to close
  • Three anonymous workforce submissions already corroborating the concern
For the CTO & COO

How it actually works in messy, real-world environments

Healthcare IT estates are not clean. proHX is designed for messy environments — not ideal ones. Here is the honest answer to every technical objection.

🏥
Source Systems
EHR, HRIS, surveys, social, ops data
🔌
Signal Ingestion
Read-only · API or file transfer · No system replacement
proHX Engine
Normalise · correlate · journey map · prioritise
🤖
CX Copilot
Synthesise · brief · govern · communicate
🎯
Leadership
Confident, prioritised, governed decisions
Integration

Designed for messy estates

Connects read-only via API where available, structured data export or secure file transfer where APIs don't. FHIR R4 and HL7 v2 supported for EHR event ingestion. No write access. No workflow disruption. If the integration breaks, source systems continue normally.

Start with what you have, a single survey stream or EHR event feed, and expand coverage over time.
Residency

Data stays where it needs to stay

Supports regional data residency requirements including sovereign cloud deployment. Organisations define exactly which data leaves their environment, in what form, under what conditions. Specified contractually before any integration begins.

Multi-market groups supported via separate tenancies with distinct residency configurations.
Privacy

Population intelligence, not individual surveillance

Built to detect patterns across journeys and segments, not to build profiles of individual patients. GDPR, HIPAA, and local frameworks supported by design. Data minimisation applied at ingestion. Workforce signals have aggregation thresholds, so no individual response is identifiable.

DPIA templates available for NHS, Gulf, and US contexts.
Security

Built for high-trust environments

Role-based access throughout. All data encrypted in transit and at rest. SSO and MFA standard. Audit logging on all data access events. Infrastructure aligned to ISO 27001 and SOC 2 standards, with formal certification on the security roadmap.

Security questionnaires, pen test results, and IG documentation available on request. Formal assurance is part of every enterprise engagement.
AI Governance

AI that supports judgment, not replaces it

CX Copilot operates on processed intelligence only, never raw patient data. No customer data used for model training. Every AI output is evidence-cited and traceable to its source signals. Human-in-the-loop by design, with full audit trail on every brief generated.

AI usage scoped per tenant. Model boundaries, prompt handling, and data flow documented for IG review.
Onboarding

From signed to surfacing in 8 weeks

Week 1-2: signal landscape mapping and integration scoping. Week 3-4: API connections established, data flowing. Week 5-6: first intelligence view validated with the team. Week 7-8: first governance brief produced and reviewed with leadership. After 8 weeks, weekly intelligence updates run continuously.

No new infrastructure. No clinical workflow changes. Cloud-native deployment on AWS or Azure, regional residency configurable.
Where we are

Built in the open. Shipped in milestones.

proHX is being developed against three named milestones: MVP, Scale, Growth. Each is scoped, evidence-led, and tied to a real path to enterprise deployment.

MVP In flight

Building the foundations

60% complete

What's underway right now.

  • Engaging our network to gather real-world data, informing the synthetic hospital network
  • Synthetic hospital network (Madinat Health) operational for product development
  • Milestone one of the intelligence layer in active development
  • Front-end key workflows in testing
  • Eight-domain Experience Framework integrated as the diagnostic layer
SCALE Next

From pilot to production

What unlocks once MVP lands.

  • Implementation partner selected, with strong routes to three top choices in progress
  • First enterprise pilot deployment with implementation partner
  • Team build to scale product development and validation
  • FHIR R4 and HL7 v2 integrations validated against live EHR environments
  • ISO 27001 and SOC 2 formal certification
GROWTH Then

Category leadership

What proHX becomes at scale.

  • Multi-tenant expansion across NHS, Gulf, and US markets
  • Cross-tenant pattern intelligence at network scale
  • proHX Lab opens for proactive piloting (ambient AI, telemedicine, value-based care)
  • Category-defining health experience intelligence standard

Ready to govern the human system?

Start with the intelligence you already have. Expand from there.