• No results found

Document Management Solution (EDMS)

N/A
N/A
Protected

Academic year: 2021

Share "Document Management Solution (EDMS)"

Copied!
27
0
0

Loading.... (view fulltext now)

Full text

(1)

Implementing TrackWise with an Electronic

Implementing TrackWise with an Electronic 

Document Management Solution (EDMS)

Alex Kotikovsky

Product Manager

Sparta Systems

p

y

Gilad Kigel

Manager, Solutions Consulting

g ,

g

Sparta Systems

(2)

Agenda

Document Management Overview

Agenda

Document Management Overview

Document Management within TrackWise

Benefits of an Integrated Solution

Benefits of an Integrated Solution

Best Practices

Demo of TrackWise Document Management

Demo of TrackWise Document Management

Q&A

(3)

Compare/Contrast Document Management 

and EQMS

(4)

EQMS Vision

EQMS Vision

Deviations & Audit Complaint Lab Issues Deviations &  Incidents Audit Management Supplier Quality  Complaint Handling Adverse Event  Management Investigations Investigations Risk Evaluation Risk Evaluation Reporting Product Registration  Tracking Training  Management Root Cause Analysis Root Cause Analysis CAPA CAPA Commitments Commitments Correspondence Correspondence Change Control Batch / IT / Process / Document  Material / Equipment Change Control Batch / IT / Process / Document  Material / Equipment Effectivity Analysis Effectivity Analysis

(5)

Typical Document Management 

Strategies

Many of our customers have existing document management systems 

i

l

th t th

t T

kWi

t li k t

Strategies

in place that they want TrackWise to link to:

Other companies that don’t already have EDMS may want to leverage 

their EQMS investment to support both.   This presentation will focus 

primarily on helping these companies understand how TrackWise can 

support document management needs

(6)

Intro to Document Management

What is it: fundamentally, the ability to control documentation 

d d

b

l

Intro to Document Management

and distribute to appropriate employees

Key features?: revision control and check in/check out 

functionality

Some companies distinguish between types of documents

Controlled – SOPs, Policies, Forms, Work Instructions

thi

th t

i

h

t l

l t b

l

d

− things that require change control approval to be released

Standard or Project documents – meeting minutes, validation 

reports, testing summaries, project plans

Do not require change control approval to be released even though some

− Do not require change control approval to be released, even though some 

may support change control (e.g., a validation plan may be electronically 

approved for CAPA or Change Control but doesn’t require the same 

approval steps as an SOP update)

For the purposes of this presentation we will focus on Controlled documents, or those that 

require Change Control approval to be released

(7)

Document Management vs. EQMS

Document Management vs. EQMS

Document Management

EQMS

Key feature

Revision control

Workflow management

Key searching capability

Display all SOPs needed to 

perform job

Ability to identify trends in 

database

Key value proposition

Ensure products are made 

per specification and 

company operates under 

l

Enables closed‐loop 

processes

control

Historical tools before 

electronic systems

Shared network drive, 

paper printouts

Paper with excel tracking

Key risks to process

1. Using outdated 

procedures

2. Not knowing procedure 

exists

1. Not completing things 

in a timely manner

2. Incomplete

documentation

exists

3. Not following 

procedure

documentation

3. Bypassing process/ late 

documentation

(8)

EQMS

EQMS

Nonconformity

CAPA

(9)

Document Management vs. EQMS

1.0 Retired

1.0 Effective

1.0 in progress

Document Management vs. EQMS

Approve

WIP

New 

SOP

2.0 Retired

2.0 Effective

2.0 in progress

Approve

WIP

Revise 

SOP

3.0 Retired

3.0 Effective

3.0 in progress

Approve

WIP

Revise 

SOP

4.0 Effective

4.0 in progress

Approve

WIP

Revise 

SOP

Discussion point: should documents become effective as soon as they are approved?

(10)

High‐level Change Process

Change request vs. change

High level Change Process

Change request vs. change 

management

− Why is the change happening?

Request

− Who does it impact?

− What actions are required?  

Regulatory implications?

Assessment

Change 

M

t

Change 

Request

Regulatory implications?

− What approvals are required?

− Real‐time status? 

Pre‐approval

Execution

Management

Post‐approval

(11)

Enterprise Change Control:

Desired State

Hierarchical relationship of one change 

d i

i

d

i i i

Desired State

Electronic  attachment

request and its associated activities

Electronic attachment and organization 

of supporting documentation

Change Request

attachment

Logical association of supporting 

information directly to change request

Automated, consistent, and efficient 

h

t l

Impact Assessment Clear i k

change control process

Clear visibility to all levels of the 

organization through centralization of 

information and dashboards

Regulatory  Assessment Linkage

information and dashboards

Accommodation of both proactive and 

reactive change activity

Implementation  Activities

(12)

TrackWise Document Management 

Options

TrackWise file attachments: 

Options

ac

se

e attac

e ts

Leveraging repository to securely store and associate 

documents to TrackWise records.  

Document Management Connector:

Integrate with existing content solutions (ex: Documentum,   

SharePoint, LiveLink)

Integrated EQMS and Document Management:  

A single, integrated solution to relate content management 

processes directly to EQMS (CAPA, Change Control, 

Regulatory Correspondence Auditing Training etc )

Regulatory Correspondence, Auditing, Training, etc..)  

(13)

TrackWise Document Management 

Key Features

Workflow 

Key Features 

Automation

Check‐in and Check‐out

Version Control

Access Control

E

l ti

Escalations

Notifications

Auto Embedding of Metadata

Auto‐Embedding of Metadata

Search and Query

(14)

Benefits of an Integrated Solution

Benefits of an Integrated Solution

(15)

Typical Quality Process

Data received and monitored by EQMS 

Typical Quality Process

y Q

Deviation or anomaly detected

Analysis preformed as directed

y

p

Interpret, document, and discuss results

Modify processes and documentation as appropriate

y p

pp p

Publish and audit system changes

Cause 

Cause and 

and 

correction 

correction 

analysis 

analysis 

performed 

performed 

Publish and 

Publish and 

archive

archive

Quality 

Quality 

information 

information 

tracked and 

tracked and 

monitored

monitored

Deviation 

Deviation 

logged into 

logged into 

system

system

Ad hoc 

Ad hoc 

review and 

review and 

discussion of 

discussion of 

results

results

(16)

TrackWise Document Management 

and EQMS

and EQMS

Lab Issues Deviations &  Audit Complaint Lab Issues Incidents Management Supplier Quality  Management Investigations Investigations Handling Adverse Event  Reporting Investigations Investigations Risk Evaluation Risk Evaluation Root Cause Analysis Root Cause Analysis Document Control Training 

Management CAPACAPA

Change Control Batch / IT / Process / Document  Change Control Batch / IT / Process / Document  Effectivity Analysis Effectivity Analysis Material / Equipment Material / Equipment

(17)

Benefits of Integrated TrackWise 

EQMS & EDMS

Ensure compliance through document control

EQMS & EDMS

Ensure compliance through document control 

Seamless integration

Reduced training cost

Reduced training cost

Improved system performance 

(18)

Case Study:

NVI (Netherlands Vaccines Institute)

Business Challenge

NVI (Netherlands Vaccines Institute)

Its previous system for managing records – a combination of Microsoft 

Excel, Microsoft Access and old‐fashioned, paper‐based methods – had 

become insufficient for managing documentation and readying reports for 

submission to the EU. 

NVI decided to seek out a centralized electronic system for document 

management that would not only ensure efficient and effective compliance 

g

y

p

with reporting standards, but also seamlessly integrate with its current 

systems 

Why TrackWise

• Compliant with European Standards, easy to generate submission 

reports

E

i t

ti

ith th

t

i i

l

fi

ti

Why TrackWise

• Compliant with European Standards, easy to generate submission 

reports

E

i t

ti

ith th

t

i i

l

fi

ti

• Easy integration with other systems, minimal configuration

• Ease of use, intuitive GUI

• Easy integration with other systems, minimal configuration

• Ease of use, intuitive GUI

(19)

Results

NVI Implementation

Results:

NVI Implementation

NVI was able to create a centralized repository for 

all its critical documents, immediately migrating more than 

20,000 documents into its new system, and eventually doubling 

,

y

,

y

g

that number to 40,000 over the next two years. 

− Leveraging and Expanding TrackWise Investment  beyond Document 

Management:

g

− Addition of 13 workflows within it its quality assurance department, 

including: 

Deviations

Corrective and Preventive Actions (CAPA)

Change Control

Internal and External Audits

(20)

Best Practices

Best Practices

(21)

Best Practices

All linked processes in a single system

Best Practices 

All linked processes in a single system

Notifications on Sunset Dates, Updated Content, etc

Dashboards of document state and status

Dashboards of document state and status

Document Templates for consistency and repeatability

Use the EDMS Connector to leverage an existing 

investment

(22)

Documents in a Corporate Hierarchy

Documents in a Corporate Hierarchy

• SOP

k

i

• Work Instructions

• Policies

• Batch Records

• Regulatory 

g

y

Submissions

• Correspondences

• CAPA Evidence

• Validation Docs

• Validation Docs

• Manuals

• Instructions

• Investigation 

Reports

• Audit Reports

• Product 

Registrations

Registrations

• Plus more

(23)

How Do Companies Manage The 

Complexity?

(24)

Define, Track, Manage and Report 

Across Your Organization

Across Your Organization

Complaint

Manufacturing  site conducts an investigation  to determine 

Investigation

Complaint Entry

Initial Assessment and 

Data Collection

Send notification to 

Customer called 

about missing 

instr ctions

cause of problem

Trend Detection

Root Cause Determination

CAPA Determination

QA for impact Analysis

Immediate Action 

Taken

instructions

(25)

Define, Track, Manage and Report 

Across Your Organization

Across Your Organization

Quality Assurance

Effectiveness

Check

Quality Assurance

Need to continuously verify  effectiveness of CAPA

CAPA

Quality Assurance

Add procedure  to verify  instructions  included before  shipping

Check Plan

Check Execution

Approvals

of CAPA  actions

Corrective Actions

Preventive Actions

Change Control

Risk Assessment

Change Control

Document Control

A Change  Request for the  new SOP  is required 

Change Control

Change Plan

Risk Assessment

Design Change Execution

A Change  Request for  related existing  SOPs

(26)

Define, Track, Manage and Report 

Across Your Organization

Across Your Organization

Employee

Document Control

A new SOP  is added for this  new process

Training

Issue retraining record to

Revision to  existing SOP triggers retraining

Document

Change Plan

new process  step An existing SOP  is updated to

Issue retraining record to 

appropriate employees 

based on job description 

and curriculum

Change Plan

Risk Assessment

Design Change Execution

is updated to  accommodate  the new process  step

(27)

Questions?

Questions?

References

Related documents