1.
WordPress in the Health Sector<br />Michael Kimb Jones<br />July 19th 2009 - WordCamp UK <br />

2.
WordPress in the NHS<br />WordPress in large enterprise<br />WordPress for local government<br />WordPress as a CMS<br />

3.
About me…<br />Michael<br />Kimb<br />Jones<br />Web Solutions Manager<br />Barnsley Hospital NHS Foundation Trust<br />

4.

5.
About me…<br />Michael<br />Kimb<br />Jones<br />Freelance Work<br />Base6 Design Ltd <br />

6.

7.
About me…<br />Michael<br />Kimb<br />Jones<br />Personal Blog: mkjones.co.uk<br />Twitter: @mkjones<br />Base6: base6design.com<br />

8.
Contents...<br />The NHS CMS Predicament<br /><ul><li>Lack of tools/strategy

9.
Issues faced

10.
Fixing the problem</li></ul>Set-up at Barnsley Hospital BEFORE the re-development<br /><ul><li>Internal/External web presence

11.
Off-shoot (rebel) sites

12.
Reasons for re-development</li></ul>Website Re-development Project <br /><ul><li>Project objectives

13.
The road to WordPress

14.
WordPress set-up (plugins, users, etc)

15.
Site stats, feedback & future plans</li></li></ul><li>The NHS CMS Predicament<br />

16.
The NHS CMS Predicament...<br />Lack of tools/strategy<br /><ul><li>There is a problem with CMS’s in the NHS

17.
No central body has been given the responsibility of providing this service

18.
This causes health organisations to waste time and money on the procurement of non-standardised and untestedCMS tools or developing their own systems</li></li></ul><li>The NHS CMS Predicament...<br />Lack of tools/strategy<br />For example...<br /><ul><li>121 Foundation Trusts

19.
121 different systemsand ideas for content management

20.
121 web development teams and 1000s of users not communicating with each other

21.
Leads to frustration, a lack of standards and a lot of wasted time and money</li></li></ul><li>The NHS CMS Predicament...<br />Issues faced <br /><ul><li>Some organisations invest more money than others depending on priorities, staffing, support

22.
Not all organisations have a dedicated and skilled team which can support or develop a CMS solution

23.
Often organisations are seen as easy targets for development firms out to make a ‘quick buck’ (NHS Cash-cow syndrome)</li></li></ul><li>The NHS CMS Predicament...<br />Fixing the problem??<br />

24.
The NHS CMS Predicament...<br />Fixing the problem??<br />Its clear that the NHS possess quality CMS solutions...<br />DoH<br />NHS Direct<br />NHS Choices<br />All of these sites must use tried and tested systems to publish content on the web<br />

25.
The NHS CMS Predicament...<br />Fixing the problem??<br /><ul><li>Why don’t these central organisations share the CMS tools they use?

26.
A sponsored centralised solution could easily be developed using existing tools and methods that could then be shared out to any organisation wishing to use it

27.
A system similar in design to the recent ‘NHS Mail’ project could be devised and made available as an option for organisations to use and participate in</li></li></ul><li>The NHS CMS Predicament...<br />Fixing the problem??<br /><ul><li>Providing the tool centrally would also alleviate the need for 3rd party hosting and support

28.
Such a tool could even be released as open-source software using a GPL-like licence allowing organisations to re-develop and modify to their specific needs

29.
Ultimately this could lead to...

30.
100s of different sites

31.
1000s of users

32.
Just 1 CMS</li></li></ul><li>So in closing...<br />Fixing the NHS CMS Predicament<br />Use WordPress?<br />OR at least adopt a similar methodology and model<br />

33.
Set-up at Barnsley Hospital BEFORE the re-development<br />

34.
Set-up at Barnsley Hospital...<br />Old External Site<br />Internal Intranet<br /><ul><li>Public facing ‘www’ site

35.
Hospital News/Events

36.
Patient information

37.
Board/Corporate Info

38.
Moderated content

39.
Internal ‘N3’ site

40.
Staff information (news, events)

41.
Departmental sub-sites (60 sites)

42.
Built in-house (Classic ASP)

43.
Un-moderated content</li></li></ul><li>Internal site has yet to be updated...<br />

44.
Re-development project focused on the external website…<br />

45.
Old external website…<br />Developed in 2004 as a ‘quick fix’<br />Static HTML site<br />Used Dreamweaver Templates<br />Lacking in content<br />Vastly out of date<br />These issues led to off-shoot sites<br />www.bhnft.nhs.uk<br />

46.
Off-shoot (rebel) sites...<br />Barnsley PGME<br />Barnsley Audiology<br />Barnsley Dietetic and Nutrition<br />Barnsley Healthy Workplace<br />Barnsley ICT Services<br />Nursing in the North<br />North Trent Cancer Network<br />Barnsley Pathology Services<br />Staff Support Services<br />

47.
Example off-shoot (rebel) site...<br />www.barnsleyaudiology.nhs.uk<br />

48.
Off-shoot (rebel) sites...<br />Barnsley PGME<br />Barnsley Audiology<br />Barnsley Dietetic and Nutrition<br />Barnsley Healthy Workplace<br />To help maintain and streamline development of these sites and after a lengthy search I had actually procured a pretty decent open-source ASP.Net CMS:<br />Umbraco (www.umbraco.org)<br />Barnsley ICT Services<br />Nursing in the North<br />North Trent Cancer Network<br />Barnsley Pathology Services<br />Staff Support Services<br />

49.
Using Umbraco…<br />Reason for choosing Umbraco<br /><ul><li>Runs on the ASP.Net platform (requirement in an NHS environment)

50.
Simple to use, install, maintain

51.
Open-source

52.
FREE

53.
The best free ASP.Net available </li></li></ul><li>Using ASP.Net…<br />The NHS Is a very PURE Microsoft environment which makes .NET the standard for Enterprise and Web Development<br />

54.
Using PHP/MySQL…<br />Getting PHP/MySQL in the organisation was one of the greatest challenges I faced as a web developer<br />In the end it came down to money….<br />In order to build upon the Umbraco CMS I insisted that we would require the Pro (supported) AND some expert training as I had little or no time to learn Umbracoto the required level<br />

55.
The problem with Umbraco…<br />Moving away from Umbraco<br /><ul><li>No robust support community

56.
No funding for paid support/training (Pro version)

57.
No knowledge on how or if it could be scaled

58.
Long learning curve

59.
We had finally allowed PHP/MySQL in the organisation</li></li></ul><li>Losing Umbraco…<br />A recent Twitter on how I moved away from the Umbraco CMS once we had a strategy in place which allowed for PHP/MySQL applications to be included in our infrastructure <br />

60.
Losing Umbraco…<br />Passionate developers and a emerging community <br />

61.
Losing Umbraco…<br />Umbraco is one of the very few decent FREE ASP.Net open-source CMS’s but in my opinion it can’t compete with the WordPress experience <br />

62.
Reasons for re-development<br />Umbraco<br />In-house CMS (Classic ASP)<br />Static HTML<br />Inconsistency in front-end design and back end technology<br />This went on for a number of years before being addressed<br />

63.
Reasons for re-development...<br />Core external site was underdeveloped and out of date<br />Relevant Hospital content was stretched over multiple websites<br />The Hospital brand was not strongly reflected on any of the existing sites<br />No clear CMS strategy – ‘anything goes’ <br />

64.
Reasons for re-development...<br />No GOOD CMS strategy <br /><ul><li>Using a mixture of

65.
Self-built CMS tools

66.
Static HTML

67.
Umbraco

68.
External Companies

69.
Content was not centralised

70.
No standards were in place

71.
The whole thing was a mess….</li></li></ul><li>Website Re-development Project<br />

72.
Project objectives...<br />

73.
Project objectives...<br />Fix everything I’ve just brought up<br /><ul><li>Re-develop the external website from the ground up

74.
Design a theme which reflected the Hospital brand

75.
Bring all off-shoot sites under the same umbrella

76.
Ensure the resulting system is easy to use and expandable </li></li></ul><li>The road to WordPress...<br />Although I’d been using and advocating WordPress for a few years it <br />hadn’t had any impact on my work at the hospital <br />

77.
Developing the new site...<br />

78.
Clearly defined navigation structure...<br />More useful and informative than the previous version<br />

79.
Corporate information...<br />

80.
Service information...<br />

81.
Service information...<br />

82.
Service information...<br />

83.
Stats on the new site...<br />Moved to the new domainwww.barnsleyhospital.nhs.uk<br />Developed in6 weeks<br />Hostingcosts£200 PA<br />

84.
Stats on the new site...<br />334 Pages<br />35 Posts<br />10Plugins<br />WPv2.8<br />10,000k Monthlyvisitors<br />5 Active editors<br />

85.
Stats on the new site...<br />100% <br />Positive feedback fromusers AND editors<br />

86.
WordPress Set-up…<br />Essential Plugins<br /><ul><li>All in One SEO Pack

87.
Contact Form 7

88.
Fold Page List

89.
Role Scoper

90.
TinyMCE Advanced

91.
WordPress Database Backup</li></li></ul><li>WordPress Set-up…<br />Favourite Plugins<br />Fold Page List<br />Role Scoper<br />WordPress Database Backup<br />

92.
WordPress Set-up…<br />Favourite Plugins<br />Fold Page List<br /><ul><li>Instantly enhances the use of pages in WordPress

93.
Comes with a built-in breadcrumb system

94.
Allows developers to easily query child/parent ID’s</li></li></ul><li>Using Fold Page List…<br />

95.
WordPress Set-up…<br />Favourite Plugins<br />Role Scoper<br /><ul><li>Turns a standard WordPress installation into a multi-user CMS without the need for WPMU

96.
Extremely advanced user role management

97.
Allows user role management of individual post or pages

98.
Ability to give editors their own sub-areas to work on

99.
Easy to use interface</li></li></ul><li>Using Role Scoper…<br />

100.
Using Role Scoper…<br />

101.
Using Role Scoper…<br />

102.
WordPress Set-up…<br />Favourite Plugins<br />WordPress Database Backup<br /><ul><li>Daily, weekly or monthly database backups

103.
Option to archive or email

104.
No hassle, it just works</li></li></ul><li>Using WordPress Database Backup<br />

105.
The future…<br />Future Plans<br /><ul><li>Give every hospital service the ability to maintain their own section

106.
Reign in more off-shoot sites that are yet to be converted

107.
Integrate social apps – Twitter, YouTube

108.
Implement blogs for Chief Executive and board members

109.
Multi-language version</li></li></ul><li>To conclude…<br />UsingWordPressWe..<br /><ul><li>Were able to develop a large website on a short deadline

110.
Ended up with a great CMS solution

111.
Spend hardly any money

112.
Are confident future CMS challenges have been met

113.
Never looked back…</li>