The role of the project manager is to drive progress on a GIP development project or projects. This includes development of project-specific work plans, task outlines and work descriptions, acquiring resources and assiging work, and tracking / follow-up on tasks and deliverables. The project manager focuses on deliverable timeliness, and on complying with LSIT design and build guidelines.

As the development activities associated with GIP become more varied and multiple projects get underway, it may be necessary to add a Project Admnistrator. This individual would be responsible for: maintaining volunteer information, intake and pre-screening of volunteers, creation/updating of MS Project plans, development and production of project management reports, identifying and following up on project variances and production issues, and mangement of project libraries, documents, work papers and work products.

1.1) IT Organization
1.2) Job Desc./Roles/Resp.
1.3) Compliance
1.4) Regulatory Compliance
1.5) Quality
1.6) Internal Quality Audit
1.7) Software Lifecycle Management

2.1) Configuration and Change Management
2.2) Requirements Management
2.3) Service Delivery
2.4) Help Desk
2.5) Contracting
2.6) Network Provisioning
2.7) Service Level Management
2.8) Documentation and Document Control
2.9) Training Development and Delivery
2.10) Backup
2.11) Disaster Recovery

3.1) General Strategy and Budgeting
3.2) Network and Infrastructure Strategy
3.3) Business Applications Architecture and Strategy
3.4) Database Architecture and Data Management Strategies
3.5) Middleware or Data Interchange Strategies
3.6) Electronic Commerce Strategies
3.7) Integration Strategies

4.1) Desktop Computing Management
4.2) Server Complex Management
4.3) Network Management
4.4) Telecommunications Management (wired and wireless)
4.5) Glass House (Mainframe) Computing
4.6) Wide Area Network (WAN) Management
4.7) Physical Data Storage
4.8) Power
4.9) Environmental / Structure
4.10) Infrastructure Acquisition
4.11) Infrastructure Disposal

5.1) Application / Package Planning
5.2) Application / Package Development
5.3)Application / Package Testing
5.4)Application / Package Deployment
5.5)Application / Package Maintenance
5.6)Application / Package Decommissioning
5.7)Package Selection
5.8)Package Implementation
5.9)Application / Package Integration

6.1) Data Management
6.2) Metadata Management
6.3) Standards Integration
6.4) Data Retention and Archiving
6.5) Data Interchange

7.1) Application Testing
7.2) Database Testing
7.3) Security Testing
7.4) Integration Testing
7.5) Integrated Risk Management
7.6) Root Cause Analysis
7.7) Resolution Management

8.1) Data Security
8.2) Access Controls
8.3) Network Intrusion Detection
8.4) Alerting
8.5) Lockdown Controls
8.6) Biometrics
8.7) Safety Planning

9.1) Measurement and Analysis
9.2) Integration of Practices
9.3) Resolution Techniques
9.4) Adopting and Implementing Standards

10.1) Scoping Projects
10.2) Staffing Projects
10.3) Developing Project Plans
10.4) Managing Project Teams
10.5) Vendor Management
10.6) Monitoring and Controlling Projects
10.7) Reporting on and Closing Projects

11.1) Labeling
11.2) Clinical Study Applications
11.3) Patient Data Management
11.4) Market Aproval Applications
11.5) Sales Communications
11.6) Marketing Communications
11.7) Product Problem Management
11.8) Recall Management

12.1) Automated Laboratory Equipment
12.2) Automated Manufacturing Equipment
12.3) Automated Distribution Systems

The GIP Series will need individuals to serve in editorial capacities. Often, Subject Matter Experts and Contributors are so familiar with their subject that they may leave out information that is germane to the implementation of a practice, or assume greater familiarity with specific issues or techniques than is actually the case with the audience. Each practice document will have an editor, and there will be an editorial board on which editors will serve. This board will serve to insure that there is consistency in enforcement of documentation standards, and that workproducts and practice documements have been appropriately reviewd and approved for publication.

When practice documentation is particularly technical or the subject matter of a GIP publication is particularly dependent on the implementation of one or more specific technologies, the series Editor may choose to assign a Technical Editor to the project. The Technical Editor serves several functions: to insure that the technical content of a practice document is accurate and clearly represented, that explication of and instruction in a technology is appropriately written for the target audience, and also that technical information is presented in a way that is neutral with regard to vendors of specific technology solutions. This role will be particularly important to practices that are heavily reliant on vendor or consultant input.

Often, Subject Matter Experts and other contributors will have great knowledge and expertise in Good Informatics Practices but may not be able to clearly translate that knowledge into practices that can be implemented in other organizations. The TEchnical Writer assists the GIP working groups and SMEs in translating their practice knowledge into implementable practices. The technical writer will follow published LSIT style guides and insure that practice and technique documentation conforms to guidelines and is easy to understand and interpret.

The Proofreader assists the series Editor and the Working Group to insure that changes are correctly made and reflected in workproducts, and that appropriate version controls are implemented. To this end, the proofreader serves as more than simply a reader of the document or a grammarian - the proofreader will need to have some knowledge of the subject, the ability to understand the meaning of the information communicated, and be able to manage practice documents through the revision cycle.