PAAB Tag Report 2025

A quarterly review of the eFiles tag report 
Total number of submissions*
QUARTER 1 QUARTER 2 QUARTER 3 QUARTER 4
2107 2174

*Refers to unique eFiles. This number does not account for iterations within each file.

 Total number of client tags (prior to validation) 
QUARTER 1 QUARTER 2 QUARTER 3 QUARTER 4
18 10
Tag submitting company and manufacturer distribution 
QUARTER 1 QUARTER 2 QUARTER 3 QUARTER 4
4 & 1 1 & 4
 Therapeutic area distribution
QUARTER 1 QUARTER 2 QUARTER 3 QUARTER 4

4

Pulmonary

3

Neurology

3

Psychiatry

3 Dermatology
2 Oncology
2 Infection & Infestation
1 Gastrointestinal

4

Psychiatry

3

Dermatology

2

Pulmonary

1

Women’s Health

 Total number of tags deemed valid following internal review
QUARTER 1 QUARTER 2 QUARTER 3 QUARTER 4
9

3

 

Validated tag breakdown
QUARTER 1 QUARTER 2 QUARTER 3 QUARTER 4
2 Inconsistent with code guidance
2 New issue raised late in the review
2 Issues with level of expertise
1 Inconsistencies with historic approvals for the same brand
1 Particularly helpful comment
1 New issue raised late in the review

1

Issue with level of expertise

1

New issue raised late in the review

1

Request unclear even following clarification call

 

Q2 PAAB Action Taken:

While no consistent trends were observed across this quarter’s tickets, PAAB continues to use each one as an opportunity to reinforce best practices with the Review team.

The tickets prompted a helpful reminder around the importance of avoiding late comments. While we strive to prevent these entirely, we recognize that on rare occasions they may occur. In response, Reviewers discussed practical ways to help minimize the impact on clients, such as prioritizing the review upon resubmission, offering to jump on a quick call, and being as clear and specific as possible about the nature of the comment and potential solutions.

Reviewers also discussed how to enhance the clarity of their guidance overall. This includes providing concrete examples, direct links to relevant guidance documents, and references to precedent files. These help to better explain both the rationale for the request and how to address it in revisions.

Reasons for not validating a tag:

The invalid tags this quarter had a trend in misunderstanding of PAAB Code guidance documents by the submitter. This led to the submitter perceiving there to be a lack of expertise. Evaluation of the initial guidance and final ruling uncovered no lack of expertise.  

Q1 PAAB Action Taken:

In one case that resulted in two tags, a piece was reviewed based on the pre-NOC Product Monograph. When the NOC was granted, the monograph had changed and no longer supported the claim in question. However, the reviewer did not identify this update and proceeded with the review. The discrepancy was later caught in a subsequent submission and addressed at that time. This incident prompted a reminder to PAAB staff during a reviewer meeting to carefully assess any changes between pre-NOC and NOC Product Monographs, as such changes may impact the validity of previously reviewed content.

Several tags also led to one-on-one follow-ups with reviewers to address, in general terms, clarity of written correspondences with respect to intent and accuracy of comments and the precision of code application. As part of this process, the team was reminded to refer to previous layouts when applicable, and to guide clients to supplemental documents when they can provide a clearer explanation of how specific code sections apply.

Reasons for not validating a tag:

We’ve observed a recurring issue with the use of the tag: “The requested revision was unclear to me even following a clarification phone call.” In several instances, no corresponding call is documented in the eFile. Please note that this tag is only valid if a call has actually occurred. Be sure to use this tag only after a clarification call has taken place.

Additionally, some tags marked as “Perceived issue with level of expertise” were deemed invalid. In these cases, the reviewers' feedback was accurate, and the resulting changes were appropriate. Upon review, it appeared that clearer explanations or more precise references to relevant guidances/advisories may have helped improve understanding for the client. Reviewers have been reminded to provide specific rationale and direction to support clarity.

Confidence in confidentiality

As a reminder, client tags trigger internal audits for validation by PAAB’s Director of Pre-clearance Services, Yin Man. Any tags pertaining to Yin are validated by the Commissioner and removed from the report provided to Yin. No Reviewer, Senior Reviewer or Director is EVER aware of tags generated by clients. You can be confident in the confidentiality of the tagging system. For additional reassurance, the tagging system, tag assessments, and documented actions taken will periodically be reviewed by an external auditor.

What does PAAB use the tags for?

  • Staff and system performance metrics
  • To identify trends and training opportunities
  • To stay inform on what is going well (best practices) and areas for improvement

If you’d like to learn more about the client tagging system, check out the Client Tagging System Advisory. You’ll also find links to useful videos on  tagging a review and tagging phone calls.

Is there more information you would like to know and see in the next quarterly update? Let us know on the Forum.  

Quarterly PAAB Tag and CEI Report - Q1 2025.pdf
Quarterly PAAB Tag and CEI Report - Q2 2025.pdf

TOPICS

PAAB Q&A

Do you have questions? We have answers!

Learn More

POPULAR TOPICS

Powered by Innovasium