FAVA HEALTH LTD

Fava Clinical Genomics Platform

Fava Clinical Genomics Platform is a cloud-based software service that enables genomic data to be translated into actionable clinical use. It supports the interpretation, presentation, and integration of genomic insights into clinical workflows, helping healthcare organisations apply genomic information consistently, safely, and effectively in everyday care.

Features

• Secure cloud platform for clinical genomics data
• Integration of genomic data from labs to clinical IT systems
• Structured interpretation of genomic results for clinical use
• Genomic decision support embedded in clinical workflows
• Role-based access controls for clinical users
• Configurable workflows aligned to local pathways
• Standards-based data models for interoperability
• Full audit trails for data access and usage
• Intuitive interfaces for clinicians and healthcare teams
• Scalable architecture for future genomic use cases

Benefits

• Translate genomic results into consistent, actionable clinical decisions
• Reduce variation in how genomic information is applied in care
• Embed genomic insights directly into everyday clinical workflows
• Support safer, more informed prescribing and treatment decisions
• Improve clinician confidence when using complex genomic data
• Streamline delivery of genomic results across clinical teams
• Enable scalable adoption of genomics across services and pathways
• Support governance, audit, and responsible use of genomic data
• Reduce implementation burden for organisations adopting genomics
• Adapt genomic use cases as clinical and service needs evolve

• Education pricing available
• Free trial available

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

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 videha@favahealth.com. Tell them what format you need. It will help if you say what assistive technology you use.

Framework

G-Cloud 15

Service ID

722957496030108

Contact

Videha Sharma
07735360958
videha@favahealth.com

About your service

• Service categories:

  Application Development and Deployment

  Data management

  Data integration and intelligence

  • Data Ingestion and Transformation Software
  • Data Access Infrastructure Software
  • Composite Data Framework Software
  • Master Data Intelligence Software
• Multi cloud support: No

Service scope

• Software add-on or extension: Yes, but can also be used as a standalone service
• What software services is the service an extension to: Fava Clinical Genomics Platform can integrate with clinical IT systems such as electronic health records and prescribing systems to support use within existing workflows. It can also be used as a standalone web-based service where integration is not required or available.
• Cloud deployment model: Hybrid cloud
• Service constraints: The service is delivered as a managed, cloud-based application and does not require specific local hardware. Planned maintenance and updates are carried out periodically and scheduled to minimise disruption to users. Short periods of reduced availability may occur during maintenance, with advance notice provided where possible. Deployment and integration with existing clinical IT systems may depend on local system capabilities, configuration, and governance arrangements. Internet connectivity is required to access the service.
• System requirements:
  • Modern web browser with JavaScript enabled
  • Secure internet connection for cloud service access
  • User authentication via individual named user accounts
  • Role-based access configured by the buyer
  • Ability to upload or receive structured genomic data files
  • Integration access to clinical IT systems where required
  • Compliance with local information governance and security policies
  • Secure email access for notifications and user communications
  • Buyer-managed user devices meeting organisational security standards
  • Compliance with local information governance and security policies

User support

• Email or online ticketing support: Yes
• Support response times: We aim to respond to support queries within one business day during UK business hours (Monday to Friday). Support requests received at weekends or on public holidays are monitored and will be responded to on the next business day.
• User can manage status and priority of support tickets: No
• Phone support: No
• Web chat support: No
• Onsite support: No
• Support levels: Fava Clinical Genomics Platform is provided with a standard support service included in the subscription price. Standard support is delivered via email during UK business hours (Monday to Friday) and covers general usage queries, issue reporting, and assistance with service configuration. We aim to respond to support requests within one business day.; ; At this stage, all customers receive the same standard level of support at no additional cost. There are no separate tiered support packages published as part of the framework offering.; ; For some customers, a named service or technical contact may be provided to support delivery, coordination, and escalation, depending on the scope of the call-off contract. Where required, enhanced support arrangements — including prioritised support, extended hours, or dedicated technical oversight — can be agreed and priced separately at call-off.; ; Support is delivered by the Fava team, including senior technical and clinical staff, with access to specialist expertise where required.
• Support available to third parties: Yes

Onboarding and offboarding

• Getting started: Fava Clinical Genomics Platform supports users through a structured onboarding and enablement process tailored to different user roles. During implementation, support is provided to local implementation teams, clinical leads, and digital or informatics teams to configure the service in line with local workflows and requirements. This includes guided onboarding sessions, configuration support, and implementation documentation.; ; For end users, such as clinicians, the service is designed to be intuitive and embedded within existing workflows. Users are supported through role-appropriate guidance, including online documentation, walkthroughs, and contextual help within the service. Where appropriate, remote training sessions or demonstrations can be provided to support adoption and understanding of the service.; ; Onsite training is not provided as standard but can be agreed where required as part of a call-off contract. This blended approach ensures effective implementation while minimising disruption to clinical practice and supporting scalable rollout across organisations.
• Service documentation: Yes
• Documentation formats:
  • HTML
  • PDF
• End-of-contract data extraction: At the end of a contract, buyers can request the extraction of their data held within the service. Data will be provided in a structured, commonly used electronic format suitable for reuse or transfer to another system. The specific format and method of transfer will be agreed with the buyer to align with local requirements, data types, and information governance policies.; ; Data extraction is coordinated by Fava as part of the contract close-out process to ensure accuracy, completeness, and security. Where integrations are in place, data can be provided via secure file transfer or agreed interfaces, as appropriate. Documentation can be provided to support understanding of the extracted data structure.; ; Following confirmation that data has been successfully extracted and transferred, remaining customer data will be securely deleted from the service in line with agreed retention periods and applicable data protection requirements. This process supports continuity of service, data portability, and responsible handling of sensitive healthcare information at contract end.
• End-of-contract process: At the end of the contract, the service will be transitioned in line with the agreed contract terms. Standard close-out activities included within the contract price cover coordination of contract termination, confirmation of user access removal, and support for buyer-requested data extraction in a structured electronic format.; ; Where required, Fava will work with the buyer to agree a short transition period to support an orderly exit, including clarification of timelines and responsibilities. Following confirmation that data has been successfully extracted, remaining customer data will be securely deleted in accordance with agreed retention periods and applicable data protection requirements.; ; Additional services beyond the standard close-out process may be provided by agreement and at additional cost. These may include extended transition support, bespoke data extraction formats, additional documentation, or technical assistance to support migration to alternative systems. Any additional costs would be agreed with the buyer in advance as part of the contract close-out arrangements.; ; This approach ensures a clear, controlled, and transparent end-of-contract process while supporting data portability and responsible service exit.
• Documentation accessibility standard: WCAG 2.2 AA

Using the service

• Web browser interface: Yes
• Supported browsers:
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari
• Application to install: No
• Designed for use on mobile devices: No
• Service interface: Yes
• User support accessibility: WCAG 2.2 AA
• Description of service interface: The service provides user-facing interfaces designed to support the use of genomic information in clinical practice. This includes integration with existing clinical systems to surface genomic decision support within routine workflows, as well as an in-context launch to a secure web-based results viewer. The results viewer presents genomic information in a structured, clinically relevant format to support interpretation and decision-making. Interfaces are role-based, ensuring users only see information relevant to their role. The service is accessed via a standard web browser and is designed to fit alongside existing clinical IT systems without disrupting established processes.
• Accessibility standards: WCAG 2.2 AA
• Accessibility testing: The service interface has been co-designed with primary and secondary end users, including clinicians, and has undergone iterative usability testing to assess clarity, workflow fit, and ease of use in clinical contexts. To date, testing has focused on general usability rather than formal testing with specific assistive technologies (such as screen readers). Accessibility considerations have been incorporated into design decisions, and further testing with assistive technology users can be undertaken as the service evolves or where required by a buyer.
• API: Yes
• What users can and can't do using the API: The service provides application programming interfaces (APIs) to support integration with existing clinical IT systems and workflows. APIs are used by authorised technical teams acting on behalf of the buyer (such as IT teams or implementation partners), rather than by end users such as clinicians.; ; Through the API, authorised users can configure integrations to enable secure exchange of data between the service and local systems. This includes setting up data flows to receive genomic results, trigger clinical decision support, and enable in-context access to the results viewer within existing clinical applications. Where appropriate, integrations may align with relevant healthcare interoperability standards (for example HL7 FHIR), depending on local system capabilities and implementation requirements.; ; The API supports updates to configuration and integration settings to adapt to local workflows, data sources, or service changes. Changes are managed in a controlled manner and subject to appropriate governance and access controls.; ; End users, such as clinicians, do not interact directly with the API and cannot modify API behaviour. The API is not intended for unrestricted self-service use and is made available only to authorised parties as part of agreed implementations.
• API documentation: Yes
• API documentation formats: Open API (also known as Swagger)
• API sandbox or test environment: Yes
• Customisation available: Yes
• Description of customisation: The service can be customised to reflect local clinical pathways, workflows, and organisational requirements. Customisable elements include configuration of clinical decision support rules, knowledge base content, workflow logic, user roles and permissions, and integration settings with local clinical IT systems. This allows the service to be adapted to different care settings while maintaining a consistent and governed core platform.; ; Customisation is achieved through configuration rather than changes to the underlying software code. Configuration is typically undertaken during implementation, working collaboratively with the buyer and relevant stakeholders to ensure alignment with local policies, clinical practice, and information governance requirements. Updates to configuration can be made over time to reflect changes in clinical guidance, service models, or local needs.; ; Customisation is carried out by authorised users acting on behalf of the buyer, such as clinical leads, digital or informatics teams, or approved implementation partners. End users, such as clinicians, do not modify the system configuration directly. They interact with the service through predefined workflows and interfaces tailored to their role. This approach supports local flexibility while ensuring safety, consistency, and appropriate governance across deployments.

Scaling

• Independence of resources: The service is delivered as a multi-tenant, cloud-based platform designed to ensure fair and reliable use across organisations. Logical separation is used to isolate customer data and configurations, and service capacity is managed centrally to prevent individual users or organisations from adversely affecting others. The underlying cloud infrastructure is designed to scale to accommodate variations in demand, and service usage is monitored to identify and manage performance issues. This approach ensures consistent performance and availability for all users while supporting growth and changing usage patterns across the service.

Analytics

• Service usage metrics: Yes
• Metrics types: The service can provide usage metrics to support service monitoring and evaluation. Metrics may include volumes of service interactions, such as number of times clinical decision support is triggered, alerts or recommendations returned, and access to the results viewer. Where appropriate, aggregate usage metrics can be shared with the buyer to support service evaluation, quality improvement, and governance. Metrics are provided in a way that respects information governance and patient confidentiality requirements.
• Reporting types: Reports on request
• Resource tagging: No
• 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: Another external penetration testing organisation
• 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 their data by submitting a request to Fava, who will coordinate data export as part of routine service operations or at contract end. Data is provided in a structured, commonly used electronic format suitable for reuse or transfer to other systems. The export method and format are agreed with the buyer to reflect data types, local requirements, and information governance policies. Where appropriate, secure electronic transfer methods are used. Documentation can be provided to support understanding of the exported data.
• Data export formats:
  • CSV
  • Other
• Other data export formats:
  • HL7 FHIR
  • OpenEHR
• Data import formats:
  • CSV
  • Other
• Other data import formats:
  • HL7 FHIR
  • OpenEHR
  • JSON

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)

Availability and resilience

• Guaranteed availability: The service is designed to be highly available and is hosted on resilient public cloud infrastructure with redundancy across core components. Fava targets a monthly service availability of 99.5%, excluding planned maintenance windows agreed in advance with the buyer. Availability is measured at the service interface level.; ; Planned maintenance, where required, is scheduled outside of normal working hours wherever possible and communicated to buyers in advance. Emergency maintenance may be required on occasion to address security or stability issues.; ; Service availability commitments and service level agreements (SLAs) are agreed as part of each Call-Off Contract. Where availability falls below the agreed service level in a given period, service credits may be applied in line with the Call-Off Contract terms. Service credits are typically calculated as a proportion of the monthly service charge and applied against future invoices, rather than as direct financial refunds.
• Approach to resilience: The service is designed for resilience using a cloud-native architecture hosted on public cloud infrastructure. Core service components are deployed with redundancy to reduce single points of failure, and the platform is designed to scale to accommodate changes in demand. Monitoring is used to identify and respond to service issues, supporting timely recovery.; ; Datacentre resilience, including physical security, power, cooling, and environmental controls, is provided by the underlying cloud infrastructure provider. These facilities are designed for high availability and are operated in accordance with recognised industry standards. Detailed information about datacentre resilience and specific architectural controls can be provided to buyers on request.; ; This layered approach ensures resilience at both the application and infrastructure levels while allowing the service to be delivered securely and reliably across different deployment environments.
• Outage reporting: Service outages or significant service disruptions are communicated to buyers through direct notification. This typically includes email updates to nominated buyer contacts, providing information on the nature of the issue, its impact, and progress towards resolution. Where appropriate, follow-up communications are provided once service is restored. At present, the service does not provide a public status dashboard or outage reporting API. Alternative reporting mechanisms, such as agreed reporting formats or access to status information, can be discussed with buyers as part of the implementation or support arrangements.

Identity and authentication

• User authentication needed: Yes
• User authentication:
  • Identity federation with existing provider (for example Google Apps)
  • Other
• Other user authentication: Users access the service through integration with their primary clinical system. Clinicians authenticate to their existing clinical IT system using local authentication controls. When the service is launched in context, the user’s identity and role are securely asserted by the upstream system and trusted by the service. This allows authenticated access without requiring users to manage separate usernames or passwords. Access is restricted to authorised users and is limited to the appropriate clinical context and permissions associated with their role.
• Access restrictions in management interfaces and support channels: Access to management interfaces and support channels is restricted to authorised personnel only. Administrative access is limited based on role and responsibility, following the principle of least privilege. Authentication and access controls are applied to ensure only approved staff can view or modify system configuration, data, or support information. Support requests are handled through controlled channels, with access limited to named contacts and appropriate internal teams. All access is logged and reviewed to support accountability and audit requirements.
• 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)

Audit information for users

• Access to user activity audit information: Users contact the support team to get 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: At least 12 months
• How long system logs are stored for: At least 12 months

Security governance

• Named board-level person responsible for service security: Yes
• Security governance certified: No
• Security governance approach: Security governance is embedded into the design, development, and operation of the service. Responsibility for security sits with senior leadership, with oversight of risk management, secure development practices, and incident response. The service follows cloud security best practices and is supported by external penetration testing and vulnerability management. Security risks are identified, assessed, and addressed through documented processes, with remediation actions tracked. Information governance and data protection requirements are considered throughout the service lifecycle. Fava is formalising its governance through implementation of a quality management system (QMS) and working towards Cyber Essentials Plus and NHS Digital Technology Assessment Criteria (DTAC).
• Information security policies and processes: Fava maintains a set of information security policies and operational processes designed to protect confidentiality, integrity, and availability of data throughout the service lifecycle. Security responsibility sits with senior leadership, with day-to-day oversight led by the technical leadership team. Roles and responsibilities for information security are defined, including incident management, access control, and risk ownership.; ; Policies cover areas such as secure system design and development, access management, data protection, incident response, vulnerability management, and supplier assurance. These policies are supported by documented processes to identify, assess, and manage security risks, including regular review of system changes and security findings.; ; Compliance with policies is supported through technical controls, secure development practices, and staff awareness. External penetration testing and vulnerability assessment are used to validate the effectiveness of controls, with findings tracked and remediated. Security incidents are logged, investigated, and escalated appropriately.; ; Fava is formalising its policies and processes through the implementation of a quality management system (QMS) and alignment with NHS Digital Technology Assessment Criteria (DTAC). Information security governance is reviewed regularly to ensure policies remain effective and proportionate as the service evolves.
• Software Security Code of Practice: Yes

Operational security

• Configuration and change management standard: Supplier-defined controls
• Configuration and change management approach: Configuration and change management for the service follow defined internal processes to ensure changes are controlled, traceable, and assessed for risk. Service components, application code and configuration, are tracked throughout their lifecycle using version control and change records, providing visibility from development through to deployment.; ; Proposed changes are reviewed to assess potential impacts on security, performance, and service reliability, including data protection and access controls. Changes are tested prior to release and deployed in a controlled manner.; ; These processes are being formalised through the implementation of a quality management system, aligned with ISO 9001 and NHS Digital Technology Assessment Criteria.
• Vulnerability management type: Supplier-defined controls
• Vulnerability management approach: Vulnerabilities are identified through a combination of external penetration testing, routine security review, and monitoring of relevant threat intelligence. Potential threats are assessed based on severity, likelihood, and potential impact on confidentiality, integrity, and availability of the service. Identified vulnerabilities are prioritised and tracked to remediation. Patches and mitigations are deployed in a timely manner, with higher-risk issues addressed as a priority. Information on emerging threats is obtained from cloud service providers, security advisories, dependency and framework notifications, and relevant national guidance. Processes are being formalised as part of an evolving quality management system and DTAC alignment.
• Protective monitoring type: Supplier-defined controls
• Protective monitoring approach: Protective monitoring is used to identify potential security or service issues through logging, monitoring, and alerting of key system events. Monitoring focuses on indicators of compromise, abnormal behaviour, and service degradation. When a potential compromise is identified, it is investigated promptly, with appropriate containment and remediation actions taken based on severity and impact. Security incidents are escalated internally and managed through defined response processes. Higher-risk incidents are prioritised for immediate investigation and resolution, with response times proportionate to the nature and potential impact of the issue.
• Incident management type: Supplier-defined controls
• Incident management approach: The service follows defined incident management processes to identify, assess, and respond to incidents in a timely manner. Pre-defined processes are in place for common event types, including service disruption and security incidents. Users can report incidents through agreed support channels, such as email or support requests. Incidents are logged, investigated, and prioritised based on impact and severity. Where required, incident updates and summary reports are provided to buyers, including details of impact, actions taken, and any follow-up measures to reduce the likelihood of recurrence.
• Post-quantum cryptography secure: No

Secure development

• Approach to secure software development best practice: Supplier-defined process

Public sector networks

• Connection to public sector networks: No

Pricing

• Discount for educational organisations: Yes
• Free trial available: Yes
• Description of free trial: Free or trial access may be provided on a time-limited basis for evaluation, research, or pilot use. This typically includes access to agreed features and functionality within a defined scope. Production deployment, full support, and ongoing service commitments are not included. Trial duration and scope are agreed in advance.

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: 0%
• Between £2,500,001 and £5,000,000: 0%
• Over £5,000,001: 0%

Non-mandatory Standards and certifications

• ISO/IEC 27001 certification: No
• 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: E400540e-72ff-4f29-8dc1-863a714a00a5
• Cyber essentials plus: No
• Cyber Essentials Alternative: None of the criteria
• Other security certifications: No

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

    • Providing opportunities for, and measuring and monitoring of, staff workforce conditions over time, including employee engagement, involvement in decision-making and satisfaction and adapting to any changes in the results, with clear processes for acting on issues identified
    • Plans to engage the contract workforce in deciding the most important workplace issues to address
    • Activities that support an environment where staff are educated about, and feel empowered to, address their physical wellbeing
    • Activities that support an environment where staff are educated about and feel empowered to report and address bullying and harassment
    • Payment of more than the National Minimum Wage or National Living Wage (as appropriate) to the contract workforce
    • Understanding of in-work progression issues affecting the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • 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
    • 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

  • 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
    • 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: 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 3: Resilient, innovative and flexible supply chains: Support economic growth through enabling resilient businesses, opportunities for small businesses and voluntary, community and social enterprises

    • Understanding of the types of businesses in the market and the level of participation by new businesses, entrepreneurs, start-ups, SMEs, VCSEs and mutuals
    • Activities that demonstrate a collaborative way to work with a diverse range of businesses as part of the supply chain
    • Understanding of local demographics, needs and opportunities for the co-design of the goods, services and works to be delivered under the contract
    • Measures to involve local stakeholders and/or users in design (e.g. in the design of services, systems, products or buildings)
    • Measures to engage users and communities and build relationships to increase community integration build trust and influence how the contract is delivered
    • Plans to respond flexibly and adapt approaches to community engagement and initiatives

  • 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
    • 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

    • Understanding of employment and skills issues, and of the skills and employment shortages of high growth sectors relating to the contract
    • Understanding of the issues affecting the representation of disabled people in the workforce in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors
    • 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
    • Understanding of the issues affecting inequality in employment, skills and pay in the market, industry or sector relevant to the contract, and in the supplier’s own organisation and those of its key sub-contractors. Measures to tackle inequality in employment, skills and pay in the contract workforce
    • 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 the issues affecting the development of new skills by target cohort
    • Understanding of the underlying factors affecting improvements to reduce barriers to entry and training schemes for the target cohort(s) related to the contract workforce
    • Creation of outreach activities to create a pipeline of employees for the future contract delivery

  • 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
    • Inclusive and accessible recruitment practices, development practices and retention policies that support-focused activities including those provided in the Guide for line managers on recruiting, managing and developing which support people with a disability or health condition
    • Actions to invest in the physical and mental health and wellbeing of the contract workforce

Service documents

• Pricing document

  PDF

• Service definition document

  PDF

• Terms and conditions

  PDF

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 videha@favahealth.com. Tell them what format you need. It will help if you say what assistive technology you use.