Skip to main content

Help us improve the Digital Marketplace - send your feedback

INHEALTHCARE LIMITED

Digital Health Platform

Our digital health platform allows clinicians to automate monitoring, self-care, behavioural change and create virtual wards using a range of patient communication tools. Integrated with GP and clinical electronic patient records. We consider clinicians and are patient led in everything we do, focusing on real NHS problems rather than technology.

Features

  • Ensures patients data is safe and accessible by clinicians
  • Inclusive and bridges the digital divide
  • Enables an integrated, paperless NHS
  • Less time on paperwork, more time with patients
  • Gives clinicians full visibility of a patient's health
  • Support NHS England Strategic initiatives
  • Triaged list of patients and the ones requiring support
  • Step up and down of patients based upon their needs
  • Better outcomes for patients and savings for NHS providers

Benefits

  • Hosted in the NHS secure network (HSCN)
  • Patient services accessible by over 99% of the population
  • Integrated with GP and hospital clinical systems
  • One-click patient referral from GP systems
  • Direct upload of patient results into patient's health record
  • Integrated with NHS national patients systems
  • Flexible, digital pathway engine
  • Services designed by the NHS

Pricing

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at tenders@inhealthcare.co.uk. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

9 6 3 8 0 0 5 7 4 7 3 3 0 3 2

Contact

INHEALTHCARE LIMITED Jonathan Lowther
Telephone: 01423 642480
Email: tenders@inhealthcare.co.uk

About your service

Service categories

Applications

Production and operations

Service industry and public sector operations

  • Healthcare
Multi cloud support
No

Service scope

Software add-on or extension
No
Cloud deployment model
Public cloud
Service constraints
Yes – the service has a small number of operational constraints:
Planned maintenance: Occurs outside core clinical hours wherever possible, with advance notice and change control. Short service interruptions may be required for major upgrades.
Connectivity and browser support: Requires reliable internet access and use of supported, up-to-date browsers/devices for the web portal and patient app.
Third-party dependencies: Availability of some integrations (e.g. clinical systems, NHS Spine) is dependent on the uptime and change cycles of those third-party services.
System requirements
  • Modern HTML5 browser: latest Chrome, Edge, Safari or equivalent.
  • Reliable broadband or 4G connectivity for staff and patient access.
  • Smartphone for app users: iOS 17+/Android 14+ recommended.
  • Standards-compliant email, SMS and telephony services for notifications.
  • Ability to access public cloud services from NHS networks
  • Optional: VPN or secure API gateway for system integrations.
  • Local endpoint protection and anti-virus aligned to organisation security policy.
  • User devices configured to permit JavaScript, cookies and HTTPS.
  • Compatible Bluetooth or cellular medical devices for optional device monitoring.
  • For SSO, standards-based identity provider supporting SAML2 or OpenID.

User support

Email or online ticketing support
Yes
Support response times
Proposed response times
Weekdays (Mon–Fri, standard support hours):
Urgent, service-affecting queries – initial response within 4 working hours.
Routine queries, configuration questions and “how do I?” requests – same business day, and always within 1 working day.
Weekends and bank holidays:
We respond to priority/critical issues only (service availability, data integrity, patient-safety concerns) with the same initial target (within 4 hours).
Non-urgent questions raised at weekends are picked up on the next working day.
User can manage status and priority of support tickets
Yes
Online ticketing support accessibility
WCAG 2.2 AA
Phone support
Yes
Phone support availability
9 to 5 (UK time), Monday to Friday
Web chat support
No
Onsite support
Yes
Support levels
We provide a single, comprehensive support level aligned to NHS service needs.
Support levels
Standard Service Desk Support (included):
Incident management, service requests, “how do I?” queries.
Phone and email, 09:00–17:00 UK time, Monday–Friday (excluding bank holidays).
Prioritisation based on impact/urgency, with defined response targets for critical vs routine issues.
At present we do not offer multiple paid “bronze/silver/gold” tiers. The standard support level is included within the core service charges described in the financial model, with no additional per-incident fees.
Costs
Standard support: included in the contracted service price.
Any enhanced or bespoke support arrangements (e.g. out-of-hours non-critical cover) would be scoped and priced separately by agreement.
Technical account management
A named implementation / customer success lead is provided during mobilisation and early life.
A dedicated ongoing Technical Account Manager or Cloud Support Engineer can be added as an optional, separately priced service if required.
Support available to third parties
Yes

Onboarding and offboarding

Getting started
We provide structured onboarding to accelerate safe adoption and minimise operational disruption.
Mobilisation and onboarding
Joint mobilisation plan covering clinical, operational, IT and IG workstreams.
Configuration workshops to align digital pathways, escalation rules and reporting to local models.
Support to integrate with EPRs, GP systems and shared care records.
Training
Train-the-trainer sessions for clinical leads, service managers and super-users.
Role-specific training for administrators, frontline clinicians and operational teams.
Training is usually delivered online (Teams); onsite sessions can be arranged by agreement where clinically or operationally beneficial.
Materials and documentation
Comprehensive user guides, quick-reference sheets and admin manuals.
Technical integration documentation for IT and supplier teams.
Update briefings and release notes when new features or pathways are introduced.
Early life support
Hyper-care period after go-live with increased monitoring and rapid response to issues.
Regular check-ins to review usage, resolve issues and refine configuration.
Service documentation
Yes
Documentation formats
  • HTML
  • PDF
  • Other
Other documentation formats
  • Word
  • Powerpoint
  • Excel
End-of-contract data extraction
At contract end we follow an agreed Exit Plan so you retain full control of your data and can transition safely to your chosen solution.
Approach
We agree an exit timeline and cessation date, keeping the live service available during the exit window so clinical services are not disrupted.
We provide a complete export of your service data (for example, patient records, pathway enrolments, readings, questionnaires, alerts, and audit history) in commonly used, machine-readable formats agreed in advance.
We supply an accompanying data dictionary / schema describing tables, fields, coding and relationships to support import into replacement systems or your data warehouse.
Where appropriate, we can provide multiple extracts (e.g. snapshot plus final delta near switch-over) to support a phased migration.
After you have confirmed safe receipt and validation of the data, we decommission the service in line with ICO requirements.
End-of-contract process
At the end of the contract we agree and deliver a formal Exit Plan.
We will:
Agree a time and date for services to cease.
Allow you to continue using the service up to the cessation date, including transferring data to you or a replacement supplier, subject to continued payment of normal service charges.
Maintain access and monitoring while any patient episodes remain active.
Cease the service at the agreed time and date.
Provide a full copy and inventory of all data relating to your service, with details of the data structures.
We are not obliged to disclose Inhealthcare confidential information or transfer any assets, contracts, employees or third-party licences.
Included in contract price
Exit planning activities as above.
Provision of data copy, inventory and schema.
Self-service data extraction via supported interfaces with no additional fee.
Additional cost
If you ask us to continue storing data for archiving instead of transferring it, this is covered by a separate Service Agreement with its own commercials.
Documentation accessibility standard
WCAG 2.2 AA

Using the service

Web browser interface
Yes
Supported browsers
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
Application to install
Yes
Compatible operating systems
  • Android
  • IOS
  • MacOS
  • Windows
Designed for use on mobile devices
Yes
Differences between the mobile and desktop service
The My Inhealthcare app lets patients submit readings, answer questionnaires and connect Bluetooth devices, with prompts and offline support. The Inhealthcare Professional app allows healthcare professionals to record observations at the point of care. Desktop services provide the full clinical portal: caseload dashboards, detailed patient records, configuration of pathways and thresholds, audit history, reporting and data export, and integration management. Desktop is optimised for richer views and administration; mobile is optimised for simple, accessible data capture.
Service interface
Yes
User support accessibility
WCAG 2.2 AA
Description of service interface
The service interface is a secure, web-based clinical portal with role-based access. Users see caseload dashboards, alerts and task lists, with drill-down to individual patient records, trends and audit history. Configurable views allow filtering by service, site or risk status. Integrated tools support messaging, video, documentation and pathway management. The interface is intuitive, accessible and designed around NHS workflows, enabling safe remote monitoring, escalation and collaboration across multidisciplinary teams.
Accessibility standards
WCAG 2.2 AA
Accessibility testing
We routinely test the patient and clinician interfaces with common assistive technologies and accessibility tools.
Our web interfaces are tested with NVDA and JAWS screen readers to confirm that key journeys (log-in, navigation, completing questionnaires, viewing results, responding to alerts and messages) are fully operable and understandable via audio output. We validate correct focus order, heading structure, link text, form labels and error messaging.
We also test keyboard-only navigation (no mouse), ensuring all interactive elements are reachable via tab/shift+tab and clearly indicated by visible focus states. High-contrast modes, colour contrast ratios and scalable text are checked to meet WCAG 2.1 AA.
Issues identified in assistive-technology testing are logged, prioritised and resolved through our standard release and regression-testing process.
API
Yes
What users can and can't do using the API
Our API enables NHS partners to integrate local systems with the Inhealthcare Platform while preserving clinical and governance controls.
What users can do
Create and update patient records, enrol patients onto agreed digital pathways / virtual wards, and exchange observations, questionnaire responses and status updates with EPRs, GP systems and shared care records.
Trigger patient-facing digital interactions (e.g. reminders, questionnaires, education) while we manage channel delivery (app, SMS, web, telephony).
Extract data for reporting and analytics into ICS data platforms and BI tools.
Set-up via API
Following onboarding and IG/clinical safety approvals, we provide test and production endpoints, credentials and specifications. Your integration engine or EPR sends referral/enrolment, demographics and observation messages to our APIs; we validate, match to patients and apply the configured pathway logic.
Making changes via API
Users can update demographics, pathway membership, caseload assignment, and request additional digital contacts; data can be refreshed on demand for analytics.
Key limitations
The API cannot create or materially alter pathways, NEWS2/PEWS or other clinical algorithms, change RBAC/security controls, or move hosting outside the agreed UK environment. Those changes are managed through the Inhealthcare Toolkit and governed change control.
API documentation
Yes
API documentation formats
PDF
API sandbox or test environment
Yes
Customisation available
Yes
Description of customisation
Our pathways include organisation and patient-level configuration options, including question sets, frequency and duration of monitoring, clinical thresholds/targets and escalation rules, patient communication preferences. Operational setup: organisation and pathway names, teams, working hours, and notification routes.

Scaling

Independence of resources
We minimise cross-customer impact through architecture, controls and capacity management.
Isolated, scalable platform: Multi-tenant, cloud-hosted services with logical separation and clustered, autoscaling components, so no single customer exhausts shared capacity.
Capacity and monitoring: Proactive capacity planning, real-time performance monitoring and alerting (latency, errors, queue depth), with engineers able to intervene rapidly.
Demand controls: Per-integration safeguards (e.g. rate control, queuing) and prioritisation of clinical, time-critical workloads over non-urgent/background tasks so high demand from one user doesn’t degrade others.

Analytics

Service usage metrics
Yes
Metrics types
Via the data warehouse we provide a rich set of service metrics to support operational management, assurance and improvement, for example:
Activity and utilisation: referrals, enrolments, active caseload, discharges.
Engagement: completion rates for readings/questionnaires, missed submissions, channel usage.
Clinical risk and response: breaches of thresholds, alerts raised, escalation volumes, time to review/intervention.
Flow and outcomes: virtual length of stay, pathway completion, onward referrals, discharge destinations.
Equity and access: metrics segmented by site, team and key demographics to support monitoring of variation and inequalities.
Reporting types
  • API access
  • Real-time dashboards
  • Regular reports
  • Reports on request
Resource tagging
Yes
FOCUS resource tagging
No

Resellers

Supplier type
Not a reseller

Staff security

Staff security clearance
Other security clearance
Government security clearance
Baseline Personnel Security Standard (BPSS)

Asset protection

Knowledge of data storage and processing locations
Yes
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
No
Datacentre security standards
Managed by a third party
Penetration testing frequency
At least once a year
Penetration testing approach
‘IT Health Check’ performed by a CREST-approved service provider
Protecting data at rest
Encryption of all physical media
Data sanitisation process
Yes
Equipment disposal approach
A third-party destruction service
Data sanitisation type
Deleted data can’t be directly accessed / Cryptographic Erasure

Data importing and exporting

Data export approach
Users can export data in several ways, depending on their role and purpose.

Self-service exports:
Authorised users run reports and export caseloads, readings, questionnaires and activity logs to CSV/Excel for local analysis.
Automated / bulk exports:
Agreed datasets are extracted on a scheduled or event-driven basis into your data warehouse/BI tools via secure, structured interfaces.
Programmatic access:
Approved systems retrieve near real-time data (e.g. observations, alerts, pathway status) through our APIs for dashboards or shared care records.
All exports are role-based, auditable and configured to meet local IG requirements.
Data export formats
  • CSV
  • Other
Other data export formats
  • JSON
  • XML
Data import formats
  • CSV
  • Other
Other data import formats
  • JSON
  • XML
  • HL7
  • FHIR

Data-in-transit protection

Data protection between buyer and supplier networks
TLS (version 1.2 or above)
Data protection within supplier network
  • TLS (version 1.2 or above)
  • Other
Other protection within supplier network
We protect data within our network using layered controls:
Segregated UK cloud environments with strict separation of production, test and customer data.
Encryption at rest and in transit across databases, storage and internal services.
Hardened network security using virtual networks, firewalls and security groups to restrict traffic.
Strong access control with RBAC, least privilege, MFA and regular access reviews.
Centralised logging and monitoring with alerting for suspicious events and a defined incident response process.
Backups and high availability to protect against data loss and support recovery objectives.

Availability and resilience

Guaranteed availability
We guarantee high availability through a formal SLA.
Guaranteed availability
We commit to a minimum 99.9% monthly availability for the production platform (web application, clinical dashboards, APIs and messaging services).
Measured per calendar month, at the platform boundary, excluding: agreed planned maintenance windows, third-party or network failures outside our control, and force majeure.
Planned maintenance
Scheduled mostly out of hours, with advance notice.
Designed not to exceed the availability commitment over the month.
Approach to resilience
Our service is designed for high resilience across application, infrastructure and datacentre layers.
Platform resilience
Deployed in a UK cloud environment with multi-AZ architecture, load-balanced services and autoscaling to handle failures and demand spikes.
Stateless application tiers with redundant instances; no single point of failure for core components (APIs, rules engine, messaging, dashboards).
Managed databases with built-in high availability, point-in-time recovery and automated failover.
Data and recovery
Encrypted, geo-resilient storage with regular, tested backups.
Documented business continuity and disaster recovery plans, including defined RPO/RTO targets and periodic DR exercises.
Datacentre resilience
Underlying datacentres provide redundant power, cooling, networking and physical security, certified to recognised international standards.
Network resilience through diverse connectivity options and redundant edge components.
More detailed architectural and datacentre resilience information (including diagrams) is available on request under appropriate confidentiality.
Outage reporting
We combine proactive monitoring with structured customer communications.
Detection and triage
24/7 infrastructure and application monitoring (availability, latency, error rates, queues).
Alerts automatically raise incidents to our on-call engineers for investigation and remediation.
How we notify customers
For major incidents or outages, we send email alerts to nominated customer contacts (e.g. service managers, IT, on-call leads), including summary, impact, and next update time.
For high-impact issues we will also phone key contacts where agreed (for example, to clinical or operational leads).
Once resolved, we issue a closure/update email describing cause, fix and, where appropriate, follow-up actions.
Dashboards and APIs
We do not currently provide a public status dashboard or a dedicated outage/status API.
Service performance and incident history are instead shared through routine service reviews and reports, plus ad hoc reporting on request.

Identity and authentication

User authentication needed
Yes
User authentication
  • Multi-Factor Authentication (MFA)
  • Public key authentication (including by TLS client certificate)
  • Identity federation with existing provider (for example Google Apps)
  • Username or password
  • Other
Other user authentication
Standards-based tokens (e.g. OAuth2/JWT) for API access.
Network controls (VPN/HSCN) further restrict where users can connect from, but primary authentication is as above.
Access restrictions in management interfaces and support channels
Management and administrative interfaces are tightly restricted using role-based access control, least-privilege permissions and MFA for all privileged accounts. Access to cloud management consoles and core configuration is limited to a small, vetted operations team, typically via VPN or approved corporate networks with full audit logging.
Support channels (service desk, remote assistance) are limited to authorised customer contacts. We verify identity before discussing sensitive information, access tickets via RBAC-controlled tools, and only request the minimum data required. Passwords are never disclosed or asked for over support channels.
Access restriction testing frequency
At least once a year
Management access authentication
  • Multi-Factor Authentication (MFA)
  • Identity federation with existing provider (for example Google Apps)
  • Dedicated link (for example VPN)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
Between 1 month and 6 months
How long system logs are stored for
Between 1 month and 6 months

Security governance

Named board-level person responsible for service security
Yes
Security governance certified
Yes
Security governance standards
  • CSA CSM version 4.0
  • ISO/IEC 27001
  • Other
Other security governance standards
- Cyber Essentials Plus (information and cyber security).
- NHS Data Security & Protection Toolkit (DSPT) – standards met/exceeded.
- ISO 13485 (medical device quality management – including governance of safety and risk).
- Compliance with GDPR and UK Data Protection Act 2018 for data protection governance.
Information security policies and processes
Inhealthcare operates an ISO 27001-certified Information Security Management System covering people, process and technology, supported by ISO 13485, Cyber Essentials Plus, DSPT “standards exceeded” and GDPR compliance.
Governance and reporting
The Board approves our security strategy and risk appetite.
A named Data Protection Officer and Clinical Safety Officer oversee data protection and clinical risk; operational responsibility sits with our information security and infrastructure leads.
Security, privacy and clinical risk are standing items at senior management and change control forums.
Policies and controls
Our policy suite includes information security, access control, secure development, supplier security, incident management, business continuity, acceptable use and data protection. Controls include UK-hosted AWS infrastructure, role-based access, MFA for privileged accounts, encryption in transit and at rest, logging and monitoring, regular patching, penetration testing and load testing.
Assurance and compliance
All staff complete mandatory induction and annual refresher training, supported by policy attestation and targeted campaigns. We conduct internal audits, external certification audits and DPIAs, maintain full audit trails and run rehearsed incident and continuity plans; findings and KPIs are reported to the executive team with actions tracked to closure.
Software Security Code of Practice
Yes

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
We operate ISO 27001- and ITIL-aligned configuration and change management. All infrastructure, applications and integrations are recorded in a CMDB / asset register with owners, environments, versions and dependencies; changes are tracked from design through test, deployment and decommissioning via tickets and documented build/release pipelines. Any change requires an RFC describing scope, rollback, testing and security implications. Security impact is assessed through risk analysis, segregation-of-duties review and, where relevant, DCB0129/IG review and threat modelling. High-risk changes require CAB approval and may trigger additional controls (e.g. code review, pen testing); outcomes are logged and reviewed post-implementation.
Vulnerability management type
Complies with a recognised standard, for example CSA CCM v4.0 or SSAE-18 / ISAE 3402
Vulnerability management approach
We operate an ISO 27001- and DSPT-governed vulnerability management process.
Threat assessment: Continuous vulnerability scanning, code review and annual pen tests, combined with risk assessment (asset, exposure, data sensitivity, exploitability) to prioritise remediation.
Patching timescales: Critical, actively exploited vulnerabilities are patched as quickly as practicable, typically within 14 days; high-risk issues are normally addressed within the standard patch cycle; lower-risk items are scheduled via planned maintenance.
Threat intelligence: We track vendor advisories, NHS Cyber Alerts, NCSC/CERT feeds, supplier bulletins and security community updates.
Protective monitoring type
Supplier-defined controls
Protective monitoring approach
We use layered protective monitoring across infrastructure, applications and access.
Potential compromises are identified through centralised logging, alerting on suspicious patterns (e.g. failed logins, privilege changes, anomalous API use), vulnerability scanning, cloud-native security alerts and integrity checks on key systems.
When an alert triggers, an incident is logged, risk-rated and picked up by on-call engineers, who investigate, contain, eradicate and recover following our ISO 27001 incident process, with evidence preserved.
High-severity security incidents are triaged immediately, with initial response typically within 1 hour of alert, and escalated to senior management as required.
Incident management type
Supplier-defined controls
Incident management approach
We operate ISO 27001- and ITIL-aligned incident management with predefined runbooks for common events (service degradation, outage, security alerts, data issues). Users report incidents via the service desk by phone or email, using agreed contact details and impact/urgency categories; our team logs, prioritises and tracks them through to closure. Major incidents follow an enhanced process with executive escalation and clear communication timelines. We provide incident reports via email and service reviews, including root cause, impact, remediation and preventative actions.
Post-quantum cryptography secure
No

Secure development

Approach to secure software development best practice
Independent review of processes (for example CESG CPA Build Standard, ISO/IEC 27034, ISO/IEC 27001 or CSA CCM v4.0)

Public sector networks

Connection to public sector networks
Yes
Connected networks
Health and Social Care Network (HSCN)

Pricing

Discount for educational organisations
No
Free trial available
No

Discount percentage by annual call-off contract value (excluding VAT)

Less than £250,000
0%
Between £250,000 and £500,000
0%
Between £500,001 and £1,000,000
0%
Between £1,000,001 and £2,500,000
5%
Between £2,500,001 and £5,000,000
5%
Over £5,000,001
5%

Non-mandatory Standards and certifications

ISO/IEC 27001 certification
Yes
Who accredited the ISO/IEC 27001
BSI
ISO/IEC 27001 accreditation date
Thursday 26 June 2025
What the ISO/IEC 27001 doesn’t cover
Outsourced development
ISO 28000:2022 certification
No
ISO 9001 certification
No
Quality management systems (QMS)
Yes
CSA STAR certification
No
PCI certification
No
Cyber essentials
Yes
Please provide your Cyber Essentials Certificate Number
D1cbb0ca-9616-4e81-b4d2-0d42af681483
Cyber essentials plus
Yes
Please provide your Cyber Essentials Plus Certificate Number
2f9e3e3e-af2f-4637-9eae-cf61b6d4e7f8
Other security certifications
Yes
Any other security certifications
  • DSPT (NHS Data Security and Protection Toolkit)
  • DTAC ( Digital Technology Assessment Criteria)

Social value

Section B - Commitment for Future: Delivery
  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 1: Fair work: That offers fair wages and good working conditions. Help people get a job, stay in work, and progress in their careers, with good employment opportunities across the country. Notes: Where there is a large proportion of labour costs in the contract, commercial teams should consider MAC in Outcome 1 as a priority

    • New or retained jobs on the contract workforce in the relevant area that meet the criteria set out in MAC 1b, 1c and 1d
    • Monitoring of employee engagement rates (by protected characteristic) and, where necessary, the development of actions to ensure all voices are heard across the diversity of the workforce
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Plans for an appropriate income replacement policy for staff who are required to spend time away from work to care for a sick dependent or close relative
    • Measures to support in-work progression to help people in the contract workforce, to move into higher paid work by developing new skills relevant to the contract
    • Support for the contract workforce by providing career advice, and providing opportunities for staff working on the contract with in-work progression career development into known skills shortages or high growth areas
    • Volunteering opportunities for staff
    • Understanding of the modern slavery risks and issues affecting the market, industry, sector or country (of origin or of source) relevant to the contract, and the workforce in the supplier’s own organisation and those of its key subcontractors
    • Measures to identify, mitigate and manage modern slavery risks relating to the contract and how these will be implemented
    • Outline policies and practices to be applied to or put in place for the contract to mitigate and manage modern slavery risks, including: Pre-employment checks, recruitment practices. Workplace conditions, safeguarding plans and processes in place and regular monitoring with relevant groups considered, which may include sampling
    • How these flow down the supply chain and are monitored Illustrative examples include reporting, site visits, audits, etc.
    • How to ensure business decisions re: price/cost, short lead times, payment timescales do not create modern slavery risks in the supply chain
    • How the supplier will work with NGOs, trade unions or other businesses to address modern slavery risk
    • Means of influencing staff, suppliers, customers, communities and/or any other appropriate stakeholders with respect to modern slavery risks relating to the contract
  • Mission: Kick start economic growth. To secure the highest sustained growth in the G7 - with good jobs and productivity growth in every part of the country making everyone, not just a few, better off.

    Policy Outcome 2: Skills for growth: Supporting growth sectors and addressing skills gaps.

    • Understanding of employment and relevant skills issues, and of the education and training issues relating to the contract. Illustrative examples: demographics, skills shortages, new opportunities in high growth sectors, geographic/local community and skills/employment challenges
    • Support for educational attainment relevant to the contract, including training schemes that address skills gaps and result in recognised qualifications
    • Activities to support relevant sector related skills growth and sustainability in the contract workforce. Illustrative examples: careers talks, curriculum support, literacy support, safety talks and volunteering
  • Mission: Make Britain a clean energy superpower: To cut bills, create jobs and deliver security with cheaper, zero-carbon electricity by 2030, accelerating to net zero

    Policy Outcome 4: Sustainable procurement practices: Reducing carbon footprints, minimising waste, and promoting the use of clean energy and green technologies.

    • Understanding of opportunities for additional environmental benefits delivery in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Collaborative ways of working with the supply chain to deliver additional environmental benefits in the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Delivery of additional environmental benefits through the performance of the contract, including working towards net zero carbon emissions and use of clean energy and green technologies
    • Understanding of how to influence staff, suppliers, customers, communities and/or any other appropriate stakeholders through the delivery of the contract to support climate and nature protection and improvement
  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 6: Employment and training: For those who face barriers to employment

    • Inclusive and accessible recruitment practices, and retention-focused activities, including those provided in the Guide for line managers on recruiting, managing and developing people with a disability or health condition
    • Working conditions which promote an inclusive working environment and promote retention and progression
    • Inclusive and accessible development practices, including guidance for line managers on recruiting, managing and developing people with a disability or health condition
  • Mission: Break down barriers to opportunity: By reforming our childcare and education systems, to make sure there is no class ceiling on the ambitions of young people in Britain

    Policy Outcome 7: Creating a pipeline of opportunities: For the contract workforce, reducing barriers to entry for under-represented groups.

    • Understanding of issues relating to entering the contract workforce
  • Mission: Build an NHS fit for the future: That is there when people need it; with fewer lives lost to the biggest killers; in a fairer Britain, where everyone lives well for longer.

    Policy Outcome 8: Increasing productivity through physical and mental wellbeing: In the supply chain and communities in the relevant area.

    • Understanding of issues relating to health and wellbeing, including physical and mental health, in the contract workforce
    • Understanding barriers to access to health and social care services or employment opportunities e.g. digital inclusion
    • Actions to invest in the physical and mental health and wellbeing of the contract workforce

Service documents

Request an accessible format
If you use assistive technology (such as a screen reader) and need versions of these documents in a more accessible format, email the supplier at tenders@inhealthcare.co.uk. Tell them what format you need. It will help if you say what assistive technology you use.