1. VUMC Content Manager March 29, 2005

2. Last Week Unable to get dummy data from Eric till tomorrow (Wednesday March 30 th ) We focused on moving ahead Detailed Outline of Final Paper Sectioned of Paper to begin composition Rough drafts done by the end of the week Spent some time with the website Yes we know it is bad Adding more content

3. Eric Lin’s Schedule March 30th - - Create a blank database of student tables - Place in accessible server - Obtain dummy data, x4, for use April 4th - - Follow-up to discuss any needs and conserns April 8th - - Follow-up to discuss any needs and conserns April 15th - - Possible preview of project April 26th - - Project Day

4. Paper at 10,000 ft I. Project Overview II. Project Proposal III. Research IV. Solution Requirements V. Vendor Surveys VI. Solution Recommendation

5. For Starters Project Overview Project Proposal Sponsor Info Nature of Problem Sponsor’s Thoughts on Solution

6. Research Sponsor Interview Individual Coordinator Interviews Thoracic Coordinator Anesthesiology Coordinator Neurology Coordinator Urology Coordinator Aiding in Coordinator Duties Data Item Categories Workflow Creation  Resident Applications  Resident Evaluations  Duty Hours  Conference Scheduling Meetings with GME Office/Information Technology Group Integration Requirements of Solution  Open Architecture System  VUMC must own hardware  VUMC must own data

7. Solution Requirements Ability to Capture Multiple Forms of Data Workflow Document Revision Control Automatic Routing of Documents Notifications Exception Reporting Open Architecture System Security Ability to Attach Meta Data to each object Index/Search Capabilities Vast Database Storage Administration

8. Vendor Surveys Existing Software tailored towards Resident Management Akcia’s GME Management System  Features  Issues New Innovations  Features  Issues

9. Vendor Survey Continued… Content Management Solution DCS  Stellent middleware products  Software Features  Library Services  Index/Search and personalization  Security  Conversion  Workflow Automation  Administration Revision Control  Hardware Architecture  SQL database manager (Customer Owned)  Metadata Content Server  Workflow Server  Web-based GUI  DCS Services Available  Document Scanning  Forms Design & Capture  Custom Programming

10. End and Questions Finally Solution Recommendation Technical Issues How long should paper be, already some lengthy issues? Examples of previous papers?