Clinical Informatics and Data Management Unit by 2Um1O0QL

VIEWS: 10 PAGES: 6

									  CLINICAL INFORMATICS AND DATA MANAGEMENT UNIT
DEPARTMENT OF EPIDEMIOLOGY AND PREVENTIVE MEDICINE
                MONASH UNIVERSITY




{ENTER PROJECT
     NAME}


            PROJECT BRIEF TEMPLATE
1.        DOCUMENT INFORMATION

 Project Name:
 Prepared By:                                                             Document Version No:         2
 Title:                                                                   Document Version Date:       15/09/2011
 Reviewed By:            Christopher Reid                                 Review Date:


1.1        DOCUMENT VERSION HISTORY
Version       Version
Number        Date        Revised By        Description                                         Filename
1             1/6/2011                      Document Created




1.2        APPROVALS
           This document requires the following approvals. Signed approval forms should be filed
           appropriately in the project filing system
Name                               Title                                                 Date          Version
                                   Principal Investigator

                                   Senior Project Officer

Christopher Reid                   Head, CIDMU

                                   Monash Departmental Head (where relevant)




1.3        DISTRIBUTION LIST
Name                               Title                                                                    Date of Issue




CIDMU_Project Brief TemplateV3                        Page 1 of 6                                 6/28/2012 10:10 PM
2.         TABLE OF CONTENTS


1.       DOCUMENT INFORMATION ..................................................................................................................... 1

     1.1        DOCUMENT VERSION HISTORY ....................................................................................................................... 1
     1.2        APPROVALS ................................................................................................................................................ 1
     1.3        DISTRIBUTION LIST ....................................................................................................................................... 1

2.       TABLE OF CONTENTS ............................................................................................................................... 2

3.       PROJECT DEFINITION ............................................................................................................................... 3

     3.1    BACKGROUND ............................................................................................................................................. 3
     3.2    PROJECT OBJECTIVES .................................................................................................................................... 3
       3.2.1     Risk .................................................................................................................................................. 3
       3.2.2     Benefits ........................................................................................................................................... 3
     3.3    INTERESTED PARTIES .................................................................................................................................... 3
     3.4    INTERFACES ................................................................................................................................................ 4

4.       PROJECT MANAGEMENT TEAM STRUCTURE ............................................................................................ 4

5.       ROLE DESCRIPTIONS ................................................................................................................................ 4

     5.1        EXECUTIVE.................................................................................................................................................. 4
     5.2        SENIOR SUPPLIER ......................................................................................................................................... 4
     5.3        SENIOR USER .............................................................................................................................................. 4
     5.4        PROJECT MANAGER ..................................................................................................................................... 4

6.       REFERENCES ............................................................................................................................................ 4

7.       TECHNICAL SOLUTION .......................................................................ERROR! BOOKMARK NOT DEFINED.5

     7.1        DELIVERY OBJECTIVES (SCOPE) ...................................................................... ERROR! BOOKMARK NOT DEFINED.5
     7.2        ASSUMPTIONS ............................................................................................ ERROR! BOOKMARK NOT DEFINED.5
     7.3        EXCLUSIONS ............................................................................................... ERROR! BOOKMARK NOT DEFINED.5
     7.4        ESTIMATED TIME TO COMPLETE...................................................................... ERROR! BOOKMARK NOT DEFINED.5

8.       ROLES AND RESPONSIBILITIES ................................................................................................................. 5




CIDMU_Project Brief TemplateV3                                                 Page 2 of 6                                                       6/28/2012 10:10 PM
3.      PROJECT DEFINITION
3.1      BACKGROUND
         CLIENT to COMPLETE - Please provide a short description of the project)



3.2      PROJECT OBJECTIVES
         CLIENT TO COMPLETE – What do you want the system to do?
         EG: To develop a web based data capture and reporting systems that enables:
         a) Collection of data from XXX sites?
         b) Collection of data for XXX participants
         c) Collection of data for XX visits per participant
         d) Collection of data for XXX duration
         e) Collection of data on XX forms (e.g. baseline, follow up adverse event). Are any of the
            forms repetitive (e.g. daily)?
         f) Is the proposed database entirely a new system or is it a web version of an existing
            system?
         g) If an existing system is available, how different is the proposed system from the existing
            system?
         h) Do we need to merge the data from old system? If yes, should this be done periodically or
            once for all?
         i) How much data do you intend to collect using the proposed database (number of records
            and number of elements)?
         j) Are there any reporting requirements? E.g. management reports and clinical reports
         k) Any other special requirements?
         l) Proposed project time lines i.e. when do you want the system to be available by?



3.2.1       RISK
     CLIENT TO COMPLETE - (Identify risks associated with development, delay, stakeholders etc.)



3.2.2       BENEFITS
            CLIENT TO COMPLETE – What are the benefits you are expecting from this system – data
            capture, reporting etc.?
            EG: The following benefits are expected from implementation of the system:
             Data capture from multiple sites
             On-line error checking
             Central reporting



3.3      INTERESTED PARTIES
     CLIENT TO COMPLETE – Who else is involved in this that may want to have a say – other
     stakeholders?




CIDMU_Project Brief TemplateV3                   Page 3 of 6                             6/28/2012 10:10 PM
3.4      INTERFACES
     CLIENT TO COMPLETE - Are there any data feeds or interfaces with other systems that are
     required?



4.     PROJECT MANAGEMENT TEAM STRUCTURE


     CLIENT to COMPLETE - Please nominate as identified in chart

                                               Executive:
                                           Chris Reid + Client
                                            Stakeholders (2)

                                 Senior Supplier:            Senior User:
                                 TBA - CIDMU to              TBA - (CLIENT
                                   complete)                  Nominee)

                                 Project Manager:
                                 TBA - (CIDMU to
                                   complete)




5.     ROLE DESCRIPTIONS
5.1      EXECUTIVE
         (CLIENT TO COMPLETE - Name the key stakeholders that should be able to sign off on the
         requirements)

5.2      SENIOR SUPPLIER
         (CIDMU to complete - This will be a CIDMU Systems Development or Senior Project
         Manager)



5.3      SENIOR USER
         (CLIENT to complete - This will be the Study Project Officer that will be heavily involved in the
         requirements specifications and user testing)



5.4      PROJECT MANAGER
       (CIDMU to complete - This will be the lead software development officer for the project)



6.     REFERENCES
     CLIENT TO SUPPLY             -   Data Dictionary
                                  -   Project Protocol
                                  -   Any other relevant documentation



CIDMU_Project Brief TemplateV3                      Page 4 of 6                          6/28/2012 10:10 PM
7.       ROLES AND RESPONSIBILITIES


        Corporate/       Provide details of the corporate or programme quality management system
       Programme
       Management        Provide quality assurance

                         Approve the Project Product Description
                         Approve the Quality Management Strategy
        Executive
                         Confirm acceptance of the projects product
                         Provide the customer's quality expectations and acceptance criteria
                         Approve the Project Product Description
                         Approve the Quality Management Strategy
        Senior User      Approve Product Descriptions for key user products
                         Provide resources to undertake user quality activities and product approval
                         Provide acceptance of the project product
                         Approve the Project Product Description
                         Approve the Quality Management Strategy

      Senior Supplier    Approve the quality methods, techniques and tools adopted in product development
                         Provide resources to undertake supplier quality activities
                         Approve Product Descriptions for key specialist products
                         Document customers quality expectations and acceptance criteria
                         Prepare the Project Product Description (with users)

     Project Manager     Prepare the Quality Management Strategy
                         Prepare and maintain the Product Descriptions
                         Ensure Team Managers implement the quality control measures agreed in Product
                                 Descriptions and Work Packages
                         Produce products consistent with Product Descriptions
                         Manage quality controls for the products concerned
      Team Manager
                         Assemble quality records
                         Advise the Project Manager of product quality status
                         Advise the Project Manager on the Quality Management Strategy
                         Assist the Project Board and Project Manager by reviewing Product Descriptions
     Project Assurance
                         Advise the Project Manager on suitable quality reviewers/approvers
                         Assure the Project Board members on the implementation of the Quality Management
                                Strategy i.e. the proper conduct of the project management and quality procedures
                         Provide administrative support for quality controls

      Project Support    Maintain the Quality Register and quality records
                         Assist Team Managers and members with the application of the projects quality processes




CIDMU_Project Brief TemplateV3                        Page 5 of 6                                      6/28/2012 10:10 PM

								
To top