Engaged. Knowledge. Application

Nowadays, workflows are wide spread in the business world. The desire to streamline operations in any business sector and benefit from a standard approach has allowed this concept to develop and integrate components almost inevitable to the information systems.
Here is an overview of what these strange structures called "workflow" or "workflow" ...
According to Wikipedia, "A workflow is a flow of information within an organization, such as automatic transmission of documents between people."
In the following, I will try to popularize this concept, hoping to explain it and better clarify the definition given on Wikipedia.
The "Workflow" is an answer to the 5 "Wh" questions:
A workflow is a set of activities or tasks, each with:
The answer is a physical entity (physical object) or not (an idea or information). This entity is what will operate in a "flow" and undergo transformations or qualifications.
Example: a protocol for clinical trials is subject to several treatments before including it in a file for authorization to market a drug.
These are actors in a process for dealing with entities that move between them. Each player has a role in defining precisely its authority to "make" and "don'ts".
Example: the submission of a clinical study protocol is
Requirements will imply, for example, that the HPV can not edit the document.
A specific activity can explain a treatment in a given process. The activity must have a clear and reproducible procedure, generally limited to a well established role.
Example: the PL "writes" the protocol of the clinical study. It has the role of "Creation / Modification" on documents of type "Protocol". Writing procedure is defined as follow:
(In general, the original copy is briefly locked: at the time of its copy or his crash. Reading some content is like making a local copy as if to modify it. Readers can modify their local copy but can neither "overwrite" the remote copy, nor create a new version.)
An activity takes place, in principle, "after" and/or "before" another one, hence, the "Precedence" relationship between activities. This concept is important insofar as the activities in a workflow are always ordered (kind of sequence).
An activity may "precede" a number of activities and / or "forward" one or more activities. Going even further, an activity can be executed when one or more or even "all" preceding activities are completed or when some conditions are verified. We, then, speak about "Triggering" condition of the activity.
If an activity is triggered, usually stakeholders are "notified" either by email or by a particular display in a list of tasks or on the home screen of an application.
Example: The "Verification" of a document can't be executed before its creation or before a new modification of a published "version" (key word ==> cf. Subsection "9 - Life cycle") of the document. But the "Writing" of a document is quite possible after a "check". "Loops" in a workflow are very common!
Each activity can be activated only when a certain number of conditions, other than the trigger itself, are met. All of these conditions is the context. Usually, those conditions are verified on the entity submitted into the workflow.
Example: If the document is already experiencing a workflow, it is not possible to "Editor" to initiate a 2nd workflow above. Moreover, a document being verified can not undergo activity approval.
Those "virtual" activities signify the start or end of a workflow. They handle the triggering and the activation conditions of the "start" or the "end" of the workflow.
The "Life Cycle" (LC) of an entity is an ordered sequence of states. Each state is a set of parameters with well-defined values. The status of an entity is described through the values of these parameters. An entity undergoing a workflow will transit across different states. Executing an activity on an entity will modify its parameters. So, usually, this modification is followed by a change of state of the entity. To retrieve a document to a given state, we use the term "version". Thus, a new version of an approved document should be created before making any further changes on it.
Example: The protocol for a clinical study follows this:
Tags:
Join the U.S. FDA and Major Pharma and Device Manufacturers who attend our events; Pfizer, Merck, Johnson & Johnson, AstraZeneca, Medtronic, Boston Scientific, Alcon, Schering-Plough, Roche, Bristol Myers Squibb, Becton Dickinson and more...
***SCHEDULE***
GLP LIVE Training Workshops - (click here for complete brochure)
Two GLP Workshops in Two Locations
1. The Brass Tacks of GLP: Practical Understanding of the Fundamentals As Never Before Explained
2. Writing Effective GLP Docments
March 9-10, 2010 San Diego
March 11-12, 2010 San Francisco by a GLP Subject Matter Expert
Medical Device Software Validation LIVE Training Workshops - (click here for complete brochure)
Two Workshops in Two Locations
1. Medical Device Software Validation: System Definition and Requirements: Incorporating Effectiveness and Compliance in Software Design
2. Implementing Critical Processes for Effectively Supporting Medical Device Software Validation Programs
March 24-25, 2010 Iselin, NJ
May 19-20, 2010 Waltham, MA by Boston Scientific
CAPA LIVE Training Workshops - (click here for complete brochure)
Two Workshops
1. CAPA: Effective System Management - One Industry Professional Shares His Expertise
2.Supplier-Related CAPA: Conducting Effective Root Cause Investigations
April 20-21, 2010 Boston/Waltham, MA
by a CAPA Subject Matter Expert
GMP LIVE Training Workshop: Master Production Batch Records - (click here for complete brochure)
Effective Generation and Control of Master Production Batch Records (MPBR)
April 22, 2010 Boston/Waltham, MA by a GMP Subject Matter Expert
May 12-13, 2010 Hilton Woodbridge-Iselin, NJ by a GMP Subject Matter Expert
To View Previously Recorded Webinars Click Here
Special 21 CFR Part 11 Recording Package - Click Here for More Details
Recent Webinar TESTIMONIALS:
"It was the perfect presentation for my audience. Over the last year, since I started retraining all my frequent fliers, I have gone over or flagged for action every concern in that presentation. I had people in the audience that needed a final re-enforcement. I believe every "hot-topic" in Change Control was covered". - Anuja Rajbhandari, Change Control Specialist - AstraZeneca - CLICK HERE TO VIEW THE WEBINAR ON CHANGE CONTROL
"Enjoyed it. It was like the trainer has worked at our facility!!" - Carol S. Spicer, Director, Quality, Training and Support Services - Bridge Laboratories - CLICK HERE TO VIEW THE WEBINAR ON GLP DEVIATIONS

U.S. Toll Free: 877-823-4GXP
Outside the U.S. +1-561-795-2785
Fax: +1-561-798-8138e-mail: info@enkap.com
1480 Royal Palm Beach Blvd.,Suite A, Royal Palm Beach, FL 33411, U.S.

enKap Terms and Conditions
All sales are final
Legal Disclaimer
This product and any of its enclosures, attachments or appendices, references to online information, conferences or preparations of materials in a variety of formats are created to provide you with accurate and authorative information concerning the subject matter covered. However, this product and any other ancillary items disseminated in connec-
tion with same are not necessarily prepared by a person licensed to practice law in a particular jurisdiction.
enKap, Inc. is not engaged in rendering legal advice, and this product is not a substitute for the advice of an attorney. If you require legal or other expert advice, you should seek
the services of a competent attorney or other professional.
enKap, Inc. necessarily is not, cannot and will not be liable for any claims, damages, or regulatory legal proceedings initiated as a consequence of you, the customer, modifying,
altering, adding to or deleting portions of any product initially provided by enKap, Inc.
Once any original document provided by enKap, Inc. to you, whether in print or electronic format, has been manipulated or customized by you, then the responsibility for the
document’s accuracy, correctness, and compliance are solely yours.
If any action, claim for damages, or regulatory proceedings is commenced against enKap, Inc. as a consequence of your alteration or modification, etc. of the document templates
or other originally provided materials, then and in that event, you agree to indemnify enKap, Inc. for such claims, and for any attorney’s fees expended by enKap, Inc. in connec-
tion with defense of same.
© copyright 2010 enKap
© 2010 Created by enKap
You need to be a member of enKap community to add comments!
Join enKap community