| Major Hospital (Western US), Web Content Management Tool |
| Client |
Major Hospital (Western USA) |
 |
| Project |
Web Content Management Tool |
Executive Summary:
Since its inception in early 20th century, this hospital has evolved to become one that is internationally renowned for the best patient care modern medicine has to offer. It is committed to providing superior outpatient, acute, sub-acute and home patient care, breakthrough biomedical research, graduate and undergraduate medical education, and community service.
The hospital cares for some 150,000 patients per year, and over 1,000 primary care physicians and specialists attend to these patients, supported by a support staff of many thousands more. Many patients are eligible to receive the newest treatments by participating in Cedars-Sinai's active clinical research program. More than 300 principal investigators and 500 employees are involved in this research, resulting in over 300 papers appearing in peer-reviewed medical journals each year.
All of these world-class services are provided at a multi-building campus, where over 10,000 users access over 500 different information technology applications running on many different platforms. This has created a complex web of inter-related systems that users have to navigate as part of doing their jobs. Perot Systems has a facilities management contract for managing the IT resources. The hospital also has an extensive Enterprise Information Systems (EIS) group that supports and develops the IT applications. Consulting assignments are handed out by the EIS department.
The hospital has been a client of Aviana since 2000. |
|
| One of the significant projects Aviana has implemented at the hospital is: |
| Business Issues |
| The hospital maintains large and complex website(s) to provide relevant information to both internal users as well as the external public. EIS management wanted to provide the non-technical business units and subject-matter experts the ability to add, delete and update the content on the corporate web site(s), without having to learn HTML, database programming or any programming language. This would allow the users to publish the best possible information in a timely manner without having to depend on the EIS department to maintain the website content. |
|
| Solution |
| Aviana developed a Website Content Management Tool for the EIS Department, that can be used by the (non-technical) business users. This gave them the ability to very easily upload and maintain data on the web site from an easy-to-use interface. This tool was such a success that the hospital later expanded its use to support other specialized functional areas. |
|
Architectural Overview of Custom Web Content Management Tool |
| |
| Features of The Web Content Management Tool |
| The Web Content Management (WCM) application designed by Aviana includes the following component modules: |
Users & Access Privileges |
 |
User Management: The WCM Tool has the ability to add, change or delete users. Users have User Ids, Names, Passwords, Email Addresses and Group Assignments |
|
Group Assignments: Users may be assigned to one of two groups (User/Admin). |
|
Role-Based Access Privileges: The WCM Tool provides role-based security and access privileges: |
| |
 |
User Role: "User" level users are able to access the WCM Tool, add or edit content, but not move any new or edited content to the production website |
|
Admin Role: "Admin" level users are able to access the WCM Tool, add or edit content, review work (new edited content) completed by users, as well as move approved pages to production |
|
|
|
| WCM Tool Navigation/Environments |
|
WCM Menu: Users are able to navigate within the WCM Tool environment by using a menu. The menu are displayed upon successful logon to the WCM Tool |
|
Data Environments: The WCM Tool will support three data environments: (1) an internal SQL Server database that will store all template data and web page data developed using the WCM Tool templates; (2) the staging area - where pages are generated from the web page generation engine; and (3) the production environment. |
|
| Web Page Templates (Programmer Maintained) |
| One template page (and associated code in the code generator) is needed for each Page Type supported by the website. The WCM tool supports approximately 30 such templates. |
|
Page Deletion: If a page is deleted, that is part of the top menu or side menu, the appropriate menu are updated |
|
Web Page Content Editing: Users have the ability to edit a selected page, and to save the modified file for later review by supervisor (Admin level user) |
|
Page Preview: Users have the ability to preview the current page (being edited) |
|
|
| Menu Editor |
|
Top Menu: An editor is provided for editing the top menu and any associated drop-down menus associated with the top-level choices |
|
Side Menu: An editor is provided for the side menu and any associated drop-down menus associated with the top-level choices. |
|
| Page Generation Engine |
|
Specific Page Publication: A page generation engine is provided to move one page to the staging or production area from the WCM tool environment |
|
Batch Publication of All Pages: Users have the ability to schedule a task to generate all pages afresh into the staging area from the tool |
|
Page Migration to Production: Users have the ability to schedule a task to move all pages from the staging area to the production area. |
|
| Basic Workflow Management |
|
Pending-Approval Queue: Any page saved to the WCM Tool by any user is flagged for approval and added to a "queue" of other such pages |
|
Page Review and Approval: "Admin" level users are able to access the workflow management area and review the list of pages that are pending review/approval; generate the page into the staging area after review (remove from queue); promote that page directly to production (a copy will be kept in the staging area also) |
|
Page Approval and Publication: From the review page, the admin user is able to send an email to the regular user (author of the page), if the page cannot be approved. This provides a feedback mechanism from the approver to the content creator. |
|
| Technical Environment: Front-end: MS Visual Studio (ASP, Visual Basic, VC++), HTML, XML; Back-end: Oracle 8i, SQL Loader, PL/SQL, XML. |
|
|
|
