The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
56
The Drupal Prescription A Case Study of Florida Hospital Presented by: Rick Mann
-
Upload
acquia -
Category
Technology
-
view
7.201 -
download
1
description
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.
Transcript of The Drupal Prescription - A Case Study of Florida Hospital - Rick Mann
The Drupal PrescriptionA Case Study of Florida Hospital
Presented by: Rick Mann
Our Drupal Journey So Far…
Where we’ve come from Where we are now A few lessons learned Where we’re going
2
Who Are We?
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 Services3
We have deployed Drupal as an Enterprise Web Platform…
• On our Intranet to promote communication and collaboration• On the Internet to enhance the
Florida Hospital brand and drive revenue
Our Intranet Story
Once Upon a Time…Our Problem
Last year, our Intranet looked like this:
Intranet Issues
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
7
Intranet Issues, continued…
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
8
Distributed Responsibility 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
9
What Were Our Goals? 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
10
Our Internet Story
12
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
13
FH Internet Timeline
• Problem: Proprietary “CMS”– Most pages static HTML – Vulnerable to XSS– $0.05 & $0.10– Increased demand on web FTE
13
14
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
What Did 700k Buy Us?
• 12 Websites• 5000 Hours (Approx)• Equivalent to 3 person team @ 75% Billable
15
16
In-source Strategy
• Reduce Dependence• Maximize Investment– Reduce Expense– Increase Revenue
16
What We Considered Insite = custom .NET app Quickr (QP replacement / IBM) Sharepoint (.NET / Microsoft) Liferay (Java / Open Source) Drupal (PHP / Open Source)
17
Why Did We Even Look @ Drupal?
Pro: Implementation cost and time Pro: Synergy with MIS & Marketing web
team Shared skill set for development and support Shared infrastructure
Con: No pre-existing in-house experience Existing team not open-sourced focused Learning curve
18
Drupal Gap Analysis
Can Drupal do this? Asked Acquia for help. Concurrent testing and learning Learned what other questions to ask:
Single vs Multi-site install? How can we limit end-user admin? How do I secure it? …and others.
19
What Sold Us on Drupal?
A mature product with a proven track record It’s cheaper Existing “out of the box” features/modules Enterprise 2.0 features available Very strong Community support
“There’s a module for that” Enterprise level support available (Acquia) It’s staff-able It’s scalable and extendable
20
How Did We Get IT Approved? Pitch to IT management
Who else is using it? How does it compare? Transition and support plan
Pitch to our users Oooh, shiny! Chance to “spring clean”
Plan for the future Formation of Intranet Committee
IT, Marketing, HR, Internal Communications
Sustainable features and support model
21
Our Current SolutionInsite Department Sites
What Did We Give Our Users?
A solid, foundational, easy to use content management system
Categorized menus Simplified admin menu Clean, simple, unified theme Banner & block customization
23
Modules We Used Administration Menu CKEditor ACL / Node Access Role Delegation / User
Protect Vertical Tabs LDAP + Add LDAP user
(custom)
Clean URLs / Path Auto Calendar / Date API /
Calendar Pop-up Image Cache Statistics / Google Analytics Email Logging and Alerts
24
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
Internet Team
DesignerDesigner
Project Management
Project Management
IntegrationIntegration InfrastructureInfrastructure
Department ManagerDepartment Manager
DevelopersDevelopersFront End Dev(X)HTML, CSSFront End Dev(X)HTML, CSS
Intranet Team
Department ManagerDepartment Manager
DevelopersDevelopersFront End Dev(X)HTML, CSSFront End Dev(X)HTML, CSS
Our Server Infrastructure
Currently Hosting:
135+ Department & Team Sites
45+ Externally Facing Marketing Sites
Intranet User Training Plan
We faced a wide range of end user skill sets
IT trainers provide classroom training Required training for everyone Two classes / roles:
Content Creator Site Owner
Trainers would field “how to” questions
29
Intranet Implementation Timeline
Began with Alpha/Beta deployment to key content and dept. owners Gave us time to tweak our deployment Allowed users direct access to us
Set user deadline Only had three departments ask for
extensions Since deployment, trained over 200+
users
30
Intranet Intangibles to Success(so far…)
MIS Management open to new ideas Talented resources
Intranet team had PHP / open source experience FH technical services team provided infrastructure
Alpha & Beta roll-outs Early adopter perception Focus groups
31
Ongoing User Support & Engagement
• Internal Drupal Users Site– Video refresher training
– Forums & Blog
– On-going feedback
• Lunch and Learns• Q&A lab sessions
32
Specific examples of how we’ve used Drupal.
Our Challenges (Intranet) Internal
Still no clear organization direction Policies regarding social content Demanding end users Fractured content (too many sites)
With Staffing/Support Intranet team does other work
With Perception “I want SharePoint / a Portal”
52
Our Feature Roadmap(default site template)
Enterprise 2.0
Comments Forums Blogging (User & Micro) Taxonomy / Tagging Subscriptions Drupal Commons
53
Drupal
Continue to empower the users
Web Forms & Workflow CCK / Views Provide additional
“advanced” training
Internet Plans for the Future
• floridahospital.com– Drupal Redevelopment
• my.floridahospital.com– Middle Tier Development (jBoss)– Integration– HIE
• Ongoing Marketing & Specialty Development
54
55
“Something quippy goes here”
Take Initiative Start with a solid foundation Develop roadmap to guide you and keep you on track Pick a technology to build on Plan for change (management) Maintain the momentum
