The eCTD summit

You are currently browsing the The eCTD summit blog archives for January, 2009.

eCTD on Twitter

  • Malta: Requirements on Electronic submissions for New Applications within National and European procedures #ectd
    http://bit.ly/9m1pQl
    2010/09/08 09:39
  • Check out Reed Tech's LabelDataPlus super search tool for SPL, searching repository of of 27052 drug labels:
    http://bit.ly/cYdc98
    2010/09/07 12:03
  • Highlights of IRISS Interoperability group’s July, August mtgs posted, incl some FDA news
    http://bit.ly/bPEeEN & http://bit.ly/brD5OY #ectd
    2010/08/31 10:07

Visit GlobalSubmit

gs_logo22

The eCTD Company™

Our Visitors

Archive for January, 2009

Australia Re-Releases M1 Guidance for CTD

posted by Kathie Clark @ 11:35 PM
Tuesday, January 27, 2009

In my last post, I mentioned new TGA eCTD information.  TGA has also updated CTD module 1 guidance.

The TGA has released a new version of Module 1: Administrative Information and Prescribing Information For Australia, dated November 2008. Fortunately this agency includes a nice Document Change Record at the beginning of the document. Changes include:

  • References to TGA organisation and titles updated
  •  Text amended to reflect changes in GMP clearance for prescription medicines as a result of the introduction of TGA eBusiness Services (Part B Module 1.7)
  • Addition of Module 1.13 Information relating to Pharmacovigilance (Part B Module 1.13)

Module 1.13 is entirely new. It consists of a Risk Management Plan for Australia, as outlined in Chapter 1.3 of EudraLex Volume 9A – Pharmacovigilance for Medicinal Products for Human Use (version September 2008).

New AU eCTD Guidance

posted by Kathie Clark @ 8:18 PM
Friday, January 23, 2009

Australia has published their long-awaited eCTD guidance:

The AU M1 guidance bears a strong resemblance to EU Module 1 Specification. 

I noticed a few interesting items in the Guidance for Industry:

  • Section 4.1 allows for Word or RFT to be submitted in addition to PDF for general narrative documents (not just in M1 and M2).  This is considered a review aid, but in this case both documents are stored together in the eCTD (presumably linked into the backbone), not stored separately outside the eCTD such as is the case with MS Word for M1 and M2 in EU.  The AU guidance seems to imply that M1/M2 Word documents are stored outside the eCTD as in EU - it’s a little unclear as to whether these can be linked into the backbone.
  • Section 4.4 includes a list of documents that must be text searchable, and a list of documents that do not need to be text searchable.  To my knowledge, this has not been required in the past for eCTD, only for NeeS (with the possible exception of a few individual authorities in Europe).  Some companies will need to update their procedures to OCR key documents - although of course it’s better to create them from MS Word source in the first place.

FDA to begin rejecting eCTDs for significant technical issues

posted by Kathie Clark @ 2:29 AM
Wednesday, January 21, 2009

Due to the increased adoption of the eCTD and number of submissions received by the U.S. FDA, submission quality is receiving increased focus and attention at the U.S. FDA. In recent conversations with FDA officials, they have expressed a commitment to increase their diligence and oversight with respect to submission quality and have signaled their intention to begin rejecting eCTD sequences having significant technical issues. Although no specific date has been established for this step, expect an announcement of intent early in 2009, with enforcement beginning some months later.

What are Significant Technical Issues?

Significant technical issues are those defined in eCTD validation criteria However, expect these criteria to be updated and re-issued based on several factors:

Enhancement of FDA’s Validation Software. FDA recently updated their validation software (GlobalSubmit VALIDATE Version 5). The updated software detects additional errors not documented in the current validation criteria. These error checks were added based on feedback from FDA IT staff and reviewers. The new software went live in CBER and CDER in late November.

Analysis of Error Trends. The new software also allows the FDA to fulfill a PDUFA mandate to report back to sponsors on eCTD errors. Specifically, PDUFA IV Information Technology Plan, DRAFT, December 2007, requires reports on “Total number of standards-based electronic submissions that fail to comply with FDA electronic submission standards, along with a distribution of these submission failures across categories of failure or problem type”. After studying the distribution of eCTD submission errors, FDA may choose to re-classify the severity of some of the errors.

Issues and Inefficiencies Caused by Problematic eCTDs. FDA also experienced problems with invalid data (especially application and sequence numbers) in the course of moving to VALIDATE 5 and integrating with other databases and systems at FDA. This caused a significant amount of manual processing to address the problems and resulted in delays in the upgrade and integration process. As the number of eCTD sequences received by the FDA is growing exponentially, they cannot continue to accept sequences that need to be manually corrected before they can be loaded and made available to reviewers.

Groundwork Already Established

This action should not come as a major surprise to sponsors. FDA has been laying the groundwork for this step for some time. FDA validation criteria defines the impact of a high severity error as “The error is a serious technical error which prevents the processing of the submission and will require resubmission. The submission is considered not received by FDA.”

In the guidance document “Guidance for Industry: Providing Regulatory Submissions in Electronic Format — Receipt Date”, they say:

The FDA will consider a technically deficient application not received until the technical deficiencies are resolved and the application is resubmitted. Examples:
Defect in media, lack of electronically readable application form, re-use of sequence number, missing index.xml and/or us-regional.xml, virus
High priority errors identified in validation criteria

Sanctions are also discussed in Section IIH of “Providing Regulatory Submissions in Electronic Format - Human Pharmaceutical Product Applications and Related Submissions Using the eCTD Specifications”.

Impact and Recommendations

FDA anticipates that the step may result in the rejection a few percent of all sequences, based on the quality of submissions currently being received. It is not their intent to issue Refuse to File for a rejection, but it will prevent the PDUFA clock from starting, resulting in a significant cost impact to sponsors. Delays also increase the chance of a complete response- which stops or extends the PDUFA clock.

I strongly recommend that all organizations who produce eCTDs establish quality processes and procedures to ensure the quality of submissions. Tools that support eCTD review and validation are essential to ensure the overall quality and integrity of the submission to avoid costly errors and the potential rejection of the submission sequences. However, even the best tool must be used in combination with a thorough, repeatable, documented process in order to yield consistently excellent results.

Good bye NeeS!

posted by Kathie Clark @ 11:45 AM
Friday, January 9, 2009

Sounds like EMEA stayed busy through the holiday season as they posted four new or updated guidance documents at the end of December. Most significantly, EMEA implementation of electronic-only submissions and mandatory eCTD submissions in the centralised procedure: Statement of Intent tells us:

“From 1 January 2010, the EMEA will mandate the use of the eCTD format for all electronic-only submissions for all applications (new and existing) and all submission types. Rapporteurs and CHMP members will not receive paper copies or other electronic formats.”

As with the rest of the EMEA’s statements and guidelines pertaining to eCTD, this only applies to the Centralised Procedure.

A “matching” statement of intent for non-eCTD electronic submissions tells of the retirement of NeeS. It also announces the introduction of a set of specific guidelines on submission structure, format and presentation, which non-eCTD submissions should adhere to for the centralised procedure from 1 February 2009 until such time as the eCTD format is mandatory. These guidelines are found in EMEA implementation of electronic-only submissions eCTD submission: Practical guidelines relating to Non-eCTD submissions.

Finally, the highly useful document EMEA Implementation of Electronic Submissions and eCTD Submissions Statement of Intent Q&A Relating to Practical and Technical Aspects has been re-issued. Changes are minor and include asking for virus checking information in the cover letter instead of a reviewer guide, and acknowledging a discrepancy between the eCTD file naming
convention and the PDF file naming requirements for EPAR (product information) documents (you are advised to use eCTD file naming conventions for the time being).

My collegue discussed this announcement with EMEA representatives this week, and they have indicated that although they are not in a legal position to require electronic submissions, they strongly recommend against paper submissions.

(P.S. After an internal struggle, I suppressed the urge to label this post “It’s Been NeeS”.)

The eCTD summit is proudly powered by WordPress