Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Drupal Prescription<br />A Case Study of Florida Hospital<br />Presented by:Rick Mann<br />
Our Drupal Journey So Far…<br /><ul><li>Where we’ve come from
Where we are now
A few lessons learned
Where we’re going</li></ul>2<br />
Who Are We?<br /><ul><li>Who is Florida Hospital?
A faith-based, not-for-profit healthcare provider founded in 1908 & located in Central Florida
8 Campuses, 2,188 beds, 16,500 employees
One of the largest hospitals in the country
Over 1,000,000 patients treated annually
18 Urgent Care Centers, Health Plan, Home Health, Ancillary Services</li></ul>3<br />
We have deployed Drupal as an Enterprise Web Platform…<br /><ul><li>On our Intranet to promote communication and collabora...
On the Internet to enhance the Florida Hospital brand and drive revenue</li></li></ul><li>Our Intranet Story<br />
Once Upon a Time…Our Problem<br />Last year, our Intranet looked like this:<br />
Intranet Issues<br /><ul><li>The Front Page: “Insite”
Just links; Not dynamic; Ugly
Never leveraged properly
No organizational pride
No centralized content owner
Gets 12,000 visits a day</li></ul>7<br />
Intranet Issues, continued…<br /><ul><li>80+ Department Sites:
End of life support with vendor (for current version)
Proprietary / hard to customize
Inconsistent UI from site to site
Training drop-off & orphaned content
Other misc. technical issues
Ultimately, we had to do a complete replacement</li></ul>8<br />
Distributed Responsibility<br /><ul><li>Small IT staff supports infrastructure
2 people; not their only support/development duties
MIS department has a history of self-reliance
Individual site content owned by the departmental end-users
Hand full of static FTP sites
Don’t like our solution? Use Notepad :P</li></ul>9<br />
What Were Our Goals?<br /><ul><li>Replace our dept CMS
Meet the needs of 80% of our users
Ease the transition
Provide additional functionality
Consistent theme
Easy to administer & add features
Strong community support
Enterprise support partner
Create a foundation to build on</li></ul>10<br />
Our Internet Story<br />
FH Internet Timeline<br />Internet strategy driven by Marketing & PR<br />In 2003 Marketing decided to buy a server and bu...
FH Internet Timeline<br />Problem: Proprietary “CMS”<br />Most pages static HTML <br />Vulnerable to XSS<br />$0.05 & $0.1...
FH Internet Timeline<br />August 2007: “Rock-star” physician recruited<br />Web marketing focus<br />Changed interactive a...
What Did 700k Buy Us?<br />12 Websites<br />5000 Hours (Approx)<br />Equivalent to 3 person team @ 75% Billable<br />15<br />
16<br />In-source Strategy<br />Reduce Dependence<br />Maximize Investment<br />Reduce Expense<br />Increase Revenue<br />...
What We Considered<br /><ul><li>Insite = custom .NET app
Quickr (QP replacement / IBM)
Sharepoint (.NET / Microsoft)
Liferay (Java / Open Source)
Drupal (PHP / Open Source)</li></ul>17<br />
Why Did We Even Look @ Drupal?<br /><ul><li>Pro: Implementation cost and time
Pro: Synergy with MIS & Marketing web team
Shared skill set for development and support
Upcoming SlideShare
Loading in …5
×

The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann

8,088 views

Published on

Learn how Florida Hospital and Acquia partnered to replace an existing legacy CMS and deliver a core Intranet architecture to support 100 separate but standardized Drupal sites used for collaboration and content management within months.

Florida Hospital, with 8 campuses and 2,188 beds, is an acute-care medical facility operated by the Seventh-day Adventist Church. It serves as a community hospital for Greater Orlando and as a major tertiary referral hospital for Central Florida and much of the Southeast, the Caribbean and Latin America. Adventist Health System, Florida Hospital’s parent company, operates 37 hospitals in ten states making it the largest not-for-profit protestant healthcare system in the United States.

Published in: Technology
  • Be the first to comment

The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann

  1. 1. The Drupal Prescription<br />A Case Study of Florida Hospital<br />Presented by:Rick Mann<br />
  2. 2. Our Drupal Journey So Far…<br /><ul><li>Where we’ve come from
  3. 3. Where we are now
  4. 4. A few lessons learned
  5. 5. Where we’re going</li></ul>2<br />
  6. 6. Who Are We?<br /><ul><li>Who is Florida Hospital?
  7. 7. A faith-based, not-for-profit healthcare provider founded in 1908 & located in Central Florida
  8. 8. 8 Campuses, 2,188 beds, 16,500 employees
  9. 9. One of the largest hospitals in the country
  10. 10. Over 1,000,000 patients treated annually
  11. 11. 18 Urgent Care Centers, Health Plan, Home Health, Ancillary Services</li></ul>3<br />
  12. 12. We have deployed Drupal as an Enterprise Web Platform…<br /><ul><li>On our Intranet to promote communication and collaboration
  13. 13. On the Internet to enhance the Florida Hospital brand and drive revenue</li></li></ul><li>Our Intranet Story<br />
  14. 14. Once Upon a Time…Our Problem<br />Last year, our Intranet looked like this:<br />
  15. 15. Intranet Issues<br /><ul><li>The Front Page: “Insite”
  16. 16. Just links; Not dynamic; Ugly
  17. 17. Never leveraged properly
  18. 18. No organizational pride
  19. 19. No centralized content owner
  20. 20. Gets 12,000 visits a day</li></ul>7<br />
  21. 21. Intranet Issues, continued…<br /><ul><li>80+ Department Sites:
  22. 22. End of life support with vendor (for current version)
  23. 23. Proprietary / hard to customize
  24. 24. Inconsistent UI from site to site
  25. 25. Training drop-off & orphaned content
  26. 26. Other misc. technical issues
  27. 27. Ultimately, we had to do a complete replacement</li></ul>8<br />
  28. 28. Distributed Responsibility<br /><ul><li>Small IT staff supports infrastructure
  29. 29. 2 people; not their only support/development duties
  30. 30. MIS department has a history of self-reliance
  31. 31. Individual site content owned by the departmental end-users
  32. 32. Hand full of static FTP sites
  33. 33. Don’t like our solution? Use Notepad :P</li></ul>9<br />
  34. 34. What Were Our Goals?<br /><ul><li>Replace our dept CMS
  35. 35. Meet the needs of 80% of our users
  36. 36. Ease the transition
  37. 37. Provide additional functionality
  38. 38. Consistent theme
  39. 39. Easy to administer & add features
  40. 40. Strong community support
  41. 41. Enterprise support partner
  42. 42. Create a foundation to build on</li></ul>10<br />
  43. 43. Our Internet Story<br />
  44. 44. FH Internet Timeline<br />Internet strategy driven by Marketing & PR<br />In 2003 Marketing decided to buy a server and build websites<br />Approached IT, but…<br />Built 10 sites for the key service lines<br />Campuses started to follow<br />20-25 sites<br />12<br />12<br />
  45. 45. FH Internet Timeline<br />Problem: Proprietary “CMS”<br />Most pages static HTML <br />Vulnerable to XSS<br />$0.05 & $0.10<br />Increased demand on web FTE<br />13<br />13<br />
  46. 46. FH Internet Timeline<br />August 2007: “Rock-star” physician recruited<br />Web marketing focus<br />Changed interactive agency<br />Drupal 5<br />Development requests intensified<br />Agency $$ increased<br />2008: 12 sites ~ $700k in Outsourced Drupal Development<br />14<br />14<br />
  47. 47. What Did 700k Buy Us?<br />12 Websites<br />5000 Hours (Approx)<br />Equivalent to 3 person team @ 75% Billable<br />15<br />
  48. 48. 16<br />In-source Strategy<br />Reduce Dependence<br />Maximize Investment<br />Reduce Expense<br />Increase Revenue<br />16<br />
  49. 49. What We Considered<br /><ul><li>Insite = custom .NET app
  50. 50. Quickr (QP replacement / IBM)
  51. 51. Sharepoint (.NET / Microsoft)
  52. 52. Liferay (Java / Open Source)
  53. 53. Drupal (PHP / Open Source)</li></ul>17<br />
  54. 54. Why Did We Even Look @ Drupal?<br /><ul><li>Pro: Implementation cost and time
  55. 55. Pro: Synergy with MIS & Marketing web team
  56. 56. Shared skill set for development and support
  57. 57. Shared infrastructure
  58. 58. Con: No pre-existing in-house experience
  59. 59. Existing team not open-sourced focused
  60. 60. Learning curve</li></ul>18<br />
  61. 61. Drupal Gap Analysis<br /><ul><li>Can Drupal do this? Asked Acquia for help.
  62. 62. Concurrent testing and learning
  63. 63. Learned what other questions to ask:
  64. 64. Single vs Multi-site install?
  65. 65. How can we limit end-user admin?
  66. 66. How do I secure it?
  67. 67. …and others.</li></ul>19<br />
  68. 68. What Sold Us on Drupal?<br /><ul><li>A mature product with a proven track record
  69. 69. It’s cheaper
  70. 70. Existing “out of the box” features/modules
  71. 71. Enterprise 2.0 features available
  72. 72. Very strong Community support
  73. 73. “There’s a module for that”
  74. 74. Enterprise level support available (Acquia)
  75. 75. It’s staff-able
  76. 76. It’s scalable and extendable</li></ul>20<br />
  77. 77. How Did We Get IT Approved?<br /><ul><li>Pitch to IT management
  78. 78. Who else is using it?
  79. 79. How does it compare?
  80. 80. Transition and support plan
  81. 81. Pitch to our users
  82. 82. Oooh, shiny!
  83. 83. Chance to “spring clean”
  84. 84. Plan for the future
  85. 85. Formation of Intranet Committee
  86. 86. IT, Marketing, HR, Internal Communications
  87. 87. Sustainable features and support model</li></ul>21<br />
  88. 88. Our CurrentSolution<br />Insite<br />Department Sites<br />
  89. 89. What Did We Give Our Users?<br /><ul><li>A solid, foundational, easy to use content management system
  90. 90. Categorized menus
  91. 91. Simplified admin menu
  92. 92. Clean, simple, unified theme
  93. 93. Banner & block customization</li></ul>23<br />
  94. 94. Modules We Used<br /><ul><li>Administration Menu
  95. 95. CKEditor
  96. 96. ACL / Node Access
  97. 97. Role Delegation / User Protect
  98. 98. Vertical Tabs
  99. 99. LDAP + Add LDAP user (custom)
  100. 100. Clean URLs / Path Auto
  101. 101. Calendar / Date API / Calendar Pop-up
  102. 102. Image Cache
  103. 103. Statistics / Google Analytics
  104. 104. Email Logging and Alerts</li></ul>24<br />
  105. 105. Internet Major Accomplishments 2010: <br />Established World-class hosting environment<br />In-house Team development<br />Launched 30+ Sites<br />Migrated 12 Drupal sites from agency to FH<br />$1M in in-sourced development<br />Reduced outsource development from 100% to 20%<br />25<br />
  106. 106. Internet Team<br />Project Management<br />Department Manager<br />Front End Dev<br />(X)HTML, CSS<br />Developers<br />Designer<br />Infrastructure<br />Integration<br />
  107. 107. Intranet Team<br />Department Manager<br />Front End Dev<br />(X)HTML, CSS<br />Developers<br />
  108. 108. Our Server Infrastructure<br />Currently Hosting:<br />135+ Department & Team Sites<br />45+ Externally Facing Marketing Sites<br />
  109. 109. Intranet User Training Plan<br /><ul><li>We faced a wide range of end user skill sets
  110. 110. IT trainers provide classroom training
  111. 111. Required training for everyone
  112. 112. Two classes / roles:
  113. 113. Content Creator
  114. 114. Site Owner
  115. 115. Trainers would field “how to” questions </li></ul>29<br />
  116. 116. Intranet Implementation Timeline<br /><ul><li>Began with Alpha/Beta deployment to key content and dept. owners
  117. 117. Gave us time to tweak our deployment
  118. 118. Allowed users direct access to us
  119. 119. Set user deadline
  120. 120. Only had three departments ask for extensions
  121. 121. Since deployment, trained over 200+ users</li></ul>30<br />
  122. 122. Intranet Intangibles to Success(so far…)<br /><ul><li>MIS Management open to new ideas
  123. 123. Talented resources
  124. 124. Intranet team had PHP / open source experience
  125. 125. FH technical services team provided infrastructure
  126. 126. Alpha & Beta roll-outs
  127. 127. Early adopter perception
  128. 128. Focus groups</li></ul>31<br />
  129. 129. Ongoing User Support & Engagement<br />Internal Drupal Users Site<br />Video refresher training<br />Forums & Blog<br />On-going feedback<br />Lunch and Learns<br />Q&A lab sessions<br />32<br />
  130. 130. Specific examples of how we’ve used Drupal.<br />
  131. 131.
  132. 132.
  133. 133.
  134. 134.
  135. 135.
  136. 136.
  137. 137.
  138. 138.
  139. 139.
  140. 140.
  141. 141.
  142. 142.
  143. 143.
  144. 144.
  145. 145.
  146. 146.
  147. 147.
  148. 148.
  149. 149. Our Challenges (Intranet)<br /><ul><li>Internal
  150. 150. Still no clear organization direction
  151. 151. Policies regarding social content
  152. 152. Demanding end users
  153. 153. Fractured content (too many sites)
  154. 154. With Staffing/Support
  155. 155. Intranet team does other work
  156. 156. With Perception
  157. 157. “I want SharePoint / a Portal”</li></ul>52<br />
  158. 158. Our Feature Roadmap(default site template)<br />Enterprise 2.0<br /><ul><li>Comments
  159. 159. Forums
  160. 160. Blogging (User & Micro)
  161. 161. Taxonomy / Tagging
  162. 162. Subscriptions
  163. 163. Drupal Commons</li></ul>Drupal <br /><ul><li>Continue to empower the users
  164. 164. Web Forms & Workflow
  165. 165. CCK / Views
  166. 166. Provide additional “advanced” training</li></ul>53<br />
  167. 167. Internet Plans for the Future<br />floridahospital.com<br />Drupal Redevelopment<br />my.floridahospital.com<br />Middle Tier Development (jBoss)<br />Integration<br />HIE<br />Ongoing Marketing & Specialty Development<br />54<br />
  168. 168. “Something quippy goes here”<br /><ul><li>Take Initiative
  169. 169. Start with a solid foundation
  170. 170. Develop roadmap to guide you and keep you on track
  171. 171. Pick a technology to build on
  172. 172. Plan for change (management)
  173. 173. Maintain the momentum</li></ul>55<br />
  174. 174. Rick Mann<br />IT Manager, Florida Hospital<br />email: rick.mann@flhosp.org<br />Twitter: rickdotm<br />56<br />

×