Presentation is loading. Please wait.

Presentation is loading. Please wait.

CANOPY – MERCY CASE STUDY Jim MacInnes – Technology Manager APPNOVATION TECHNOLOGIES Affan Waheed – Executive Director Brian Boyer - Manager Mercy.

Similar presentations


Presentation on theme: "CANOPY – MERCY CASE STUDY Jim MacInnes – Technology Manager APPNOVATION TECHNOLOGIES Affan Waheed – Executive Director Brian Boyer - Manager Mercy."— Presentation transcript:

1 CANOPY – MERCY CASE STUDY Jim MacInnes – Technology Manager APPNOVATION TECHNOLOGIES Affan Waheed – Executive Director Brian Boyer - Manager Mercy

2 ABOUT MERCY Sisters of Mercy Health System, which was formed in 1986, transitions in 2011 to one name - Mercy - across four states Hospitals: 31 Outpatient Facilities: nearly 300 Service Area: Arkansas, Kansas, Missouri, Oklahoma Sixth largest Catholic health care system in the U.S. Co-workers: 38,000 Physicians: 5,200 Named 2012 "Most Wired" health care organization by the American Hospital Association - the ninth time since 1999 Named top health care supply chain operation in the world, just second overall to Cardinal Health $60 million data center provides fail-safe protection and power. When an EF5 tornado struck Mercy's Joplin facility in 2011, patient records electronically backed up at offsite data center were immediately available

3 ABOUT APPNOVATION

4 MERCY INTRANETS 31 hospitals and 300 clinics across the midwest (Arkansas, Kansas, Missouri and Oklahoma) Each location developed and maintained their own intranet Each intranet used its own technology and support structure

5 BAGGOT STREET It was determined that a single unified co-worker portal was needed to support a vision of One Mercy and that began the start of Baggot Street as that portal Since then Baggot Street has been launched as the home page for all 38,000 co-workers

6 DOCUMENT REPOSITORY Needed repository to store all documents from the previous intranets into a single repository Types of documents: Policies - enforced policies for a department, hospital, region, etc Forms - filled out by both staff and customers User content - personal folder for users to upload anything they want

7 WORKFLOW Mercy wanted an approval workflow for documents Workflow needed to be started based on type of document and department Allow users to choose who would review, with department head having final approval

8 WEB CONTENT SYSTEM Baggot Street portal would become the one place for all co-workers to go to find people, places and things across all of Mercy’s various data stores (Sharepoint, Wiki, Knowledge base, Document Repository, etc). Drupal was chosen as the CMS

9 DRUPAL PROS & CONS Open Source Easily extensible Strong Developer community Poor document repository functionality Poor workflow functionality + _

10 DOCUMENT REPOSITORY Evaluated Alfresco and Sharepoint Alfresco was chosen: Ease of integration Ability to support the enterprise Ease of use Cost

11 OBJECTIVES FROM MERCY FOR APPNOVATION Understand the Alfresco system architecture requirements to enable integration with Baggot Street, Develop and “stand-up” the Alfresco foundation required for the integration Provide consulting and training to facilitate the Mercy Health team to develop, customize and maintain the integration between Alfresco and Drupal for Baggot Street

12 WHY APPNOVATION & CANOPY Mercy Health originally reached out to Alfresco about using its software as the backend repository for all of their various Drupal web properties It was apparent that Appnovation’s Canopy solution would be a perfect fit

13 ABOUT CANOPY Integrates the highly scalable and popular open source website development tool (Drupal) with a world class open source document repository application (Alfresco) with allowing for the best of both worlds. The Canopy framework is a set of services and APIs used to accelerate the integration of Drupal and Alfresco in an enterprise environment. Canopy combines the flexibility of Drupal as a front end web development platform with the power of Alfresco as an Enterprise content management and workflow system.

14 APPNOVATION & CANOPY Appnovation is the only Afresco partner specializing in Drupal / Alfresco integrations Canopy was named “Solution of the Year” by Alfresco No other partners were presented to Mercy by Alfresco Appnovation was brought on to supplement the Mercy develop team

15 PROJECT MANAGEMENT There were approximately 19 people working on this project. 9 members from Mercy Health: 1 Project Sponsor 5 Developers 1 Business Analyst 2 Quality Assurance Analyst 10 members from Appnovation: 1 Account Manager 1 Project Manager 1 Technical Architect 5 Developers 1 Quality Assurance Analyst 1 Themer

16 PROJECT APPROACH Combination of Waterfall and Agile methodologies. Phase #1:Functional Requirements Discovery Phase #2:Technical Requirements Discovery & Architecture Design Phase #3: Development (Alfresco Intranet Set-up) Phase #4: Training

17 COMMUNICATION Daily status meetings were held with representatives from both teams in attendance. Utilized such tools as WebEx and Skype to allow screen sharing (for more efficient troubleshooting) and to provide real-time support and communication. Appnovation developers provided one-on-one training to mercy developers and extended exceptional support regarding code logic and implementation. AppNovation provided the expertise to architect the environment for Mercy based on the number of users and estimated number of documents and the various integration points

18 ARCHITECTURE

19 INTEGRATION POINTS

20 DRUPAL-ALFRESCO DATA SYNCHRONIZATION INTEGRATION Appnovation developed several custom REST based webscripts for mercy in order to batch certain operations into one call instead of several: These custom REST based webscripts/APIs served as a bridge for synchronizing group nodes, group members, taxonomy terms and department/sub-department nodes between Drupal and Alfresco. Content is then able to synchronize in “real-time” meaning that at the time content is created on Drupal, it will also simultaneously be sent to Alfresco as well. If for any reason the content was not successfully delivered to Alfresco, the content will not be saved in Drupal and the user will be notified.

21 Custom webscripts were also created in Alfresco to handle the manipulation of custom metadata Appnovation also set terms to be synchronized by using Alfresco’s category system and creating a series of scripts to link up to Drupal’s taxonomy through the ScriptAPI in Alfresco. Appnovation team used the ScriptNode API to create the folder hierarchy based on the parent node of the company DRUPAL-ALFRESCO DATA SYNCHRONIZATION INTEGRATION

22 DRUPAL – ALFRESCO – CMIS - APACHESOLR DOCUMENT SEARCH INTEGRATION Mercy Health wanted to be able to have faceted searching on the documents available in Alfresco. The Apachesolr module handles this out of the box. In order for Apache solr to index documents from Alfresco, CMIS API was used to retrieve documents from Alfresco. Once the documents are available in Drupal, they are then saved as an Alfresco Document node and will be indexed by Apachelsolr the next time a cron job is executed.

23 DOCUMENT UPLOAD FROM ALFRESCO TO DRUPAL Mercy Health wanted the ability for users to upload their documents from Drupal to Alfresco. For regular documents, CMIS API was used to upload content while for form documents custom webscripts were developed on top of CMIS API to trigger a workflow in Alfresco. Using CMIS to upload either document type (regular or form) would then trigger custom scripts built by Appnovation to set the metadata of the reviewer and department head.

24 CUSTOM WORKFLOW Mercy Health had a custom requirement that when a document was uploaded, the “uploader” would then be prompted to choose to the person to set as the reviewer and the department head. Any reviewer would then be allowed to specify multiple users to review and approve the document. Once every reviewer had approved the document, it would then move on to finally be reviewed by the department head. Once the document is reviewed by all parties, (finishing with department head), it is then assigned back to the initial reviewer so they could then publish the document manually. At any point the document is rejected the whole process would be returned to the initial reviewer.

25 WORKFLOWS

26 DEMO - SCREENCAST

27 QUESTIONS? Thank You For Your Participation! CANADIAN HEADQUARTERS 152 West Hastings Street Vancouver BC, V6B 1G8 UNITED STATES OFFICE 3414 Peachtree Road, #1600 Atlanta Georgia, 30326-1164 UNITED KINGDOM OFFICE 3000 Hillswood Drive Hillswood Business Park Chertsey KT16 0RS, UK www.appnovation.com info@appnovation.com

28

29

30


Download ppt "CANOPY – MERCY CASE STUDY Jim MacInnes – Technology Manager APPNOVATION TECHNOLOGIES Affan Waheed – Executive Director Brian Boyer - Manager Mercy."

Similar presentations


Ads by Google