Yorkshire and the Humber Co-Design Model

These were compiled in 2012 and have not been updated.

Yorkshire and the Humber logo

Quick start

For those who are confident and just want to use the model. Download and use the Template: Yorkshire and the Humber Co-Design Model for local use and follow the Guide: Yorkshire and the Humber Co-Design Model to help you populate your model with local data.

What is the model?

The Yorkshire and the Humber Co-Design Model (formerly known as the Yorkshire and the Humber Commissioner Financial Model) is a decision-making support tool to aid understanding of the financial impact of moving end of life care out of hospital and into alternative care settings. It is spreadsheet-based and runs in Microsoft Excel.

Who will it help?

Anyone who wants to look at the actual and alternative costs of end of life care for their local populations, including commissioners, clinicians, performance managers and finance managers.

Case studies of tool deployment

During the autumn of 2011, two sites were selected as early adopters for the YH Co-Design tool and were supported to use the tools and to apply their own local data. A YH Co-Design case study for Lancaster, Morecambe, Carnforth and Garstang Clinical Commissioning Consortium provides further details of the process, the learning and impact of using the tool.

What does the model do?

It enables users to look at actual and alternative costs and volume of end of life care now, in five years with no service change, and in five years with service change, based on local data. While the current version of the model focuses on frail elderly patients, it can be adapted for patients with a wide range of conditions (for example, cancer).

The tool is being developed to improve ease of:

  • calibration with local demographics and data sets;
  • analysis of the number and cost of hospital episodes in the last months of life; and
  • analysis of local alternative health and social care pathways.

This work is being carried out through work with Early Adopter locations during the Winter of 2011.

What does the model not do?

  • It is not a clinical decision making tool.
  • It does not give definitive financial solutions but should be used to inform discussions locally about alternative affordable changes to care pathways and settings.

How do I use the model?

The model is designed for use with partners and in multi-disciplinary discussions, for example with commissioners, clinicians (including GPs, community nurses, palliative care consultants, geriatricians), hospital-based data coding specialists and performance analysts, to decide how best to apply the model for local services. The process is:

  • decide on the data and populate the data input sheets;
  • confirm the relevant care pathways for the identified population (including ‘no change’);
  • review and agree the parameters within the model and adapt for local circumstances;
  • run the model to generate four reports for local discussion:
    • current year cost and volume;
    • predicted position in five years time with no change in how patients are treated (future present);
    • predicted position in five years time, if patients benefit from being treated through alternative care pathways (future scenario);
    • potential hospital bed days released by the service change.

What do I need to do to get started?

We estimate that, over approximately a 12-week period, you will need 10 days of an analyst’s time, 6 days of a commissioner’s time and 2 days each for all others directly involved to create your first version.

Support for users

Information and resources are provided on this website to support users. Additional support is available from neolcin at phe dot gov.uk link  or contact the tool developer Lois Bentley.


This tool was produced in collaboration with the following organisations:

NHS Hull NHS Wakefield District Bridges

Return to the End of Life Care Modelling Tools page

End of Life Care Profiles
Data Sources
Advice and information
Validates against XHTML 1.0   Cascading stylesheet compliance   Single A Accessibility compliance