|
|
Improvement Report: Systemwide Improvement of Services for Older People
The London Older People's Service Development Programme supported collaborative working across health (secondary and primary care), social care, housing and voluntary sector agencies using evidence-based, preventive approaches to produce measurable improvements in health and community care services for older people (promoting independence and preventing unnecessary entry or re-entry to hospital).
|
Successful Measurement for Improvement
Successful measurement is a cornerstone of successful improvement. The key is to choose the right measurements, so that you can see results quickly and adapt your interventions accordingly, putting less strain on resources and more focus on outcomes.
|
A Picture Is Worth a Thousand Words
Plotting data over time offers insights and maximizes the learning from any data collected by revealing patterns and improvement opportunities.
|
Try Walking the Golden Line
When trying to streamline a complex process, it is sometimes best to imagine an ideal system that contains only value-added steps.
|
Mitigating the Risks of Running Improvement Tests While Maximizing the Learning: An Excerpt from The Improvement Guide
The scale of the test should be decided according to (1) the degree of belief that the change will result in improvement, and (2) the risks from a failed test.
|
Understand Variation in Data
Understanding the nature of the variation in data is paramount in decision-making about improvement efforts.
|
One Size Does Not Fit All — Think Segmentation
Health care organizations need to move beyond a "one size fits all" approach, and strive to customize services for individual needs.
|
View Your Organization as a System
View the organization as a system, rather than a collection of individuals or departments working side by side.
|
Think Improvement, Not Inspection
Some inspection is always necessary, but inspection cannot always catch problems that are inherent in the system itself.
|
No Sample Is Too Small
Sometimes it is best to test a change on one customer, then two, then a few more, before implementing the change on a broad scale.
|
|
|
