Understanding of Requirement
Explain your understanding of the Authority's requirements for a digital patient communication platform and the outcomes it must deliver, including key success measures.
Word Limit: 500 words1. Understanding of the buyer's objective
The Partnership needs one communications platform to reduce DNAs and avoidable rebooking, and to give every organisation confidence that messages are correct, secure and auditable. It must support outpatient, diagnostic and community services at scale without creating manual workarounds.
The outcomes you are buying are:
- fewer DNAs and late cancellations
- fewer appointment-query calls
- consistent patient experience across sites
- auditability and reporting for IG and improvement
Success measures (set from current baselines at mobilisation; reported monthly) are:
- 10–15% DNA reduction within 6 months (PAS/EPR attendance codes)
- 8–12% call deflection within 3 months (telephony reason codes where available)
- ≥98% delivery success; failures categorised and trended
- ≥20% reduction in same-day cancellation/reschedule handling time (workflow timestamps)
- ≤3% monthly opt-out rate, with exception reporting
- 100% audit trail completeness, evidenced through audit extracts
If any measure is outside tolerance for two consecutive cycles, corrective action is owned jointly by the Delivery Manager and the Partnership operational lead, tracked to closure in the service review.
2. What "good" looks like in day-to-day operations
You will judge the service on reliability and control: the right message to the right patient, at the right time, across multiple PAS/EPR environments and clinic rule sets. The platform must handle reminders, cancellations/reschedules, pre-assessment and preparation instructions, and follow-ups. Where two-way messaging is used, replies must route into a staffed workflow (triage rules, escalation, agreed service hours and fallback handling), not unmanaged mailboxes.
3. Information governance, clinical safety and assurance
The Partnership will expect demonstrable compliance with UK GDPR and NHS IG requirements, including secure processing, role-based access, and retention aligned to local policy. The service must support DPIA completion and provide auditable records of message content, dispatch attempts and outcomes.
We meet NHS DSPT requirements (currently assessed to Standards Met) and operate an ISO 27001-aligned ISMS (ISO 27001 certified), evidenced by our current assessment/certification and applicable control set.
Clinical safety controls must prevent inappropriate messaging (for example reminders after cancellation), with a maintained hazard log and safety case and clear sign-off. Template approval sits with the Partnership communications delegate; clinical safety sign-off sits with the named Clinical Safety Officer.
4. Integration and interoperability requirements
The platform must integrate with PAS/EPR and scheduling systems to pull appointment data, patient identifiers and contact preferences, and to manage data quality issues (duplicates, missing numbers, conflicting preferences).
It must work via APIs where available and via secure file transfer where not, without losing auditability, with reconciliation so what was scheduled is what was communicated.
5. Reporting requirements
Reporting must support operational management and improvement: delivery rates by channel, failed delivery reasons, opt-outs, and two-way response rates. Definitions must be consistent across organisations. A standard pack will be issued monthly, with a weekly exceptions view during mobilisation and any period of elevated risk (e.g. pathway changes or template updates).
6. Added value expectations in NHS setting
Added value is practical: shorter time to benefit, reduced admin burden, and measurable improvements evidenced in the reporting above.