12.06.2014 Views

The development of Local Healthwatch in Kent Part one: key findings

The development of Local Healthwatch in Kent Part one: key findings

The development of Local Healthwatch in Kent Part one: key findings

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Recommendations<br />

<strong>The</strong> follow<strong>in</strong>g series <strong>of</strong> recommendations is based on the synthesis <strong>of</strong><br />

contributions from participants. <strong>The</strong> <strong>key</strong> forum for consider<strong>in</strong>g and manag<strong>in</strong>g<br />

these recommendations should be the <strong>Local</strong> <strong>Healthwatch</strong> Development<br />

Group established <strong>in</strong> June 2011. Each recommendation is followed by a<br />

suggestion for the lead agency to deliver the proposal.<br />

Involv<strong>in</strong>g stakeholders<br />

1. All participants <strong>in</strong> the statement <strong>of</strong> read<strong>in</strong>ess process should receive<br />

a copy <strong>of</strong> the report and be <strong>in</strong>vited to <strong>of</strong>fer further comments and<br />

reflections. <strong>The</strong>se contributions should be <strong>in</strong>corporated <strong>in</strong>to the work<br />

<strong>of</strong> the <strong>Local</strong> <strong>Healthwatch</strong> Development Group. Suggested lead: <strong>Kent</strong><br />

County Council<br />

2. All participants should form the core <strong>of</strong> a database <strong>of</strong> <strong>in</strong>terested<br />

parties <strong>in</strong> the <strong>development</strong> <strong>of</strong> K LHW. <strong>The</strong>y should be kept <strong>in</strong>formed<br />

<strong>of</strong> progress and provided with further opportunities to engage <strong>in</strong> the<br />

<strong>development</strong> <strong>of</strong> plans. <strong>The</strong> core database should be expanded to<br />

<strong>in</strong>clude a wider group <strong>of</strong> stakeholders, services users and patients<br />

and a communication plan developed. Suggested lead: <strong>Kent</strong> County<br />

Council<br />

3. A timel<strong>in</strong>e for the <strong>development</strong> <strong>of</strong> K LHW should be developed and<br />

shared with stakeholders. Suggested lead: NHS <strong>Kent</strong> and Medway<br />

4. <strong>The</strong> commitment and <strong>in</strong>terest amongst stakeholders highlighted by<br />

the statement <strong>of</strong> read<strong>in</strong>ess process should be used to cont<strong>in</strong>ue to<br />

take a whole system approach to the <strong>development</strong> <strong>of</strong> K LHW over the<br />

next six months. <strong>The</strong> <strong>Local</strong> <strong>Healthwatch</strong> Development Group should<br />

consider the use <strong>of</strong> toolkits from appreciative <strong>in</strong>quiry and ‘strengths<br />

based approaches’ to <strong>in</strong>form its work. Suggested lead: All parties<br />

5. LINks and other stakeholders <strong>in</strong>clud<strong>in</strong>g Patient <strong>Part</strong>icipation Groups<br />

and CVS organisations should be <strong>in</strong>vited to cont<strong>in</strong>ue to collect and<br />

share stories from patients and service users about their experiences<br />

and what K LHW could mean to them. <strong>The</strong> stories will give further<br />

<strong>in</strong>sight about what an effective K LHW should do and how it would<br />

help local people. <strong>The</strong> stories should be collated and used to <strong>in</strong>form<br />

the co-production <strong>of</strong> K LHW. Suggested lead: LINks<br />

30<br />

<strong>The</strong> <strong>development</strong> <strong>of</strong> <strong>Local</strong> <strong>Healthwatch</strong> <strong>in</strong> <strong>Kent</strong>: assess<strong>in</strong>g read<strong>in</strong>ess for <strong>Local</strong> <strong>Healthwatch</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!