
















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
1. Introduction 1.1 Adverse Event Reporting Requirements 1.2 Oracle Argus Safety Database Overview 1.3 Argus Affiliate vs Argus Safety 2. Argus Workflow Overview 2.1 Workflow Concept (States) 2.2 Audit Trail & Process Tracking 2.3 End-to-End Case Lifecycle 3. Business Process / Workflow Diagram 4. User Roles in Case Processing 4.1 Data Entry 4.2 Case Triager 4.3 Quality Controller 4.4 Medical Reviewer 4.5 Unblinding Group 4.6 Expedited Reporting Team 5. Case Processing Steps 5.1 Case Intake 5.2 Case Triage 5.3 Data Entry 5.4 Quality Control (QC) 5.5 Medical Review 5.6 Unblinding 5.7 Case Lock 5.8 Distribution 5.9 Follow-up Pending 5.10 Archived / Closed 6. Argus Safety Configuration 6.1 Configuration Process Overview 6.2 Administrator Login 6.3 Login Rules & Security 6.4 Argus Console Access 7. System Administration 7.1 Changing Password 7.2 Logging Out 7.3 Required Fields 8. System Features 8.1 Type-Ahead Fields 8.2 Standard Icons
Typology: Slides
1 / 24
This page cannot be seen from the preview
Don't miss anything!

















Each pharmaceutical and biotechnology company are required by law to
capture and report adverse event data on their drug, device and vaccine
products
entered into the Argus Safety suite of modules
Argus Affiliate and Argus Safety
Case Safety Reports (ICSRs), otherwise known as cases, through the
complete life cycle from receipt of information to submission of reports
to regulatory authorities
Argus Affiliate is used to capture cases at a local level and submit them
for central processing in Argus Safety
of cases and to ensure compliance with regulatory requirements.
The Argus Safety workflow ensures structure of case processing and
also retains an audit trail of the entire workflow process:
Argus divides the case processing workflow into units of work called
“states”.
Each workflow state is a set of items that can be performed by a defined
user or a group in a pre-defined sequence
Argus tracks the movement of each case that has been entered, from one
required workflow state to the next, until the case has been fully
processed and closed
Data Entry
Case Triager
e.g. seriousness, relatedness, expectedness determinations
Quality Controller
Medical Reviewer
Typically a physician but could be other HCP (company dependent)
Unblinding Group
Expedited Reporting
Case Triage
Who
Tasks
duplicate or not
follow-up may be done during case triage
Considerations
therefore it is important that it is performed by a person suitably
qualified.
Data Entry
Who
Tasks
or Medical Review)
Considerations
data and then have someone else review
medical background “own” the case from beginning to end.
Medical Review
Who
Tasks
assessments, seriousness assessments, listedness assessments
for closure after reporting
for corrections to be addressed
Considerations
then have another Argus user document the findings in the system, add
updates and comments to the case and route it to the next step.
Who
Tasks
the patient was given
Considerations
unblinding in Argus
report to partners or authorities if required.
Unblinding
Distribution
Who
Tasks
Considerations
acknowledgement for an electronic submission is received. One of the
following approaches is usually taken:
the corrections and lock the case again
the whole workflow again
Follow-up Pending
Who
Tasks
Considerations
are made. After the third attempt the case will be closed.
The number of attempts made varies by type of case and company policy
Argus Safety Configuration Process Overview
To configure Argus Safety, the Administrator must follow a particular
sequence of steps. Steps that fall later in the sequence might depend on
those that appear earlier. It is, therefore, important for the Administrator
to use the following flowchart as a guideline for configuring Argus Safety.
Tip:
■ The modules display in bold text identify the modules you have
permission to access.
■ Your login user ID and password are valid for all accessible Argus
modules.
■ This is the single point of login for all the Argus modules.
Enter the User Name and Password to login to Argus Safety.
Note: The password is case-sensitive.
Select the database name from the drop-down Database list.
Press Enter or click Login.
Click Argus Console to launch the Argus Console Administrator screen.
Changing the Administrator's Password
Select Utilities -> Change Password in Argus Safety.
The Change Password dialog opens.
Enter the current password and the new password.
Confirm the new password and click OK.
Logging out
Click Close to log out from the Argus Console application.
To log out at any time from Argus, click Logout.
Required Fields
Fields that are marked with a red flag image and associated with an
orange boundary are required fields. These fields must be filled in, to
proceed with the configuration requirements.