Your SlideShare is downloading. ×

Word Press In The Health Sector


Published on

My recent presentation detailing the re-development of the Barnsley Hospital website.

My recent presentation detailing the re-development of the Barnsley Hospital website.

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. WordPress in the Health Sector
    Michael Kimb Jones
    July 19th 2009 - WordCamp UK
  • 2. WordPress in the NHS
    WordPress in large enterprise
    WordPress for local government
    WordPress as a CMS
  • 3. About me…
    Web Solutions Manager
    Barnsley Hospital NHS Foundation Trust
  • 4.
  • 5. About me…
    Freelance Work
    Base6 Design Ltd
  • 6.
  • 7. About me…
    Personal Blog:
    Twitter: @mkjones
  • 8. Contents...
    The NHS CMS Predicament
    • Lack of tools/strategy
    • 9. Issues faced
    • 10. Fixing the problem
    Set-up at Barnsley Hospital BEFORE the re-development
    • Internal/External web presence
    • 11. Off-shoot (rebel) sites
    • 12. Reasons for re-development
    Website Re-development Project
    • Project objectives
    • 13. The road to WordPress
    • 14. WordPress set-up (plugins, users, etc)
    • 15. Site stats, feedback & future plans
  • The NHS CMS Predicament
  • 16. The NHS CMS Predicament...
    Lack of tools/strategy
    • 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
  • The NHS CMS Predicament...
    Lack of tools/strategy
    For example...
    • 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
  • The NHS CMS Predicament...
    Issues faced
    • 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)
  • The NHS CMS Predicament...
    Fixing the problem??
  • 24. The NHS CMS Predicament...
    Fixing the problem??
    Its clear that the NHS possess quality CMS solutions...
    NHS Direct
    NHS Choices
    All of these sites must use tried and tested systems to publish content on the web
  • 25. The NHS CMS Predicament...
    Fixing the problem??
    • 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
  • The NHS CMS Predicament...
    Fixing the problem??
    • 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
  • So in closing...
    Fixing the NHS CMS Predicament
    Use WordPress?
    OR at least adopt a similar methodology and model
  • 33. Set-up at Barnsley Hospital BEFORE the re-development
  • 34. Set-up at Barnsley Hospital...
    Old External Site
    Internal Intranet
    • 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
  • Internal site has yet to be updated...
  • 44. Re-development project focused on the external website…
  • 45. Old external website…
    Developed in 2004 as a ‘quick fix’
    Static HTML site
    Used Dreamweaver Templates
    Lacking in content
    Vastly out of date
    These issues led to off-shoot sites
  • 46. Off-shoot (rebel) sites...
    Barnsley PGME
    Barnsley Audiology
    Barnsley Dietetic and Nutrition
    Barnsley Healthy Workplace
    Barnsley ICT Services
    Nursing in the North
    North Trent Cancer Network
    Barnsley Pathology Services
    Staff Support Services
  • 47. Example off-shoot (rebel) site...
  • 48. Off-shoot (rebel) sites...
    Barnsley PGME
    Barnsley Audiology
    Barnsley Dietetic and Nutrition
    Barnsley Healthy Workplace
    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:
    Umbraco (
    Barnsley ICT Services
    Nursing in the North
    North Trent Cancer Network
    Barnsley Pathology Services
    Staff Support Services
  • 49. Using Umbraco…
    Reason for choosing Umbraco
    • 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
  • Using ASP.Net…
    The NHS Is a very PURE Microsoft environment which makes .NET the standard for Enterprise and Web Development
  • 54. Using PHP/MySQL…
    Getting PHP/MySQL in the organisation was one of the greatest challenges I faced as a web developer
    In the end it came down to money….
    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
  • 55. The problem with Umbraco…
    Moving away from Umbraco
    • 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
  • Losing Umbraco…
    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
  • 60. Losing Umbraco…
    Passionate developers and a emerging community
  • 61. Losing Umbraco…
    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
  • 62. Reasons for re-development
    In-house CMS (Classic ASP)
    Static HTML
    Inconsistency in front-end design and back end technology
    This went on for a number of years before being addressed
  • 63. Reasons for re-development...
    Core external site was underdeveloped and out of date
    Relevant Hospital content was stretched over multiple websites
    The Hospital brand was not strongly reflected on any of the existing sites
    No clear CMS strategy – ‘anything goes’
  • 64. Reasons for re-development...
    No GOOD CMS strategy
    • 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….
  • Website Re-development Project
  • 72. Project objectives...
  • 73. Project objectives...
    Fix everything I’ve just brought up
    • 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
  • The road to WordPress...
    Although I’d been using and advocating WordPress for a few years it
    hadn’t had any impact on my work at the hospital
  • 77. Developing the new site...
  • 78. Clearly defined navigation structure...
    More useful and informative than the previous version
  • 79. Corporate information...
  • 80. Service information...
  • 81. Service information...
  • 82. Service information...
  • 83. Stats on the new site...
    Moved to the new
    Developed in6 weeks
    Hostingcosts£200 PA
  • 84. Stats on the new site...
    334 Pages
    35 Posts
    10,000k Monthlyvisitors
    5 Active editors
  • 85. Stats on the new site...
    Positive feedback fromusers AND editors
  • 86. WordPress Set-up…
    Essential Plugins
  • WordPress Set-up…
    Favourite Plugins
    Fold Page List
    Role Scoper
    WordPress Database Backup
  • 92. WordPress Set-up…
    Favourite Plugins
    Fold Page List
    • 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
  • Using Fold Page List…
  • 95. WordPress Set-up…
    Favourite Plugins
    Role Scoper
    • 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
  • Using Role Scoper…
  • 100. Using Role Scoper…
  • 101. Using Role Scoper…
  • 102. WordPress Set-up…
    Favourite Plugins
    WordPress Database Backup
    • Daily, weekly or monthly database backups
    • 103. Option to archive or email
    • 104. No hassle, it just works
  • Using WordPress Database Backup
  • 105. The future…
    Future Plans
    • 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
  • To conclude…
    • 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…