
As I discussed in my previous post, FDA issued version 1.5.1 of Study Data Specifications in January of 2010. Although the changes in the new version were not great, they were significant for eCTD as a new specification for organizing datasets was defined. The change has to do with how the files are organized in the file structure in which an eCTD is delivered to indicate whether they were STDM or legacy format. However, the change had no effect on the Table of Contents that is visible to a reviewer (created from the eCTD XML backbone). In a recent development, ICH M2 working group has defined an update to the valid values list for study tagging files to introduce file tags that would allow a review tool to identify dataset types when displaying the eCTD Table of Contents.
The new specifications for organizing study datasets and their associated files in folders are summarized in the following figure. In the document, an accompanying table provides further definition of the folders.
New Dataset Folder Organization
Compare this with the folder structure required in the previous specification:
Previous Dataset Folder Organization
You will see an important difference: tabulations must be assigned to a folder based on whether they are STDM datasets or legacy format. A second difference is that there is now a separate folder for datasets under analysis, where previously analysis datasets were placed directly in the analysis folder.
At the recent ICH meeting in Estonia, the valid-values.xml that defines file tags used to identify the documents in studies was amended to better support the different types of data:
Look for the new valid-values.xml on the ICH websites in a zip file. You should talk with your publishing vendor to find out how and when they will support the updated specification.
One final note – the FDA recently retired their own version of the valid-values.xml and reverted to the ICH version. That means that they restored the file tag of nonclinical-data. However, the preferred file tag for a nonclinical study is pre-clinical-study-report.
As most people who work with eCTD are aware, agencies will accept clinical study reports structured in one of two ways:
There are advantages and disadvantages to each, which are outside the scope of this posting (you can request GlobalSubmit’s white paper “What Makes an eCTD Clinical Study Easily Reviewed by the FDA?” if you are interested in more detail). And in fact, thorough our work with the FDA, GlobalSubmit has found that some clients take a “hybrid” approach and submit a legacy report along with other files. Whatever approach is taken, the study, through the mechanism of the study tagging file, must be constructed so that each component is properly tagged and identified.
In a recent gathering with representatives from a number of Pharma companies, the question was raised (mainly regarding US submissions) as to which of the two formats sponsors were using.
The companies who have been submitting eCTD for some time appear to have made the switch to the granular/E3 format for the most part. However, they had different ways of meeting the review and approval challenges that are brought on when you no longer have a single document (or set of paper binders) to approve:
Sponsors need to understand how clinical reviewers will be seeing the studies they submit. You can see some FDA presentations on this subject on GlobalSubmit’s Agency Presentations page. Sponsors can also contact us to learn more about the FDA’s eCTD viewer, which is a GlobalSubmit product.
*** Update: the links below, which had been working fine between when this was posted and today (May 18), appear to be no longer functional. Possibly the AAPS had not meant them for public consumption; however, I have not been contacted by them so I don’t know this for sure. Apologies that the links no longer work but they are out of my control. - K.C. ***
You could contact the AAPS, or see if you can track down the speakers and ask them for the presentations. The following email addresses were included:
Agencies:
Health Canada: ereview@hc-sc.gc.ca
EMEA: eCTD@emea.europa.eu
PMDA: ectd-helpdesk@pmda.go.jp
MPA: karin.grondahl@mpa.se
FDA: gary.gensinger@fda.hhs.gov
The AAPS Workshop on Strategic Management of CMC Dossiers in the eCTD Format: What CMC Professionals Need to Know Now! was held March 9-11, 2009. There were some great presentations, and best of all they are publically available. The agenda contains links to the presentations.
All the presentations were good but some of the highlights for me appear below. There’s great information on Japan and Health Canada that has been rather hard to locate recently, and lots of discussion about some of the more puzzling and problematic aspects of eCTD as they relate to CMC in particular – so you know there will be discussions about metadata, granularity, and the tradeoffs in structuring M2 and M3.
Evdokia Korakianiti of EMEA presented eCTD: EMEA Experiences containing FAQs received by the EMEA, concerning CMC metadata, CEPs, ASMF – plus some great key messages for industry.
The presentation eCTD in Japan by Harve Martins has lots of good info on eCTD in Japan that has not been readily available – such as details and examples on lifecycle (handled in an accumulative approach in Japan), Module 1 TOC, cover letter and form information, module 5 unique requirements, validation details, submission instructions, etc. I’ve reproduced the update on the number of sequences received in Japan (keep in mind that a reference application is something like Health Canada’s co-submission – in effect a review aid for a paper submission.) 
Health Canada’s Vianney Caron presented e-Submissions at Health Canada which reviewed HC’s history and future direction with eCTD, challenges and issues with CMC documents, especially the QOS. Health Canada also presented statistics on the number of eCTDs they have been receiving (they now get about 7% of their regulatory activities in eCTD format).
Regulatory Activities in eCTD format (NDS, SNDS, ANDS, SANDS, NC)
About 8.2% of submissions are currently failing validation, well down from the 31% experienced in early days. Following the lead of FDA and EMEA, they have provided their top 10 list of validation errors:
1. Inactive bookmarks -no link destination
2. Inactive hyperlinks -no link destination
3. External links -pointing to the folder or destination that does not exist in the folder structure on the CD/DVD. The folder or destination would only exist in the sponsor's repository.
4. Incorrect naming of the 3011 form (correct name is hc-sc-3011-en.pdf)
5. Unreferenced files in the index.xml or ca.regional.xml
6. Life cycle management of the document: invalid file reference or no previous ID found
7. Subfolders created in ca regional folder
8. Missing top level folder
9. Missing attestation letter; content as per eCTD Guidance, letter needs to be dated and signed
10.Printed content of MD-5 Checksum does not match the one in the index-md5.txt file
Health Canada strongly recommends electronic submissions in eCTD format, and they plan to expand the existing architecture to support as many application types across product line as possible. Some of their next steps in support of eCTD include:
The eCTD Industry Forums –Europe presentation by Phyllis Thomas of AstraZeneca UK summarizes discussions by the CMC eCTD informal industry group and EFPIA eCTD-Q topic team. It has lots of discussion about metadata and repeating section issues, including illustrative examples. It also discusses issues and areas that lack clarity that have been passed on as Q&A and in turn referred to the harmonization taskforce (some of them not yet resolved).
ICH & Regional Guidance and Terminology by Hans van Bruggen provides a comprehensive summary of eCTD status in many regions (including individual EU countries). Again, this is information that is hard to find and nearly impossible to find in one place.
In Points to Consider for Case Studies in Lifecycle-Biologics, Colleen Godshall of Merck addresses some of the issues that have always caused me to hold CMC people in awe: however do they perform impact analysis of change and manage the approvals and notifications requirements that are so different in every region? Concrete examples are provided, such as “Adding a New Air Handler to a Class 100 Area used to manufacture multiple vaccines”. Ms. Godshall also talks about managing 3.2.A.1 for both US applications, which allow cross-applikcation linking, and International Marketing Authorizations, which do not.
A presentation by Pamela Cafiero of Boehringer Ingelheim, Simultaneous eCTD Applications in US and EU: Similarities/Differences and the Reasons Behind them, gives detail on a subject I’ve been asked about many times – what are the real differences in content between US and EU Module 3? She also gives recommendations about document identification (header/footer), Referencing between CMC documents, referencing and linking within Module 3 (her minimalist approach resulted in about two dozen links between Module 3 documents and was the same in US and EU), and recommendations and examples of CMC metadata, leaf titles and the relationships between them.
Phyllis Thomas of AstraZeneca UK also spoke about USING MODULE 3 (FOR INDs). She focused on encouraging the use of granularity in IND M3 (even though it is not required) and some special considerations for INDs such as Placebos, Comparators, and Introductory CMC text.
In general, the changes proposed in Version 3.3.3 were more beneficial to industry that to regulators. The agencies had concerns about the cost and effort of implementing the specification as it was largely focused on incorporating the STF into the eCTD backbone. FDA already considers that they have a satisfactory solution in the STF as it stands, and other regions have not identified any requirements for the STF. Japan in particular was said to be concerned about having to update newly completed procedures and tools to support 3.3.3 in the short term; however, a PMDA representive at the DIA Doc Management meeting expressed “strong support” for eCTD 4.0 during the February 7th International Regulatory Update session.
The M2 EWG also expressed a desire to improve the narrative portion of the specification and address those change requests that can be resolved without changes to the DTD. To the extent possible, existing Q&As will also be incorporated. This revised specification document will be issued as eCTD Version 3.2.1 during the coming months. Version 3.2.1 of the eCTD specification will be accompanied by an updated version of the Study Tagging File (STF) specification, version 2.6.1, which will address improvements to the narrative portion of this specification in the same way but will also not make any changes to the existing STF DTD.
See http://estri.ich.org/eCTD/news.htm for details.