Oracle® Argus Safety Japan

User's Guide

Release 8.1.2

E93580-01

February 2018

Oracle Argus Safety Japan User's Guide, Release 8.1.2

E93580-01

Copyright © 2018 Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Where to Find More Information

- Documentation Accessibility

1 Case Form

- 1.1 Reporter Information

- 1.2 Products Tab

- 1.3 Analysis Tab

- 1.3.1 PMDA Information tab

- 1.3.1.1 PMDA Information: General Tab

- 1.3.1.1.1 Functionality Changes

- 1.3.1.2 PMDA Information: Comments Tab

- 1.3.1.2.1 Functionality Changes

- 1.3.2 Product License Value

- 1.3.3 PMDA Event Reportability Updates

- 1.3.4 Case Form - PMDA Analysis tab

- 1.3.5 PMDA E2B Report Mapping Updates

- 1.4 Activities Tab

- 1.5 Additional Information Tab

- 1.6 Regulatory Reports Tab

- 1.7 Conformance Rules Tab

2 Case Actions

- 2.1 PMDA Event Reportability

3 Worklist

- 3.1 Literature Intake Updates

- 3.1.1 Import Tab Changes

- 3.1.2 Processing Tab Changes

- 3.1.3 Changes to Literature Duplicate Check

- 3.1.4 Changes to Existing Screen Label

4 Reports

- 4.1 Reports: PMDA Expedited Reports

- 4.1.1 Report Scheduling

- 4.1.2 Paper Reports

- 4.1.2.1 Additional Expedited Report Updates

- 4.1.2.2 Printed Paper Reports—Formatting Details

- 4.1.3 User Interface - Reporting Rules Configuration

- 4.1.4 Expedited Reports on DLP

- 4.1.5 PMDA Device Reports

- 4.2 Reports: PMDA Periodic Reports

- 4.2.1 DLP at Report Level

- 4.2.2 Periodic Reports on DLP

- 4.2.3 Upgrade Considerations

- 4.2.4 Advanced Conditions in J Periodic Reports

- 4.2.5 Check in/Checkout Enhancements

- 4.2.6 Other Changes

- 4.2.7 Periodic Safety Report

- 4.2.7.1 Format

- 4.2.7.2 PSR /ReSD Details

- 4.2.7.2.1 Subject of Report

- 4.2.7.2.2 Product Selection

- 4.2.7.2.3 Periodic Safety Report/ReSD

- 4.2.7.2.4 Scheduling

- 4.2.7.2.5 Security

- 4.2.7.2.6 Printing PSR / ReSD

- 4.2.7.2.7 Deleting PSR / ReSD

- 4.2.8 Clinical Study Periodic Safety Report (now J-DSUR)

- 4.2.8.1 Format

- 4.2.8.2 J-DSUR Details

- 4.2.8.2.1 Subject of Report

- 4.2.8.2.2 Product Selection

- 4.2.8.2.3 J-DSUR

- 4.2.8.2.4 Scheduling

- 4.2.8.2.5 Security

- 4.2.8.2.6 Printing CSPSR

- 4.2.8.2.7 Deleting A J-DSUR

- 4.2.8.3 J-DSUR - Cover

- 4.2.8.4 J-DSUR - Form 2

- 4.2.8.4.1 Domestic Serious AE, etc. Case Occurence Status Line Listing

- 4.2.9 Seiyakukyo Line Listing Report (Individual Report Common Line List)

- 4.2.9.1 Configuration Screen

- 4.2.9.2 Report Output Format

- 4.2.9.3 Report Output Filter Criterion

- 4.2.9.4 Report Output Field Mappings

- 4.2.9.5 CSV Output Format

- 4.2.9.6 Periodic Report Process Flow

- 4.3 Non-Reportable and Invalid Events

5 Utilities

- 5.1 MedDRA Browser

Preface

This document describes the steps for using the components of the Oracle Argus Safety Japan application.

Where to Find More Information

Oracle Help Center

The latest user documentation for Oracle Health Sciences products is available at http://docs.oracle.com/en/industries/health-sciences/.

My Oracle Support

The latest release notes, patches and white papers are on My Oracle Support (MOS) at https://support.oracle.com. For help with using MOS, see https://docs.oracle.com/cd/E74665_01/MOSHP/toc.htm.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

1 Case Form

This chapter lists the changes that have been introduced in Case Form.

1.1 Reporter Information

- The Institution ID textbox in Case Form > Reporter Information section is available for both English as well as Japanese users.

Figure 1-1 Case Form Report Information section - Sample Output

- The following are the attributes for this field:

- Field Name (Unique Field Label): Reporter Institution ID

- Field Form Label: Institution ID

- Field Form Label (J)

- Help Text: Enter the Institution ID for the Reporter.

- Help Text (J)

- Hidden radio option set to No. Hiding is allowed.

- Read Only options are unchecked and disabled.

- E2B Field and Research Field are unchecked by default.

- Japanese IME Toolbar is disabled for this field in Case Form even for Japanese user.

- Case Form Field Length: 15 AN. No validation required for alphanumeric data check.

- Both English and Japanese fields point to a common value.

- This field value is populated based on the Institution ID selected for the Reporter from the Report Information Lookup dialog from the Book-in screen.

- This field also allows manually entered / updated value directly in the Case Form irrespective of the value specified in the Institution field for the reporter. Manually entered Institution and institution ID field values are allowed in the Reporter Information section even if they are not specified / linked to each other as per Console Institution code list.

- As both the Institution or Institution ID fields can be present in Reporter Information, and if the user opens up Reporter Lookup for this reporter, then Reporter Lookup searches for reporters in Case or Console data based on the following logic:

- Out of Institution and Institution ID fields first use Institution ID field with the rest of the search criteria fields. The Institution value is not used in this scenario on the Reporter Lookup search dialog.

- If the Institution ID field is not specified in the Reporter Information or if it does not exist in the type-ahead values for this field on Reporter Lookup, then automatically remove the Institution ID field value in Reporter Lookup and search based on Institution field with rest of the search criteria fields.

- If Institution field value also does not exist in the type-ahead values for this field on the Reporter Lookup, then remove the Institution field value as well in the Reporter Lookup and search based on rest of the search criteria fields.

- If "Search all the reporters who belong to the institution found from the current search item" search option is also used, then it performs a search based on Institution ID or Institution Name - whichever is available on the Reporter Lookup dialog to identify the first set of reporters and subsequently use those reporters for second level search.

- This field is printed in Case Form Print for Reporter Information section as displayed for both English and Japanese users.

Figure 1-2 Case Form Report Information Print - Sample Output

- This field is audit-logged.

- This field is available under the following modules:

- Case Listing Report

- CIOMS II Line Listing Report

- CDA Report

- Advanced Conditions

- Case Form Letter Placeholders as specified below:
[reporter_inst_id:primary]

[reporter_inst_id]:[n]

[reporter_inst_id:selected]

[reporter_inst_id:corresp_contact]

- Console Field Labels: Under ARGUS SAFETY > GENERAL > Reporter

- Console Field Validations: Under ARGUS SAFETY > GENERAL > Reporter

1.2 Products Tab

- The PMDA Device Information section below Device Information section on Case Form > Products tab > Device sub tab contains fields as specified in the screen mockup displayed below:

Figure 1-3 Case Form - PMDA Device Information section

- This case form section is available to all Oracle Argus Safety Japan (Argus J) users on both English as well as Japanese views as uncollapsed by default only when Japanese module is enabled.

- It is displayed with Japanese labels on both English as well as Japanese views as this section is not meant for translation of data.

- The Modify, View and No Access rights to this section are based on the "Product Information (Device View)" option in Console > Access Management > Groups > Case Form section.

- Tabbing order of case form elements respects this section in the order of UI elements as left to right and top to bottom.

- The "PMDA Device Information" checkbox in Case Print - section selection dialog only to the Argus J user.

- This checkbox is added right after "MedWatch Device Information" option in the Case Print options dialog. All the options after it are shifted further by one place.

- This checkbox gets selected and unselected when user uses "Select All" and "Unselect All" options.

- This checkbox remains unchecked by default and is disabled unless its parent section checkbox "Product Device Information" is checked by the user. If "Product Device Information" is unchecked later, then "PMDA Device Information" also gets unchecked and disabled. Case Form Print PDF report prints this section in Japanese after "MedWatch Device Information" section if it is selected for printing in the section selection dialog.

Figure 1-4 Case Form Print - PMDA Device Information Section

- The "PMDA Device Information" checkbox in Case Copy - section selection dialog only to the Argus J user.

- This checkbox is added right after "MedWatch Device Information" option in the Case Copy options dialog. All the options after it are shifted further by one place.

- This checkbox is selected and deselected when the user uses the "Select All" and "Unselect All" options.

- This checkbox is unchecked by default and is enabled for user selection.

- The Case Form Copy function copies this section when a case is copied with this section checked in the Case Copy options dialog.

- All fields of this section are audit logged as other case form product device fields.

- All fields of this section are available under Console > System Configuration > Field Labels, Field Validations, and Advanced Conditions screens under the tree structure ARGUS SAFETY > PRODUCTS > PMDA Device. These fields are NOT required for Aggregate Reports.

- In Console ' System Configuration ' Field Labels screen, all these fields are available with the following attributes:

- Hidden radio option set to "No". Hiding is allowed.

- Read-Only options have been unchecked and disabled.

- E2B Field and Research Field are unchecked by default.

- The Route of acquiring OTC drugs field under Product Information captures the route of acquisition of company's own products in form of pre-defined PMDA specified code list values, when it is an OTC drug, and is transmitted in the J2.6k element of PMDA E2B R3.
This field is available in the J view only to the local user for Local data entry after global lock.

This field is enabled only when the product is marked as suspect, and there exists at least one Japan license in the case for which Console > License Configuration > "OTC Product" flag is marked as checked.

In case the product category (for both blinded or broken blind cases) is changed between Suspect / Concomitant / Treatment or Product license are re-evaluated (from the Event Assessment tab) the enabling criteria for this field is also re-evaluated based on the latest case data.

- You can modify the J Drug Code for a Company product and retain the product as a Company product.

- The corresponding English product name for a J Drug populates (only if it is blank):

- When you encode a drug using J Drug Browser from Case form > Products tab (Japanese) > Encode button in to Case form > Products Tab (English) > Product Information > Product name using the English Drug Name value that is loaded in J Drug Schema using English sub file.

- When you add the J Drug to the Case form > Patient/Parent > Other Relevant History Section in to the corresponding English field in the Case Form.

- When you add or select a study drug, which is a J Drug configured from Console > Business Configuration > Study Configuration (J pop-up) in to Case Form > Product name.

- When you select the Study Drug (in Case form for a Study case) as J Drug (as configured in study configuration), in to English version of the case form only if it is a not blinded study (as it does for the existing products).

- In a Globally locked and Locally Unlocked case if you encode a Non-company product with the J Drug using J Drug Browser in to the corresponding English Drug Name shall not be updated to Case Form-> Product Name

- Besides, the corresponding English product name is NOT updated in the English version of the Case Form > Product name, in a Globally locked and Locally Unlocked case when you encode a Non-company product with the J Drug using J Drug Browser.

- The Malfunction Information section is available under Case form > Products > Device (Tab) > Device Information.

This section contains the following fields:

- Reported Malfunction: Enter the Malfunction Name as reported by the Reporter.

- Determined Malfunction: Enter the Malfunction Name as Determined by the Company.

- Listedness: Select the Listedness of Malfunction in respect of the device. This drop-down list has the values:
<blank> (default)

Listed

Unknown

Unlisted

- Reportable: Select the Reportabilty of the Malfunction. This drop-down list has the values:
<blank> (default)

Yes

No

- Add: This button lets you add a new blank row to the table, and is always enabled.
You can add up to 50 rows using this button. If the number of rows exceed 50, on click of Add button, an error message is displayed.

When this screen re-loads or is refreshed, the empty rows are not displayed.

The first row is highlighted in light yellow (selected) by default as standard Case Form behavior.

- Delete: This button lets you delete a row from the table, and is always enabled.
To delete a row, select a row, and click Delete.

A warning message is displayed.

- Future Actions: This drop-down list has the values:
<blank> (default)

Recall (Repair)

Request to suspend the use

Providing the information

TBD

- A new field, Status of Patient's health damage, has been added under Case form > Products > Device (Tab) > PMDA Device Info. This drop-down list has the values <blank>, Exists, Does not exist and Unknown.

- You can select any value in PMDA Device Info > Medical Device Reporting Category irrespective of the Device Information > Malfunction value. This implies that irrespective of the value selected in the Malfunction drop-down list, you can select all the possible values under Medical Device Reporting category.

- You can enter values in First time use, Times of use and Since the first use fields at the same time, independent of each other.

- A new field J-DRUG is added in Case Form > Product > Substance Information.

- This field populates the J Drug Code of the Ingredient as configured in Argus Console > Business Configuration > Product and Licenses > Product (J Data Entry) > Key Ingredients.

- This field is editable.

1.3 Analysis Tab

- Up and Down buttons have been added to the PMDA tab.

- By default, the focus is on the first record. No action is performed when the user clicks on "Up" button when the focus is on the First record. If the focus is on any other record other than the first record, the system interchanges the position of the current record and previous record by clicking the "Up" button.

- No action can be performed when the user clicks on "Down" button when the focus is on the Last record. If the focus is on any other record other than the last record, the system interchanges the position of the current record and next record by clicking the "Up" button.

- If there is no row in this section, then clicking on "Up" and "Down" buttons does not cause action.

- For existing customer data, the sort order value for existing records is populated as same as the order in which these were displayed to the user.

- The change in ordering of these product license rows in PMDA General tab is audit-logged.

- The product license ordering on the PMDA General sub-tab is also respected by the following:

- PMDA Comments sub-tab > Product License dropdown

- Case Form Print > PMDA General and Comments tab

- PMDA E2B Report > Ordering of product dosages in DRUG section as per the logic specified below

- PMDA Paper Report > Ordering of product dosages in DRUG section as per the logic specified below

- The common profile switch "Japan License to be available in case for Assessment and reporting" in Console > System configuration > Common profile switch > Argus J has the following values:

- Option 1: All valid Japan Licenses (default)

- Option 2: User Selected License only

All the changes made to this profile switch are audit logged.

- PMDA E2B and Paper Reports (Marketed Form 1-6 and Investigational Form 1-6) list the suspect products using the order of products specified in PMDA tab. Logic to be considered for PMDA E2B report is provided below, with the only change from the previous logic being for point b:

- The company product for which the ICSR is scheduled is always listed first.

- For the other company suspect Japanese products which are displayed on the PMDA tab, the order of products is considered from the PMDA tab.

- The remaining suspect products (which are not listed on the PMDA tab).

- Other concomitant products.

- For each of the above categories (c), and (d), if there are multiple products, then the "Product details/First Dose" are used for the ordering of products. Earlier dates are before the later dates.

- If there are multiple products with the same "Product details/First Dose" under any of the above category (c) and (d), then they are ordered using the product sort ID used in the case itself.

- Within a product, if there are multiple dosage regimens, then they are ordered based on the dosage start dates.

- If the date being used for ordering is null, then the product is put at the end in the same category.

- For the Partial date, if the date is considered as 15th of the month, the month is considered as June of the year.

Figure 1-5 Case Form - PMDA tab

1.3.1 PMDA Information tab

The PMDA Information tab comprises two sub-tabs: General and Comments, as depicted in the following figure:

The details about the General and Comments sub-tabs are given in the following sub-sections:

- PMDA Information: General Tab

- PMDA Information: Comments Tab

1.3.1.1 PMDA Information: General Tab

The following figure depicts the General sub-tab of the PMDA Information tab:

The following table lists the fields in the General tab:

Table 1-1 Fields in the General tab

#

Field Name

Description

1

General

This represents the name of the sub-tab under PMDA tab.

2

Comment

This represents the name of the sub-tab under PMDA tab.

3

Japan first information Received Date (For Reporting)

This field represents the editable text box which displays the date the case was received by the Japanese pharma company (initial receipt date captured during case book-in). The format is YYYYMMDD. In case of a local case, this date represents the Case Initial Receipt date. In global case, this date is automatically populated by the date first opened by J user. The value is stored in the case when you perform direct/indirect Save. For example, accept from worklist stores the value indirectly.

4

Follow-up received date

This field represents the non-editable text box which displays the date the case follow-up information was received by the pharma company. If the follow-up is marked significant, the Japan Follow-up Received date is used as the reference date to schedule the reports. The format is YYYYMMDD.

5

Safety received date / or Central received date

This field represents the non-editable text box which displays the date the Safety group received the case. The format is YYYYMMDD.

6

Significant Changes

This is a non-editable checkbox to indicate whether the follow-up is significant or not. If the follow-up is significant, the Japan Follow-up date overrides the date used for report scheduling.

7

Japan follow-up received date

This field represents the editable text box which displays the date the case follow-up information is received by the pharma company. If the case is originated in some country other than Japan, this date represents the date first opened by the J user after the follow-up. If the follow-up is marked significant, the Japan follow-up received date is used as the reference date to schedule the reports. The format is YYYYMMDD.The time stamp of Case Open date done by first Japanese user after the latest foreign follow-up is automatically populated.The value is stored in the case when you perform direct/indirect Save. For example, accept from worklist stores the value indirectly.

8

Drug name and license number

The number of rows in this section is equal to the number of reports that need to be submitted to PMDA for this case. One report is scheduled for each of the Marketed License. One report each is scheduled for each Study License. The field is read only and show concatenation of Trade Name with License Number in brackets.

9

New Drug Category

This field represents the drop-down to select License Category LM to select value for E2B J.8 item.

10

Japan Reporting type (OBSOLETE)

This field indicates the Reporting Type. It is a drop-down list showing three possible values: Case Reporting, Research Reporting, and Action Taken.

NOTE: This dropdown is no longer available. However, as per the standard approach, the existing database column along with existing value are retained as is, the text "OBSOLETE" is added at the beginning of the DB column comments (for both upgraded and fresh schema). The database column is marked as deprecated during the upgrade script.

11

Japan Reporting category

This field represents a drop-down List containing Reporting Category LM. This is a mandatory field for Argus J user. The selection of this field determines the report being created (ADR, Infection, Research, or Measures in foreign countries). The entries shown in this list are determined at run time by the values selected in items 9,10 and 12.When Reporting Category is not selected, the license does not create the report.The format of the value displayed in this drop-down is: [Reporting Category] - [Description]

12

Domestic Case / Foreign CaseClinical / Marketed

There are two fields which are non-editable text boxes. The first shows whether the case is foreign (if the country of incidence is not equal to Japan) or domestic (if the country of incidence is Japan).The second field shows the license type:

Investigational, if the license on which the ICSR is based on is for an investigational drug, device, or vaccine.

Marketed, if the license on which the ICSR is based on is for a marketed drug.

13

Completion Report (Case Complete)

This checkbox indicates the completion of the case report. A new Case Complete checkbox field is added to the License List box. This field is the driver for the E2b field J.6. A separate J.6 must be recorded for each ICSR. By default, this box is not checked.

14

PMDA Identification Number

The PMDA Number is displayed in the PMDA tab where all the ICSR licenses are displayed. This is the PMDA Acknowledgment Number given in Ack message item B.1.3. This number is used in J.4b from the first follow-up report.

15

Clinical Compound Number in the study of this case

This field is read only when the study is selected from the Study look up. When the study information is manually entered, Clinical Compound Number is editable. If there is no study information, the field is disabled.

16

Domestic

This field represents the Read-only text that is determined by the system.

17

Marketed

This field represents the Read-only text that is determined by the system.

1.3.1.1.1 Functionality Changes

The following are the functionality changes for the PMDA Information > General tab:

1. This tab is unique to Argus J module implemented system. It also displays the number of reports to be submitted for the case. Each row in the lower section represents a report. The number of reports to be submitted for a case is determined as per the following logic:

- General Rule

- Reports are submitted for Marketed or Investigational licenses in Japan only for the suspect company products in the case.

- All Japanese licenses (including hidden) listed in the event assessment are listed.

- All suspected products with license and all Investigational licenses are listed in the PMDA General Tab.

- Priority order of the Suspected product (Drug, Device, Vaccine) list is:
Primary Suspected Product License

Product entry order in the Case Form

Marketed license, then Investigational

- The license is displayed as the Trade Name and the License Number in parenthesis.

2. Japanese Receipt Date and Follow Up Dates table:
It captures the Japanese received date label as Japanese received for each recorded follow-up in the PMDA tab. The system displays a list of all follow-ups that are entered in the General tab with the option to specify Japanese received for each follow-up entry.

- When you change the Japanese Received Date from default, the justification pop-up with the message Please enter the reason of information receipt date change is displayed, wherein you are required to enter the reason of this date change.

- When you change the Japanese Receipt Date or Japanese Follow-Up Date, if the changed date is older than the date in the Information Receipt Date of General tab, a pop-up window with the following error message is displayed:
The date cannot be older than the first information receipt date of the case.

- For the purpose of Report Scheduling in Japan, the Japanese Aware Date is used by checking the flag on Use Japanese Aware Date for Reporting as configured in the Reporting Destination Code List of Console. The Japanese Aware Date has the same behavior as the Standard Aware Date.

3. Reporting Category:
The Reporting Category is a drop-down list with the values from Reporting Category Code List.

- The Reporting category is a drop-down list with the values, as indicated in the table below. The drop-down content of the field depends on the previous selection in:

- AE/Infection (in Infection check box in Event tab) - This is used only if all the events are AE, or all the events are Infection.

- Domestic / Foreign (in Country of Incidence, PMDA tab, Dom = JP, Frgn <> JP)

- License Type (Investigational or Marketed)

- You can refer to the following table for the list of Reporting Categories in the drop-down list.

- The system clears the Japan Reporting Category if the dependent fields are modified after the selection has been updated.

Table 1-2 List of Reporting Categories

R2 Category

R3 Category

Category Description

AE/ Infection (in event tab)

Dom / Frgn

License Type

Paper Reports

A

AA

Case reports on infections in Japan (post-marketing)

Infection

Dom

Mkt

Form 1, 2

(6 pages)

B

AB

Case reports on adverse drug reactions in Japan (post-marketing)

AE

Dom

Mkt

Form 1, 2

(6 pages)

C

AC

Case reports on infections in foreign countries (post-marketing)

Infection

Frgn

Mkt

Form 1, 2

(6 pages)

D

AD

Case reports on adverse drug reactions in foreign countries (post-marketing)

AE

Frgn

Mkt

Form 1, 2

(6 pages)

E

AE

Research reports on infections (post-marketing)

Infection

Any

Mkt

Form 3, 4

(2 pages)

F

AF

Research reports on adverse drug reactions (post-marketing)

AE

Any

Mkt

Form 3, 4

(2 pages)

G

AG

Reports on corrective action such as discontinuation of manufacturing, recall, disposal in foreign countries (post-marketing)

Any

Any

Mkt

Form 5, 6

(2 pages)

H

DA

Case reports on infections in Japan (clinical trial)

Infection

Dom

Inv

Form 1, 2

(6 pages)

I

DB

Case reports on adverse drug reactions in Japan (clinical trial)

AE

Dom

Inv

Form 1, 2

(6 pages)

J

DC

Case reports on infections in foreign countries (clinical trial)

Infection

Frgn

Inv

Form 1, 2

(6 pages)

K

DD

Case reports on adverse drug reactions in foreign countries (clinical trial)

AE

Frgn

Inv

Form 1, 2

(6 pages)

L

DE

Research reports on infections (clinical trial)

Infection

Any

Inv

Form 3, 4

(2 pages)

M

DF

Research reports on adverse drug reactions (clinical trial)

AE

Any

Inv

Form 3, 4

(2 pages)

N

DG

Reports on corrective action such as discontinuation of manufacturing, recall, disposal in foreign countries (clinical trial)

Any

Any

Inv

Form 5, 6

(2 pages)

O

BC

Research reports on quasi-drugs

Any

Any

Any

Form 3, 4

(2 pages)

P

BD

Research reports on cosmetics

Any

Any

Any

Form 3, 4

(2 pages)

4. PMDA Tab > General > Linked Product section collects product in the Assessment table with the following rules:

- System checks:

- If the case is a foreign case

- If the case has non-company product(s).

- The non-company product(s) is/are marked as Suspected.

- Under all above conditions, suspected company product in this case has equivalent Japanese license.

- If there is non-company suspected drug in foreign cases, that product Trade Name and Generic name are used for matching with the Keywords from Console J > Code List > Argus J > Reportable Product Keyword.

- This keyword is used for finding related company product family which needs reportability assessment when foreign case has non-company suspected drug. The keyword text is matched within either the Product Name or Generic Name fields of the Case Form. If entered keyword matches (partially or fully), the matching product family's Japanese license is assessed in the PMDA tab.

- When there are multiple Japanese licenses in the matching family, all of these licenses are listed for assessment in the PMDA tab.

- Products already existing in the Case form are not populated here.

- In this section, the Causality Assessments are available.

- Listedness is always Unknown for this section.

- Hyperlinks are not available for this Assessment section.

Table 1-3 Field Descriptions

Field

Argus J User display

Product

Company product(s) using J Reportable Keyword are displayed.

Event PT (Description) / LLT

Event(s) in the case are displayed

D/S

D/S information is displayed as read-only

SeriousnessSeverityDuration

Event information is displayed as read-only

Reported Causality

Reported Causality type-ahead drop-down

Determined Causality

Determined Causality type-ahead drop-down

- You can assess the product for reportability in this table.

- This section's display status (Maximize/Minimize) is not dependent on a user preference:

- This section is automatically minimized if there is no data.

- This section is automatically maximized if there is data.

5. When you enter future date in Initial Receipt Date in Case Form > General tab > General Information > Initial Receipt Date, or PMDA Tab > General > Initial Information Receipt date, the application displays the following validation message:
Receipt Date cannot be a future date

6. Product Change Justification:

- When you click the OK button (the button appears in each follow-up row of Product Change Justification column in the follow-up info table), the Justification Table pop-up is displayed to view update information.

- The button is enabled only when Product Change justification exists for the case.
For example, Scenario # 1 - it only asks for justification if there is a submitted report against the product which is subject to deletion and you unlock the case with follow-up to delete that product.

Scenario # 2 - In addition, when you create a company product:

- Schedule an Expedited report against the company product.

- Get that report to Submitted status.

- Unlock case a, add follow-up and change the company product to a different company product (change justification is displayed).

- Enter something and navigate to PMDA tab.

- The button is enabled.

- The Justification list populates all the product justifications entered for the follow up.

- The Translation justification is editable using the following steps:

- Select the justification from the list. This highlights the row.

- Click the Editing the justification button.
This opens Justification pop-up and you can edit the justification.

7. When you select the Research Report Type Reporting category, a pop-up Reason for subject of the Research Report is displayed to enter the reason of the Research report.

- The pop-up UI section opens only when any one of the suspected drug license table has one of following Reporting Category selected:

Table 1-4 Reporting Categories

#

Reporting Category (English meaning)

5

Research/Infection report (Marketed drug)

6

Research/ADR report (Marketed drug)

12

Research/Infection report (Investigational drug)

13

Research/ADR report (Investigational drug)

15

Research report (Quasi drug)

16

Research report (Cosmetics)

- The information is multiply stored when multiple suspected licenses with the Research Reporting Category exist. Each Research Reporting Category has a circle in Green color symbol after the justification is entered in the pop-up window.

- Justification pop-up

- User Interface:

The following table explains the fields used in the Justification dialog box:

#

Field Label Value

English Label Name

Purpose

Field Length

Audit Log

1

N/A

Reason of Research Report

Title of the UI

N/A

N/A

2

N/A

Assessment Result

Read Only

N/A

N/A

3.

N/A

Reason of Research Report

Title of the section

N/A

N/A

4.

Reason for subject of the Research Report - Possibility of occurrence of serious disease such as cancer, disorder, or death

Possibility of occurrence of serious disease such as cancer, disorder, or death

Radio button Yes - exists
無No - does not exist

N/A

Yes

5.

Reason for subject of the Research Report - Significant change on event or infection occurrence number, frequency, and condition

Significant change on event or infection occurrence number, frequency, and condition.

Radio button Yes - exists
無No - does not exist

N/A

Yes

6.

Reason for subject of the Research Report - It doesn't have acknowledged effectiveness

It doesn't have acknowledged effectiveness

Radio button Yes - existsNo - does not exist

N/A

Yes

7.

Reason for subject of the Research Report - Problems

Problems

Text Field, 20,000 field length.

20,000

Yes

8.

N/A

OK

Button

N/A

N/A

9.

N/A

Cancel

Button

N/A

N/A

Items # 4, 5, and 6 have radio buttons Yes and No to store the answer.

Field #2, Assessment Result, is a read-only field to show either the value from Literature Intake Assessment or the Reporting Category selected in the PMDA General tab. The following table illustrates the drop-down content based on the Reporting Category:

#

Drop-down Content (English meaning)

Reporting Category

1

Not Necessary

2

AE Case

A, B, C, D, H, I, J, K

3

Research/Infection report (Marketed drug)

E

4

Research/ADR report (Marketed drug)

F

5

Research/Infection report (Investigational drug)

L

6

Research/ADR report (Investigational drug)

M

7

Research report (Quasi drug)

O

8

Research report (Cosmetics)

P

9

Measures in foreign countries including discontinuation of manufacture, recall and withdrawn (Marketed drug)

G

10

Measures in foreign countries including discontinuation of manufacture, recall and withdrawn (Investigational drug)

N

- The Problems section text field stores text information.

- At least one Yes radio button has to be filled in the User Interface, and if this condition suffice, the UI can be closed. If this is not fulfilled, a message:
At least one question has "Yes" selected is displayed to suffice the condition.

- This is not printed in the Case Form Print.

- Once you select Research Reporting Category and enters the reason, and then re-selects the Reporting Category to Non-Research Reporting Category, the system displays a warning message:
Trying to select non-Research Reporting Category. If changed, the already entered "Reason of the Research Report" will be removed. Continue? is displayed.

If you select OK, the reason is deleted. If Cancel is selected, the Reporting Category change is aborted.

8. New fields are added under Literature Information section.

- Country of publication: Captures the Country of Publication for each literature in research or foreign measures reports. The data captured in this field is transmitted in the J2.15.r element of PMDA E2B R3.

- Study/trial classification: Identifies ”Clinical trial/study” or ”Non-clinical trial/study” for each literature publication in the research reports. This dropdown has the following values:
<Blank> (Default)

Clinical trial/study

Non-clinical trial/study

The configured data is transmitted in the J2.13.r.1 element of PMDA E2B R3.

- Literature Lookup dialog: Similar "Country of Publication" (type ahead) and "Study / Trial classification" (dropdown) are provided in the Literature Look-up dialogue for searching literature. The corresponding "Country of Publication" and "Study / Trial classification" values are populated in the Case Form for the selected Literature in the look-up dialogue when opened by any (both English and J) user from any (both English and J) tab.

- Both the fields are available in the J view only, and available for editing for local user after the global lock.

9. Each section has the Minimize button to hold the sections. The Associated Product Assessment section is minimized when the product does not exist.

10. Based on the TIKEN configuration in the console, if the license is available in PMDA Info > General > Suspect Product Licenses and it is a foreign case (that is, COI is other than Japan) then the TIKEN icon is displayed in the Product Name and License Number column as follows:

1.3.1.2 PMDA Information: Comments Tab

The following figure depicts the Comments sub-tab of the PMDA Information tab:

The following table lists the fields in the Comments tab:

Table 1-5 Fields in the Comments tab

#

Field Name

Description

1

General

This represents the Sub-tab of the PMDA Information tab.

2

Comment

This represents the Sub-tab of the PMDA Information tab.

3

Product, License No

This is a drop-down field. It allows you to enter J specific narrative information based on the each suspected drug license.

4

Comment on incomplete

This field is unique to Japan. This field is an editable text that maps to DTD element J.7 as per PMDA. In case of an incomplete report, input a comment in J.7 <mhlwadmicsrcommentsincomplete> for the report being incomplete.

5

E.g. Cure_All MKT (xxxxxxxxxxxxxxx)

This field represents the E.g. Sample License for which the narratives are being written. All the narratives written in the various text boxes are applicable to this License.

6

Counter measure for the future

This field is unique to Japan. This field is an editable text that maps to the J.9<mhlwadmicsrcountermeasures> DTD element as per PMDA.The company inputs the counter measures for the future based on the evaluation made by the reporting company on the concerned adverse effect infection, etc.For foreign case, the company inputs the counter measures taken by the Japanese reporting company, and not the foreign company. The field size is 10000J.

7

Other references

This field is unique to Japan. This field is an editable text that maps to the J.10/J2.11<mhlwadmicsrreporttimesevent.> DTD element as per PMDA for E2B R2 or E2B R3 respectively.

8

Comment of sender

This field is unique to Japan. This field is an editable text. This refers to the B.5.4 < sendercomment > element.

9

Remarks 1

This field is unique to Japan. This field is an editable text that maps to the J.13.1 DTD element as per PMDA. The DTD element name is:<mhlwadmicsrremarks1>

10

Remarks 2

This field is unique to Japan. This field is an editable text that maps to the J.13.2 DTD element as per PMDA. The DTD element name is:<mhlwadmicsrremarks2>

11

Remarks 3

This field is unique to Japan. This field is an editable text that maps to the J.13.3 DTD element as per PMDA. The DTD element name is:<mhlwadmicsrremarks3>

12

Remarks 4

This field is unique to Japan. This field is an editable text that maps to the J.13.4 DTD element as per PMDA. The DTD element name is:<mhlwadmicsrremarks4>

13

Copy the comments in this tab to other reporting licenses

This button copies all the comments in the UI to other licenses in the list. When there is only one product, the button is disabled.

The following new fields have been added to enter information for each license that is available in the Product, License No drop-down:

- Retrospective analysis of infection

- Summary of report content

- Comments relating to start date of reporting timeframe

- Start date of reporting timeframe drop-down list

- Reason for downgrade report

- Downgrade report flag drop-down list with the options System Calculated, Downgrade, Nullification

1.3.1.2.1 Functionality Changes

The following are the functionality changes for the Comments tab:

1. This tab captures narratives data for various J DTD elements that are reported in E2B reports being submitted to PMDA.
For details, refer to the DTD Mapping document.

2. Product, License drop-down contains the same suspected drug licenses listed in the PMDA General tab. This is to include distinct narratives for each license. Each comment is applied to the selected License Number within the drop-down field. So a unique narrative field is available for each license. In the Product, License drop-down, licenses are displayed in the following format:
Trade Name (License number)

Depending on which license is picked, appropriate Narrative fields is displayed.

3. When Copy the comments in this tab to other reporting licenses is clicked, a message Comments already exist for other licenses and will be overwritten. Do you wish to continue? is displayed. If you click OK, the copy process is continued, and if you click Cancel, the copy is canceled.

4. This tab has auto text generation functions on each text box:

- UI: (buttons are located on the right side of each binocular icon).

- The label of the button Generate

- The function of the button is the same as Generate buttons in the Analysis tab. The PMDA tab does not have English or other languages equivalent fields, therefore, the auto narrative functions populate the texts by using Japanese Narrative template of the Console Configuration.

5. The following new comments fields are added in the Product License No dropdown list:

- Retrospective analysis of infection (J2.9): Captures the information from analysis of infection cases for blood products as specified in the PMDA Guideline for Retrospective Review of Blood Products. This will be used only for reporting of infection case reports.

- Summary of report content (J2.16): Capture the summary of the main issues found in the respective report for Study Reports and Reports on Overseas > Actions.

- Comments relating to start date of reporting timeframe (J2.2.2): Captures any user comments for explaining the value of J2.2.1 – Start date of Reporting Timeframe element in the PMDA E2B (R3) report.
Start date of reporting timeframe: This is the corresponding dropdown list added to capture the manual user input for J2.2.1 - Start date of Reporting Timeframe element in the PMDA E2B (R3) report. This dropdown list has the following value:

- System-Calculated : This is the default value and the value for all the Aware date (J) (Japanese date format) i.e. the date's corresponding to significant follow-ups for that case. you may change the value manually.

- Reason for downgrade/Nullification report (J2.8.2/C.1.11.2): Captures the reason for downgrading/nullification of a report.
Downgrade report flag: A corresponding dropdown list is added to capture the manual user input to indicate to the application if next PMDA E2B/Paper report for the license is scheduled as a downgrade or nullification in the scenario when no reporting rule matches. This dropdown list has the following values:

- System-Calculated (Default)

- Downgrade

- Nullification

- To edit both Comments relating to start date of reporting timeframe and Reason for downgrade/Nullification report dropdowns after the case lock (globally and locally locked), set the profile switch Allow user to update the "Reason for Downgrade/Nullification report" and "Comments for start date of reporting timeframe" after the case is locked(globally and locally locked) as Yes.

1.3.2 Product License Value

- The Product License display value on PMDA tab has been changed at the following places:

- PMDA General tab > Product Licenses section ' Product License column

- PMDA Comments tab > Product License dropdown field

- The following display value format is used at these places for product license values:
<Case Form Product Tab Name (J)><space><#[x]><space>(<License Trade Name (J)>)<space>(<License Type><space>-<space><License Number>)

Where

<Case Form Product Tab Name (J)><space><#[x]>: is the same text that is displayed as Product tab name for the product to Argus J user. "<space><#[x]>" is present only if the tab name is same for multiple products either due to multiple study drug under same study or due to non-study multiple products with same name.

<License Trade Name (J)>: is the Trade Name (J) from Console license configuration for the license of the product.

<License Type>: is printed as "Inv" or "Mkt" base on whether the License Type is Investigational or Marketed.

<License Number>: is the License Number from Console license configuration for the product license.

1.3.3 PMDA Event Reportability Updates

- The following field values from the PMDA Event Reportability Print section are available/stored in database tables/columns so that they can also be queried for other custom reporting needs:

- Reportability Status - Reportable, NUPR Reportable, Not-Reportable

- Reportability Timeframe value in days

- To avoid unwanted performance impact on Case Save action, these field values should not be calculated on each case save. These are calculated based on only the following actions:

- Manual method - "Recalculate PMDA Event Reportability" button
A new button "Recalculate PMDA Reportability" has been added to Case Form > Analysis > PMDA Info > General tab > Product License section header bar right before the "Up" and "Down" buttons.

Clicking on this button triggers the fresh calculation of the PMDA Event Reportability data.

This button is not displayed when the user opens a previous case revision in the Case Form.

- Automatic method - Case Lock action
A new common profile switch has been added in Console > System Configuration > System Management > Argus J > Reporting as described below:

Key Label: Perform PMDA Event Reportability calculation on each Case Lock

Key Type: Radio Options

Key Options: "Yes" and "No"

Default Value: "No"

If this common profile switch is set to "Yes", then when the case is locked from any point in Argus Safety application, it triggers the fresh calculation of the PMDA Event Reportability data.

- The following is implemented during the PMDA Event Reportability calculation process:

- While these values are being calculated by application, a standard processing icon is displayed on the case form.

- If any unsaved changes are done by the user in the case data before clicking this button, then all those changes are considered and saved during the calculation process.

- Once the calculations have been completed, the calculated values are saved in the appropriate database tables, along with the case revision data.

- After successful completion, a standard Argus Safety message box is displayed with OK button and message - "PMDA Event Reportability data has been successfully calculated and saved with the case data for the current case revision." This is applicable only for "Recalculate PMDA Event Reportability" button click and not for Case Lock action.

- For the latest case revision, these field values are available in regular Argus Safety database case form tables.

- For previous case revisions, the field values are available in the DLP database case form history data tables.

- For the case revisions, for which PMDA Event Reportability data is not calculated, it is carried-over from its previous case revision for the case form / DLP database tables as well as for displaying it in the Case Print.

- Case Form Print > PMDA Event Reportability section > Reportability column > Reportability Status and Timeframe value is calculated / printed based on the reporting rules that existed at the calculation point.

- Other fields which are displayed as part of Case Form Print > PMDA Event Reportability section for each case revision are not required to be saved in database tables, but are calculated / printed along with the reportability fields in the Print PDF for that case revision.

- Following field values in Case Form Print > PMDA Event Reportability section are also calculated / printed based on the Console configurations that existed at the calculation point.

- Outline of Clinical Trials (J.12 section)

- Listedness As per Datasheet (based on the active datasheet as that point)

- The following note is printed at the bottom of PMDA Event Reportability section print - "# PMDA Event Reportability last calculated on case revision # <XXX> at <YYYY/MM/DD HH:mm:ss> JST", where:

- <XXX> is the case revision number as displayed in case revisions dialog for which the PMDA reportability was calculated.

- at <YYYY/MM/DD HH:mm:ss> is the time when it was last calculated as per the Japan standard time. It is calculated based in the common profile switch Argus J > Reporting > "Offset from GMT used to calculate Japanese date/time fields (in hours)"

- For existing/migrated cases, the data displayed as part of Case Form Print > PMDA Event Reportability section will not be available for previous or latest case revisions. It will be created going forward as those cases are saved by users in Argus Safety application.

- No audit log is required for these values calculated and stored in database as these as internally calculated values and no updates are allowed from any user interface.

- This PMDA Reportability data is not copied during Case Copy action.

- While calculating the earliest timeframe value for PMDA Event Reportability section, existing application logic considers only those matching reporting rules for which the reporting destination is configured as below to identify if it is a PMDA or non-PMDA reporting rule:

- Reporting Destination > Agency Type field is specified as Regulatory Authority and

- Reporting Destination > Agency Country field is specified as Japan.

1.3.4 Case Form - PMDA Analysis tab

The Case Form for the PMDA Analysis tab comprises the Case Analysis tab, the BfArM Information tab, the MedWatch Device Information tab, the AFSSaPS Info tab, and the PMDA Information tab, as depicted in the following figure:

1.3.5 PMDA E2B Report Mapping Updates

- PMDA profile E2B transmission logic for SERIOUSNESS [A.1.5.2] tags considers those events which have been included in the PMDA E2B based on event reportability criteria. This is applicable to the following tags:

- SERIOUSNESSDEATH

- SERIOUSNESSLIFETHREATENING

- SERIOUSNESSHOSPITALIZATION

- SERIOUSNESSDISABLING

- SERIOUSNESSCONGENITALANOMALI

- SERIOUSNESSOTHER

- E2B transmission logic for SERIOUSNESSDEATH tag which currently looks at death details even though it is not related to any event included in the E2B has been removed. It is transmitted as 1 (Yes), only if at least one event which is included the E2B report has Death associated with it. Otherwise, it is transmitted as 2. This is applicable to all E2B profiles - ICH, FDA, EMEA and PMDA.

- DRUGSTARTDATEFORMAT and DRUGSTARTDATE (B.4.k.12a and b): PMDA profile E2B transmission logic is also corrected to consider only the reportable events (which are included in the E2B report) when applying the following existing rule:
When a case has REACTIONSTARTDATEFORMAT and REACTIONSTARTDATE (B.2.i.4a and b) earlier than the first suspect drug's DRUGSTARTDATEFORMAT and DRUGSTARTDATE (B.4.k.12a and b), then the system does not transmit the first suspect drug's B.4.k.12a and b for PMDA reports. When there are multiple events, the comparison is executed in between the oldest REACTIONSTARTDATE, and DRUGSTARTDATE. If there are partial dates, the date are considered as 15th of the month, and the month is considered as June of the year. (The first suspect drug here means the drug for which the report has been scheduled).

- All the E2B check validations for all profiles - ICH, FDA, EMEA and PMDA, related to the following tags have been corrected to refer to only the seriousness of the events which are included in the E2B report:

- SERIOUS

- SERIOUSNESSDEATH

- REACTIONOUTCOME

- For PMDA E2B reports, if there are no reportable events for the E2B / PMDA Paper Reports, then instead of opening PMDA ICSR Validation Report with missing mandatory tag errors for REACTIONMEDDRAPT and REACTIONMEDDRALLT tags, the application displays an Argus standard messagebox with OK button and error message - 'No reportable event exists for the report'.

- This logic is applicable for PMDA Reporting Catergories A,B, C, D, H, I, J, K only.

- This logic is not applicable to downgrade or nullification reports.

- This message is displayed in all scenarios wherever the application attempts to open PMDA ICSR Validation Report directly or indirectly, including but not limited to, the following scenarios:
User attempts to open PMDA E2B report in E2B Viewer

User attempts to open PMDA ICSR Validation Report

User attempt to import follow-up E2B and the application is attempting to open PMDA ICSR Validation Report because the E2B being created for the target case does not have any reporting event.

- A common profile switch identifies the default viewing format of the PMDA E2B R3 report in the E2B viewer.

- Native XML View - All the ICH and PMDA specific elements are listed as per the PMDA E2B R3 Mapping.

- Decoded View - The ICH and PMDA element in the decoded formats are listed here as per the applicable decoded value based on the allowed values set for the element against the profile. Besides, the element number and decoded element description (both English and J) are based on the "Data Element R3" and Title/J Title respectively as specified by the PMDA E2B R3 Mapping.

- HL 7 View - The report appears with in HL7 message format as per the PMDA Guidance.

- Paper View - The report appears in PDF format as per the PMDA Guidance.

1.4 Activities Tab

- Local Lock / Unlock details are displayed as part of Routing comments log in the Case Form > Activities tab. This displays the Date of local lock/unlock, User who performed the local lock/unlock similar to the existing global lock functionality.
The text "Case Locally Locked for JP" or "Case Locally Unlocked for JP" is populated prior to the user added comments in the Local Lock screen, corresponding to the Local lock or unlock action. Note that "JP" is the standard A2 country code for the country Japan defined in the Argus Console ' Countries code list.

- When a case is globally/locally locked or globally/locally unlocked at the same time, only one entry is added to the Routing Comments log.

- The application records the corresponding routing comments described above even in scenarios where the system user (such as AGservice) performed the local lock/unlock action.

- Case Print includes the Local Lock/Unlock routing Comments as listed above, and is printed under the Routing Comments Log section.

1.5 Additional Information Tab

- Notes and Attachment section of Additional Info tab has been updated with an option to sort on the column headers (similar to Activities tab 'Action Items sorting feature) to sort the records based on the fields in Notes and Attachment section:

Field

Description

#

By default, "Upward Arrow" is displayed on the column header "#"
System displays the records in the ascending order of the sequence in which the records are entered.

On clicking the column header "#" for the first time, records are sorted in the descending order (numerically) of the Sequence number and "Downward Arrow" are displayed next to "#" column header.

On clicking the column header "#" for the second time, records are sorted in the descending order (numerically) of the Sequence number and "Upward Arrow" are displayed next to "#" column header.

On subsequent clicks to "#" column header, system toggles between "Downward Arrow" and " Upward Arrow " and its corresponding toggle functionality.

Classification

On clicking this column header for the first time, records are sorted in the ascending order (alphabetically) of the Classification and an "Upward Arrow" is displayed next to the "Classification" column.
On clicking this column header for the second time, records are sorted in the descending order (alphabetically) of the Classification and a "Downward Arrow" is displayed next to the "Classification" column header.n header.

On subsequent clicks to the "Classification" column header, the system toggles between "Upward Arrow" and "Downward Arrow" and its corresponding toggle functionality.

Keywords

On clicking this column header for the first time, records are sorted in the ascending order (alphabetically) of the "Keywords" and an "Upward Arrow" is displayed next to the "Keywords" column header.
On clicking this column header for the second time, records are sorted in the descending order (alphabetically) of the "Keywords" and a "Downward Arrow" is displayed next to the "Keywords" column header.

On subsequent clicks to the "Keywords" column header, the system toggles between the "Upward Arrow" and "Downward Arrow" and its corresponding toggle functionality.

Date

On clicking this column header for the first time, records are sorted in the ascending order (chronologically) of the "Date" and an "Upward Arrow" is displayed next to the "Date" column header.
On clicking this column header for the second time, records are sorted in the descending order (chronologically) of the "Date" and "Downward Arrow" is displayed next to the "Date" column header.

On subsequent clicks to the "Date" column header, the system toggles between "Upward Arrow" and "Downward Arrow" and its corresponding toggle functionality.

Description

On clicking this column header for the first time, records are sorted in the ascending order (alphabetically) of the "Description" and an "Upward Arrow" is displayed next to the "Description" column header.
On clicking this column header for the second time, records are sorted in the descending order (alphabetically) of the "Description" and a "Downward Arrow" is displayed next to the "Description" column header.

On subsequent clicks to the "Description" column header, the system toggles between the "Upward Arrow" and "Downward Arrow" and its corresponding toggle functionality.

- Sorting is remembered only till the time when the case is kept open.

- After the records in Notes and Attachments are sorted, if the following options are invoked without closing the case, the sort order is respected in these modules (similar to Activities 'Action Items sorting feature):

- Case Form Print

- Medical Review

- Copied Case

Figure 1-6 Case Form - Additional Information tab

1.6 Regulatory Reports Tab

- In the Argus J version of the Regulatory Reports tab, the 'Unsubmit Report' menu option (which appears from submitted reports icon for J users only) has been renamed to 'Schedule Nullification'.
On selecting this menu option, a new E2B nullification report gets scheduled against the original report but it does not change the status of the original submitted report.

- The Schedule Local Reports Only checkbox under the Total Number of Rows section in the Regulatory Reports tab of the Case Form is visible only when the configuration switch "Case Form Configuration | Auto Regulatory Scheduling is not set to None.

- If case data is updated and reporting category is also changed after a PMDA E2B report is scheduled and generated, the report must be rescheduled to populate the correct data based on changed reporting category.

- The following changes are made to the Manual Report Scheduling Dialogue:

- Urgent Report (J2.3): A new checkbox "Urgent Report" is added in the Manual report scheduling dialogue. Select this option to mark the report as Urgent Report.

- When an Urgent report is scheduled manually, the text "Urgent Report" is appended/embedded to the Report Comments adjacent to the existing text "Manual:". For example, Manual: (Urgent Report) <comments>.
The same comments appears under the Report details (Dialogue) > Scheduling(tab) > Reason for Scheduling.

- When a report against a license for which Case form > Analysis Tab > PMDA Information Tab > Comments Tab > Start date of reporting timeframe, is not "System-Calculated" and reporting destination is configured with Reporting Destination > EDI > Use Japanese Aware Date for Reporting checkbox is selected, then by default, the Aware Date appears as the date selected in "Start date of reporting timeframe" dropdown, and you can change this value manually.

- A context menu option Draft Export is added to export the report in RTF format in Draft mode.

- This context menu option appears to the J user when J License is enabled, and PMDA Paper Report (1-2, 3-4, 5-6) is scheduled against the agency configured with PMDA E2B R3 profile. Besides, the Draft link must be enabled for the respective report.

- When the PMDA E2B R3 Paper report is generated using this context menu option, the Draft water mark is embedded similar to when you generate a Draft report by using the Draft link. The data that is printed in the RTF format appears as exactly when you use Draft link for the PDF format.

- The output of the Draft export from this option adheres to Blinded/Not-blinded report requirement based on the user permission.

- The report viewed from anywhere across the application provides the option to export the PMDA E2B Paper Report (1-2, 3-4, 5-6) in RTF format by using the Export button.

- This Export button is disabled by default, and enabled only for the reports with status as Generated, Approved or Submitted.

- This Export button appears to the J user when J License is enabled, and PMDA Paper Report (1-2, 3-4, 5-6) is scheduled against the agency configured with PMDA E2B R3 profile.

- The data printed in the RTF format appears as exactly when you use the Final link for the Case Form.

- The output of the export from this button adheres to Blinded/Not-blinded report requirement based on the user permission.

1.7 Conformance Rules Tab

- Provides a framework that allows you to configure conformance rules (validations against the ICSR reporting profiles: ICH, EMA, eVAERS and PMDA) based on the individual E2B R3 Profiles.

- You can configure parameters for each ICSR Element Node for which data is transmitted.

- The Conformance Rules tab data is copied to the new profile when you copy any existing ICSR profile.

- The following table list the fields available in the Conformance Rules tab:

Table 1-6 Fields in the Conformance Rules tab

#

Field Name

Type

Description

1

Field Name/ Field Name (J)

Textbox

Enter the Field Name or Label of the Case Form or Console UI corresponding to the element's mapping logic.

- ICH, EMA, and eVAERS: English

- PMDA: Japanese

- PMDA E2B R3: See Mapping xls'Mapping(Sheet) > UI Field Name(J)

2

Field Location

Textbox

Enter the Case Form or Console UI field location or path corresponding to the element's mapping logic.

- ICH, EMA, and eVAERS: English

- PMDA: Japanese

- PMDA E2B R3: See Mapping xls'Mapping(Sheet) > UI Field Name(J)

3

Data Type

Drop Down

Select from the following options:

- <blank> (Default)

- Text

- E2B Code

- Country

- Date/Time

- MedDRA Version

- MedDRA Term/Code

- PMDA E2B R3: See Mapping xls > Mapping(Sheet) > PMDA Data Type DTD R3

4

Data Length

Textbox

Enter a numeric value.For PMDA E2B R3: See Mapping xls > Mapping(Sheet) > PMDA Length DTD R3

5

Mandatory Along with

Dropdown

Select a DTD_ELEMENT name from the list of all the elements available from the same parent of the selected element (except the selected element itself). Default value is <blank>.

For PMDA E2B R3: See Mapping xls > Mapping(Sheet) > Mandatory Along with

6

Allowed Value Check Required

Checkbox

Unchecked by default.For PMDA E2B R3: See Mapping xls > Mapping(Sheet) > Allowed Values

7

Allowed Values

Button

On Clicking this button, "Allowed value configuration" dialog box appears to configuring the allowed values for the selected elements for that profile.

This button is enabled only if "Allowed Value Check Required" checkbox is selected.

For PMDA E2B R3: See Mapping xls > Mapping(Sheet) > Allowed Values

8

Primary Validation Category

Drop Down

This option is available only for ICH, EMA, and eVAERS profile.This drop-down list has the values:

- <blank> (Default)

- Mandatory

- Conditional Mandatory

- Optional

- Other Fatal Validation

- Do not enter

9

Additional Validations

Button

On clicking this button, the "Additional Validation Configuration" dialog box appears that enables you to configure the SQL based validations for the element.This button is available only for ICH, EMA, and eVAERS.

10

PMDA Specific Fields

10.1

Reporting Category

Label

This field represents a drop-down list containing Reporting Category LM. This is a mandatory field.

Determines the report being created (ADR, Infection, Research, or Measures in foreign countries). The list values are determined at run time by the values selected in items 9,10, and 12.

When Reporting Category is not selected, the license does not create the report.All the Reporting Category R3 Codes (AA,AB,AC,AD,AE,AF,AG,DA,DB,DC,DD,DE,DF,DG,BC,BD) as configured in the Reporting Category (flex code list) are listed here, along with Nullification.

10.2

Reporting Category Description

Label

Describes the corresponding Reporting Category.

10.3

Primary Validation Category

Drop Down

This dropdown is available for PMDA profile only.

This field has the values:

- <blank> (Default)

- Mandatory

- Conditional Mandatory

- Mandatory for Completion Report

- Conditional Mandatory for Completion Report

- Optional

- Do not Enter

- Other Fatal Validation

For PMDA E2B R3: See Mapping xls > Mapping(Sheet) > Reporting Category wise Conformance

10.4

Additional Validations

Button

On clicking this button, the "Additional Validation Configuration" dialog box appears that enables you to configure the SQL based validations for the element.

This button is available against each Reporting Category.

11

Save

Button

On clicking the save button the changes are committed to the database and the audit logs.

Saving the data also includes any changes done in the "Allowed Value Configuration" and "Additional Validation Configuration" dialog boxes.

It also validates if a Primary category exists for the ICSR element.

- For Non-PMDA profile: Element Level

- For PMDA profile: Reporting Category Level

If there exists a row with primary category as blank, an error message is displayed:

"Please select a Primary Validation category for the element" Title: "ICSR Validation"

12

Print

Button

On clicking the print button, entire Conformance Rule tab data is printed.

2 Case Actions

This chapter lists the changes that have been introduced in Case Actions in the Argus Safety 8.1 release.

2.1 PMDA Event Reportability

1. "PMDA Event Reportability" has been added to the "Print Case" dialog which opens up from Case Actions > Print > Case Form (Ctrl+Alt+P) in the location specified in the mockup screen below.

- This option is displayed only for Argus J users.

- This option is enabled for the Users belonging to at least one User Group having Modify/View access to Console > Access Management > Groups > Case Form > Case Analysis-PMDA option.

- "Select All" and "Deselect All" buttons update the checkbox for this section as well.

2. On marking this option in Print Case dialog, the "PMDA Event Reportability" section is printed in the Case Form report after PMDA Comments section.

3. All the fields of the PMDA Event Reportability section in Case Form Report print data as per the version of the case opened.

4. A green dot symbol is displayed right after the Reporting Category dropdown value in Case Form ' PMDA Comments sub tab for each product license as soon as a reporting category is selected for that product license.

- Research Reporting Category:
If the user selects a Reseach Reporting Category (E, F, L, M, O and P), then the application retains the existing functionality of automatically opening the existing Research Reporting Category Justification dialog.

All existing functionality related to Research Reporting Category Justification dialog is retained as is.

- Other Reporting Category:
If the user selects any other Reporting Category, then the standard Justification dialog opens up automatically.

Manual clicking on the green dot symbol also opens up the standard Justification dialog to capture the final assessment text in Japanese for that product license as displayed below.

Figure 2-1 Case Form - Reporting Category Justification dialog

The dialog displays the list of pre-configured justification text from Justification code list for this field. By default, "Not Specified" is available in Justification code list for this field.

The justification dialog is displayed in Japanese to capture final assessment text in Japanese with max length of 20000 characters.

The title of this justification dialog is displayed as "Assessment Justification".

The justification text is optional and the green dot is always displayed for non-research reporting categories even if no justification text is specified so that user can click on it and provide it at any point of time later.

- Data fields from Justification dialogs for both research as well as non-research categories are printed in Case Form Print along with PMDA General tab > Product License section as shown below:

5. The PM DA section contains the following columns:

- Reporting Category:
This column prints the list of distinct Reporting Categories for the Japanese Product License as selected in PMDA tab in an alphabetical order.

Reporting Categories which are not mentioned in PMDA-General tab are not printed in PMDA Event Reportability section.

- Product License:
This column prints the Japanese Product Licenses as listed in the PMDA General tab against the associated reporting categories listed in the first column in the same order, as listed in the PMDA General tab.

The product licenses which do not have a reporting category assigned to them are not listed in this section.

- Assessment Reason:
This is printed at Product License level at the end of all the event rows.

It is printed in the format - "????: <Value>".

The value is printed as specified on Case Form > PMDA Comments sub tab > Product License section > Reporting Category > Research Reporting Justification dialog > "Reason for subject of the Research Report - Problems" for research reporting categories (E, F, L, M, O and P) and regular Justification dialog for all other reporting categories. for the current product license.

If no value is available to print, then only header text is printed.

- Outline of Clinical Trials:
This is printed at Product License level at the end of all the event rows.

This is printed only for Investigational Reporting categories (H, I, J, K, L, M and N). It is left blank for other reporting categories as this information is not printed in PMDA Expedited Reports for other reporting categories.

It is printed based on data from all the studies configured in Console with matching clinical compound number as for the current product license configuration.

Latest study configuration data from Console would be used to print these fields for the case revision data being printed.

It is printed in following format:

- Event (PT/LLT)
This column prints all the events entered in the case in the format: <Description as reported in Japanese (Event PT (J) / LLT (J))> as displayed on the screen mockup below.

If description as reported in Japanese is missing, then the following is printed in the Event column:

<Desc. as reported in English>

All these events are repeated against all the product licenses, listed in the same order as in the Case Form > Event Assessment tab

An Asterisk(*) is printed in this column for the events that are marked as "Do not include in Reports" in the below format:

<Description as reported in J> (PT (J) / LLT (J))*

A footnote "Event that are excluded from reportability" is printed at the end of Event Reportability section of Case Form Report if the case has events marked with "Do not include in Reports" in the Case Form Events tab.

The text "No MedDRA Term" is printed for events which are not encoded in the below format:

<Description as reported (No MedDRA Term)>

- Seriousness
If the Event is "Fatal", then '"F" is printed against the Event.

Else if the Event is "Life Threatening", then "LT" is printed against the Event.

Else if the Event is neither "Fatal" nor "Life threatening", but has any other Seriousness criteria marked, '"S" is printed against the Event.

Else "NS" is printed against the Event.

However, if the Event is neither "Fatal" nor "Life threatening" and the Console Common Profile Switch under Argus J > E2B > "Seriousness criteria in Event Reportability Matrix" is configured to "Case Level Seriousness", then the value for this column is printed same for all events based on Case Form > Analysis tab > Case Seriousness field.

- Listedness
This column prints the Listedness of the event as per datasheet followed by listedness as determined in the case. It is assessed against the same datasheet version that is used in Case Form Event Assessment tab.

This column prints 'Unlisted' for Unlisted events and 'Listed' for Listed events as per the listedness specified in Case Form Event Assessment tab.

This column prints 'Unknown for events with Listedness set to 'Unknown'.

This column prints 'Data not entered' for events without listedness entered.

While determining the listedness as per datasheet, only latest datasheet from Console would be executed against the case revision data being printed.

- Causality (As Reported / As Determined)
This column prints the Causality As reported followed by causality as determined.

This column prints the causality terms in Japanese as per the Event Assessment tab for "As Reported", and "As Determined".

This column prints 'Data not entered' for events without relatedness entered.

- Listedness Justification
If Listedness Justification (J) is available for the Product License - Event, then it is printed in a row below Seriousness, Listedness, and Causality columns.

If Listedness Justification (J) is not available, then Listedness Justification entered in English is printed.

Otherwise, Listedness Justification row is not printed.

This value is printed in the format as below:

<Justification Value>

- Causality Justification
If Causality Justification (J) is available for the Product - Event, then it is printed in a row below Seriousness, Listedness, Causality columns.

Otherwise, If Causality justification (J) is not available, then Causality justification entered in English is printed.

Otherwise Causality justification row is not printed.

This value is printed in the format as below:

<Justification Value>

If both Listedness Justification and Causality Justification are available, then these are printed in the same row but in separate lines.

- Reportability
This column prints 'Reportable' or 'Non-Reportable' based on the final reportability of the event as per the existing logic in the Event Reportability matrix.

For reporting category A and B only, if the event is not reportable as per PMDA Event Reportability matrix criteria then it is assessed if it is reportable for Non-Serious Unlisted Periodic Report (PSR Form 7-2) as per the following criteria. If it is reportable in PSR Form 7-2, then 'NUPR Reportable' is printed, Otherwsise, 'Non-Reportable' is printed.

Event is not serious as per Case Form Events tab

Event is related (either of As Reported or As Determined Casuality is reportable) for the current product as per Case Form Event Assessment tab.

Event is unlisted for the current product license as per Case Form Event Assessment tab

Event is not marked as Infection event as per Case Form Events tab

For all the events which are "Reportable", the same cell also prints the event reporting timeframe for which this event qualifies to be reported.

This value is printed right under the "Reportable" text in format - "(<xx>?)" e.g. "(15?)" (15 days)

This value is derived for each event based on the report scheduling rules configured in Console for the current license and current reporting category. The shortest timeframe from the matching rule is printed.

Latest reporting rules from Console would be executed against the case revision data being printed.

As reporting rules are executed against the case data in the database, hence any unsaved changes in the case would not be accounted while matching the reporting rules.

If no matching rules are found, then nothing is printed for event reporting timeframe.

6. If the Product, Event or Justification data do not fit in their respective columns, the text wraps within its own cell of the table.

7. This information as displayed below is printed below a header row with section label:
"PMDA Event Reportability" (similar to header row for other case form section).

8. If no data is present for this section then, it prints "No information present" in the header row itself (same as for other case form sections).

Figure 2-2 Case Form - PMDA Event Reportability section of Case Form Report

3 Worklist

This chapter lists the changes that have been introduced in Worklist in the Argus Safety 7.0.3 release.

3.1 Literature Intake Updates

3.1.1 Import Tab Changes

- When the option "Assign User" is clicked in the Context menu of Literature Intake 'Import tab, Assign pop-up displays the active J user belonging to at least one User Group having access to Console ' Access Management ' Groups ' Menus ' Literature Intake menu option.

- A new column "Assessment Group" has been added to the Import tab with filtering and sorting capability.

- Standard Argus Safety Type ahead has been provided for User group filter to display a list of user groups.

- The system displays only those User Groups that are present in the records available on the screen.

- The type-ahead field value is blank by default.

- Context menu in Import tab of Literature Intake screen contains the following new options. These options are added in the order / location as depicted in the screen mockup below.

- Modify Import date

- Assign User group

- Modify Import date for multiple items

Figure 3-1 J Literature Intake - Import tab context menu

- On clicking 'Modify Import date', a dialog is opened with import date populated in a text box for the selected Literature intake record. Users can modify this date and use 'OK' to confirm or 'Cancel' to cancel the updates.

Figure 3-2 J Literature Intake - Modify Import Date

- Users can enter the date in Standard Japanese date format. Partial dates can not be allowed. The application displays existing standard Argus Safety error message box for not allowing partial date entry, as displayed below.

Figure 3-3 J Literature Intake - Message for Partial dates not allowed

- In case of any other error in modify import date action e.g. if user blanks out the date and click OK button, standard Argus Safety error message box is displayed with message - Modify Import Date failed.

- On clicking 'Modify Import date for multiple items' the same Modify Import Date dialog is displayed for all the items for which the checkbox in the first column is checked with default value as blank. Users can specify the modified import date which is updated for all the items for which the checkbox in foe first column was checked.

- All standard validation related to partial or blank date is same as for the "Modify Import Date" action for single item.

- On clicking 'Assign User group', Assign User Group dialog is opened.

- Standard Argus Safety Type ahead feature is provided to display list of user groups.

- The system displays only those User Groups that have access to Console > Access Management > Groups > Menus > Literature Intake menu option.

- By default, the value present in the base screen is displayed as selected value. If no value was present for this field in the base screen till now, then it displays blank as default value.

- "Assign User" and "Assign Literature Type" dialogs also display the already selected values as pre-populated when invokes these content menu actions to change these.

Figure 3-4 J Literature Intake - Assign User Group

- In case of any other error in assign user group action, standard Argus Safety error messagebox is displayed with message - 'Assign User Group failed'.

- User group selected in 'Assign User Group' dialog is displayed in 'Assessment Group' column in the base screen.

- Assessment Group is printed in the Print list report generated from Import tab.

Figure 3-5 J Literature Intake - Import tab Print list

- The literature item is moved from the Import tab to the Processing tab on clicking the "Accept" option only when:

- Literature is assigned to a User (existing functionality) or a User Group or both

- Product Family is selected (existing functionality)

- Literature type is selected (existing functionality)

3.1.2 Processing Tab Changes

- A new column 'Assessment Group' has been added to the Processing tab with filtering and sorting capability.

- Standard Argus Safety type ahead has been provided for User group filter to display list of user groups.

- The System displays only those User Groups that are present in the records available on the screen.

- The type-ahead field value is blank by default.

- User Group assigned in the Import tab for the Literature Intake record is displayed for the corresponding record in Processing tab.

- A new option 'Group' has been added to the View filter. The default option has been retained as 'Individual'.

- When 'Group' option is selected, the system displays cases based on the following logic:

- Cases assigned to the current user

- Cases assigned to users belonging to the same User Group as the current user

- Cases assigned to User group to which the current user belongs

Figure 3-6 J Literature Intake - Processing tab

- Assessment Group is printed in the Print list report generated from Processing tab.

Figure 3-7 J Literature Intake - Print list from Processing tab

- If "Assessment" is not completed for Literature Data, and user selects the context menu option "Create case/Process unnecessary assessment", the system does NOT display error message 'Assessment result doesn't exist' and moves forward for case creation and displays the Book-in screen.

- If the case has been created without specifying the "Assessment" in the Processing tab, then "Processed" tab displays the values for "Assigned", "Assessment' and "Assesment Date" as blank.

3.1.3 Changes to Literature Duplicate Check

- A new column 'Assessment Group' has been added to the Duplicate Search screen - search results grid.

- When duplicate search is executed from the Case data, the 'Assessment Group' field value is left blank.

- When duplicate search is executed from the Literature Intake, assigned User Group is displayed in the "Assessment Group" column.

Figure 3-8 J Literature Intake -Literature Duplicate check

3.1.4 Changes to Existing Screen Label

- Import tab: Label "Asigned to" has been changed to "Assessment Owner".

- Processing tab: Label "Owner" has been changed to "Assessment Owner".

- Processed tab: Label "Owner" has been changed to "Screening Owner".

- Processed tab: Label "Assigned" has been changed to "Assessment Owner".

- These new labels are also reflected in their Print PDF output.

4 Reports

4.1 Reports: PMDA Expedited Reports

This section describes the J specific PMDA Expedited Report changes.

4.1.1 Report Scheduling

As part of the PMDA E2B R3 implementation, the application is enhanced for the reporting related requirements.

- Urgent Report flag: You can schedule an Urgent report for a Product License based on the value of Case form > Analysis Tab > PMDA Information Tab > General Tab > Urgent Report Checkbox for that License.

- Aware Date: You can schedule a report for an Aware Date based on the value selected in the Case form > Analysis Tab > PMDA Information Tab > Comments Tab > Start date of reporting timeframe drop-down for that License.

- Downgrade/Nullification flag: Determines whether the report is Nullification or Downgrade. The preference is given to the manually selected value Case form > Analysis Tab > PMDA Information Tab > Comments Tab > Downgrade Report flag drop-down for that License.
Besides, the logic to schedule Nullification report in case Investigation license for Event invalidation scenarios is updated to be in synchronization with Marketed Report.

- Nullification Against changed Reporting Category: Enables you to schedule both R2/R3 as Nullification report against a License for which Reporting Category was changed. The new Justification field is used as the Nullification reason.

- Aware Date/Due Date of a downgrade/Nullification reports: Schedules a Downgrade/Nullification report based on the Aware date and Due Date as per the latest case data rather than copying from previous report.

- Nullification Report Distribution flag: Enable you to maintain Downgrade/Nullification report status (to not always mark the schedule Downgrade/Nullification report) for Auto Transmission, and follows a regular follow-up report workflow (as configured).

4.1.2 Paper Reports

Argus J is able to generate and submit the following expedited paper report formats specified by PMDA (both E2B R2 and E2B R3) for drugs.

PMDA forms for Marketed Drugs:

- Drug AE/Infection case report form 1

- Drug AE/Infection case form 2 (5pages)

- Surveillance report on drug, quasi drug, cosmetic case report form 3

- Surveillance report on drug, quasi drug, cosmetic case report form 4

- Surveillance report on measures taken for drug outside Japan such as production termination, recall, rejection, etc. form 5

- Surveillance report on measures taken for drug outside Japan such as production termination, recall, rejection, etc. form 6

PMDA forms for Investigational Drugs:

- Investigational product AE/Infection case report form 1

- Investigational product AE/Infection case form 2

- Surveillance report on investigational product research report form 3

- Surveillance report on investigational product research report form 4

- Surveillance report on measures taken for investigational product outside Japan such as production termination, recall, rejection, etc. form 5

- Surveillance report on measures taken for investigational product outside Japan such as production termination, recall, rejection, etc. form 6

Besides, for PMDA R2 Report—Paper Report generation logic for PMDA Marketed Form 1 and 2, and PMDA Investigation Form 1 and 2 are enhanced to be in synchronization with CIOMS and MedWatch reports for different type of users.

The Report Form List is used in the following sections:

- Console J - Expedited Report Rules - Form section (irrespective of whether Japanese module is enabled or disabled)

- Schedule New Expedited Report dialogue - Form section (only if Japanese module is enabled)

- Medical Review - Preview of Expedited Report (only if Japanese module is enabled)

Report Handling

If an initial paper report (or a follow-up) was scheduled with Agency having the PMDA E2B R2 profile, and now the Agency configuration is updated to E2B R3 profile then the paper report respects the ongoing series and a new follow-up is generated in R3 paper format.

Note that, when submitting a follow-up report for a report submitted and received as an R2 Report, it is possible to switch to an R3 Report. However, submitting a follow-up report for a report submitted and received as an R3 Report, you will not be able to switch to an R2 Report.

Figure 4-1 Sample R3 Report

Sending a FAX report (PMDA Paper Report Form) for immediate notifications

In case of a death in a case, it is now possible to generate and send a FAX report for immediate notification to PMDA.

In the PMDA E2B profile, the Argus Safety application distinguishes the PMDA reporting destination from other partner reporting destinations configured in Argus Console, based on the Agency Type and Agency Country fields configured in the Reporting Destination code list.

The E2B or Paper Report is scheduled for PMDA only when the When Agency Type is Regulatory Authority and Country is selected as Japan.

In the event of this not being the case, the application will not transmit the J.4b value in it and will also not perform the associated validation for the J.4b value.

The E2B Viewer > PMDA Paper Report Forms view still displays the associated J.4b value for PMDA E2Bs as it is still based on an E2B report.

4.1.2.1 Additional Expedited Report Updates

The Expedited reports which are faxed to the PMDA need to be identified by which receiver is sending the information. This is done by the Additional Header information on the report output.

- The following profile switches are added to Console > System Configuration > Argus J > Reporting. These switches are specific to the Enterprise:

#

Field Label

Field Length

1

Marketed: Form 1,2

40

2

Marketed: Form 3,4

40

3

Marketed: Form 5,6

40

4

Investigational: Form 1,2

40

5

Investigational: Form 3,4

40

6

Investigational: Form 5,6

40

These switches are depicted in the following figure:

- The Reporting Destination Configuration has an Include FAX Header on PMDA Paper Reports Argus J user-specific checkbox on the Agency Configuration tab.

- This checkbox is enabled only when FAX is selected as the Preferred Method and is reset to disabled and blank when Preferred Method is set to something else.

- By default, this field is unchecked for existing and newly created Reporting Destinations.

- You can mark this option for a Reporting Destination and the changes made to this flag are audit logged and printed as part of Codelist Maintenance Print PDF.

- Fax header is printed only if the Include FAX Header on PMDA Paper Reports is marked for that Reporting Destination.

- Text entered in the Common Profile Switch is printed on the first page of the PMDA Paper Report:

- Fax header text is printed in MS Mincho font of size 16.

- Fax header text is printed in the line below the Report Format Number and is aligned to the left.

Figure 4-2 Fax Header in R2 Paper Report

Figure 4-3 Fax Header in R3 Paper Report

- If you clear the Fax Header Text for the PMDA Paper reports in the Common Profile Switch, the header is left blank in the report.

Note printed on PMDA Paper Reports > Marketed Forms 1, 3 and 5 is removed as it is a data entry description (for FAX as well as when sent through Email ) Report

Note to be removed (English Translation)

Marketed Form 1

Note: Format No.2(1) to (5) have to be attached

Marketed Form 3

Note: Form 4 should be attached together.

Marketed Form 5

Note: Attach Form 6 together.

The following figure depicts the PMDA Paper Report Sample:

- PMDA Marketed Form 1 and 2, and PMDA Investigation Form 1 and 2 Paper Report generation logic are enhanced to be in synchronization with CIOMS and MedWatch reports for different type of users.

User

Description

Restricted

User for whom Console > Access Management > Argus > User > "Protect from Printing Unblinded Information" is checked.

Non-Restricted User

User for whom Console > Access Management > Argus > User > "Protect from Printing Unblinded Information" is not checked.

Blinded Study Case

Case with a blinded study which is still not eligible for unblinding irrespective of the fact that the blind for the case is broken or not it shall be considered as a blinded case.

Blinded Report

The report for which the configured Blind Study Product is marked as Yes.

- When a restricted user generates/prints the report for a Blinded Study Case (Blinded report and Not Blinded report), if the "Blind in PMDA AE Paper Report" checkbox is selected, the profile elements are printed as blinded.

- When a Non-Restricted user generates:
Blinded Report: The application generates/prints a report as a Blinded Study Case, if the "Blind in PMDA AE Paper Report" checkbox is selected, and the profile elements are listed as blinded.

Not Blinded Report: A "Do you want to hide Unblinded Information?" dialog box appears.

If you select "No", the report is printed without blinding the any information.

If you select "Yes", the report is printed after blinding the profile elements for which "Blind in PMDA AE Paper Report" checkbox is selected.

- For blinding B.4.K.2.1 MEDICINALPRODUCT and B.4.k.2.2 ACTIVESUBSTANCENAME, the report is printed in the following format:
B_<Blinded Study Name>(B_<Study Level CCN)>)

- Blinded G.k.2.2 & G.k.2.3.r.1/ G.k.2.3.r.2(a,b)/ G.k.2.3.r.3(a,b) are printed as:

- G.k.2.2 MEDICINALPRODUCT—Prints <Study Level CCN> for the PMDA Paper report forms 1-2.
For blinded output, when CCN from J2.12 tag is printed for G.k.2.2, J2.12 is suppressed, so that it is not repeated in the same field.

- G.k.2.3.r.1/ G.k.2.3.r.2(a,b)/ G.k.2.3.r.3(a,b) ACTIVESUBSTANCENAME—Prints <Generic Name from Case form> for the PMDA Paper report forms 1-2.
In case G.k.2.3.r.1 is required to be printed along with G.k.2.3.r.2 or G.k.2.3.r.3, for blinded output, the application prints <Generic Name from Case form> only once without repeating in place of G.k.2.3.r.2 or G.k.2.3.r.3.

- For blinded output, products that are only study drugs are blinded. All non-study drugs in the case are not blinded in the Paper Form.

- Blinding J.10/J2.11 (mhlwadmicsrreporttimesevent) element is governed based on the "Blind in PMDA AE Paper Report" in ESM Mapping and "Blind J.10/J2.11 in PMDA AE Paper" of the License for which the report is scheduled (PMDA E2B R2 or PMDA E2B R3 respectively).
a. If in PMDA Profile, for J.10/J2.11 "Blind in PMDA AE Paper Report" is unchecked, then irrespective of the value the checkbox "Blind J.10/J2.11 in PMDA AE Paper " for the corresponding License against which the report (blinded or not blinded) is scheduled, and also irrespective of the Blinded status of the case, J.10/J2.11 is not be blinded for both Restricted as well as Non-Restricted user.

b. If in PMDA Profile, for J.10/J2.11 "Blind in PMDA AE Paper Report" is checked:

i. If the checkbox "Blind J.10/J2.11 in PMDA AE Paper " " for the corresponding License against which the report is scheduled is checked then irrespective of the Blinded status of the case when a restricted user prints/views the PMDA Paper Report Form 1-2 MKT/INV the application always Blinds the J.10/J2.11 data in the report, and when Non-Restricted user prints/views the PMDA Paper Report Form 1-2 MKT/INV:

* Blinded Report: The application prints/views the PMDA Paper Report Form 1-2 MKT/INV, and always Blind the J.10/J2.11 data in the report.

* Not Blinded report: The application prompts a "Do you want to hide Unblinded Information?" dialog box. If you select "No", then the report is printed without blinding the J.10/J2.11, but if select "Yes", then the report is printed after blinding the J.10/J2.11.

ii. If the checkbox "Blind J.10/J2.11 in PMDA AE Paper " " for the corresponding License against which the report is scheduled is un-checked, and the case is a blinded study case, when a restricted user prints/views the PMDA Paper Report Form 1-2 MKT/INV the application Blinds the J.10/J2.11 data in the report, and when Non-Restricted user prints/views he PMDA Paper Report Form 1-2 MKT/INV:

* Blinded Report: The application prints/views the PMDA Paper Report Form 1-2 MKT/INV, and always Blinds the J.10/J2.11 data in the report.

* Not Blinded report: he application prompts a "Do you want to hide Unblinded Information?" dialog box. If you select "No", then the report prints without blinding the J.10/J2.11, but if you select "Yes", then the report prints after blinding the J.10/J2.11.

iii. If the checkbox "Blind J.10/J2.11 in PMDA AE Paper" for the corresponding License against which the report is scheduled is un-checked and the Case is not a blinded study case, irrespective of the restricted and Non-Restricted user J.10/J2.11 is not blinded.

- You can now print the submitted Blinded PMDA Paper Report from Reports > Compliance > Submitted Reports using Print Submitted Report without getting the following error:
"Cannot print PMDA Paper Report for J E2B (Report Form Id = <report form id>, Case Num = <case num>) as user does not have access to blinded information."

4.1.2.2 Printed Paper Reports—Formatting Details

The general guidelines while printing the data in the paper form:

- Prints textual values instead of the coded values to aid human readability.

- If the number of rows to be printed in a multi-record section does not fit a page, then the same section is continued to the next page along with the table header until all the records are printed completely.

- If a non-repeatable field value exceeds the space available in the page, it is continued to the next page to print the overflowing value (like in MS word) until the full value is printed completely. All other fields are printed as per the format.

- The separators are used as:

- Comma ','—Multi byte

- Bracket '(' and ')'—Multi byte

- Colon ':'—Multi Byte

- Dash '-'—Single byte

- Null flavor printing is also supported in Paper Forms.

- True/False is printed in all forms as Yes/No respectively.

- A form starts only in a new page in the PDF irrespective of previous page data.
For example, if Form 2 Page 1 data is printed from page 3 of a report till page 4, then Form 3 Page 2 data is printed starting from page 5 and not from page 4 itself.

- If the "Include FAX Header on PMDA Paper Reports" checkbox under the Reporting Destination > Agency Information tab is checked, then the Fax header is printed in the report as configured in the common profile switches for the respective PMDA paper report under Console > System Configuration > Argus J > Reporting.

- Text entered in Common Profile Switch is printed on the first page of the PMDA Paper Report.

- Fax header text is printed in MS Mincho with font size 16.

- Fax header text is printed in the line below the Report Format Number and is aligned to the left.

- The page number is printed in the Footer (center aligned) for each page.
Format: <Current Page Number>/<Total Number of pages>

- The report page number for each page (other than the main page 1, 3, and 5) is printed in the first table within the label .
Format: Report page number<space>/<space>Total pages in that report

4.1.3 User Interface - Reporting Rules Configuration

This functionality allows configuration of Regulatory Reporting rules for scheduling Japanese reports.

The following are the functionality changes related to the PMDA Expedited reports:

- The License Category and Reporting Category fields are visible in Audit Log for Expedited Reporting Rules.

- The Reporting Rules algorithm has been updated to respect the License Category configured in Expedited Reporting Rules.

- The Reporting Category and License Category fields are printed below the Cover Letter field label under the Expedited Report Rule Information section of the print output.

- If a report is generated for a License with PMDA Device Classification 1 configured either

then a warning Incorrect PMDA Device Classification 1 configured for the license is displayed. On continuing, the report will display no information for PMDA Device Classification 1.

4.1.4 Expedited Reports on DLP

In addition to supporting revisions supported by local data entry and local locks, DLP has been enhanced to address existing gaps faced by customers while generating Expedited Reports in DLP.

A version in DLP is defined as case data that corresponds to an aware date when a significant data was received (initial receipt date or significant follow up dates).

A revision is defined as committed case data changes that spans from one version to the other and that always corresponds to a locked version.

When DLP is enabled for Expedited Report Generation:

- Global Expedited Reports are generated based on the latest DLP case revision that corresponds to the aware date on which the report was scheduled. Global reports has been generated even if the case is in unlocked state if a case version exists for that aware date on which the report was scheduled. This is applicable to both Draft and Final reports.

- If a lock does not exist for the Aware Date on which the report was scheduled, the application picks up the next immediate DLP case revision for a later Aware Date for which a lock exists.

- If no lock exists for any later aware date, see below.
Note that this is an outlier condition and the customer is expected to lock the revisions for which reporting obligation exists.

If no lock exists at all for any case revision, the report will not be generated, until the case is locked. Similarly, the Case Form will not display the Final report hyperlink or the Regenerate Report menu.

Further, the Batch Report Generation AG Service will not process the case. However, if the report is run as Draft, the report generates the draft, based on the latest case revision, even if no lock exists for any case revision.

Till this release, if more than one aware date existed in between case locks (global), the reporting scheduling algorithm determined the due date of the report based on the latest aware date, instead of the earlier aware dates in the same case processing cycle.

This has now been corrected so that the report scheduling algorithm determines the due date of a report against the earliest aware date (i.e., significant follow-up) in the case for the current case lock cycle.

Note that in this scenario, the reported data is based on the case revision corresponding to the later aware date. Also note that this scenario occurs mostly when the "Case Form Configuration | Auto Regulatory Scheduling" option is set to "Significant" or "Manual".

- Local Expedited Reports are generated based on the latest DLP local case revision corresponding to which a local lock exists for Japan country for the Japanese aware date on which the report was scheduled (irrespective of current local lock state). This is applicable to both Draft and Final reports.

- Note that the Japanese aware date is the J initial received or J significant follow-up dates if the USE_JPN_AWARE_DATE is enabled for the Reporting Destination. If the switch is not enabled, it is the global aware date. This is existing functionality.

- If a local lock does not exist for the aware date on which the report was scheduled, the system shall pick up the next immediate DLP local case revision for a later aware date for which a local lock does exists. If no local lock exists at all for any case revision, the local report shall not be generated. However, if the report was run as Draft, the report shall generate the draft based on the latest case revision even if no lock exists for any case revision, or for any case revision for an aware date later to the aware date for which the report was scheduled.

- J Expedited Reports always considers the J initial received and J significant follow-up dates as J aware date for determining due dates if the USE_JPN_AWARE_DATE is enabled for the Reporting Destination as with the existing functionality. If there is no Japan aware date or if the USE_JPN_AWARE_DATE is not set, the system defaults to the global aware date. This is applicable during follow-ups as well i.e., when there is no corresponding J follow-up date for a follow-up, the system takes the default global follow-up date.

4.1.5 PMDA Device Reports

1. Two new Japanese expedited device report forms have been added to all expedited report listing sections in Argus Safety.

- The following form options are displayed (in Japanese) to both English as well as Japanese users:
Report Form 8: Medical Device Malfunction/Infection Case Report (Form 8)

Report Form 10: Medical Device Research Report/Measure in foreign countries Report

- These form options are displayed to both Japanese as well as English users.

- These form options are supported at all the following locations in Argus Safety:
Console J - Expedited Report Rules - Form Section (irrespective of whether Japanese module is enabled or disabled)

Console J - Code list / Batch report generation (irrespective of whether Japanese module is enabled or disabled)

Case Form - Toolbar - Draft (only if Japanese module is enabled)

Schedule New Expedited Report dialogue - "Form" dropdown (only if Japanese module is enabled)

Medical Review - Preview of Expedited Report (only if Japanese module is enabled)

Create Unscheduled report (only if Japanese module is enabled)

View Submitted report (irrespective of whether Japanese module is enabled or disabled)

Bulk Report by Form (irrespective of whether Japanese module is enabled or disabled)

- These forms are not added to the Utility Blank Report Form User Interface as the Utility Blank Report Form feature has been deprecated from Argus Safety 7.0.1 release onwards.

2. These report forms open up in Microsoft Word format (.doc) from all the places in Argus Safety application as specified (but not restricted to) in the above specified list using the following forms provided by PMDA retaining all its fields, dropdowns and macros. However, these WORD forms are not meant to be edited and updated back into Argus Safety application.

- The message box which prompts to ask the user if the expedited report will print blinded data or not is not displayed for these Japan Device Report Forms as there is no blinded data printed in these reports.

- During Bulk Transmit Email process, these WORD report forms will not be merged even if Reporting Destination - Report Transmission Options have been configured to do so.

Note:
Merge feature is not required for these reports because the frequency of these Japan Device reports is quite low and there will hardly be any point of time when multiple WORD forms would exists in the system pending to be transmitted to a reporting destination.

3. These report forms are generated in Microsoft Word format (.doc) itself from both Draft and Final mode.

Note:
These Japan Device Report Form 8 and 10 are not required to be supported on DLP case revision data as of now, because other PMDA Paper Reports and E2B are also not supported on DLP case revision data.

4. No mandatory field validation will be done during generation of these report forms, except for the following. All other validations are expected to be achieved by using Case Form Field Validations feature on the desired fields of the PMDA Device Information section.

- If the value specified in Case form/Products tab/Device sub tab/PMDA Device Information section/Medical Device Reporting Category dropdown for the product for which the report is scheduled does not match with the allowed values for Form 8 or Form 10, then instead of opening the Report Form, application displays an error in the standard Argus Safety message box with OK button and the following message:
'Case does not have matching device reporting category for the selected device report form'

- The same error is logged as a report generation error, including if it occurs during background generation through Argus Safety Service. This error is also visible in the Report Details dialog - General tab at the bottom, as is displayed for the E2B generation errors.

5. Regulatory Reporting Rules Algorithm:

- The Argus Safety Expedited Reporting Rules engine also considers "Device Reporting Category" dropdown value while matching rules against cases. It gets compared against the Case Form ' Products tab ' Device sub tab ' PMDA Device Information section ' Medical Device Reporting Category dropdown field value.

- Argus Safety Expedited Reporting Rules engine scheduled the due date for these Japanese Device reports based on the Japan Aware Date, as configured in Reporting Destination configuration.

- The Argus Safety Expedited Reporting Rules engine schedules only one Japanese Device Report for each matching rule, for each suspect device product in a case, even if the case has multiple Japanese Device Licenses of the same License Type in the Event Assessment tab of the case. It also respects the Reporting Destination configuration for "Suppress Duplicate Reports", as configured.

- If multiple matching product licenses of the same device license type exist for a suspect device product in the Event Assessment tab, the license with the earliest award date of the matching product is considered for scheduling the report.

- If the original product license for which the initial / previous follow-up report was scheduled is no longer available but another product license of the same product matching the same rule exists, then a follow-up report is scheduled in subsequent cycles instead of a downgrade.
Downgrade is scheduled only when no licenses for that product matching that rule exist in the case.

6. Draft report view: The following logic is followed for PMDA Device Report Forms 8 and 10 to identify the product license when these reports are opened up in draft view, where no product license and reporting destination is not specified:

- The Draft report view is applicable to the following areas:
Toolbar - Draft icon

Medical Review screen

- It uses the first matching suspect device product as per the sort order of products in the case form products tab which has the matching "Medical Device Reporting Category" specified in the "PMDA Device Information" section.
The following criteria is used to find matching Medical Device Reporting Category for the Japanese Device Form:

Allowed Device Reporting Categories for PMDA Device Form 8:

a. Malfunction without health damage

b. Malfunction with health damage

c. Infection

Allowed Device Reporting Categories for PMDA Device Form 10:

a. Research Report

b. Measures in Foreign Country Report

Earliest award date: Japanese marketed device active license (withdrawn date later than the Initial Receipt date) of such product is used.

If Japanese marketed device license is not available, the Japanese investigational device license matching the above specified criteria is used.

If no such Japanese device license is available for the matching product, then it considers matching any (irrespective of license country or license type) earliest award date active device license for the product.

In case of multiple device licenses with same award date, it uses the license with the earliest internal license id (primary key) value.

- If no product exists with the matching "Medical Device Reporting Category" for the Report Form, then instead of opening this form, the application displays an error in the standard Argus Safety message box with OK button and message - "Case does not have matching device reporting category for the selected device report form".

- It uses the agency as specified in the Argus J common profile switch - "Default name of Regulatory Agency for Draft Expedited PMDA Reports" for such draft report views.

7. Manual Report Scheduling dialog for Argus J users is modified as specified below:
If the user selects "Downgrade Report" as a dropdown option in the dialog header, then the "Report Form" dropdown list is updated to only display E2B and PMDA Marketed and Investigational Forms 1 - 6. Other expedited report forms or PMDA Device Report Forms are not displayed for "Downgrade Report" option.

4.2 Reports: PMDA Periodic Reports

In Japan, the PMDA accepts CSV format of Non-serious, Unlisted Periodic Report as well as paper format, and many pharma companies have started to submit using CSV forms. The following is the list of the functionality changes as a result of this requirement:

- PSR ReSD configuration is enhanced by adding parameter for generating Non serious, Unlisted PSR in Paper and CSV format.

Configuration Parameter

Validation Rule

Radio button with options Paper Report(FD Report)

When TBD is set to Paper Report in the PSR Configuration screen, Non-serious, Unlisted PSR(Form 7-1 and 7-2) are generated in the Paper Form.When TBD is set to FD Report in the PSR Configuration screen:The Form 7-1 and Form 7-2 checkboxes in the PSR Configuration screen are checked and disabled.The Print the report content as Case Listing in the separate paper PSR Configuration parameter is unchecked and disabled.Non-serious, Unlisted PSR (Form 7-1 and 7-2) are generated in CSV format.The Form 7-1 is generated in Paper format along with other PSR/ ReSD forms.

- The radio button is set to Paper Report in the existing PSR Configuration for an upgraded database, if Form 7-1 or Form 7-2 is marked.

- The Argus Safety standard Advanced Conditions control (as present in English Periodic Reports) is provided in PSR ReSD Configuration screen for inclusion or exclusion of cases for all forms of PSR and ReSD reports.

UI Element

Validation Rule

Dropdown

The drop-down list displays the default options: None and New in the drop-down list. None is displayed by default.The Advanced Condition names are displayed in the alphabetical order.On specifying an Advanced condition, the system runs the query on the cases retrieved from Product selection and Reporting Time frame.

Advanced Condition Lookup button

The Advanced Condition Lookup dialog box is displayed on clicking this button.

AC

On clicking the AC button, the system displays a message with Yes, No, and Cancel buttons.If you select Yes , the system displays the Advanced Condition Query Set screen.If you select No, the system displays the Advanced Condition screen.If you select Cancel, the system closes the message.If you do not have rights to create or modify AC's, the AC button on the Japanese Periodic Report Configuration screen displays the following message in Japanese:
You do not have the rights to create new Advanced Conditions.If there is no AC specified in Japanese Periodic Configuration screen, the Advanced condition (None) is printed.If there is an AC specified in Japanese Periodic Configuration screen, the Advanced condition(<AC Name>) is printed..

- The Data population logic of FD report is the same as that of the Paper Report.

- Every J Periodic Report or Form (not limited to the ones specified below) that fetches data based on the E2B Report submitted to the authority also considers the PMDA E2B R3 report along with the PMDA E2B R2 report.

- PSR (Form 3, and 4)

- ReSD (Form 4,5,7,8, and 9, and Listed/Unlisted Tabulation)

- Seiyakukyo Clinical and Domestic Study Cases

4.2.1 DLP at Report Level

- The DLP Configuration radio buttons, Use Current Case Version and Use DLP Case Version is moved to the Report level for PSR/ReSD, CTPR, and Seiyakukyo reports. The PSR/ReSD Report Configuration screen is shown below:

- These radio button options are displayed only when DLP is enabled.

- The DLP Configuration radio buttons, Use Current Case Version and Use DLP Case Version are moved to the Report level in the Configuration Print Report of PSR/ReSD, CTPR, and Seiyakukyo reports. The PSR/ReSD Report Configuration print is shown in the screen below:

- The DLP Configuration radio buttons, Use Current Case Version and Use DLP Case Version) are moved to the Report level in the CSPR Report Configuration screen, as shown in the screen below.

- These radio button options are displayed only when DLP is enabled.

- The DLP Configuration radio buttons, Use Current Case Version and Use DLP Case Version are moved to the Report level in the CSPR Report Configuration print, as shown in the screen below.

- The DLP Configuration radio buttons, Use Current Case Version and Use DLP Case Version are moved to the Report level in the Seiyakukyo Report Configuration screen, as shown in the screen below.

- These radio button options are displayed only when the DLP is enabled.

- The DLP Configuration radio buttons, Use Current Case Version and Use DLP Case Version are moved to the Report level in the Seiyakukyo Report Configuration print, as shown in the screen below.

4.2.2 Periodic Reports on DLP

A "global" revision/version in DLP is defined as the qualifying revision/version of case data that is selected as per current logic while running a Periodic report in DLP. Today, this revision/version is based on the Japanese aware dates for Japanese Periodic reports.

A "global cleanup" revision in DLP is defined as the qualifying data clean up revision of case data that is selected as per current logic while running a Periodic report in DLP with option "Next Completed Version".

Note that today this revision/version is based on the Japanese aware dates for Japanese Periodic reports.

When Japanese Periodic Reports (PSR/ReSD, CSPSR, and Seiyakukyo) are generated on DLP using "Last Completed Version", then reportable revision of the case is the last local lock revision that corresponds to the qualifying global revision before the report end date. If there is no local lock corresponding to the qualifying global revision, then the reportable revision of the case becomes the qualifying global revision.

If there is no globally locked version, then the reportable revision of the case is the last local revision that corresponds to the qualifying global revision before the report end date.

When Japanese Periodic Reports (PSR/ReSD, CSPSR, and Seiyakukyo) are generated on DLP using "Next Completed Version", then the system searches for case revision of the last local lock that corresponds to the qualifying global cleanup revision before report end date. If there is no local lock corresponding to the qualifying global revision, then the reportable revision of the case becomes the qualifying global revision.

If there is no globally locked clean-up version, then the reportable revision of the case is the last local revision that corresponds to the qualifying global clean-up revision or qualifying global version or revision, whichever is available, before the report end date.

4.2.3 Upgrade Considerations

In the upgraded database, the DLP Configuration radio buttons at Report level are set as per settings of the parameter at Form level (prior to upgrade) for the PSR/ReSD, CSPR, and Seiyakukyo reports.

4.2.4 Advanced Conditions in J Periodic Reports

- The following changes are made to the Japanese Periodic reports when Advanced condition is used for filtering cases along with Use DLP Case version.

- ACs are applied on DLP case data for all forms of PSR/ReSD, CSPR, and Seiyakukyo reports:
If the PSR/ReSD has the Exclude events which don't meet the condition from the past data option checked, the ACs are applied as of the end date of the latest reporting period for the previous reporting period cases in the PSR: Forms 3-4 and ReSD: Forms 4-5.

If the PSR/ReSD has the Exclude events which don't meet the condition from the past data option unchecked, the system fetches the past data as per the existing functionality (without applying AC).

- On clicking the Print button in the PSR Configuration screen for generating Draft or Final PSR report:

- The system displays the following message:
Report submitted to Background Report Processing. Please view the status of the Report from Reports > Periodic Reports > Background Periodic Report Status screen.

- Upon generation of the Report, the following links are displayed in the PSR Configuration screen:
FD Reports

DRAFT link for PSR Paper report(along with Form 7-1) and CSV 1, 2, 3 links for Forms 7-1 and 7-2 OR

FINAL link for PSR Paper report(along with Form 7-1) and CSV 1, 2, 3 link for Forms 7-1 and 7-2

Paper Form report (Existing functionality)

DRAFT link for PSR Paper report OR

FINAL link for PSR Paper report

- PSR Paper report is opened in IE window on clicking on DRAFT or FINAL links.

- On clicking the links CSV1, 2, 3, the system displays the corresponding CSV file in MS Excel.
The following table illustrates the PSR ReSD Report Library:

Field separation

Comma(,)

Text separation

Double Quotation("")

File Naming convention

File name of Final CSV is as follows:COMPANY_ABBREVIATION_NAME-YYYYMMDD-001_1_{Randnum}.csvCOMPANY_ABBREVIATION_NAME-YYYYMMDD-001_2_{Randnum}.csvCOMPANY_ABBREVIATION_NAME-YYYYMMDD-001_3_{Randnum}.csvThe 3 digit number is incremented when more than one report is generated on the same day for the same company. COMPANY_ABBREVIATION_NAME is Company Identifier in Codelist > Reporting Destination > EDI
COMPANY_ABBREVIATION_NAME-YYYYMMDD-00X is printed on the bottom of the form 7-1 Paper report.

Randnum is a system generated number and is not printed on the 7-1 Paper report.

The file name for the Draft report is as per Argus Safety.

The following figure depicts the Form 7-1 in CSV format:

- On generating Form 7-1, 7-2 in FD format, 3 CSV files are generated.

- Data printed in CSV file1 is mentioned below:

- These field values are printed as it is, as in the PSR Form 7-1 PDF Output unless specified.

- In case of multiple licenses for a product, each product license and all the corresponding field values are printed as a separate row.

- During Report generation, data is truncated if it exceeds the field length specified in the Report Mapping table below:

English Title

Field Length

Data Property

Trade Name

100J

The Trade Name of each product is printed in a separate row and numbering is not used.

Generic Name

1000J

The Generic Name of each product is printed in a separate row, and numbering is not used.

Drug Classification

35AN

The Drug Action Classification is printed in a separate row and numbering is not used.

License Number

16AN

The License Number is printed in a separate row and numbering is not used.

Award Date

200J

The Japan Award date is entered in the MM/DD/YYYY format.If the Month or Day value is less than 10, it prints without 0. For example, 8/1/2011.Award date of each Product is printed in a separate row and numbering is not used.

IBD

8N

The International Birth Date is printed in YYYYMMDD format.IBD of each Product is printed in a separate row and numbering is not used.

Indication

5000J

The logic of printing data is the same as Paper Report- Column - Indication
The Indication of Product is printed in a separate row and numbering is not used.

Use

5000J

It is populated by default value.

Quantity and formulation

5000J

The logic of printing data is the same as Paper Report- Column Amount and Formulation

- Data printed in CSV file 2 is as follows:

- These field values are printed as it is in the PSR Form 7-1 PDF Output, unless specified.

- During Report generation, the data is truncated if the data exceeds the field length specified in the Report Mapping table below:

English Title

Field Length

Data Property

Investigational time frame

17N

The Investigational Unit Timeframe is printed in the following format: YYYYMMDD-YYYYMMDDFor single digit values for MM and DD, leading 0 is added.

Aware date

8N

Reporting Timeframe starting date (Assigned Date) is printed in the following format:
YYYYMMDDFor single digit values for MM and DD, leading 0 is added.

Action taken for ensuring safety and planned action for safety based on the static data

10000J

This field is used to enter the description in the output format.

Note

5000J

This field is used to enter the description in the output format

MedDRA version number

4N

The latest MedDRA J version configured in Console is printed.For example, 13.1

Report date

8N

It is printed as the current database date converted into Japan time zone (by using the common profile switch under Argus J > Reports > Offset from GMT used to calculate Japanese date/time fields (in hours) ) on which the report is being executed.It is printed in the following format: YYYYMMDDFor single digit values for MM and DD, leading 0 is added.The above logic is used in Paper Report also.

Address

200J

Sender Address: A.3.1.4a-c in the following format: [A.3.1.4c][A.3.1.4b][A.3.1.4a].It is printed as a single line with no line breaks or spaces between these field values.

Name

100J

Name of person responsible for sending report A.3.1.3b-e in the following format:[Company Name (J)] [A.3.1.3b]space[A.3.1.3e]space[A.3.1.3d]space[A.3.1.3c].A.3.1.3 is printed as a single line with no line breaks.Line break between [CompanyName(J)] and {A.3.1.3}

- Data printed in CSV file 3 is as follows:

- These field values are printed as it is in the PSR Form 7-2 PDF Output, unless specified.

- During Report generation, the data is truncated if it exceeds the field length specified in the Report Mapping table below:

English Title

Field Length

Data Property

Number

20AN

The logic of printing data is the same as Paper Report- Column Number

Preferred Term

100J

The logic of printing data is the same as Paper Report- Column Preferred Term

MedDRA code

8N

The logic of printing data is the same as Paper Report- Column MedDRA Code

Gender

1N

It is printed based on the Case Form > Patient tab > Gender field value The following is printed:1 for Male2 for Female 3 for Unknown and NULL

Age (Value)

5N

Age (Value) for B.1.2.2a E2B element
Leave the field blank when this is unknown.

Age (Unit)

3N

Age (Unit) for B.1.2.2b E2B elementLeave the field blank when this is unknown.

AE Occurring Date (Value)

8N

The Year and Month of AE is printed in the following format:YYYYMMDDYYYYMMYYYYLeave the field blank when this is unknown.

AE Occurring Date (Unit)

3N

The Year and Month of AE is printed in the following format:102 for CCYYMMDD610 for CCYYMM602 for CCYYLeave the field blank when this is unknown.

Outcome

1N

Event outcome based on the E2B code for B.2.i.8 element.

Report Type

1N

Note, Trade Name

100J

This field is used to enter the J drug code. When the code is not available, enter the Product Name (J).

Note / Remark

1000J

If this non-serious, unlisted adverse event was reported in individual expedited report during the investigational time frame, enter the reports (PMDA Acknowledgement Number).
The PMDA Acknowledgement Number is printed as "X-YYYYYYYY" where:

X is the reporting category alphabetic value (J.4a), and
YYYYYYYY is the unique identifier assigned by PMDA for the customer report submission for the corresponding E2b report (J.4b).

The PMDA Acknowledgement Number is updated in the following reports/forms":

PSR Form 4 and ReSD Form 5 -> ID Number column

PSR Form 7-2 -> Remark column

Seiyakukyo Line Listing report -> Ack Number column

When the event was reported in multiple safety reports, all the PMDA Acknowledgement Numbers are printed in this section, by printing each ID one below the other in different lines.

Leave the field blank if there is no data to output.Example: 2-05030000 2-05030011

- Upon generation of the Final PSR Report in FD format, the Report link is displayed in the Reports > Compliance > Periodic screen.

- The View Report option for the Japanese Periodic reports is renamed as Edit and View Report.

- On clicking View and Edit Report for the mixed PDF and CSV PSR Report, the View and Edit dialog box is displayed with separate options to view PDF and CSV report.

- On clicking View and Edit Report for the PSR Report (Paper format), CSPR, and Seiyakukyo reports, the View and Edit dialog box is displayed by hiding the following:

- Label: Select one of the actions below

- Labels: CSV1, CSV2, CSV, and its corresponding Checkin/Checkout and Comments buttons.

- Button: FD Report Validation

English Label Name

View and edit PSR/ReSD

Properties

Title

English Label Name

Select one of the actions below:PDF OutputCSV1CSV2CSV3

Properties

Fixed labels

English Label Name

View

Properties

- This button is always enabled (regardless of the Checkin/Checkout status) for all users.

- On clicking the View button for CSV report before/after Publishing, the system opens the CSV Report in Excel in Read-only mode.

- On clicking the View button for Paper report before Publishing, the system opens the report in Word.

- On clicking the View button for Paper report after Publishing, the system opens the Final report in PDF format.

English Label Name

Checkin

Properties

- This button allows you to check-in the individual reports.

- When the Checkin button is clicked for a CSV report, the Argus Safety standard Checkin dialog box is displayed.

- The Check In dialog box captures the comments for 255 characters.

- The system allows you to specify only .csv files in the Filename field. If you upload some other file type and click OK, the following standard message application is displayed by this common file upload control:
This is not valid file to upload. Allowed file types are {X}

- When the Check-in button is clicked for a Paper report, the Argus Safety standard Checkin dialog box is displayed to specify the report file name and Checkin Comments.

- The system allows only .doc files to be specified in the Filename field. If you upload some other file type and click OK, the following standard message is displayed by this common file upload control:
This is not valid file to upload. Allowed file types are {X}

English Label Name

Checkout

Properties

- After the report is checked-in, the Checkin button is changed to Checkout.

- The Checkout button is disabled after the report is published.

- Only one user is able to checkout a report.

- When the Checkout button is clicked for a paper report or CSV report, the system displays the Checkout dialog box:

- The Checkout dialog box allows you to specify the checkout comments of a maximum size of 255 characters.

- OK and Cancel buttons are provided in the Checkout dialog box:

- The Cancel button cancels the Check Out operation and closes the Checkout dialog box.

- On clicking the OK button for a Paper report, the system opens the report in Microsoft Word in the Update mode.

- On clicking the OK button for CSV report, the system opens the report in Microsoft Excel in the Update mode.

- After the report is checked out, the Checkout button is changed to Checkin.

- The same user uses this button to checkin the revised checkout file. For other users, this button becomes disabled as long as it is checked-out by the original user.

- If you open the Checkout dialog box and completes the Check Out operation after sometime (after another user has already checked - out the report), the following message is displayed:
Report cannot be checked-out as it is in use by another user

English Label Name

FD Report Validation

Properties

- This button is enabled only after all the CSV and WORD reports are checked-in at least once. When this button is clicked, data in all the CSV files are validated.
When there are no error messages, the Argus Safety standard message box with message -

No problem was found in the report is displayed with an OK button.

- The following validation is executed and the errors are displayed in the form of PDF report.

- The character check is executed. If there is invalid character specified:
(Item [X-X], Row YY: Invalid character is used)

N (Numeric) - Only 0-9, ., E, +, and - that are used for displaying integers or floating point representation are allowed. Full-width characters are not allowed.

AN (Alpha Numeric) - half-width (1byte) alphabet, Numbers and special characters specified in Argus J common profile switch - Characters to be allowed to use in AN (Alphanumeric) E2B items are used. Full-width (2byte) characters are not used.

J (Japanese) (100J mean 50 double byte J chars) - Full-width characters and AN are used which is same as E2B J validation. Characters specified in Argus J common profile switch - Additional invalid character to be checked in Japanese character validation is considered.

- Field length check is executed. If there are more characters than the maximum length, the following message is displayed:
(Item [X-X], Row YY: Numbers of characters is exceeding the defined maximum value.)

- The data format for data items 1-5,1-6,2-1, 2-2, 2-6 in above Data Property is checked, and when format is not correct, the following message is displayed:
(Item [X-X], Row YY: Data format of the column is invalid)

The Validation errors belonging to the data from the CSV files are listed separately. The errors within the CSV file are listed category wise such as Character check, Field length, and Data Property. If there are no errors for all property checks for a CSV file, No problem was found in the report is printed below the CSV#.

- The following validation message in FD Validation report is displayed, when column in CSV does not match with the format specified by Regulation:
The structure of the columns in the CSV file is not in required format

This validation is verified first on clicking FD Report Validation button. If the structure of the CSV file is not in required format, the further validations are not checked for that CSV file.

English Label Name

Publish

Properties

- The Publish button is enabled only after all reports are checked-in at least once.

- This button is disabled when any of the report is checked out.

- When the report is not published, you can check in/checkout the report as many times as you want.

- After the Publish button is executed and the PDF file is created only for Paper report, the system automatically opens only the Paper report on the UI. In addition, the Check-in / Check-out button is disabled and the label is changed to Check-out.

- The Publish button converts the checked-in Paper report in word document to the PDF file as it is with the same layout. The CSV report that is checked in remains as is and is not converted to PDF.

- Once Publish is done, the Paper report in word format of the report is no longer available from the Final link and the PDF format overwrites the generated/updated Word format in the database. The Draft link generates the fresh report in Microsoft Word format.

English Label Name

Close

Properties

On clicking this button, the system closes the View and Edit Report dialog box.

English Label Name

Comments

Properties

- On clicking this button, the Comments dialog box is displayed with the Check-in/Checkout comments.

- The comments are displayed pertaining to the PDF/CSV for which Comments button is clicked.

- The Comments dialog box displays the Version Number, Username, Action, Date(Time stamp in User Local date with GMT offset), and Comments entered in the descending order of the Dates.

- Version of the first check-out is considered version 1.

- Version number is incremented on every Check-in.

- Version number is not displayed for subsequent checkout (after first checkout).

- The Comments dialog box is closed on clicking the OK button.

- The Report Submission process is the same as other PSR forms.

- The following Common Profile Switches are moved from Common Profile Switch > ARGUSJ > E2B to Common Profile Switch > ARGUSJ > Reporting in Fresh and Upgraded database.

- Additional invalid characters to be checked in Japanese character validation.

- Characters to be allowed to use in AN (Alphanumeric) E2B items.

- Perform Japanese character validation at E2B Check and E2B Report Generation.

- The Perform Japanese character validation at E2B Check and E2B Report Generation Common Profile Switch is renamed as Perform Japanese character validation at E2B Check, E2B and Periodic Report Generation. This change in the Common Profile Switch is applicable for upgraded database.

Note:
In the future, all periodic report will have the same CSV format options.

4.2.5 Check in/Checkout Enhancements

Checkin/Checkout dialog box changes described above for PSR/ReSD reports are applicable for the following Japanese reports:

- CSPR

- Seiyakukyo Report

4.2.6 Other Changes

The TEXT_J data for TRANSLATION_ID ='User Name' is misspelled in LM_TRANSLATION_LABEL table.

4.2.7 Periodic Safety Report

4.2.7.1 Format

The system allows the definition of PSR reports for products. The purpose is to define a fixed set of PSR reports for PRIMARY AGENCY (the various regulatory authorities as optional) and then associate products with these reports. The PSRs can then be scheduled automatically.

PSR applies only for Japanese licenses.

- The system contains a configuration screen to define a PSR report. A new menu item, Reports > Periodic Reports > PSR/ReSD Reports is created. When this is clicked, the following page is displayed.

PSR Main Window

- If the report is being currently opened by another for modification, the system displays the following message:
The report which is selected is being used by XXXX and cannot be modified.
where XXX is the full user name of the user has opened it.

- The labels and buttons related to the CSV files and FD validation reports are hidden in the Edit and View Report dialog box invoked for the PSR Report (Paper format), CSPR, and Seiyakukyo reports.

- The Create from Template button that is available on Argus E PSUR and CTPR section is not added for Japanese PSR, ReSD configuration.

- This page displays a list of the PSR reports stored in the system.

- You can add a new report by clicking on the New Report button.

- The Copy button makes a copy of an existing report:
When you copy an existing PSR Report, all the configuration of the report including timeframe rows are copied.

Report Name of new copy has copy of in front of the name.

When the configuration is copied, the past dates in the schedule frequency, JAD, IBD, and Assigned date are also copied as read-only. The other sections of the copied configuration are editable.

When you copy an existing non-submitted PSR report, all the configuration including timeframe rows are copied. As the original report is non-submitted, all the timeframe rows are retained as non-editable or editable as they were in the original PSR. The JAD, IBD, and Assigned Date become editable or non-editable depending upon if there are timeframe rows in the copied PSR which are non-editable.

- The Modify button displays the report definition.

- The Delete button allows you to delete a report after displaying the following confirmation message:
Proceeding to Yes will remove the report configuration. Proceed?

- Clicking Print, results in displaying a new dialog prior to report preview allowing you to select from several preview or direct export options: Word output.

- The Delete option is only available if there are no final reports generated for the Periodic Reports. The Delete option only hides the report from the list.

- In the recently executed Periodic Report section, a link is available for the last executed report only if the Report is still available on the Report Server.

- Clicking New or Modify in the above screen displays the PSR Configuration Window.

- Once the state of the report is changed to Submitted, you cannot update the configuration of that PSR. This is done by disabling the OK button. For example, when the state is un-submitted, the report is editable again. In addition, when the non-editable configuration is opened, the following warning message is displayed:
This configuration is not modifiable because the status of this Periodic Safety Report is Submitted
When you click OK, this displays the Configuration window.
When you click Cancel, the configuration window is not displayed.

- When the status of the report is Submitted, only the configuration page is printed.

- The Copy can be done any time while the configuration exists.
When you create PSR after 2nd time, the new copy of the configuration is required. You can then modify the content to print the current PSR.

- Before saving the PSR configuration, Report Name, Primary Agency, Product Selection, and at least one time frame need to have a value entered.
When these are not entered, the following messages are displayed:

When Report Name is not entered:

Report Name is not entered

When Primary Agency is not entered:

Primary Agency is not entered

When selected product is not available:

Product is not selected

When At least one time frame is not entered:

Investigation time frame is not configured

The following message is displayed along with the above error:

It is necessary to enter above information in order to save the configuration

- When Modify, Copy, Delete, or Print button is clicked without a selection of report, a pop-up is displayed to select a report.

4.2.7.2 PSR /ReSD Details

4.2.7.2.1 Subject of Report

Field Name

Description

Report Name

Manually Input a Name for the Report. It is displayed in the Reports > PSR Reports dialog box.

Report Category

Manually Input a Name for a Report Category. It is displayed in the Reports > PSR Reports dialog box.

Primary Report Agency

This list contains the Regulatory Authorities configured in List Maintenance > Regulatory Authorities (LM_REGULATORY_CONTACT table).
If there is no Japanese Authority name configured, the English name is listed.

The system allows you to select multiple agencies from the List of Agencies such that the report can be submitted to multiple agencies at the same time.The primary agency can be defined in this drop- down.When Japanese Message Profile is not configured in Console J for the selected Primary Agency, or when you add the agency with PMDA E2B R3 (or R2) in the Report Configuration, an error message is displayed as:

Selected Primary Agency doesn't have configured Message Profile (I or J) in Argus Console > Reporting Destination/EDI.

Once you click OK, the selection of the Primary Agency goes back to the previous selection. This check is executed when you try to go to the other tab, or click OK to save the configuration.

Report Number

Manual entry text field that allows you to enter a report number.

Print all configuration criteria on separate cover page

Check box to print out the configuration of this report when the report is printed. When this is clicked, the Configuration page is printed at the beginning of the PSR/ReSD word print output. The page numbering of the PSR/ReSD does not include the Configuration page.

4.2.7.2.2 Product Selection

Field Name

Description

Available Ingredients

This list contains the Ingredients used for the products configuration. It is stored in the LM_PF_INGREDIENT_J table once a product has been configured.
The system allows filtering the Ingredients within the available list of Ingredients by a entering the Ingredient name and clicking the Filter button.

The search is performed in Japanese ingredient name only. If the name is blank, enter English ingredient name.

Filter

Indication

This list contains the Indication configured for the product containing the ingredient in C5 section. Use this to narrow down the products displayed in C8.The system allows to multi-select Indications using the standard Windows functionality of CTRL+CLICK.If Japanese name is not available, the English name is displayed.

Available Products

This list is auto-populated once the Ingredient has been selected and displays all products from the LM_PRODUCT J table, containing the ingredient selected in C5 section. The format is Product name (Formulation, Concentration concatenated with the Concentration Units). If Japanese name is not available, the English name is displayed. The withdrawn products are displayed as well.

Selected Ingredients

When an ingredient has been selected, all products containing that ingredient are displayed in Available Products section. Multiple Ingredients can be selected at once to form a PSR product family.

Formulation

This list contains the formulation configured for the product using the ingredient in C5 section (LM_FORMULATION table). Use this to narrow down the products displayed in C8.The system allows to multi-select formulations using standard Windows functionality of CTRL+CLICK.If Japanese name is not available, the English name is displayed.

Selected Products

This list contains products that are selected from the Available Products list (C8). When at least one product is selected, the field has a blue background color. If the license is not withdrawn at the starting date of the PSR investigation timeframe, include the license in PSR and ReSD.

Additional Information

- When no Japanese ingredients, indication, or formulation is configured in the Console, the English names are displayed.

- If the product is added or deleted in the Product Selection section before the PSR/ReSD status is marked as Submitted, it displays a warning pop-up:
If the content of selected product is changed, IBD, JAD, and Assigned date can possibly be changed. Do you want to proceed?).

- If you add or delete the products in the Product Selection section before the first PSR report is marked as Submitted, it updates the IBD, Japan award date, and Assigned Date based on the new product set.

- When you copy an existing submitted PSR report, and JAD, IBD, Assigned dates are non-editable (you have not clicked the RESET button yet) and If you change the product selection, JAD, IBD and Assigned dates do not change. When this occurs, the following warning message is displayed:
Because the configuration has the record of past investigation period, JAD, IBD, and Assigned Date for scheduling configuration will not be changed by modifying the Selected Products. It is necessary to use the Reset button and re-configure the investigation period if new PSR needs to be created based on modified product selection.

- All the forms printed as PSR and ReSD have only the information regarding the selected product in this configuration window.

4.2.7.2.3 Periodic Safety Report/ReSD

Field Name

Description

Forms configuration

This field represents the main title of the UI.

Periodic Safety Report

This radio button is available to select either PSR or ReSD, so that you can create PSR and ReSD independently.This is selected as Default

Re-examination Submission Dossier

This radio button is available to select either PSR or ReSD, so that you can create PSR and ReSD independently.

Data counting configuration

Count Configuration

Exclude events which don't meet the condition from the past data

When this is checked, the events that were reported in the past PSR, but do not meet the condition at the end of current investigational timeframe are subtractedEvent was downgradedReport was nullifiedWhen this occurs, following message is printed under the first table of form 3:
Among the Events that were count in the past report, there are nullified/became non-reportable during this investigational time frame.

This is not checked by default.

Exclude events which were reported by Paper report form

When this is checked, the events that were reported by Paper Form during the investigational time frame are excluded.This is not checked by default.

Exclude Incompletion report from output

When this is checked, the events reported as incompletion report during the investigational time frame are excluded.This is not checked by default

PSR Report Form 3

Form 3 Selection (Check box)

If this is checked, PSR Form3 is printed.This is checked by default.

Print Only the Term Preferred Term (Radio Button)Lower Level (Radio Button)

This field allows you to decide which term (PT or LLT) is to be printed on the form3.PT is selected by default.

Classify based on SOC

If this is checked, the PSR Form 3 PT/LLT section is grouped by SOC. In this case, the name of the SOC is listed at top of the section, and --- is used for separator between SOC and PT/LLT. Bold line is used for separating the groups.This is checked by default.

Print the report content as Case Listing in the separate paper

When this is checked, the case listing of the report content is printed out on a separate paper. All the configuration reflects the case listing.This is not checked by default.

PSR Report FORM 4

Form 4 Selection (Check box)

If this is checked, the PSR Form4 is printed.This is checked by default.

Print Only the Term

This field allows you to decide which term (PT or LLT)is to be printed on the form4.PT is selected by default.

Order SOC Alphabetically (Check box)

If this is checked, the SOC is printed in alphabetical order. If not checked, the SOC order is same as that of the MedDRA order.This is not checked as default.

Non-Serious Unlisted PSR Report

Drug Non-Serious, Unlisted PSR

This field represents the title of the section.

Paper ReportFD Report

Radio buttons:When Paper Report is selected, Paper report format is generated.When FD Report is selected, CSV report format is generated.When FD report is selected, both 7-1 and 7-2 forms are checked in the checkboxes and these cannot be edited. Paper Report is selected by default.

PSR Report FORM 7 - 1

Form 7-1 Selection (Check box)

If this is checked, the PSR Form7-1 is printed.This is checked by default.

Print Blank Form

By checking this, the blank form is printed.This is not checked by default.

PSR Report FORM 7 - 2

Form 7-2 Selection (Check box)

If this is checked, the PSR Form7-2 is printed.This is checked by default.

Print the report content as Case Listing in the separate paper

When this is checked, the Case listing of the report content is printed out on a separate paper.This is not checked by default.

Separate Page Numbering (Check box)

When this is checked, the Page number is independent (starts from 1) for each form.This is checked by default.

Use Current Case VersionUse DLP Case Version

This radio button control is only displayed if DLP is enabled.
Use Current Case Version is selected by default.Based on the PSR Configuration for DLP, the report is executed accordingly using latest Case Revision or using the DLP Case Revision.

ReSD Report FORM 4

Form 4 Selection (Check box)

If this is checked, the ReSD Form4 is printed.This is checked by default.

Print Only the Term Preferred Term (Radio Button)Lower Level (Radio Button)

Allows you to decide which term (PT or LLT) you want to print on form4.PT is selected by default.

Classify based on SOC

If this is checked, the PSR Form 3 PT/LLT section is grouped by SOC. In this case, the name of the SOC is listed at the top of the section, and --- is used as separator between SOC and PT/LLT. Bold line is used for separating the groups.This is checked by default.

Print the report content as Case Listing in the separate paper

When this is checked, Case Listing of the report content is printed out on a separate paper.This is NOT checked by default.

ReSD Report FORM 5

Form 5 Selection (Check box)

If this is checked, the ReSD Form5 is printed.This is checked by default.

Print Only the Term

Allows you to decide which term (PT or LLT) is to be printed on form4.PT is selected by default.

Order SOC Alphabetically (Check box)

If this is checked, the SOC is printed in alphabetical order.
If this is not checked, the SOC order is same as that of the MedDRA order.This is not checked by default.

ReSD Report FORM 7

Form 7 Selection (Check box)

If this is checked, the ReSD Form 7 is printed.This is checked as default.

ReSD Report FORM 8

Form 8 Selection (Check box)

If this is checked, the ReSD Form 8 is printed.This is checked by default.

ReSD Report FORM 9

Form 9 Selection (Check box)

If this is checked, the ReSD Form 9 is printed.This is checked by default.

ReSD Report Tabulations

Tabulations

If this is checked, all the tabulations in the section are checked and included in the print.This is checked by default.

Tabulation for Unlisted Events

When checked, this tabulation is included in the print.This is checked by default.

Tabulation for Listed Events

When checked, this tabulation is included in the print.This is checked by default.

Case Overview Tabulations

When checked, this tabulation is included in the print.This is checked by default.

Overdose Tabulation

When checked, this tabulation is included in the print.This is checked by default.

Accident Exposure Tabulation

When checked, this tabulation is included in the print.This is checked by default.

Additional Information

- Separate page numbering always follow the previous form of PSR and ReSD. The following is the order of the page numbering sequence:
PSR Form 3, 4, 7, 7-2, ReSD Form 4, 5, and 789

- When you select PSR, ReSD using the radio button, the system selects all the forms available for each set of report automatically (PSR - above table 1, 7, 10, and 13) (ReSD - above table 15, 20, 23, 25, 27, and 29). By default, PSR is selected and PSR forms are selected.

- If the radio button is used to select the PSR form, the previously checked forms on the ReSD are unchecked. If the radio button is used to select the ReSD form, the previously checked forms on PSR are unchecked. While the PSR is selected, the ReSD section is disabled. While ReSD is selected, PSR section is disabled.

- If you close the configuration and opens again, the configuration on the UI remains as it was at the time of the last operation.

- All the forms format are based on the Novartis PSR form sample.

- You are not allowed to change the configuration parameters for PSR Form 3, 4 and ReSD Form 4, 5; if there are any past (non-editable) timeframe rows. If there are past timeframe rows in the scheduling frequency table, configuration of the PSR Form 3, 4 and ReSD form 4, 5 is non-editable.

- When you check the Print the report content as Case Listing in the separate paper, the Case Line Listing along with the report content is printed on a separate paper.

- The Case Listing is printed only for the current timeframe for PSR form 3, ReSD Form 4 and PSR Form 7-2.

- This line listing is independently printed (using separate page) regardless of the Configuration Printing check box status. If you checked the option to print out the configuration content and Case Listing, the Case Listing is appended after the configuration content.

- The order of the print is Configuration > Form 3 Line Listing > Form 7-2 Line Listing > All the actual reports

- The Case Line Listing report does not follow the Separate Page option. The Case Line listing is always separated and starting from page 1 for each form.

PSR Form 3 Case Line Listing

#

Field Name

Description

1

PSR/ReSD Case Line Listing

This field represents the section title.

2

Periodic Safety Report

This field represents the 2nd title.

3

Periodic Safety Report form #3

This field represents the title for Form 3 section.

4

Types of adverse event

The List of AEs are printed using exactly the same rule and order as that of the PSR Form 3.

5

Case Number

All the reported AE's case numbers are printed in this field. These case numbers are separated by comma.

6

Number of AEs reported during this timeframe

Number of the AEs available also on the PSR form 3 for this report's investigational timeframe.

PSR Form 7 Case Line Listing

#

Field Name

Description

1

PSR/ReSD Case Line Listing

This field represents the section title.

2

Non Serious, Unlisted Periodic Safety Report

This field represents the 2nd title.

3

List of non-serious, Unlisted adverse event

This field represents the title for Form 7-2 section.

4

(form 7 body)

This section is always same as the PSR form 7.

5

Case Number

The Argus case numbers are added using this field.

ReSD Form 4 Case Line Listing

#

Field Name

Description

1

PSR/ReSD Case Line Listing

This field represents the section title.

2

Re-examination submission dossier

This field represents the 2nd title.

3

ReSD Form #4

This field represents the title for Form 4 section.

4

Types of adverse event

List of AEs are printed using exactly the same rule and order as that of PSR Form 3

5

Case Number

All the reported AE's case numbers are printed in this field. These case numbers are separated by comma.

6

Number of AEs reported during this timeframe

Number of the AEs available also on the ReSD form 4 for this report's investigational timeframe.

4.2.7.2.4 Scheduling

Field Name

Description

Delivery quantity

This field represents the title of the section. This section displays the delivery quantity information for each timeframe row, when that row is clicked.

Clear All

When you click this button, all the entered information on this UI is cleared (The data entered by you only. For example, the Delivery Quantity and Delivery Unit for all the products in the Delivery Quantity section is removed but the product names remain in each row.When this is clicked, a confirmation window with the following message is displayed:
If you continue, the entered information is erased. Do you want to continue?.

The content in the UI is deleted when you enter OK.No actions are taken on the table if you select Cancel in the message window.

Products

Product names used in this PSR appear as default. The names can be changed only at first report generation. From second report, names are read-only unless they are newly added.The maximum text length is 70.

Delivery quantity during this period

This field represents the text entry for numbers.The maximum text length is 12 (including the decimal point and number). Only numeric character and decimal point are allowed.

Unit

Type ahead functionality with console J Unit (J). For the units data that does not have unit(J), if unit (J) is not available, the field is left blank.You can change the unit only at first report generation.

Total Amount

Text entry for number. Only when the entered units are the same, the calculated total from above is displayed in this field. Maximum text length is 15 (including the decimal point and number). Only numeric character and decimal point are allowed.

Entering the Delivery Quantity

Delivery quantity table is entered into the report only when this is checked. This is unchecked by default. If this is not checked, the Delivery section of the report is blank (unchecking does not delete the values in UI).

4.2.7.2.5 Security

4.2.7.2.6 Printing PSR / ReSD

Field Name

Description

Report Batch Printing

Run at

You can specify the time of Reporting using this field. The date entry is in Japanese.

Run Now

This field represents the Print now option.

Print As

You can select printing option from Final, Draft, Internal, or Other.

Other

Due Date

Automatically populate the calculated value by using the due days.

Generating the Document

Generation of the document is executed using the following process:

1. Click View Report in the Reports > Compliance > Periodic Reports.

2. Check-out the report from the View and edit PSR/ReSD pop-up.

3. Edit the checked-out word document

4. Check-in using the same View and edit PSR/ReSD pop-up.

5. Publish the PDF file (converting from the checked-in word doc)

Printing Requirements

- The system allows you to Print the Report and update the Report output in the Word document.

- The change of the configuration for the same investigation timeframe can be done multiple times only before the status is changed to Submitted. The changes in the configuration after the Submitted status of the PSR is applied on the next investigational time period.

- From the Reports > Compliance > Periodic Reports, selecting View Report allows you to View the PSR/ReSD Report in Word document to upload the report.

- When the J user opens Reports > Compliance > Periodic Reports from the menu, the Japanese UI is displayed for Periodic report list. The pop-ups for the PSR View and Edit are Japanese.

Field Name

Description

Trade Name

The J UI displays available Japanese data. When Japanese data is not available, the English data is displayed.The Trade Name section displays the multiple trade names using comma separated list of the selected products.The Trade Name displays the original product selected: English or Japanese. If PSUR was created for the English product names, the English product name is used in the list. If the PSR is created with the Japanese product names, the Japanese product name is used in the list.If the selected product in the PSR does not have the Japanese Trade name, the English trade name is displayed for that PSR.

Destination

The Japanese UI displays the available Japanese data. When Japanese data is not available, the English data is displayed.When Destination is not available, display No specific receiver.

Description

The Japanese UI displays the available Japanese data. When Japanese data is not available, the English data is displayed.

Due Date

English date format is DD-MMM-YYYY.Japanese date format is YYYY/MM/DD

Status

Status appears in Japanese in the Japanese UI, and in English in English UI and can have the following possible values:
Deleted

Scheduled

Generated

Approved

Disapproved

Submitted

New Data Available

No Longer Required

- The report output is in Word Document. This works in the similar way as ePSUR publishing where you are allowed to edit the Word output outside the system and once generated, can publish the FINAL Word Document.

- When the report is generated and never checked out, the center button display Check-out to let you revise the document. At this time, Publish button is disabled.

- Check-out can be executed by one user only. Other users cannot check in the checked-out files.

- Once the check-out is executed, the Check-out button is changed to the Check-in button. This button is used to check-in the revised checkout file.

- When the file is checked-in, the center button is changes to the Check-out button.

- When the file is not checked-out or not published, you can check-in/check-out the file as many times as you want.

- When the file is not checked-out or not published, the group which has the access rights to this report can execute the check-in, check-out, and publish.

- The View button is always enabled (regardless of the check in/check out status). It displays the latest updated Word document or the PDF after final Publish.

- The Publish button is enabled after at least one time of the check-in action. The Publish button is disabled when the document is checked-out.

- Once the final Word file is created, the Word document is saved in the repository. All the past PSR word output are saved. When you update the Word document and uploads it, the system overwrites the automatically generated document in the database.

- Once the Publish button is executed and the PDF file is created, the Check-Out button is grayed out and disabled.

- Once the document is checked-in, the Check-in button is changed to Check-out, and the Publish button is enabled to publish the PDF report from the Word document.

- The Publish button converts the checked-in Word document to the PDF file.

- Once Publish is done, the Word document is no longer available. The Check-in / Check-out button is disabled only when the PSR is published and the label is changed to Check-out.

- When the Check-in button is clicked, the following pop-up is displayed to specify the file name. This can be done by either specifying the file name in the text box, or selecting the location using the Browse button.

- If the data is changed manually in the Word document, this change is not applied to the next report. The report needs to be changed again.

- The configuration of the PSR/ReSD can be edited while the PSR is checked-out. The change is affected only when the PSR is created again.

4.2.7.2.7 Deleting PSR / ReSD

Click Yes in the prompt shown below to delete the PSR/ReSD report.

4.2.8 Clinical Study Periodic Safety Report (now J-DSUR)

Note:
The Clinical Study Periodic Safety Report (CSPSR) is now known as J-DSUR.

4.2.8.1 Format

The system allows configure and output J-DSUR defined by the PMDA for products. The purpose is to define a fixed set of J-DSUR for PRIMARY AGENCY (the various regulatory authorities as optional) and then associate products/studies with these reports. The J-DSUR can then be scheduled automatically.The J-DSUR applies only for Japanese licenses.Argus J is capable of output J-DSUR Form 1 and Form 2.

- The system contains a configuration screen to define a J-DSUR report. A new menu item, Reports > Periodic Reports > J-DSUR ) has been created. When this is clicked, the following page is displayed.

J-DSUR Main Window

- If the report is being currently opened by another user for modification, the system displays the following message:
The report which is selected is being used by XXXX and cannot be modified.
where XXX is the full user name of the user who has it opened.

- The Create from Template button that is available on Argus E PSUR and CTPR section, is not added for Japanese PSR, J-DSUR configuration.

- This page displays a list of the CSPSR/J-DSUR reports stored in the system.

- You can add a new report by clicking the New Report button.

- The Copy button creates a copy of an existing report.
When you copy an existing CSPSR Report, all the configuration of the report including timeframe rows are also copied, and the CSPSR report gets converted to J-DSUR.

When you copy an existing J-DSUR Report, all the configuration of the report including timeframe rows are also copied.

The Report Name of the new copy has Copy of in front of the name.

When the configuration of already Submitted report is copied, the past dates in the schedule frequency, CSPSD, and Assigned Date are also copied as read-only. Other sections of the copied configuration are editable.

When you copy an existing non-submitted J-DSUR report, all the configuration including timeframe rows is also copied. As the original report was non-submitted, all the timeframe rows are retained as non-editable or editable as they were in the original J-DSUR.

- The Modify button displays the report definition.

- The Delete button allows you to delete a report after displaying the following confirmation message:
Proceeding to Yes will remove the report configuration. Proceed?.

- Clicking Print results in displaying a new dialog box prior to Report Preview allowing you to select from several preview or direct export options: Word output.

- The Delete option is only available if there are no Final Reports generated for the Periodic Reports. In any case, the Delete option only hides the report from the list.

- The generated last executed report is available from a link that fetches the report from the database.

- Clicking New or Modify displays the J-DSUR Configuration Window.

- Once the state of the report is changed to Submitted, you are not able to update the configuration of that J-DSUR. This is achieved by disabling the OK button. For example, when the state is un-submitted, the report is editable again. In addition, when the non-editable configuration is opened, the following warning message is displayed:
This configuration is not modifiable because the status of this J-DSUR is Submitted.
When you click OK, the Configuration window is displayed. When you click Cancel, the Configuration window is not displayed.

- When the status of the report is Submitted, only the Configuration page is printed.

- Copy can be done any time while the configuration exists.
When you create J-DSUR after the second time, the new copy of the configuration is required. You can then modify the content to print the current J-DSUR.

- Before saving the J-DSUR configuration, Report Name, Primary Agency, Product Selection, and at least one timeframe need to have a value entered.
Else, the following error messages are displayed:

When Report Name is not entered:

Report Name is not entered

When Primary Agency is not entered:

Primary Agency is not entered

When selected product is not available:

Product is not selected

When atleast one time frame is not entered:

Investigation time frame is not configured

When Assigned Date is not entered:

Assigned Date is not entered.

Following message is displayed along with the above error:

It is necessary to enter above information in order to save the configuration

- When the Modify, Copy, Delete, or Print button is clicked without a selection of report, a pop-up is displayed to select a report.

- If any one Submitted report is present, the Report Configuration is non-editable even if it has multiple generated reports with different states.

- If you print an existing CSPSR report, it displays only the configuration details.

4.2.8.2 J-DSUR Details

4.2.8.2.1 Subject of Report

Field Name

Description

Report Name

Manually Input a name for the report that is displayed in the Reports > CSPSR Reports dialog box.

Report Category

Manually Input a name for a Report Category that is displayed in the Reports > CSPSR Reports dialog box.

Primary Report Agency

This list contains the Regulatory Authorities configured in List Maintenance > Regulatory Authorities (LM_REGULATORY_CONTACT table).
If there is no Japanese Authority name configured, the English name is listed.

The system allows you to select multiple agencies from the List of Agencies so that the report can be submitted to multiple agencies at the same time.The primary agency can be defined in this drop-down list.When Japanese Message Profile is not configured in Console J for the selected Primary Agency, the following error message is displayed:

Selected Primary Agency doesn't have configured Message Profile (I or J) in Argus Console/Reporting Destination/EDI.

Once you click OK, the selection of the Primary Agency goes back to the previous selection. This check is executed when you try to go to the other tab, or click OK to save the configuration.

Report Number

Manual entry text field that allows you to enter a report number.

Print all configuration criteria on separate cover page

This field represents the check box to print the configuration of this report when the report is printed. When this is clicked, the Configuration page is printed at the beginning of the CSPSR Word print output. The page numbering of the CSPSR does not include the Configuration page.

If the Japanese Agency Name is not configured in the Console, the English name is displayed on the screen for that agency.

4.2.8.2.2 Product Selection

Field Name

Description

Available Ingredients

The system allows filtering the Ingredients within the available list of Ingredients by entering the Ingredient Name and clicking the Filter button.The search is performed in Japanese ingredient name only. If the name is blank, then enter English ingredient name.

Indication

This list contains the Indication configured for the product containing the ingredient in C5 section. Use this to narrow down the products displayed in C8.The system allows to multi-select Indications using standard Windows functionality of CTRL+CLICK.If Japanese name is not available, display the English name

Available Products

This list is auto-populated once the Ingredient has been selected and displays all products from LM_PRODUCT J table, containing the ingredient selected in C5 section. The format is Product name (Formulation, Concentration concatenated with the Concentration Units). If the Japanese name is not available, the English name is displayed.
The withdrawn products are displayed as well.

Selected Ingredients

This list contains the Ingredients used for the Products Configuration. It is stored in the LM_PF_INGREDIENT_J table once a product has been configured. When an ingredient has been selected, all products containing that ingredient are displayed in Available products (C8) section. Multiple Ingredients can be selected at once to form a CSPSR product family.

Formulation

This list contains the formulation configured for the product using the ingredient in C5 section (LM_FORMULATION table). Use this to narrow down the products displayed in C8.The system allows to multi-select formulations using standard Windows functionality of CTRL+CLICK.If Japanese name is not available, the English name is displayed.

Selected Products

This list contains products that are selected from the Available Products list (C8). When at least one product is selected, the field has a blue background color. If the license is not withdrawn at the starting date of the J-DSUR investigation timeframe, include the license in J-DSUR.
Data Entry Discipline: When the new product is available because the new product with the same ingredient released in the J-DSUR, you need to manually set up the new configuration. When no Japanese ingredients, indication, or formulation is configured in the Console, the English names are displayed.When you copy an existing submitted J-DSUR report, the Assigned dates remain editable. In such a scenario, if you change the product selection, the Assigned dates do not change.

All the forms printed as J-DSUR have only the information regarding the selected product in this Configuration window.When a product is moved to Selected Products field, but this does not have the Clinical Compound Number, the following error message is displayed:

Selected product doesn't have a Clinical Compound Number. It is necessary that the study product license has at least one Clinical Compound Number in order to include in the report.

If License # as well as Clinical Compound Number is not available, then for J users, if Trade Name (J) is available then it will display <License Authorization Country> (<License Type>) <Trade Name (J) from Console J>.

Else <License Authorization Country> (<License Type>) <Trade Name from Console> is displayed.

Available Studies

Lists the available studies.

Selected Studies

Lists the selected studies.

Available/Selected Studies multi-select shuttle controls

- Available Studies field dynamically lists all the company configured studies in Console, which consists of the selected J-DSUR products. The Study ID (J) value from Console > Study Configuration must be listed.

- These 2 shuttle controls have Add, Add All, Remove, and Remove All buttons to Select/Remove studies between Available and Selected Studies fields.

- If any product is added/removed from the Selected Product field, the Available and Selected Studies fields are also updated dynamically.

- The Selected Studies field is displayed in blue background, same as that of the Selected Products fields.

- If Selected Studies fields do not contain any study, clicking on OK button displays the following error message and brings the focus back on the Selected Studies field:
At least one domestic study must be selected in order to proceed with the configuration.

4.2.8.2.3 J-DSUR

#

Field Name

Description

1

Forms configuration

This field represents the main title of the UI.

2

J-DSUR

This field represents the title of the set of configuration forms.

J-DSUR Form 1

3

Report form - Clinical Trial Safety Update Report Overview

This field represents the title of the form to be configured.

4

Print Blank Form

This checkbox is used to print the blank form.

J-DSUR Form 2

5

Report form - Serious AE Case Occurrence Status Listing

This field represents the title of the form to be configured.

6

Number of subject: Study__

This is a manual data entry (Numeric only) field. You can enter total number of subject for this entire clinical study for domestic.The Maximum digits for this number is 7 for both fields.

7

Order SOC Alphabetically (Check box)

If this is checked, the SOC is printed in alphabetical order (alphabetically based on their English names). If not checked, the SOC order is same as that of the MedDRA order.

8

Include foreign AE marked as "Not include for the report in Japan" (Check box)

When this is checked, the system includes AEs in the foreign cases that have flags for Not include for the report in Japan (available in the Case Form > Event tab)

9

Use Current Case VersionUse DLP Case Version

This radio button control is only displayed if DLP is enabled.
Use Current Case Version is selected by default.Based on the J-DSUR configuration for DLP, the report is executed accordingly using latest case revision or using the DLP case revision.

10

Separate Page Numbering (Check box)
Note: When separate page numbering is not used, it always follows the previous form of J-DSUR. Order of the page numbering sequence is following: J-DSUR Form Cover, Line Listing

When this is checked, the page number becomes independent (starts from 1) for J-DSUR Line Listing.

11

Print the content of the report as case listing on separate page

If this is checked, Case Listing of the J-DSUR Line Listing content is printed on a separate page.
Note: The Case Listing is printed after the configuration content, and using following style guide template for listing.

12

OK

13

Cancel

StyleGuide_CaseList.doc

#

Field Name

Description

1

Periodic Safety Report - Case Line List

Static text

2

Clinical Study Serious Event Case Periodic Report

Static text

3

Serious AE, etc. Case Occurrence Status Line Listing

Static text

4

AE, etc. Case classification

Static text

5

AE, etc. Case Count

Static text

6

This investigation period

This column has the same output as the printed J-DSUR

7

Cumulative Total

This column has the same output as the printed J-DSUR

8

Case Number

Case Numbers that have counted events are listed with the comma used as a separator.

9

Clinical Study

Static text. This section only considers the cases, which contain the studies configured as Selected Studies in the Product Selection tab.

10

SOC

This field has the same output as the printed J-DSUR.The Case Listing is not printed for this section.

11

Event sectopm

This field has the same output as the printed J-DSUR.The Case listing is printed for this section.

12

This investigation time frame: YYYY?MM?DD????YYYY?MM?DD? - TBD

This field has the same output as the printed J-DSUR.

13

Terms for AE: MedDRA/J version ( ) was used.

This field has the same output as the printed J-DSUR.

4.2.8.2.4 Scheduling

Field Name

Description

Clinical Study Plan Submit Date

This is a manual data entry text field. It is an editable text field.
If OK is clicked, the new value remains in the field. If Cancel is clicked, the original value is replaced with the entered value in the field.CSPSD is an editable field, if the J-DSUR is not in Submitted state and it does not have any previous non-editable timeframes.Once a J-DSUR is marked as Submitted, this field becomes non-editable.

Report is due ___days after specified end date

This option allows you to specify the due date of the J-DSUR, xx days after the end date specified for the scheduling period. The value entered in this field is added to the current end date and displayed in the printing UI as due date.

Group

This option allows you to specify which Argus group is responsible for the Periodic report, once scheduled by the application. The report appears on the designated group's worklist for Reports.

Frequency of the schedule

Start Date

This field is a date entry field for the reporting timeframe starting period. It allows you to enter the starting date of each J-DSUR timeframe starting period. The first Report Timeframe Start Date is auto-calculated as per the Assigned Date. The Start Date for the first timeframe is editable till the report is submitted.
Start Date of the new row always has the next date of the previous End Date pre-populated as read-only, and End Date can be added only one at a time.The Start Date of the J-DSUR is auto-populated and reset as per the Assigned Date value, only if the first timeframe row (first start as well as end date) is editable. The Start Date of the J-DSUR is not updated based on the Assigned date, if this first timeframe row is non-editable.Whenever Start Date is auto-updated and end date is already specified, the system displays the following warning message:

Start Date for the reporting period has changed. Please update the End Date accordingly.When you enter the Start Date which is older than the latest End Date (previous row), the system displays the following error message:

Start Date must be same day, or after the latest end date.

By clicking OK, the wrong Start Date is removed.

Note: The J-DSUR contains the number of events from Submitted to the Japanese Agencies and non-reportable events within the Reporting Period.

End Date

This field is a date entry field for the reporting timeframe ending period. It allows you to enter the ending date of each J-DSUR timeframe starting period. This is an editable field.When you enter the End Date which is earlier than the same timeframe's Start Date, the system displays the following error message:
End date must be after the Start Date

By clicking OK, the wrong end date is removed.

Note:

The J-DSUR contains the number of events from Submitted to the Japanese Agencies and non-reportable events within the Reporting Period.The System does not allow you to edit the previous reporting period and only allows to edit the current reporting period.

Add

You can add editable row by clicking this button. You can add only 1 reporting timeframe which can remain in Editable state in a J-DSUR in single configuration. All the previous reporting timeframes are always in non-editable state.By default, in a freshly configured J-DSUR (non-submitted, non-copied), there is no timeframe row to begin with until you add one row using the Add button.Whenever the first timeframe row is added, the Start Date is auto-populated based on the Assigned Date.When you generate a J-DSUR, it is generated based on the last editable timeframe row.Once the report is marked with the Submitted status, all the timeframe rows are marked as Non-editable.If you do not have any editable timeframe row available in the J-DSUR, only then Add button is enabled. Else, it is always disabled.The Add button adds editable fields for Start and End date. Each row has a number that starts from 1 and is incremented for each timeframe.

Delete

You can delete the editable row by clicking this button. The Delete button cannot delete the non-editable row. For removing previous non-editable rows, you can use the RESET button. This makes sure that you do not delete any timeframe rows which J-DSUR has already submitted. When this is selected, the following warning message is displayed to confirm the operation:
Would you like to delete the highlighted row?

Reset

When this button is clicked, all the existing timeframe rows (editable as well as non-editable) are deleted. Else, the past Start and End date records are non-editable. When the Reset button is clicked, the following warning message is displayed:
By using Reset, all the past data will be removed. Do you want to proceed?

If you click OK, proceed with the reset.

If you select Cancel, leave the past data in the schedule table.When you make copy of a configuration, the Assigned Date, CSPSD, and CTPCSD are non editable unless the Reset button is used.

4.2.8.2.5 Security

4.2.8.2.6 Printing CSPSR

Generating the Document

The generation of the document is executed using the following process:

1. Click View Report in Reports > Compliance > Periodic Reports

2. Check-out the report from the View and edit J-DSUR pop-up.

3. Edit the checked-out Word document

4. Check-in using the same View and edit J-DSUR pop-up

5. Publish the PDF file (converting from the Checked-in Word document)

Printing Requirements

- The system allows you to print the report and update the report output in the Word document. The watermark is printed on the report when the Draft, Internal or <Other> is selected for printing.

- The change of the configuration for the same investigation timeframe can be done multiple times only before the status is changed to Submitted. The changes in the configuration after the Submitted status of the J-DSUR is applied on the next investigational time period.

- From the Reports > Compliance > Periodic Reports, selecting View Report allows you to view the J-DSUR Report in the Word document to upload the report.

- When J user opens Reports > Compliance > Periodic Reports from the menu, Japanese UI is displayed for Periodic report list. The pop-up for the J-DSUR view and edit is in Japanese.

#

Field Name

Description

1

PERIODIC REPORTS

Lists the Periodic Reports.

2

View All

Enables you to view all the reports.

6

Trade Name

The Japanese UI displays available Japanese data in this field. When Japanese data is not available, the English data is displayed.

7

Destination

The Japanese UI displays available Japanese data. When Japanese data is not available, the English data is displayed.When Destination is not available, No Specific Receiver is displayed.

8

Description

The Japanese UI displays available Japanese data in this field. When Japanese data is not available, the English data is displayed.

9

Due Date

The English date format is DD-MMM-YYYY.The Japanese date format is YYYY/MM/DD.

10

Status

The Status appears in Japanese in Japanese UI, and in English in English UI and can have the following possible values:
Scheduled

Generated

Approved

Disapproved

Submitted

New Data Available

No Longer Required

- Trade Name section:
The Trade Name section displays the multiple trade names using comma separated list of the selected products.

The Trade Name displays the original product selected: either English or Japanese. If PSUR was created for the English product names, the English product name is used in the list. If the J-DSUR is created with Japanese product names, the Japanese product name is used in the list.

If the selected product in the J-DSUR does not have the Japanese Trade Name, the English Trade Name is displayed for that J-DSUR.

- The report output is a Word Document. This works in the similar way to ePSUR publishing where you are allowed to edit the Word Output outside the system and once generated, can publish the FINAL Word Document.

- When the report is generated and it has been never checked out, the center button displays Check-out to revise the document. At this time, the Publish button is disabled.

- Check-out can be executed by one user only. Other users cannot check-in the checked-out files.

- Once the check-out is executed, the Check-out button is changed to the Check-in button. This button is used to check- in the revised checkout file.

- When the file is checked-in, the center button becomes the Check-out button.

- When the file is not checked-out or not published, you can check-in/check-out the file as many times you want.

- When the file is not checked-out or not published, the group which has access rights to this report can execute the Check-in, Check-out, and Publish.

- The View button is always enabled (regardless of the Check-in/Check-out status). It displays the latest updated Word document or the PDF after final Publish.

- The Publish button is enabled after the check-in has been performed atleast once. The Publish button is disabled when the document is checked-out.

- Once the final Word file is created, the Word document is saved in the repository. All the past J-DSUR Word outputs are saved. When you update the Word document and upload it, the system overwrites the automatically generated document in the database.

- Once the Publish button is executed and the PDF file is created, the Check-Out button is disabled.

- Once the document has been checked-in, the Check-in button is changed to Check-out, and the Publish button is enabled to publish the PDF report from the Word document.

- The Publish button converts the checked-in word document to the PDF file.

- Once Publish is done, the Word document is no longer available. The Check-in/Check-out buttons are disabled only when the J-DSUR is published and the label is changed to Check-out.

- When the Check-in button is clicked, the following pop-up is displayed to specify the file name. This can be done by either specifying the file name in the text box, or selecting the location using the Browse button.

- If the data is changed manually in the Word document, this change is not applied to the next report. You need to change the report again.

- The configuration of the J-DSUR can be edited while the J-DSUR is checked-out. The change is affected only when the J-DSUR is created again.

4.2.8.2.7 Deleting A J-DSUR

Click Yes on this dialog box to delete the report configuration.

Click No to exit without deleting.

4.2.8.3 J-DSUR - Cover

Summary: The J-DSUR Cover is the cover page of the J-DSUR Line Listing, and output includes the information of the configured product. This form does not contain any particular case data.

Field Name

Description

Clinical Study Drug Serious Adverse Events etc. Case Periodic Safety Report

Form

Clinical Compound Number

This field represents the Clinical Compound Number of the selected product from Console Business Configuration/Product/License.Use ([1],[2],[3]… ) numbering format for multiple Clinical Compound Numbers.

Clinical Study Plan Submit Date

This field is a manual data entry field. If this field is changed by the user and this date is later than the "Clinical Trial for Partial Change Plan Submit Date", it displays a message that CSPSD cannot be after CTPCSD.

Ingredient Name

The generic name is entered in this field. If the license is withdrawn before the starting date of the CSPSR timeframe, the generic name is not displayed.If Japanese name is not available, this field can be left blank.

Dev International Birth Date

This field is auto-populated as per the earliest Console > Product > DIDB field for the J-DSUR products. This date is used to auto-populate the first J-DSUR Start Date on the "Frequency of the schedule" table on the right side of the UI.

Trade Name

The Trade Name is based on the selected product in the Configuration window. If there are multiple products (different amount, formulation, etc), use ([1],[2],[3]… ) numbering with the trade names. You can use Trade name (J Drug code). When the code is not available in the code lists, the code is not necessary. If there is a product that has multiple Japanese licenses, all of the trade names must be listed.This field is entered when the selected product is the marketed product (Clinical Trial for Partial Change), but if this is for the Study drug, this field is left blank.

International Birth Date

This field represents the IBD from the Code List Product.
Use ([1],[2],[3]… ) numbering for multiple names.

Japan Award Date

Code List Licenses -Japan Award date
Use ([1],[2],[3]… ) numbering for multiple names.

All the Japanese award dates are listed in this field. The Japanese Award date can be retrieved from License award date field for Japanese license Code List.If the license is withdrawn before the starting date of the CSPSR timeframe, the Japan Award Date is not displayed.This field is entered when the selected product is the marketed product (Clinical Trial for Partial Change), but if this is for the Study drug, this field is left blank.

Amount and Formulation

This field represents the amount of the ingredients and formulation (from Dosage info) of the product. If multiple formulations are reported in the same form, enter the information for each formulation. The Strength and unit of the product, and formulation are listed in the following format:"Strength""unit" "Formulation"If the strength data is not available, only the formulation is listed.Use ([1],[2],[3]… ) numbering for multiple information.If Japanese name is not available, the section is left blank.

Number of the CSPSR report sent for this ingredient

This field denotes the total number of CSPSR report sent to PMDA including the current time. This starts from 1, 2, 3…

Expected Indication

Enter Primary Indication from the Business Configuration/Product/Primary Indication.Use ([1],[2],[3]… ) numbering for multiple Indications.If Japanese name is not available, this section is left blank.

Expected Use and Dosage

The information is not printed in this section. You need to enter the information in the Word document output.

Investigational Unit Timeframe

This field is used to enter the Time frame Start Date and Time frame End Date for this report. This denotes the Investigation timeframe for this report.

Study Phase

Enter Console J > Business Configuration > Studies > study phase J using this field.
When there are multiple clinical studies that use the same Clinical Compound number, use ([1],[2],[3]… ) numbering and list each study phase of all the studies using comma separated string against each number.

It only considers the studies configured as Selected Domestic Studies in the Product Selection tab.If Japanese name is not available, this section is left blank.

Approval Status in major developed countries

This field represents Approval status in major developed countries excluding Japan.
The value in this field is printed based on the earliest award date of marketed licenses (excluding the hidden link licenses for these products) for the J-DSUR product(s) for configured countries in profile switch Argus J > Reporting>'Major Developed Countries for Approval Status in J-DSUR' (comma separated A2 country codes).

Use numbering ([1],[2],[3]… ) for multiple products.

The country is printed with its A2 country codes and Aware Date year shall be printed in YYYY format.

Example: If in a JDSUR report we have 2 products P1 and P2 with P1 having 2 CCN - CCN1, CCN2 and P2 having 2 CCN - CCN3, CCN4 then approval status are printed as -

([1], [2]) US - YYYY, UK - YYYY, DE - YYYY

([3], [4]) US - YYYY, UK - YYYY, DE - YYYY

Where US, UK and DE are configured country codes in the profile switch in this particular order only.

Only Marketed Licenses related information are printed here. If Marketed License is not available then do not print any value for that country not even the A2 country code for that country.

The values are printed in the same order as A2 codes entered by user in the common profile switch.

Status of the Serious AE, etc. case occurrences

This field is used to enter TBD (As described in the Line Listing report).

Safety action based on the data analysis and safety countermeasure for the future

This field is left empty to enter the description in the output format.

Note

This field is left empty to enter the description in the output format.

From above reason, this reports Clinical Serious Case AE Periodic Reports

YYYY?MM?DD? TBD

The Date report is created in the Japanese format. It is printed as the current database date converted into Japan time zone (using the Common Profile Switch under Argus J > Reports > Offset from GMT and is used to calculate Japanese date/time fields (in hours)) on which the report is being executed.

Address

This field represents the Address of the sender (A.3.1.4a-c). Format: TBD[A.3.1.4c][A.3.1.4b][A.3.1.4a]
A line break is inserted if the address is reached to the maximum printable length for the line in the print. The address line can be 3 lines in one page, and if the 3rd line reaches the maximum length, it is printed to the next page.No spaces are used between the populated values.The Address and the Name are printed from center of the page (same as PMDA Expedited Reports Name and Address print)

Name

This field represents the Sender Identifier(Company Name (J), A.3.1.3b, A.3.1.3c, A.3.1.3d, A.3.1.3e)
Format:

TBD[Company Name (J)] [A.3.1.3b]space[A.3.1.3e]space[A.3.1.3d]space[A.3.1.3c]The print start point of [A.3.1.3b] is the same as [Company_Name_(J)] in above line.For the second line, empty space is printed between the populated valuesA line break is inserted, If A.3.1.2 reaches the maximum printable length for the line. There can be 2 lines in one page. And if the 2nd line reaches the maximum length, it is printed to the next page..

A line break is inserted, If combination of [A.3.1.3b] [A.3.1.3e] [A.3.1.3c] reaches the maximum printable length for the line. There can be 2 lines in one page. And if the 2nd line reaches the maximum length, it is printed to the next page.

The SENDERMIDDLENAME is not printed if it does not existThe Address and Name is printed from center of the page (same as PMDA Expedited Reports Name and Address print)

Receiver identifier

PMDA Receiver identifier A.3.2.2d-f in _____ section.This is printed as follows:Receiver Identifier (A.3.2.2a, A.3.2.2c, A.3.2.2d, A.3.2.2f)
Format:

[A.3.2.2a][A.3.2.2c]space[A.3.2.2f]space[A.3.2.2d]space? - TBD

Additional Information

- This cover page has Japanese license information only.

- If all the information is the same through all the numbered items, enter the numbers with one information. When there is no data available, skip the data and only print the serial numbers for which the values are present.

- If the license is withdrawn before the Start Date of the J-DSUR time frame, all the product information as well as the license information is not displayed.

- The overflow data is printed on the next page on the copy of this cover page that does not have any data other than the overflow data.

- For Ingredient Name, Indication, Study Development Phase, Amount, and Formulation, if source console values are not configured, fields on the paper form are left blank.

4.2.8.4 J-DSUR - Form 2

Summary: J-DSUR - Form 2 is the report of events that are serious (both Reported and Not Reported) during the specified investigational time period for Study drugs (including Study for partial change of the Marketed drugs).

- The past record is included in the report as cumulative Total Number of SOC and Terms.

- The number of the serious events which are either Reported or Not Reported to the PMDA within one investigational timeframe is the content for the report.

- Regardless of Incomplete or Complete report, all the events during the investigational timeframe are listed.

- If there are multiple events in one case, count each Reportable event separately. For example, if there are 2 same PTs available in the same case, the count is 1 SOC and 2 PTs.

- A case is included in the report for the current timeframe only if a significant Japanese follow-up is received for the case in the same timeframe. If there are no significant updates for the case, this case is not counted for the current period.

- If there are multiple follow-up updates (Significant or Non-significant) to a qualifying case in the same investigational time frame, count the events based on latest information on the events in the case and exclude the Deleted events during the timeframe. If the event is entered as Serious, but later in the same timeframe, this is changed as Non Serious, this event is not counted.

- The MedDRA version is the latest MedDRA J version at the time of report creation.

- The configured products that fall in DRUGCHARACTERIZATION = 1 (SUSPECTED) or 3 (INTERACTION) are collected. 2 (Concomitant) is not included.

- The date cut off for the data inclusion is based on the case's Japan first information Aware Date (in PMDA > General tab of the Case Form). If this is a follow-up case, the Aware (latest significant follow-up) Date.

- The Serious events must be Related events to be included in the list.

- An event which is included in the past J-DSUR report is included in the Cumulative Total section of the count in the report.

- For identifying the Japanese license, the license authorization country in the license configuration in Console is used. For the count of the foreign data, all configured products that have the same ingredients (regardless of the existence of Japanese license in this family) is considered as the target.

- When the End Date is set as past date, any updates/new data that meet above condition in between the End Date and the current date are not included in this line listings. The data is the latest in the given timeframe, and not between the investigational timeframe Start Date and the Report Generation Date. This is achieved when you have enabled DLP and has configured the Use DLP Case Version radio option for J-DSUR configuration.

- If there is 0 count on any counting numbering sections of the Line Listing, - is printed.

- From 2nd and subsequent pages, the table header rows are repeated at the top of the each page.

Basic Data Retrieval Rule:

Cumulative Total:

- In J-DSUR, the Cumulative Total is the count of Serious AEs that are collected between the Assigned Date and the end of the current investigation timeframe.

Investigation Time Frame

The Serious AEs from the cases collected in this investigation timeframe from among the cases retrieved by Cumulative Total.

4.2.8.4.1 Domestic Serious AE, etc. Case Occurence Status Line Listing

Field Name

Description

Serious AE, etc. Case Occurrence Status Line Listing

This field represents the title of the paper form.

Attached paper form

This field represents the header of the paper form.

Information Source

This field represents the title of the row.

Clinical Study

This field represents the title of the column. This column has data only from the report source: Clinical study and Incident Country = Japan. It only considers the cases which contain the studies configured as Selected Studies in the Product Selection tab.

Investigation Time Frame

This field represents the title of the row.

This investigation period

This field represents the title of the column. This column collects count information in this investigation period only.

Cumulative Total

This field represents the title of the column. This column collects total number of count information in the entire reporting period starting from the first Assigned Date to the end of current investigation period.If the configuration is set (checked for Exclude the event count from the cumulative total if the event doesn't meet the condition), events that were reported in the past but as the condition has been modified in the current timeframe they no longer meet the condition, are removed.

This investigation period

This field represents the title of the column. This column collects count information in this investigation period only.

Cumulative Total

This field represents the title of the column. This column collects the total number of count information in the entire reporting period starting from the first Assigned Date to the end of current investigation period.

This investigation period

This field represents the title of the column. This column collects count information in this investigation period only.

Cumulative Total

This field represents the title of the column. This column collects the total number of count information in the entire reporting period starting from the first Assigned Date to the end of current investigation period.

Number of subjects

This information is captured from the J-DSUR tab.

AE, etc Case classification

This field represents the title of the column.

AE, etc. Case Count

This field represents the title of the column.

SOC name in Japanese

The SOC count is the count of cases (not AEs). The number is collected for this inv. Period and the total of entire J-DSUR time.

PT names

All the serious AEs are counted and entered for this inv. Period and entire J-DSUR time.

This investigation time frame: YYYY/MM/DD

This investigation timeframe is entered using the Japanese date format.

Terms for AE: MedDRA/J version ( ) was used.

The used MedDRA/J version must be entered in the brackets.

4.2.9 Seiyakukyo Line Listing Report (Individual Report Common Line List)

Seiyakukyo Line Listing report is a periodic report format specified by the JPMA. This report is to be used by pharmaceutical companies in Japan to send case reports to medical institutions. It is mandated by PMDA to report study cases to medical institutions and is required to be fully compliant in Japan.Seiyakukyo periodic report is handled in the similar manner as the other Japanese periodic reports - PSR/ReSD, and CSPSR. At a high level, it has a similar Configuration screen, similar Generation, Publishing, and Handling process as other Japanese Periodic reports. However, the report output format and data is different so as to match the Seiyakukyo format.

All the following date fields in the Seiyakukyo Line Listing main report output are printed in the "YYYY/MM/DD" format:

- Dose Start Date and Dose Stop Date

- AE Onset Date

- Subject Timeframe

- Report Submission Date

- Japan Information Receipt Date

For example, full dates are printed as "2013/10/17" and partial dates are printed as "2013/10" or "2013".

This date format is applicable in Microsoft Word as well as CSV format report outputs.

4.2.9.1 Configuration Screen

- A new menu item - Individual Report Common Line List is added in Console > Groups > Menus section for the Argus Groups for Seiyakukyo report.

- It is added under Reports > Periodic Reports right after J-DSUR menu option.

- It is marked enabled by default for Administrator Group.

- It is marked enabled by default during New Argus group creation.

- It is only displayed if Console > System Management > Enabled Modules > Japanese module is enabled.

- The following options are available

- Include listed and unlisted events

- Include unlisted events only (default option)

- A new menu item - Individual Report Common Line List is added under Argus Safety > Reports > Periodic Reports menu.

- It is added under Reports > Periodic Reports right after the CSPSR menu option.

- This menu item is only available in Argus Safety if following conditions are met:
Console > Access Management > Users > User Type of the current user is configured as ARGUS J USER.

Console > System Management > Enabled Modules > Japanese module is enabled.

Console > Access Management > Groups > Menus section for Argus Groups has Reports > Individual Report Common Line List marked Enabled for at least one user groups for the current user.

- Clicking on this menu in Argus Safety displays the existing Periodic Reports Library screen, which lists all the configured Seiyakukyo reports available in the system.

- The functionality of this screen remains the same as existing except for the following:
The page breadcrumb for the Periodic Reports Library screen for Seiyakukyo is displayed as:
Reports > Periodic Reports > Serious, Unlisted AE Individual Case Communication Line List

The screen name for this screen is displayed as Serious, Unlisted AE Individual Case Communication Line List.

When you click the Open button for a submitted Seiyakukyo report whose configurable becomes non-editable, the following warning message is displayed:
This configuration is not modifiable because the status of this Individual Case Communication Line List is Submitted

- Clicking New or Open buttons on Periodic Report Library screen for Seiyakukyo reports displays the Configuration screen for Seiyakukyo reports which has 5 tabs similar to the CSPSR Configuration screen with following names. The Page Title text is: Individual Report Common Line List.

- Subject of Report

- Individual Report Common Line List

- Scheduling

- Security

- The Subject of the Report tab is the same as the existing Subject of the Report tab for CSPSR.

- The Study Selection tab has the following functionality:

Field Name

Description

Filter

This button is available adjacent to the Available Clinical Compound Numbers textbox to allow filtering the data in the Available Clinical Compound Numbers multi-select list box.When you click this button, the data is refreshed in the Available Clinical Compound Numbers multi-select list box based on the search text specified by you in the textbox.Like search is performed based on the text specified by you. For example, If you have specified ABC as the search text, it performs case-insensitive text for %ABC%.The maximum allowed length of the Filter textbox is 70 characters.

Available Clinical Compound Numbers

It lists distinct Clinical Compound Numbers for all the licenses which are configured in the Console application.

Selected Clinical Compound Numbers

This listbox is populated based on your selection and removal of Clinical Compound Numbers by using Add and Remove buttons from/to the Available Clinical Compounds listbox.
This is a mandatory field. If it is not specified, and the OK button is clicked, the following error message is displayed:
Clinical Compound Number is not selected

Add

This field allows you to move the selected item(s) from left hand listbox to the right hand listbox.

Add All

This field allows you to move all the items from the left hand listbox to the right hand listbox.

Remove All

This field allows you to move all the items from the right hand listbox to the left hand listbox.

Remove

This field allows you to move the selected item(s) from the right hand listbox to the left hand listbox.

Classifications for Clinical and Domestic Study Cases

It lists all the Case Classification (J) values from the Console code list. If J is not available, the corresponding English value is displayed.
You can select multiple values in this listbox by using Ctrl + Click and Shift + Click combinations.

The first option in this list is always displayed as: All Case Classifications

These case classifications are used for fetching the case data for Clinical and Domestic study cases reporting in Seiyakukyo report.

Classifications for Foreign "Ichihen" Study Cases

It lists all the Case Classification (J) value from the Console code list. If J is not available, the corresponding English value is displayed.
You can select multiple values in this listbox by using Ctrl + Click and Shift + Click combinations.

The first option in this list is always displayed as: All Case Classifications

These case classifications are used for fetching the case data for Foreign Ichihen study cases reporting in Seiyakukyo report.

- Seiyakukyo Report tab has the following functionality:

#

Field Name

Description

1

Individual Report Common Line List

N/A

2

Common Configuration

N/A

3

Company Name or Company abbreviation

You can specify the value of the Company Name to be printed in the second column of Seiyakukyo report using this field.
The maximum allowed length of this textbox is 60 characters.

It allows English as well as Japanese characters.

4

Section Footer Text

You can specify a text to be printed as footer text at the end of each section in the report output using this field.
The maximum allowed length for this textbox is 200 characters.

It allows English as well as Japanese characters.

5

Available Additional Columns (CSV Only)

This field lists all the available additional fields that can be added to the Seiyakukyo report CSV output. These are not applicable to the Word output.
The following fields are available in this list in the alphabetical order:

ACK Number

Blinded / Not Blinded

Determined Causality

Event Intensity

Japan Information Receipt Date

LLT

MedDRA Version

Number of times this report is submitted to PMDA

Primary Disease

Reported Causality

Report Submission Date

SOC

Study Name

6

Selected Additional Columns (CSV Only)

It lists all the selected additional fields that are added to the Seiyakukyo report CSV output. These are not applicable to the Word output.
You can move items between Available and Selected Additional Columns using the Add and Remove buttons.

While adding items, these items are listed in the same order in which they are added.

You can move items up and down using Up and Down buttons.

The Seiyakukyo report output includes these columns at the end in the same order as specified in this list.

7

Add

This field allows you to move the selected item(s) from the left hand listbox to the right hand listbox.

8

Remove

This field allows you to move the selected item(s) from the right hand listbox to the left hand listbox.

9

Up ^

This field allows you to move the selected item in the Selected Additional Columns, one position closer to top of the list.

10

Down V

This field allows you to move the selected item in the Selected Additional Columns, one position closer to the bottom of the list.

11

Clinical and Domestic Study Cases

N/A

12

Exclude events which were reported by paper report forms

If this checkbox is checked, all the events which are reported through paper reports are excluded.
This logic is applicable only for Clinical and Domestic Study cases for which events are reported based on Expedited/E2B reports.

It is unchecked by default.

13

Exclude Incompletion reports

If this checkbox is checked, all the events which are reported through Expedited/E2B reports where the value of J.6 (Mhlwadmicsrcompleteclass) = 1 (Incomplete) are excluded.
This logic is applicable only for Clinical and Domestic Study cases for which events are reported based on Expedited/E2B reports.

It is unchecked by default.

14

Include listed and unlisted events (new)

You can specify the criteria for printing the events under Regular and Domestic Study cases category using this field.
This radio button is selected by default if the "Include only serious unlisted event" checkbox was not selected for the already configured reports.

15

Include unlisted events only (new)

You can specify the criteria for printing the events under Regular and Domestic Study cases category using this field.
This radio button is selected by default:

- For all new reports.

- If the "Include only serious unlisted event" checkbox was selected for the already configured reports.

16

Foreign "Ichihen" Study Cases

N/A

17

Include foreign AE marked as "Not include for the report in Japan"

If this checkbox is checked, all the events in the cases which are marked as Not to be reported to Japan in the Case Form Events tab are also included.
This logic is applicable only for Foreign Ichihen study cases for which events are reported based on case data directly.

It is unchecked by default.

18

Append CIOMS reports

If this checkbox is checked, the CIOMS reports are created and added at the end of Seiyakukyo report output for all the cases which are printed under Foreign Ichihen Study Cases section.These CIOMS report are printed for the earliest Valid Japanese license for the first suspected product in the case. If the first suspected product does not have a Valid Japanese license, the next suspected product which satisfies this criterion is picked-up in the same order in which they are present in the case. Once the Seiyakukyo is generated as FINAL, these reports are listed in the Case under the Regulatory Reports tab in the similar manner as for English PSUR.These reports are added only in the PDF format (not in CSV), when the Seiyakukyo report is published.These reports are generated at the time of Seiyakukyo generation. The Generation Status dialog box displays the label Generating CIOMS reports for this task during the Seiyakukyo generation process. Although, generated at this stage, these CIOMS reports are visible to users after the Word format is published into PDF format.Even if you modify the Events/Cases printed in the application generated Word/CSV formats of Seiyakukyo report, the application still prints the CIOMS reports based on the application generated case list under Foreign Ichihen Study Cases section.It is unchecked by default.

19

DLP support

It displays 2 options to allow support of DLP for fetching case data for Foreign Ichihen study case: Use Current Case Version and Use DLP Case Version.
This radio button control is only displayed if DLP is enabled.

Based on the PSR/CSPSR configuration for DLP, the report is executed accordingly using the latest Case Revision or using the DLP Case Revision.

Use Current Case Version is always checked by default.

- The Scheduling tab is the same as the existing Scheduling tab for CSPSR, except for the following:

- The following date fields are not displayed as they are not applicable to the Seiyakukyo reports. All the validation checks related to these fields are also not applicable to the Seiyakukyo reports:
Assigned Date

Clinical Study Plan Submit Date

Clinical Trial for Partial Change Plan Submit Date

- The Start Date of first timeframe is editable as long as this timeframe is not submitted. However, the Start Date of second timeframes and onwards keep following the existing logic of being disabled and pre-populated as next day of the previous timeframe End Date.

- The Security tab is the same as the existing Scheduling tab for CSPSR:

4.2.9.2 Report Output Format

- This report prints information from two types of study cases:

- Clinical and Domestic Study Cases

- Foreign Ichihen Study Cases

- The report output prints the events from these 2 types as 2 separate sections starting from new pages.

- Within each of these 2 types, the report output prints the events for each of the configured Clinical Compound Numbers starting from new pages as well.

4.2.9.3 Report Output Filter Criterion

- Regular (Clinical) and Domestic Study Cases - All the data is fetched based on the events reported in the Expedited/E2B reports already reported to PMDA.

- Only the Expedited/E2B reports sent to the reporting destinations which are configured as the Seiyakukyo Configuration > Subject of Report tab > Primary Agency are considered.

- Only the Expedited/E2B reports whose cases have at least one of their Case Classifications configured as Seiyakukyo Configuration > Study Selection tab > Selected Classifications for Regular and Domestic Study Cases are considered.

- Only the Expedited/E2B reports that have J.11 (mhlwcompoundnum) element value same as one of the values configured as Seiyakukyo Configuration > Study Selection tab > Selected Clinical Compound Numbers are considered.

- Only the Expedited/E2B reports that have J.4a (mhlwadmicsrcasenumclass) element value as 8, 9, 10, and 11 (reporting categories - H, I, J, and K) are considered.

- All Nullification and Downgrade reports are ignored. However, their Initial and Follow-up reports that fall within the Seiyakukyo current timeframe are still considered.

- If multiple Initial or Follow-up Expedited/E2B reports for any product license (any series of Expedited/E2B reports) fall within the current timeframe, all of them are considered.

- Only the Expedited/E2B reports that have Report Submission Date (GMT) between and including the Start and End date (after conversion to GMT based on database time zone offset) configured for the current timeframe of the Seiyakukyo report are considered.

- If the radio option to include Unlisted events only is configures, it includes only those reported events from the Expedited/E2B reports that are unlisted in the case.
Unlisted - Specified as Unlisted in the case against atleast one Japanese Investigational license (License Drug Authorization Country as Japan) having same clinical compound number as configured in Seiyakukyo report. The Listedness specified as Unknown is not considered.

- If the radio option to include Listed and Unlisted events is configures, it includes all the reported events (listed and unlisted both).

- If the checkbox to exclude incompletion reports is checked on the Individual Report Common Line List configuration tab, any Expedited/E2B report that have J.6 (Mhlwadmicsrcompleteclass) element value as 1 (Incomplete) is ignored.

- If the checkbox to exclude Paper reports is checked on Individual Report Common Line List Configuration tab, all PMDA Paper Expedited reports are ignored.

- If the same AE/Infection event is reported in multiple eligible reports from the same case, all of them are reported multiple times in the Seiyakukyo report as well.

- All the events in Seiyakukyo report for Regular (Clinical) and Domestic Study Cases are sorted in the following order:

- Case ID Number (ascending)

- Report Submission Date (Old to New)

- Events as ordered in the expedited/E2B report

- Foreign Ichihen Study Cases - All the data is fetched based on the events present in the case data.

- Only the cases that have Country of Incidence other than Japan are considered.

- Only the cases that have at least one of their Case Classifications configured as Seiyakukyo Configuration > Study Selection tab > Selected Classifications for Foreign Ichihen Study Cases are considered.

- Only the cases that have atleast one of their Japan Information Receipt Date (significant follow-up or initial receipt date) between and including the Start and End date configured for the current timeframe of the Seiyakukyo report are considered.

- Only the cases that have one of their Japanese licenses as present in the Case Form > Event Assessment tab and have the same Clinical Compound Number configured as Seiyakukyo configuration > Study Selection tab > Selected Clinical Compound Numbers are considered.

- Only those events from the cases that have the Seiyakukyo products specified as:
Related - At least one of the As Reported and As Determined Causality in the case is specified as Reportable for this Product Event combination.

Unlisted - Specified as Unlisted in the case against at least one Japanese Marketed or Investigational license (License Drug Authorization Country as Japan) having same clinical compound number as configured in Seiyakukyo report. The Listedness specified as Unknown is not considered.

Serious - The event is specified as Serious.

- All the events in the Seiyakukyo report for Foreign Ichihen Study Cases are sorted in the following order:

- Case ID Number (ascending)

- Japan Information Receipt Date (significant follow-up or Initial Receipt Date) (Old to New)

- Events as ordered in the case

- If the checkbox to include foreign AE marked as Not include for the report in Japan is checked on the Individual Report Common Line List Configuration tab, those events are also included. Else, such events are ignored from the cases.

4.2.9.4 Report Output Field Mappings

#

Field Name

Description

1

Serious, Unlisted AE Individual Case Communication Line List

This represents the title of the paper form.
It is a fixed text to be printed in the top center of the Report Output table.

2

Clinical Compound Number

Clinical Compound Number of the report/case.
For Clinical and Domestic studies, it prints J.11 (mhlwcompoundnum) element value from the expedited/E2B report.

For Foreign Ichihen studies, it prints the Clinical Compound Number from the License Configuration for the Japanese licenses present in Case Form > Event Assessment tab.

3

Company name or Company name abbreviation

If you have specified the Company Name to be printed in the Individual Report Common Line List configuration tab, that text is printed as it is for all the event rows. Else, it is left blank.

4

Management No. (Case No)

The Argus Case ID number for the corresponding event is printed in this field.

5

Adverse Event (MedDRA-PT)

This field represents the name of the Serious and Unlisted MedDRA J Term (B.2.1.2.b)
For clinical and domestic studies:

It prints MedDRA PT (J) term based on the B.2.1.2.b (REACTIONMEDDRAPT) value from the Expedited/E2B report.

For decoding the MedDRA PT code from the Expedited/E2B report into the J Term, latest MedDRA dictionary configured for event encoding is used.

For foreign ichihen studies:

It prints MedDRA PT (J) term from Case Event record.

6

Outcome

This field represents the Reaction Outcome (B.2.i.8)
For clinical and domestic studies:

It prints the following Japanese description text for the E2B code values from the B.2.i.8 (REACTIONOUTCOME) value from the Expedited/E2B report.

For foreign ichihen studies:

It prints the Event Outcome (J) value from the Case Event record.

If no value is available in the case, then print NULL.

The Reaction Outcome footer in PSR Form 4 has E2B R3 code for Reaction Outcome against E2B R2 Code 6.

7

Gender

This field represents the Patient Gender (B.1.5).
For clinical and domestic studies:

It prints the E2B M2 Japanese description based on the B.1.5 (PATIENTSEX) value from the Expedited/E2B report or the case.

If B.1.5 is not available, print Unknown

For reporting categories L, M, and N, it is left blank.

For foreign ichihen studies:

It prints the Patient Gender (J) value from the Case Patient record.

If no value is available in the case, print Unknown

8

Age

This field represents the Patient Age (B.1.2.2/B.1.2.2.1/B.1.2.3)
It prints the Patient Age value based on the E2B logic for Patient Age elements. For example, If the Child Only checkbox in Case is checked, only GESTATIONPERIOD (B.1.2.2.1) is transmitted. If it is not checked, and if PATIENTONSETAGE (B.1.2.2) is specified, only it is transmitted else PATIENTAGEGROUP (B.1.2.3) is transmitted.

For PATIENTONSETAGE, age (B.1.2.2a) value is printed followed by the E2B M2 Japanese description of the Age Unit (B.1.2.2b) without any space in between .

For PATIENTAGEGROUP, E2B M2 Japanese description of B.1.2.3 is printed.

For GESTATIONPERIOD, TBD is printed as fixed text followed by the Gestation period (B.1.2.2.1a) value and the E2B M2 Japanese description of the unit (B.1.2.2.1b) without any space in between.

For PATIENTONSETAGE, if the unit value is Decade (B.1.2.2b = 800), special printing rule is followed.

9

Dose

This field represents the Product Dose Information (B.4.k.5.1~B.4.k.5.5/B.4.k.6)
In case of multiple dosages for the Seiyakukyo product(s), all the dosages are printed in the same cell, in the same order as in the Expedited/E2B report or as per the Product and Dosages order in the case.

Each new dose information is printed after leaving a blank line and in alignment with the corresponding dose Start/Stop date value which is printed in the next column.

For Clinical and Domestic studies, each dose information is printed using the following format:

[B.4.k.5.1][B.4.k.5.2 (using E2B M2 Japanese description)][B.4.k.5.3]?/[B.4.k.5.4][B.4.k.5.5(using E2B M2 Japanese description)] - TBD([B.4.k.6(If this does not exist, then its braces for this value are not printed. However, a blank line is left to align the Dosage Information with the corresponding dosage dates values in the adjacent column.)])

For foreign ichihen studies, each Dose Information is printed in the following format using the value directly from the Case Product Dosage Record:

[Dose][Dose Unit (J)]Code List/Dosage Frequency/[Number]TBD/[Unit Number][Unit (J)]([Dose Description (J)]) - If this does not exist, then its braces for this value is not printed. However, a blank line is left to align the Dosage Information with the corresponding dosage dates values in the adjacent column.

10

Dose Start Date ~ Dose Stop Date (Dose interval)

This field represents the Product Dosage Start/Stop DatesB.4.k.12B.4.k.14(B.4.k.15)
In case of multiple dosages for the product(s), all the dosage dates are printed in the same cell, in the same order as in the Expedited/E2B report or in the case.

Each new Dosage Date is printed after leaving a blank like and in alignment with the corresponding dosage information value which is printed in the previous column.

For foreign ichihen studies, each dosage date is printed using the Dose Start Date, Dose End Date, and Dose Duration values from the Case Product Dosage record in the same format as specified for Clinical and Domestic studies. Dose duration value is converted from seconds into appropriate unit using the same logic as used in E2B for B.4.k.15.

11

AE, etc. onset date

This field represents the Reaction Onset Date (B.2.i.4)
For Clinical and Domestic studies, it prints the REACTIONSTARTDATE (B.2.i.4a and B.2.i.4b) value.

For foreign ichihen studies, it prints the Event Onset Date from Case Event Record.

12

Country

This field represents the Country of Incidence (A.1.2)
For Clinical and Domestic studies, it prints the E2B M2 Japanese description based on the A.1.2 (OCCURCOUNTRY) value from the Expedited/E2B report.

For foreign ichihen studies, it prints the Country Name (J) value from the Case Record.

13

Information Source

This field represents the Report Type (A.1.4)
For clinical and domestic studies, it prints the E2B M2 Japanese description based on the A.1.4 (REPORTTYPE) value from the Expedited/E2B report.

For foreign ichihen studies, it prints the Report Type (J) value from the Case Record.

14

Report Type7 days/15 days

This field represents the meeting Expedited Report Criteria (A.1.9)
For clinical and domestic studies, it prints 7 days or 15 days, if the value of A.1.9 (FULFILLEXPEDITECRITERIA) is 1 or 2 respectively, in the Expedited/E2B report.

For Foreign Ichihen studies, it is left blank.

15

Subject timeframe

This field represents the Reporting Timeframe considered for the AE.
It prints the Seiyakukyo report current timeframe. The same values are printed in all the rows.

16

For the AE terms, MedDRA/ J version ( ) is used.

This field represents the MedDRA J version used for this report.
It prints the MedDRA version as currently configured in the application for event encoding.

This is repeated at the end of each Clinical Compound Number section.

17

Any additional columns added by the user in configuration (applicable only to CSV output)

Study Name:
For clinical and domestic studies, it prints the value of A.2.3.2 (SPONSORSTUDYNUMB) from the Expedited/E2B reports. For foreign ichihen studies, it prints Study ID (J) from the case record. If Study Name (J) is not available in the case, print the corresponding English value.

Blinded / Not Blinded:

For all types of cases, it prints the Japanese text - Blinded or Not Blinded, based on the Case Form > Study Information > Study Type field value for the corresponding case.

SOC:

For clinical and domestic studies, it prints the MedDRA SOC (J) Term based on the B.2.1.2.b (REACTIONMEDDRAPT) value from the Expedited/E2B report. For decoding the MedDRA PT code from the Expedited/E2B report into J Term, latest MedDRA dictionary configured for Event Encoding is used.For foreign ichihen studies, it prints the MedDRA SOC (J) Term from the Case Event record.

NOTE: Since L, M, and N category cases are not included in the report, this data will no longer be left blank for these categories.

LLT:

For clinical and domestic studies, it prints the MedDRA LLT (J) Term based on the B.2.1.2.b (REACTIONMEDDRALLT) value from the Expedited/E2B report. For decoding the MedDRA PT code from the Expedited/E2B report into J Term, latest MedDRA dictionary configured for event encoding is used.For foreign ichihen studies, it prints the MedDRA LLT (J) Term from the Case Event record.

NOTE: Since L, M, and N category cases are not included in the report, this data will no longer be left blank for these categories.

MedDRA Version:For clinical and domestic studies, it prints the MedDRA version as used in B.2.i.2.a (REACTIONMEDDRAVERSIONPT) from the Expedited/E2B report.For foreign ichihen studies, it prints the MedDRA version from the case for that Event Encoding.

NOTE: Since L, M, and N category cases are not included in the report, this data will no longer be left blank for these categories.

Report Submission Date: For Clinical and Domestic studies, it prints the corresponding Expedited/E2B Report Submission date after converting it into Japanese timezone based on the Argus J > Reporting > Offset from GMT Common Profile Switch that is used to calculate Japanese date/time fields for Interchange-J (in hours). For Foreign Ichihen studies, it is left blank.
Japan Information Receipt Date: For Clinical and Domestic studies, it prints J.3b (mhlwadmicsrinfoobtndatesource). For Foreign Ichihen studies, it prints the Japan Aware date.

ACK Number:

For Clinical and Domestic studies, it prints the eight digit PMDA ACK number received for the corresponding Expedited/E2B report. For Foreign Ichihen studies, it is left blank.

Number of times this report is submitted to MHLW:

For clinical and domestic studies, it prints J.5 (mhlwadmicsrmhlwcumreporttimes) element value. For Foreign Ichihen studies, it is left blank.

Primary Disease:

For all types of cases, it prints the Condition (J) value as present in Case Form > Patient tab > Other Relevant History section. Only those items are printed which have Primary Disease text present in the Notes (J) field. In case multiple items have to be printed, then these are printed in separate lines in the same cell.

Event Intensity:

For all types of cases, it prints the Case Form > Event tab > Intensity (J) field value.

NOTE: Since L, M, and N category cases are not included in the report, this data will no longer be left blank for these categories.

Reported Causality:
Only one value is printed for this field based on the Reported Causality values specified for those products in the case, whose valid Japanese licenses have the same Clinical Compound Number for which this event is being printed. Only the causality values that are related to the current event being printed are considered. The following rule is used to determine the value that is printed in the report output.

Related - If any of the Reported Causalities is Reportable (Consider Expeditable to Authorities is checked in Console Code list)

Not related - Else, if any of the Reported Causalities excluding Unknown is not reportable

Unknown - Else, if any of the Reported Causality is Unknown

No value - Else, if all the Reported Causalities are blank.

NOTE: Since L, M, and N category cases are not included in the report, this data will no longer be left blank for these categories.

Determined Causality:

Only one value is printed this for field based on the Determined Causality values specified for those products in the case, whose valid Japanese licenses have the same Clinical Compound Number for which this event is being printed. Only the causality values that are related the current event being printed are considered. The following rule is used to determine the value that is printed in the report output.

Related - If any of the determined causalities is Reportable (Consider Expeditable to Authorities is checked in Console Code list)

Not Related - If any of the determined causalities is Reportable (Consider Expeditable to Authorities is checked in Console Code list)

Unknown - Else, if any of the determined causalities excluding Unknown is not Reportable

No Value - Else, if all the determined causalities are blank.

NOTE: Since L, M, and N category cases are not included in the report, this data will no longer be left blank for these categories.

18

Section Footer Text

It prints the configured text as specified in Individual Report Common Line List Configuration tab > Section Footer text below the event output table right after MedDRA J Version, in a new line.
This text is repeated at the end of each Clinical Compound Number section.

19

Page Numbering

The page numbering for the Seiyakukyo report starts from 1 for each Clinical Compound Number section independently.
The page numbering for Seiyakukyo report is printed in the middle of page footer in the following format:

<current page number>/<Total Pages>

The page numbering for attached CIOMS reports starts from 1 for each CIOMS independently.

The page numbering for attached CIOMS reports is printed in the top left corner of CIOMS report table (same as in attached CIOMS in PSURs) in the following format:

<current page number>/<Total Pages>

20

Page Size/Font

The MS Word A4 Landscape page size is used for Seiyakukyo report.
Ms Mincho font is used for the report output.

4.2.9.5 CSV Output Format

The Seiyakukyo report also supports printing in the CSV format.

- The Seiyakukyo configuration data is not printed in the CSV format. Only the main Seiyakukyo report output is printed in CSV format.

- The Report Title is put as the first value in the first row.

- All the event rows from the report output including the Header row are put in separate rows.

- The MedDRA J version and Section Footer Text are put as separate rows at the end, in the same way as the report output.

- Each cell value for a row is put as individual item within that row in the CSV format.

- All the comma characters and new line characters within a cell value are supported and maintained in the CSV format. It must not break that cell value into multiple items in CSV. This is achieved by using double quote characters for the cell values to escape such characters.

- All the double quote characters within a cell value are replaced by 2 double-quote characters in the CSV format.

- All valid Japanese characters as specified for the PMDA E2B file (Main ESM J SRS > 19.6.1 point # 15 (c)) are supported by this CSV format.

- Different sections related to different case types and Clinical Compound Numbers are separated by a single blank line.

4.2.9.6 Periodic Report Process Flow

The Seiyakukyo Periodic report is handled in the same manner as other Japanese Periodic reports - PSR/ReSD and CSPSR. All the actions that are applicable to the existing Japanese reports are supported for Seiyakukyo Periodic reports as well.

- All the configured Seiyakukyo reports are listed on the Periodic Report Configuration page.

- All the actions supported on the Periodic Report Configuration page for CSPSR are supported for Seiyakukyo reports as well.

- New Report

- Copy

- Modify

- Delete

- Print

- The Print dialog box for Seiyakukyo lists 2 output formats in the drop-down adjacent to the Run Now option - Word and CSV. The Word output format is selected by default.

- Choosing the Word format for the Run Now action and clicking the OK button displays the output of the Seiyakukyo reports in Word format in the similar manner as CSPSR.

- Choosing CSV format for Run Now action and clicking the OK button displays the Seiyakukyo reports in CSV format.

- Irrespective of the format - Word or CSV, if the report is executed as Final or Draft, it is available in the same format through the standard - FINAL and DRAFT links in the row for that report on the Periodic Report Library screen. In case, you have executed the report with Internal and other options, it is available in the same format using the DRAFT link on the Periodic Repot Library screen.

- No Watermark is put on the CSV format output. It is applicable only for the Word format output in the similar manner as CSPSR.

- If a Submitted report is attempted to be printed in the CSV format, the application displays the following error message with the OK button:
The report is already submitted. You cannot print this report again in CSV format.
However, for Word format, it prints the Configuration page only without any error message.

- All the Seiyakukyo reports are also listed on the Reports > Compliance > Periodic Reports screen.

- All the actions supported on Reports > Compliance > Periodic Reports screen for CSPSR are supported for Seiyakukyo reports as well.

- The View and Edit Seiyakukyo dialog box (View Report right-click menu option) from Reports > Compliance > Periodic Reports screen, supports all the actions (in same manner as View and edit J-DSUR dialog box for CSPSR) for Seiyakukyo Word as well as CSV formats.

- View

- Check-in

- Check-out

- Publish

- The View or Check-out option displays the Seiyakukyo report in the same format (Word or CSV) that is chosen/checked-in by you.

- You are allowed to check-out the report in one format (CSV) and check-in the file in other format (WORD).

- If you click the Publish button and the last checked-in file is in the CSV format, it displays the following warning message with Yes and No buttons:
As this report exists in CSV format, it will not be converted into PDF format while publishing it. It will be published as it is in CSV format itself. Do you want to proceed?

4.3 Non-Reportable and Invalid Events

When all the event in a case become Non-Reportable then system will scheulde a Downgrade report.

When all the events in the case becomes Invalid then system will schedule a Nuliffication report for Marketed Licenses(Reporting Catgeory: 1,2,3,4).

When all the events from the previously submitted Report becomes Invalid then system will schedule a Nuliffication report for Investigational Licenses(Reporting Catgeory:8,9,10,11).

5 Utilities

This chapter lists the changes that have been introduced in MedDRA browser in the Argus Safety 7.0.3 release.

5.1 MedDRA Browser

- A new checkbox has been added in MedDRA browser "Include Non-current terms" as shown in the screenshot below. This is unchecked by default.

Figure 5-1 Case Form - MedDRA browser with Noncurrent terms option

- This checkbox is enabled only when MedDRA Browser is used for searching on local MedDRA dictionaries.

- When MedDRA Browser opens up to perform further searches on MedDRA Web Service, then this checkbox is unchecked and disabled.

- When the user searches for a term by marking "Include Non-current terms" checkbox, the system retrieves the matching non current terms along with the Current terms.

- The Non current LLT terms are displayed preceded with an asterisk (*) symbol separated by a space, in the search results grid as well as bottom section which displayed the selected term details. On clicking on non current term, system displays its PT, HLT, HLGT, and SOC terms. Note that existing application logic to determine non-currency of a term is either based on English or Japanese currency of the term in different scenarios. Hence, the asterisk (*) symbol that is displayed is appropriate.

- If MedDRA J is not configured, then only English currency is used.

- If MedDRA J is configured and MedDRA Browser is opened from a Japanese base language screen, then only Japanese currency is used.

- If MedDRA J is configured, MedDRA Browser is opened from an English base language screen (for English as well as Argus J user), and Country of Incidence is Japan, then English as well as Japanese currency is used.

- If MedDRA J is configured, MedDRA Browser is opened from an English base language screen (for English as well as Argus J user), and Country of Incidence is not Japan, then only English currency is used.

- On selecting a noncurrent term in the MedDRA browser by clicking 'Select' button, the following message is displayed:
Selected term is a non-current term in the MedDRA dictionary. Please select a current term.

- The MedDRA Browser print PDF also displays the asterisk (*) symbol in front of the non-current LLT.

Figure 5-2 Case Form - MedDRA browser Print

- The MedDRA Browser print PDF displays the footnote as follows in the Print PDF report: Non-current MedDRA term

- The following common profile switches are added to Common Profile > Case Processing > Dictionary Browser

Profile Switch

Attributes

Description

Allow User to Add Non-Current MedDRA Terms for

Option 1:
Case irrespective of Country of Incidence

Option 2:

Case where Country of Incidence is other than Japan

Default Value: Option 2
If the default value is configured, then:

For the COI other than Japan - You can select a MedDRA LLT term for which LLT (J) is non-current as it does today i.e. based on English currency.For the COI as Japan - The existing application behavior remain same, and if you add a LLT with Non-current LLT(J), an error message appears (for both English and Japanese users).

If Option 1 is configured, then:

Irrespective of COI of the case both English and Japanese users are allowed to add a LLT to the case for which LLT (J) is non-current i.e. based on English currency.

An icon indicator appears for the Non-current LLT (J) term in the English version of the Case Form similar to the Japan version for both English and Japanese users.

On change of LLT Term Sync English and Japan LLT's, irrespective of the currency

Option 1:
Yes

Option 2:

NoThis profile switch is enabled only if the profile switch "Allow User to Add Non-Current Meddra Terms for" is configured to Option 1.

Default Value: Option 2
If the default value is configured, then:

If J user updates the non-current LLT (J) to a current LLT (J), then the LLT (E) is not updated for the same PT. If J user updates the non-current LLT (J) to a non-current LLT (J), then the LLT (E) is updated for the same PT.

If Option 1 is configured, then:

For Globally Unlocked Case - If J user tries to update the LLT (J), then the corresponding LLT (E) is also updated.

For Globally Locked - Locally unlocked Case - The J is not allowed to update the LLT (J) irrespective of the MedDRA currency, and an error message is displayed:

Case is Globally locked, hence user is not allowed to update the LLT(J) term.

- Any changes to these profile switches are audit logged.

- The behavior of these profile switches for MedDRA encoding is applicable for both internal MedDRA encoding, and MedDRA encoding using Web-services.

Note:

As per the MedDRA guidelines such LLT term can never exist in MedDRA Dictionary as LLT (E) is non-current but LLT (J) is current, and hence the application is not required to handle it.

Besides, the terms for which LLT (E) and LLT(J) both are non-current are never allowed to be entered or updated in the case irrespective of the value of the switches.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2018, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.