Your SlideShare is downloading. ×
0
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

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

7,226

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 …

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
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
7,226
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
49
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 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)
  • Transcript

    • 1. The Drupal Prescription
      A Case Study of Florida Hospital
      Presented by:Rick Mann
    • 2. Our Drupal Journey So Far…
      • Where we’ve come from
      • 3. Where we are now
      • 4. A few lessons learned
      • 5. Where we’re going
      2
    • 6. Who Are We?
      • Who is Florida Hospital?
      • 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 Services
      3
    • 12. We have deployed Drupal as an Enterprise Web Platform…
      • On our Intranet to promote communication and collaboration
      • 13. On the Internet to enhance the Florida Hospital brand and drive revenue
    • Our Intranet Story
    • 14. Once Upon a Time…Our Problem
      Last year, our Intranet looked like this:
    • 15. Intranet Issues
      • The Front Page: “Insite”
      • 16. Just links; Not dynamic; Ugly
      • 17. Never leveraged properly
      • 18. No organizational pride
      • 19. No centralized content owner
      • 20. Gets 12,000 visits a day
      7
    • 21. Intranet Issues, continued…
      • 80+ Department Sites:
      • 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 replacement
      8
    • 28. Distributed Responsibility
      • Small IT staff supports infrastructure
      • 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 :P
      9
    • 34. What Were Our Goals?
      • Replace our dept CMS
      • 35. Meet the needs of 80% of our users
      • 36. Ease the transition
      • 37. Provide additional functionality
      • 38. Consistent theme
      • 39. Easy to administer & add features
      • 40. Strong community support
      • 41. Enterprise support partner
      • 42. Create a foundation to build on
      10
    • 43. Our Internet Story
    • 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
    • 49. What We Considered
      • Insite = custom .NET app
      • 50. Quickr (QP replacement / IBM)
      • 51. Sharepoint (.NET / Microsoft)
      • 52. Liferay (Java / Open Source)
      • 53. Drupal (PHP / Open Source)
      17
    • 54. Why Did We Even Look @ Drupal?
      • Pro: Implementation cost and time
      • 55. Pro: Synergy with MIS & Marketing web team
      • 56. Shared skill set for development and support
      • 57. Shared infrastructure
      • 58. Con: No pre-existing in-house experience
      • 59. Existing team not open-sourced focused
      • 60. Learning curve
      18
    • 61. Drupal Gap Analysis
      • Can Drupal do this? Asked Acquia for help.
      • 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
    • 68. What Sold Us on Drupal?
      • A mature product with a proven track record
      • 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 extendable
      20
    • 77. How Did We Get IT Approved?
      • Pitch to IT management
      • 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 model
      21
    • 88. Our CurrentSolution
      Insite
      Department Sites
    • 89. What Did We Give Our Users?
      • A solid, foundational, easy to use content management system
      • 90. Categorized menus
      • 91. Simplified admin menu
      • 92. Clean, simple, unified theme
      • 93. Banner & block customization
      23
    • 94. Modules We Used
      • Administration Menu
      • 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 Alerts
      24
    • 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
    • 109. Intranet User Training Plan
      • We faced a wide range of end user skill sets
      • 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
    • 116. Intranet Implementation Timeline
      • Began with Alpha/Beta deployment to key content and dept. owners
      • 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+ users
      30
    • 122. Intranet Intangibles to Success(so far…)
      • MIS Management open to new ideas
      • 123. Talented resources
      • 124. Intranet team had PHP / open source experience
      • 125. FH technical services team provided infrastructure
      • 126. Alpha & Beta roll-outs
      • 127. Early adopter perception
      • 128. Focus groups
      31
    • 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.
    • 131.
    • 132.
    • 133.
    • 134.
    • 135.
    • 136.
    • 137.
    • 138.
    • 139.
    • 140.
    • 141.
    • 142.
    • 143.
    • 144.
    • 145.
    • 146.
    • 147.
    • 148.
    • 149. Our Challenges (Intranet)
      • Internal
      • 150. Still no clear organization direction
      • 151. Policies regarding social content
      • 152. Demanding end users
      • 153. Fractured content (too many sites)
      • 154. With Staffing/Support
      • 155. Intranet team does other work
      • 156. With Perception
      • 157. “I want SharePoint / a Portal”
      52
    • 158. Our Feature Roadmap(default site template)
      Enterprise 2.0
      Drupal
      • Continue to empower the users
      • 164. Web Forms & Workflow
      • 165. CCK / Views
      • 166. Provide additional “advanced” training
      53
    • 167. Internet Plans for the Future
      floridahospital.com
      Drupal Redevelopment
      my.floridahospital.com
      Middle Tier Development (jBoss)
      Integration
      HIE
      Ongoing Marketing & Specialty Development
      54
    • 168. “Something quippy goes here”
      • Take Initiative
      • 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)
      • 173. Maintain the momentum
      55
    • 174. Rick Mann
      IT Manager, Florida Hospital
      email: rick.mann@flhosp.org
      Twitter: rickdotm
      56

    ×