After generating the Compliance Package, the binder enters the Draft state, and users can review and make changes to the 2253 or Supplementary Form, relative PDF links, reference documents, PI labelling material, supporting documents, or promotional material version. Do not make changes to the binder metadata, as Vault automatically generates metadata when creating the Compliance Package. Changes to the binder metadata will not be reflected in the binder.

To make changes to the documents:

  1. Navigate to the eCTD Source document. To find this document, open the document to be updated and click the eCTD Source relationship link.
  2. Update the eCTD Source document or linked supporting documents.
  3. Return to the binder.
  4. Click the Actions menu and select Regenerate Compliance Package.

Vault notifies you after Compliance Package generation is complete. The process may take several minutes to complete.

Regenerating the Compliance Package moves the binder to the Draft state, up-versions it, and updates all documents in the binder that are linked to the eCTD Source documents. Vault up-versions the 1.15.2.1.2 Annotated Version by 0.2, while others up-version by 0.1. If you manually add any documents to the binder that aren’t linked to the eCTD Source through a Vault link annotation or document link, they will not be up-versioned. If you add a new Vault link annotation, linked document, or supporting document to the Promotional material before regenerating the Compliance Package, Vault copies the document and adds the Submission Ready copy to the binder. You must edit the eCTD Source documents directly to ensure edits are reflected upon regeneration. If you remove any linked or supporting documents from the promotional material, you’ll need to delete the copied versions from the binder.

The Regenerate Compliance Package user action does not work if you manually add documents to the eCTD binder after regenerating the package.

Completing Validation on Multiple Generated Packages

Validation occurs before multi-package generation. Vault notifies you of validation errors after you select the applicable bulk action. To correct these errors, you can either click Back or click Cancel and restart the bulk generation process.

Common validation errors may include missing field values and incorrect document types.

Adding Material

If previously configured in your Vault, you can click the Actions menu and perform a user action to add documents to the binder and regenerate the Compliance Package. You can only add documents with the same Product as the Product selected when generating the eCTD Compliance Package.

On regeneration, Vault creates submission-ready copies of the new material and updates forms and the Correspondence Letter where necessary. If the added documents have supporting documents linked via the eCTD Support Documents relationship, Vault creates and adds submission-ready copies of the supporting documents.

To add documents and regenerate the Compliance Package, you must have the Edit Document and Version permission on the lifecycle state.

Vault notifies you after Compliance Package regeneration is complete. The process may take several minutes to complete.

You can open Vault-generated relative PDF links in PromoMats or in a desktop version of Adobe. In PromoMats, click the relative PDF link in a document to open the linked material in a mini-browser window.. To check the relative PDF links in Adobe:

  1. Click Export Compliance Package.
  2. Unzip the exported file.
  3. Open applicable documents in Adobe. You will not be able to do this on an internet browser.
  4. Click the relative PDF links.

To replace Vault link annotations and linked documents after generating the Compliance Package:

  1. Navigate to the clean material Promotional piece eCTD Source document in the binder. To find this document, open the document to be updated and click the eCTD Source relationship link in the Document Relationships section.
  2. Update Vault link annotations and linked documents as desired.
  3. Return to the binder.
  4. Click the Actions menu and select Regenerate Compliance Package.

When Compliance Package generation is complete, delete the binder documents from which you removed Vault link annotations. These documents were not up-versioned in the 1.15.2.1.3 Annotated Labeling Version, 1.15.2.1.4 Annotated References, and 1.14.6 Product Labeling sections. If you manually added the documents to the Compliance Package during this process, or if the documents were added as part of the regeneration process, Vault did not up-version them. Do not delete these documents if you want to keep them.

Note that, for Pre Clearance Compliance Packages, you may need to add additional manual annotations to the documents in Adobe before submitting the package to the FDA.

Reviewing the Compliance Package

When you are satisfied with the binder, you can move it to the In Review state, allowing the eCTD Regulator to review the Compliance Package. If the eCTD Regulator rejects the binder, you’ll need to move it to the Revise and Resubmit state, make the necessary changes, and regenerate the binder. Then, move the binder to the In Review state and allow the eCTD Regulator to review the package again. Once the eCTD Regulator approves the Compliance Package, move the binder to the Submission Ready state.

Reviewing the Correspondence Letter

Before exporting a Pre Clearance Compliance Package, you’ll also need to review the Correspondence Letter. For submission to the FDA, the Correspondence Letter must be a PDF file. The Correspondence Letter that is generated as part of the Pre Clearance Compliance Package is a Microsoft Word document. You can edit the document by updating the metadata directly. Once you’ve reviewed the Correspondence Letter, you’ll need to download the viewable rendition. Upload the PDF file as a new version of the Correspondence Letter document. Then, return to the eCTD binder and click Edit Binder. In the Correspondence Letter section, click the Actions menu and select Set Version Binding. Select Always show the latest version, then click Done editing to save your changes. This allows Vault to export the Correspondence Letter as a PDF file as part of the Compliance Package.

Exporting the Compliance Package

After the eCTD Regulator approves the binder, the Compliance Package Publisher can perform the Export Compliance Package user action, download the ZIP file, and extract the documents. The Compliance Package Publisher can then import the documents into a RIM Publishing Vault.

To import the Compliance Package to RIM Publishing Vault:

  1. Upload the ZIP file into a RIM Publishing Vault.
  2. Create a Submission Content Plan.
  3. Match documents from the Compliance Package to the content plan structure.
  4. Using RIM Publishing, prepare the content for submission to the FDA.

If you need to edit the package content while working in the RIM Publishing Vault, you’ll need to return to PromoMats, move the binder to the Revise and Resubmit state, and update the contents.

When the package is finalized for submission in RIM Publishing, you can submit the package to the FDA. After submitting the Compliance Package, return to your PromoMats Vault and move the binder to the Submitted state. You’ll also need to move the promotional material to the Steady state.

FAQ

Why were some documents not converted to PDF?

When generating the binder, Vault up-versions all Submission Ready Copy documents included to Draft v0.2 as a PDF unless the original source doesn’t have a PDF rendition. This may happen with large documents. You’ll need to upload a PDF of the document and manually create the relative PDF links and destinations.

What information is included in the metadata.xml file?

When you use the Export Compliance Package user action, Vault generates a ZIP file. After extracting files from the ZIP, you’ll see the contents of the binder and an XML file. The XML file contains details about documents in the binder, including 2253 and Supplementary Form field data where applicable. Download a sample metadata.xml file.

No. If the link annotation and anchor are in the same document, it won’t be converted to a relative PDF link.

If a link annotation links to multiple documents, the destination will only link to one (1) of the documents when converted to a relative PDF link. If there are multiple link annotations on the same text or area, the destination will only link to one (1) of the documents when converted.

Will the eCTD Source relationship type take me to the document used to create the Compliance Package?

The eCTD Source relationship links to the latest version of the document Vault used to create the document copy included in the Compliance Package.

Why does the Export Compliance Package notification show a higher document count than I selected at the beginning?

The binder generates Submission Ready Copies of the documents selected at the start of the bulk action, including documents linked through link annotations or linked documents, such as reference materials and PI labelling materials.

What happens if I add another XML file to the Attachments section of the binder metadata?

When you export the Compliance Package, the XML file generated includes any XML files included in the Attachments section. If you notice data is missing after exporting, you can add it as a separate XML file in the Attachments section of the binder. Then, export the Compliance Package again and the XML file generated will contain all files from the Attachments section.

Is the latest version of the 2253 form always shown in the binder, regardless of the binder version?

Yes. Performing the Generate Form 2253 action up-versions the 2253 and Supplementary forms. The latest version of the forms are available on all versions of the binder.

If I manually add documents to the eCTD Compliance Binder after it has been generated, will those documents be included in the export?

Yes. All documents in the binder are included in the export and corresponding XML file. However, it is your responsibility to ensure that the manually-added documents are correctly named to meet FDA requirements that Vault link annotations are converted to relative PDF links.

Yes. To add new promotional material to the eCTD Compliance Package, click the Add Material to Compliance Package user action. This user action must be configured by an Admin.

Can I change the Material Type after generating the eCTD Compliance Package?

No. To change the Material Type, you’ll need to archive or delete the binder and its contents and create a new Compliance Package.

Can I change the Center from OPDP to APLB (or vice versa) after generating the Pre-Clearance Compliance Package?

No. To change the Center field, you’ll need to archive or delete the binder and its contents and create a new Pre-Clearance Compliance Package.

Can I update the Correspondence Letter after generating the Pre-Clearance Compliance Package?

Yes. You can edit document fields directly on the Correspondence Letter after the Compliance Package generates. When you’re finished editing, refresh the page to update the document. Note that changes to the eCTD Source materials will only appear on the Correspondence Letter after regenerating the Compliance Package and then re-rendering the Correspondence Letter.

Can I update the Include Linked References field on the binder metadata after generating the Post Marketing or Pre Clearance Compliance Package?

No. To update the Include Linked References field, you’ll need to archive or delete the binder and its contents and create a new eCTD Compliance Package.

Why isn’t the reference material where I expect it to be?

If the same reference material has destinations for multiple materials, it only appears in one (1) section, but includes destinations of the relative PDF links from the other material. This is also true of PI labelling material.

Why isn’t PI labelling material included in my eCTD Compliance Package?

Verify with an Admin that the eCTD Compliance Package is configured correctly. When uploading PI labelling material, your Admin must be sure to assign the same document type as identified in on the Application Settings page. The document must be linked to the promotional material with a link annotation or document link. To ensure that Vault populates section (6) of the 2253 form, your Admin must attach the PI labelling document to the Current PI/Label Number field on the product record.

Why am I receiving a server issue when exporting the Compliance Package?

Exporting the Compliance Package in Firefox or Safari browsers may result in a server error. We recommend using the Google Chrome browser to export the package.

What file types can I add as the Final Video/Audio rendition type?

You can add any file type as the Final Video/Audio rendition type. Note that you should only add the Final Video/Audio rendition type to the document with the final version of the video or audio file that you are submitting to the FDA.

Which permissions do I need for eCTD Compliance Packages?

See the list of related permissions below.

How are documents named in the binder?

You can view the naming rules for documents here.

How many documents can I include in an eCTD Compliance Package?

You can include a maximum of 50 Promotional Materials in a Compliance Package. The total number of materials and supporting documents in an eCTD Compliance Package should not exceed 250.

Why aren’t my supporting documents being added to my Compliance Package?

There are two (2) criteria for adding supporting documents to a Compliance Package:

  • The supporting document must be one of the standard eCTD document subtypes in the Supporting Documents document type.
  • The supporting document must be linked to the promotional material using the eCTD Support Documents document relationship.

If one or both of the criteria are not met, Vault will not add the supporting documents to the Compliance Package.

The following permissions and document type and role permissions now control the ability to work with eCTD Compliance Packages. You must apply the document role permissions to states in the lifecycle your promotional material is using. By default, this is the Material lifecycle.

Type Permission Label Controls
Security Profile Object: Center: Read Ability to create the eCTD Compliance Package.
Security Profile Object: Promotional Material Document Type: Read Ability to create the eCTD Compliance Package.
Security Profile Object: Indication: Read Ability to create Pre-Clearance eCTD Compliance Packages. This permission is optional.
Security Profile Object: Dosage: Read Ability to create Pre-Clearance eCTD Compliance Packages. This permission is optional.
Security Profile Object: Product Indication Join: Read Ability to create the eCTD Compliance Package.
Security Profile Object: Indication: Edit Ability to edit the Indication object and create object records.
Security Profile Object: Dosage: Edit Ability to edit the Dosage object and create object records.
Security Profile Object: Product Indication Join: Edit Ability to edit the Product Indication Join object and create object records.
Document Type eCTD Submission Ready Documents: Create Binder Ability to create eCTD Submission Ready Document binders.
Document Role Material: View Content Ability to generate the eCTD Binder and all applicable documents when linked references (relative PDF links) are included. Add this permission to the state the document is in when the bulk action is performed to create the eCTD binder.
Document Role eCTD Submission Ready Documents: Download Source Ability to export the compliance package.
Document Role Edit Document Ability to add documents to the binder and regenerate the Compliance Package.
Document Role Version Ability to add documents to the binder and regenerate the Compliance Package.