The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
•Descargar como PPTX, PDF•
3 recomendaciones•5,622 vistas
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.
![Our Drupal Journey So Far… ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (10)
Destacado
Destacado (20)
Similar a The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
Similar a The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann (20)
Más de Acquia
Más de Acquia (20)
Último
Último (20)
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
- 1. The Drupal Prescription A Case Study of Florida Hospital Presented by:Rick Mann
- 3. Where we are now
- 4. A few lessons learned
- 7. A faith-based, not-for-profit healthcare provider founded in 1908 & located in Central Florida
- 8. 8 Campuses, 2,188 beds, 16,500 employees
- 9. One of the largest hospitals in the country
- 10. Over 1,000,000 patients treated annually
- 11. 18 Urgent Care Centers, Health Plan, Home Health, Ancillary Services3
- 14. Once Upon a Time…Our Problem Last year, our Intranet looked like this:
- 16. Just links; Not dynamic; Ugly
- 19. No centralized content owner
- 20. Gets 12,000 visits a day7
- 22. End of life support with vendor (for current version)
- 23. Proprietary / hard to customize
- 24. Inconsistent UI from site to site
- 25. Training drop-off & orphaned content
- 26. Other misc. technical issues
- 27. Ultimately, we had to do a complete replacement8
- 29. 2 people; not their only support/development duties
- 30. MIS department has a history of self-reliance
- 31. Individual site content owned by the departmental end-users
- 32. Hand full of static FTP sites
- 33. Don’t like our solution? Use Notepad :P9
- 35. Meet the needs of 80% of our users
- 38. Consistent theme
- 39. Easy to administer & add features
- 42. Create a foundation to build on10
- 44. FH Internet Timeline Internet strategy driven by Marketing & PR In 2003 Marketing decided to buy a server and build websites Approached IT, but… Built 10 sites for the key service lines Campuses started to follow 20-25 sites 12 12
- 45. FH Internet Timeline Problem: Proprietary “CMS” Most pages static HTML Vulnerable to XSS $0.05 & $0.10 Increased demand on web FTE 13 13
- 46. FH Internet Timeline August 2007: “Rock-star” physician recruited Web marketing focus Changed interactive agency Drupal 5 Development requests intensified Agency $$ increased 2008: 12 sites ~ $700k in Outsourced Drupal Development 14 14
- 47. What Did 700k Buy Us? 12 Websites 5000 Hours (Approx) Equivalent to 3 person team @ 75% Billable 15
- 48. 16 In-source Strategy Reduce Dependence Maximize Investment Reduce Expense Increase Revenue 16
- 50. Quickr (QP replacement / IBM)
- 51. Sharepoint (.NET / Microsoft)
- 52. Liferay (Java / Open Source)
- 53. Drupal (PHP / Open Source)17
- 55. Pro: Synergy with MIS & Marketing web team
- 56. Shared skill set for development and support
- 58. Con: No pre-existing in-house experience
- 59. Existing team not open-sourced focused
- 60. Learning curve18
- 62. Concurrent testing and learning
- 63. Learned what other questions to ask:
- 64. Single vs Multi-site install?
- 65. How can we limit end-user admin?
- 66. How do I secure it?
- 67. …and others.19
- 69. It’s cheaper
- 70. Existing “out of the box” features/modules
- 71. Enterprise 2.0 features available
- 72. Very strong Community support
- 73. “There’s a module for that”
- 74. Enterprise level support available (Acquia)
- 75. It’s staff-able
- 76. It’s scalable and extendable20
- 78. Who else is using it?
- 79. How does it compare?
- 80. Transition and support plan
- 81. Pitch to our users
- 82. Oooh, shiny!
- 83. Chance to “spring clean”
- 84. Plan for the future
- 85. Formation of Intranet Committee
- 86. IT, Marketing, HR, Internal Communications
- 87. Sustainable features and support model21
- 88. Our CurrentSolution Insite Department Sites
- 92. Clean, simple, unified theme
- 93. Banner & block customization23
- 95. CKEditor
- 96. ACL / Node Access
- 97. Role Delegation / User Protect
- 98. Vertical Tabs
- 99. LDAP + Add LDAP user (custom)
- 100. Clean URLs / Path Auto
- 101. Calendar / Date API / Calendar Pop-up
- 102. Image Cache
- 103. Statistics / Google Analytics
- 104. Email Logging and Alerts24
- 105. Internet Major Accomplishments 2010: Established World-class hosting environment In-house Team development Launched 30+ Sites Migrated 12 Drupal sites from agency to FH $1M in in-sourced development Reduced outsource development from 100% to 20% 25
- 106. Internet Team Project Management Department Manager Front End Dev (X)HTML, CSS Developers Designer Infrastructure Integration
- 107. Intranet Team Department Manager Front End Dev (X)HTML, CSS Developers
- 108. Our Server Infrastructure Currently Hosting: 135+ Department & Team Sites 45+ Externally Facing Marketing Sites
- 110. IT trainers provide classroom training
- 111. Required training for everyone
- 112. Two classes / roles:
- 113. Content Creator
- 114. Site Owner
- 115. Trainers would field “how to” questions 29
- 117. Gave us time to tweak our deployment
- 118. Allowed users direct access to us
- 119. Set user deadline
- 120. Only had three departments ask for extensions
- 121. Since deployment, trained over 200+ users30
- 123. Talented resources
- 124. Intranet team had PHP / open source experience
- 125. FH technical services team provided infrastructure
- 126. Alpha & Beta roll-outs
- 128. Focus groups31
- 129. Ongoing User Support & Engagement Internal Drupal Users Site Video refresher training Forums & Blog On-going feedback Lunch and Learns Q&A lab sessions 32
- 130. Specific examples of how we’ve used Drupal.
- 150. Still no clear organization direction
- 151. Policies regarding social content
- 152. Demanding end users
- 153. Fractured content (too many sites)
- 155. Intranet team does other work
- 156. With Perception
- 157. “I want SharePoint / a Portal”52
- 159. Forums
- 160. Blogging (User & Micro)
- 161. Taxonomy / Tagging
- 162. Subscriptions
- 164. Web Forms & Workflow
- 165. CCK / Views
- 166. Provide additional “advanced” training53
- 167. Internet Plans for the Future floridahospital.com Drupal Redevelopment my.floridahospital.com Middle Tier Development (jBoss) Integration HIE Ongoing Marketing & Specialty Development 54
- 169. Start with a solid foundation
- 170. Develop roadmap to guide you and keep you on track
- 171. Pick a technology to build on
- 172. Plan for change (management)
- 174. Rick Mann IT Manager, Florida Hospital email: rick.mann@flhosp.org Twitter: rickdotm 56
Notas del editor
- A tale of two implementations…
- 4680 hrs (3 x 75%(2080))$140 hr
- Take InitiativeShow how much can be done with a little work Our progress & plans with Drupal is a testament to what you can do with: A little vision; A little experience; “Out-of-the-box” thinkingLike a lot of you, I wondered how/where I was going to begin my journey.Lots of "terms" to worry about, Enterprise 2.0, Intranet 2.0, Web 2.0.Boil it down to specific things you want to accomplish, don't let the technology worry youCreate a catalyst:Allowing the organization to better communicate to their employeesConnect people within the organizationStart small, think big (drupal provides that framework)