Extensions
Extensions Structure
The Integration of Extensions has the following structure.
<class name="class name" >
<field name="field name" type="field type">field value</field>
...
<extensions>
<extension type="extension type" version="extension version"> <field name="field name" type="field type">field value</ field>
...
</extension>
</extensions>
</class>
Where the XML attributes represent the following:
— class name - The name of the class corresponding to the node of Assembly hierarchy.
— field name - The name of the field being imported.
— field type - The type of field being imported.
— field value - The value of the field being imported.
— extension type - The name of the Extension being imported, (example: m1-us).
— extension version - The version of the Extension being imported, (example: 3.3).
Groups of Extensions by Version and Country
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| AU | 0.9 | m1-au | 0.9 | Folder |
| node-extension | 1.0 | Folder | ||
| 3.0 | m1-au | 3.0 | Folder | |
| node-extension | 1.0 | Folder | ||
| 3.1 | m1-au | 3.1 | Folder | |
| node-extension | 1.0 | Folder | ||
| 3.2 | m1-au | 3.2 | Folder | |
| node-extension | 1.0 | Folder | ||
| AU 2.0 NeeS | au-2-0-nees | 2.0 | Folder | |
| CH | 1.0 | m1-ch | 1.0 | Folder |
| m1-ch-galenic-form | 1.0 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder | ||
| CH | 1.0.1 | m1-ch | 1.0 | Folder |
| m1-ch-galenic-form | 1.0 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder | ||
| CH | 1.1 | m1-ch | 1.1 | Folder |
| m1-ch-galenic-form | 1.1 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| CH | 1.2 | m1-ch | 1.2 | Folder |
| m1-ch-galenic-form | 1.1 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder | ||
| CH | 1.3 | m1-ch | 1.3 | Folder |
| m1-ch-galenic-form | 1.1 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder | ||
| CH | 1.4 | m1-ch | 1.4 | Folder |
| m1-ch-galenic-form | 1.1 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder | ||
| CH | 1.5 | m1-ch | 1.5 | Folder |
| m1-ch-galenic-form | 1.1 | Folder | ||
| m1-ch-responses | 1.0 | Folder | ||
| m1-ch-additional | 1.0 | Folder | ||
| m1-ch-common-form | 1.0 | Folder | ||
| CDN | 1.0 | m1-ca | 1.0 | Folder |
| node-extension | 1.0 | Folder | ||
| CDN | 2.2 | m1-ca | 2.2 | Folder |
| node-extension | 1.0 | Folder | ||
| CN | 1.0 | m1-cn | 1.0 | Folder |
| EAEU | 1.0 | eaeu_leaf | 1.0 | Leaf |
| envelope-eaeu | 1.0 | Folder | ||
| eaeu-envelope | 1.0 | Leaf |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| EU | 1.0 | envelope | 1.0 | Folder |
| eu_module_1_country_specific_information | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| m1-3-1-pim | 1.0 | Folder | ||
| m1-3-1-spc-label-pl | 1.0 | Folder | ||
| m1-additional | 1.0 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| EU | 1.1 | envelope | 1.1 | Folder |
| eu_module_1_country_specific_information | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| m1-3-1-pim | 1.0 | Folder | ||
| eu_pim_additional_documents | 1.0 | Folder | ||
| m1-3-1-spc-label-pl | 1.1 | Folder | ||
| m1-additional | 1.0 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| EU | 1.2.1 | envelope | 1.2.1 | Folder |
| eu_module_1_country_specific_information | 1.2.1 | Folder | ||
| m1-3-1-spc-label-pl | 1.2.1 | Folder | ||
| m1-3-1-pim | 1.0 | Folder | ||
| m1-additional | 1.2.1 | Folder | ||
| m1-responses | 1.2.1 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| EU | 1.3 | envelope | 1.3 | Folder |
| eu_module_1_country_specific_information | 1.2.1 | Folder | ||
| m1-3-1-spc-label-pl | 1.2.1 | Folder | ||
| m1-3-1-pim | 1.0 | Folder | ||
| m1-additional | 1.2.1 | Folder | ||
| m1-responses | 1.2.1 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| EU | 1.4 | envelope | 1.4 | Folder |
| eu_module_1_country_specific_information | 1.2.1 | Folder | ||
| m1-3-1-spc-label-pl | 1.2.1 | Folder | ||
| m1-3-1-pim | 1.0 | Folder | ||
| m1-additional | 1.2.1 | Folder | ||
| m1-responses | 1.2.1 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| EU | 2.0 | envelope | 2.0 | Folder |
| eu_module_1_country_specific_information | 2.0 | Folder | ||
| m1-3-1-spc-label-pl | 2.0 | Folder | ||
| m1-additional | 2.0 | Folder | ||
| m1-responses | 2.0 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| EU | 3.0 | envelope | 3.0 | Folder |
| eu_module_1_country_specific_information | 3.0 | Folder | ||
| m1-3-1-spc-label-pl | 3.0 | Folder | ||
| m1-additional | 3.0 | Folder | ||
| m1-responses | 3.0 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| EU | 3.0.1 | envelope | 3.0.1 | Folder |
| eu_module_1_country_specific_information | 3.0 | Folder | ||
| m1-3-1-spc-label-pl | 3.0 | Folder | ||
| m1-additional | 3.0 | Folder | ||
| m1-responses | 3.0 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| FORM | 1.1 | eu_xml_application_form | 1.0 | Folder |
| m1-eu | 1.0 | Folder | ||
| GC | 1.2 | envelope-gc | 1.2 | Folder |
| m1-gc | 1.2 | Folder | ||
| gc-envelope | 1.2 | Leaf | ||
| gc-m1-responses | 1.2 | Folder | ||
| gc-m1-additional | 1.2 | Folder | ||
| gc_module_1_label | 1.2 | Folder | ||
| gc_module_1_country_specific_information | 1.2 | Folder |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| GC | 1.5 | envelope-gc | 1.5 | Folder |
| m1-gc | 1.2 | Folder | ||
| gc-envelope | 1.2 | Leaf | ||
| gc-m1-responses | 1.2 | Folder | ||
| gc-m1-additional | 1.2 | Folder | ||
| gc_module_1_label | 1.2 | Folder | ||
| gc_module_1_country_specific_information | 1.2 | Folder | ||
| HR | 1.4 | envelope-hr | 1.4 | Folder |
| hr_module_1_country_specific_information | 1.2.1 | Folder | ||
| hr-m1-3-1-spc-label-pl | 1.2.1 | Folder | ||
| m1-3-1-pim | 1.0 | Folder | ||
| hr-m1-additional | 1.2.1 | Folder | ||
| hr-m1-responses | 1.2.1 | Folder | ||
| m1-hr | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| eu-envelope | 1.0 | Leaf | ||
| ICH | 3.2 | study_patient_information_leaf | 1.0 | Folder |
| drug_product | 1.0 | Folder | ||
| quality_appendix | 1.1 | Folder | ||
| excipient | 1.1 | Folder | ||
| clinical_indication | 1.0 | Folder | ||
| module_studies | 1.0 | Folder | ||
| m2-3-quality-overall-summary | 1.0 | Folder | ||
| m2-3-introduction | 1.0 | Folder | ||
| node-extension | 1.0 | Folder |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| JO | 1.0 | m1-jo | 1.0 | Folder |
| jo-envelope | 1.0 | Leaf | ||
| envelope-jo | 1.0 | Folder | ||
| jo_pic_doc | 1.0 | Folder | ||
| jo-additional | 1.0 | Folder | ||
| JP | 1.0 | m1-jp | 1.1 | Folder |
| japanese_leaf | 1.0 | Leaf | ||
| PIM | 2.1 | m1-3-1-pim | 1.0 | Folder |
| eu_pim_additional_documents | 1.0 | Folder | ||
| m1-eu | 1.0 | Folder | ||
| STF | 2.2 | stf | 1.1 | Folder |
| study_data_folder | 1.0 | Folder | ||
| study_report_leaf | 1.1 | Leaf | ||
| study_patient_information_leaf | 1.0 | Leaf | ||
| STF | 2.2.3.0 | stf | 3.0 | Folder |
| study_data_folder | 3.0 | Folder | ||
| study_patient_information_folder | 3.0 | Folder | ||
| module_studies | 3.0 | Folder | ||
| study_report_leaf | 3.0 | Leaf | ||
| study_patient_information_leaf | 1.0 | Leaf | ||
| STF | 2.2.5.0 | stf | 5.0 | Folder |
| study_data_folder | 5.0 | Folder | ||
| study_patient_information_folder | 5.0 | Folder | ||
| module_studies | 5.0 | Folder | ||
| study_report_leaf | 5.0 | Leaf | ||
| study_report_folder | 5.0 | Folder |
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| TH | 0.92 | m1-th | 0.92 | Folder |
| m1-th-responses | 1.0 | Folder | ||
| m1-th-additional | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| TH | 1.0 | m1-th | 1.0 | Folder |
| m1-th-responses | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| TW | 1.0 | m1-tw | 1.0 | Folder |
| node-extension | 1.0 | Folder | ||
| UA | 1.0 | envelope-ua | 1.0 | Folder |
| m1-ua-additional | 1.0 | Folder | ||
| m1-ua-responses | 1.0 | Folder | ||
| m1-ua | 1.0 | Folder | ||
| node-extension | 1.0 | Folder | ||
| ua-envelope | 1.0 | Leaf | ||
| US | 2.01 | m1-us | 1.0 | Folder |
| node-extension | 1.0 | Folder | ||
| US | 3.3 | m1-us | 3.3 | Folder |
| m1-us-meta-data-application | 3.3 | PublisherMeta Data | ||
| m1-us-admin-form | 3.3 | Folder | ||
| m1-us-form | 3.3 | Folder | ||
| m1-15-promotional-material | 3.3 | Folder | ||
| m1-15-2-materials | 3.3 | Folder | ||
| m1-15-2-1-material | 3.3 | Folder | ||
| node-extension | 1.0 | Folder | ||
| WHO | 1.0 | m1-who | 1.0 | Folder |
| ZA | 1.0 | m1-za | 1.0 | Folder |
| node-extension | 1.0 | Folder | ||
|
Group Name |
Group Version | Extension Name | Extension Version |
Class Reference |
| ZA | 2.1 | m1-za | 2.1 | Folder |
| node-extension | 1.0 | Folder | ||
| ZA | 3.1 | m1-za | 3.1 | Folder |
| node-extension | 1.0 | Folder |
Folder Extensions
m1-au
m1-au v. 0.9
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esubmissionIdentifier | string |
eSubmission Identifier |
The Application Number as provided by the agency. Default value is Application Code. |
The value should consist of the small EN letter and 6 digits ([a-z]([0-9] {6}) |
|
| applicant | string | Applicant |
Identifies the type of activity that is being submitted with the sequence, either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. |
||
| australianApprovedNames | string |
Australian Approved Name(s) |
The name of the active ingredients that are accepted for inclusion in the Australian Approved Name list. Multiple commaseparated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| productName | string |
Product Name |
The name or proposed product (trade) name to be used on the Certificate of Registration. Multiple comma-separated values can be provided. |
||
| artgNumber | string | ARTG Number |
The Australian Register of Therapeutic Goods number should be provided if available. |
The ARTG can be a four, five, or six digit number |
|
| sequenceDescription | string | Sequence Description | Content description for the submitted sequence should be one of the values from the defined list. Codes have been implemented to help provide consistency of input and reduce validation issues based on semantics of values. The sequence description defined list of codes and values is available from <http:// apps.tga.gov.au/ downloads/sequencedescription.xml>. Multiple commaseparated values can be provided. The value used in the XML should be taken from that matching eCTD Code. |
eCTD Code value from Data Administration > Sequence Description Values |
|
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| relatedSequenceNumber | string |
Related Sequence Number |
Four-digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity. | ||
| regulatoryActivityLead | string | Regulatory Activity Lead |
Identifies the group within the TGA which is expected to take the lead in the review process. The regulatory activity lead defined list of codes and values is managed at <http:// apps.tga.gov.au/ downloads/regactivity-lead.xml>. Applicants should refer to this list for current list values. |
eCTD Code value from Data Administration > Regulatory Activity Lead Values |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceType | string | Sequence Type |
Identifies the type of activity that is being submitted with the sequence: either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. The sequence type defined list of codes and values is available from <http:// apps.tga.gov.au/ downloads/sequencetype.xml>. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| xValue1 | date | Belongs to the sequenceDescription field. | |||
| xValue2From | date | In the UI, the sequenceDescription field is a | |||
| xValue2To | date | list with values, some values have or do not have additional parameters. | |||
| xValue3 | map | If customer selects a value with no | |||
| xValue3_text | string | additional parameter, then the system | |||
| xValue3_date | date | yields the following XML (see example): | |||
| xValue4 | string | ||||
|
<extensions> <extension type="m1-au" version="0.9"> <field name="sequenceDescription" type="string" >seq-desc-0000</ field> </extension> </extensions> |
|||||
|
There are four types of additional parameters:
If a customer selects the 1st type of additional parameter, the system yields the sequenceDescription field and date (see example): |
|||||
|
<extensions> <extension type="m1-au" version="0.9"> <field name="sequenceDescription" type="string" >seq-desc-22</ field> <field name="xValue1" type="date" >1487887200000</ field> </extension> </extensions> |
|||||
| If a customer selects the 2nd type of additional parameter, the system yields the | |||||
|
©Ennov 2024 Ennov |
sequenceDescription 531 fieldEnnov InSight Adminis and date range (see example): |
tration 7.3 Extensions | |||
<extensions>
m1-au v. 3.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esubmissionIdentifier | string |
eSubmission Identifier |
The Application Number provided by the agency. Default value is Application Code. The entered values should be validated before saving. | The value should consist of the small EN letter and 6 digits ([a-z]([0-9] {6}). | |
| applicant | string | Applicant |
Identifies the type of activity that is being submitted with the sequence: either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. |
||
| australianApprovedNames | string |
Australian Approved Name(s) |
The name of the active ingredients that are accepted for inclusion in the Australian Approved Name list. Multiple commaseparated values can be provided. | ||
| productName | string |
Product Name |
The name or proposed product (trade) name to be used on the Certificate of Registration. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| artgNumber | string | ARTG Number |
The Australian Register of Therapeutic Goods number should be provided if available. |
The ARTG can be a four, five, or six digit number. |
|
| sequenceDescription | string | Sequence Description | Content description for the submitted sequence should be one of the values from the defined list. Codes have been implemented to help provide consistency of input and reduce validation issues based on semantics of values. The sequence description defined list of codes and values is available from http:// apps.tga.gov.au/ downloads/sequencedescription.xml. |
eCTD Code value from Data Administration > Sequence Description Values |
|
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequenceNumber | string |
Related Sequence Number |
Four-digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| regulatoryActivityLead | string | Regulatory Activity Lead |
Identifies the group within the TGA which is expected to take the lead in the review process. The regulatory activity lead defined list of codes and values is managed at <http:// apps.tga.gov.au/ downloads/regactivity-lead.xml>. Applicants should refer to this list for current list values. |
eCTD Code value from Data Administration > Regulatory Activity Lead Values |
|
| sequenceType | string | Sequence Type |
Identifies the type of activity that is being submitted with the sequence: either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. The sequence type defined list of codes and values is available from http:// apps.tga.gov.au/ downloads/sequencetype.xml. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| xValue1 | date | Belongs to sequenceDescription field. | |||
| xValue2From | date | In UI sequenceDescription field is a list | |||
| xValue2To | date | with values, some values have or do not have additional parameters. | |||
| xValue3 | map | If a customer selects a value with no | |||
| xValue3_text | string | additional parameter, then the system | |||
| xValue3_date | date | yields the following XML (see example): | |||
| xValue4 | string | ||||
|
<extensions> <extension type="m1-au" version="3.0"> <field name="sequenceDescription" type="string" >seq-desc-0000</ field> </extension> </extensions> |
|||||
|
There are four types of additional parameter:
If a customer selects the 1st type of additional parameter, the system yields the sequenceDescription field and date (see example): |
|||||
|
<extensions> <extension type="m1-au" version="3.0"> <field name="sequenceDescription" type="string" >seq-desc-22</ field> <field name="xValue1" type="date" >1487887200000</ field> </extension> </extensions> |
|||||
| If a customer selects the 2nd type of additional parameter, the system yields the | |||||
<extensions> m1-au v. 3.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esubmissionIdentifier | string |
eSubmission Identifier |
The Application Number as provided by the agency. Default value is Application Code. |
The value should consist of the small EN letter and 6 digits ([a-z] ([0-9]{6}) |
|
| applicant | string | eBS Client ID |
Identifies the type of activity that is being submitted with the sequence, either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. |
||
| australianApprovedNames | string | Approved Name(s) |
The name of the active ingredients that are accepted for inclusion in the Australian Approved Name list. Multiple comma-separated values can be provided. |
||
| productName | string | Trade Name(s) | The name or proposed product (trade) name to be used on the Certificate of Registration. Multiple commaseparated values can be provided. | ||
| artgNumber | string |
ARTG Number(s) |
The Australian Register of Therapeutic Goods number should be provided if available. |
The ARTG can be a four, five, or six digit number |
|
| submissionOrApplicationNumber | string |
Submission of Application Number(s) |
The submission number(s) or application number(s) applicable to the sequence being submitted. Multiple comma-separated values can be provided. |
||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequenceNumber | string |
Related Sequence Number |
Four-digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity. | ||
| regulatoryActivityLead | string | Regulatory Activity Lead |
Identifies the group within the TGA which is expected to take the lead in the review process. The regulatory activity lead defined list of codes and values is managed at <http:// apps.tga.gov.au/ downloads/regactivity-lead.xml>. Applicants should refer to this list for current list values. |
eCTD Code value from Data Administration > Regulatory Activity Lead Values |
|
| submissionMode | string |
Submission Mode |
Until the work grouping and work sharing functions are sufficiently developed for specific guidance to be published, the only valid mode is 'single' which denotes a single regulatory activity. |
One of "single", "work-sharing", "work-grouping" |
|
| sequenceType | string | Sequence Type |
Identifies the type of activity that is being submitted with the sequence: either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. The sequence type defined list of codes and values is available from <http:// apps.tga.gov.au/ downloads/ sequencetype.xml>. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| sequenceDescription | string | Sequence Description |
Content description for the submitted sequence should be one of the values from the defined list. Codes have been implemented to help provide consistency of input and reduce validation issues based on semantics of values. The sequence description defined list of codes and values is available from <http:// apps.tga.gov.au/ downloads/ sequencedescription.xml>. |
eCTD Code value from Data Administration > Sequence Description Values |
|
| xValue1 | date |
If a customer selects the 3rd type of additional parameter, the system yields the
sequenceDescription field and number/date pair (see example):
Where: 999__uniqueSuffix__0 - it is xValue3_text, "999" is number and "__uniqueSuffix__0" is predefined suffix 24-Feb-2017 - it is xValue3_date If a customer selects the 4th type of additional parameter, the system yields the
sequenceDescription field and description (see example):
|
|||
| xValue2From | date | ||||
| xValue2To | date | ||||
| xValue3 | map | ||||
| xValue3_text | string | ||||
| xValue3_date | date | ||||
| xValue4 | string | ||||
| string | Contact Email | The email is used to notify the applicant in case of change in application status. Must be valid email format. |
The value must represent a valid e-mail, the validation mask is ^([\sa-zA- Z0-9._%-]+@[azA-Z0-9.-]+\.[azA-Z]{2,4})$ |
||
m1-au v. 3.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esub-id | string | e-Identifier | The Application Number provided by the agency. Default value is Application Code. The entered values should be validated before saving. |
The value should consist of the small EN letter and 6 digits ([a-z] ([0-9]{6}) |
|
| client-id | string | eBS Client ID | Identifies the type of activity that is being submitted with the sequence: either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. | ||
| aan | string | Approved Name(s) | The name of the active ingredients that are accepted for inclusion in the Australian Approved Name list. Multiple comma-separated values can be provided. | ||
| product-name | string | Trade Name(s) | The name or proposed product (trade) name to be used on the Certificate of Registration. Multiple commaseparated values can be provided. | ||
| artg-number | string |
ARTG Number(s) |
The Australian Register of Therapeutic Goods number should be provided if available. |
The ARTG can be a four, five, or six digit number |
|
| submission-number | string | Submission or Application Number(s) |
The submission number(s) or application number(s) applicable to the sequence being submitted. Multiple comma-separated values can be provided. |
||
| sequence-number | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| related-sequence-number | string |
Related Sequence Number |
Four-digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity. | ||
| reg-activity-lead | string | Regulatory Activity Lead |
Identifies the group within the TGA which is expected to take the lead in the review process. The regulatory activity lead defined list of codes and values is managed at <http:// apps.tga.gov.au/ downloads/regactivity-lead.xml>. Applicants should refer to this list for current list values. |
eCTD Code value from Data Administration > Regulatory Activity Lead Values |
|
| submission-mode | string |
Submission Mode |
Until the work grouping and work sharing functions are sufficiently developed for specific guidance to be published, the only valid mode is 'single' which denotes a single regulatory activity. | One of “single”, “work-sharing”, “work-grouping” | |
| sequence-type | string | Sequence Type |
"Identifies the type of activity that is being submitted with the sequence, either the regulatory activity type if it is the first sequence of the regulatory activity or supplementary information if it is a follow-up to information already submitted for the regulatory activity. Content description for the submitted sequence should be one of the values from sequence-description. Refer to the sequence description for the current list of values. Please be aware that additional attributes for sequence description cannot be specified in workgrouping submission mode. The examples listed below are a subset of the overall list and show how to handle the different approaches. Multiple Sequence Type/Sequence description pairs are used if Submission Mode is set to work-grouping" |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code | |
| sequence-description | string | Content description for the submitted sequence should be one of the values from the defined list. Codes have been implemented to help provide consistency of input and reduce validation issues based on semantics of values. The sequence description defined list of codes and values is available from <http://apps.tga.gov.au/downloads/sequence-description.xml>. | eCTD Code value from Data Administration > Sequence Description Values | ||
| xValue1 | date |
Belongs to sequenceDescription field. In UI sequenceDescription field is a list with values, some values have or do not have additional parameters. If a customer selects a value with no additional parameter, then the system yields the following XML (see example): seq-desc-0000 There are four types of additional parameter:
If a customer selects the 1st type of additional parameter, the system yields the sequenceDescription field and date (see example): seq-desc-221487887200000 If a customer selects the 2nd type of additional parameter, the system yields the sequenceDescription field and date range (see example): seq-desc-20 xValue1 date Belongs to sequenceDescription field. In UI sequenceDescription field is a list with values, some values have or do not have additional parameters. If a customer selects a value with no additional parameter, then the system yields the following XML (see example):seq-desc-0000 There are four types of additional parameter:
If a customer selects the 1st type of additional parameter, the system yields the sequenceDescription field and date (see example): seq-desc-221487887200000 If a customer selects the 2nd type of additional parameter, the system yields the sequenceDescription field and date range (see example): seq-desc-2014878872000001487973600000 If a customer selects the 3rd type of additional parameter, the system yields the sequenceDescription field and number/date pair (see example): seq-desc-19 Where: 999__uniqueSuffix__0 - it is xValue3_text, "999" is number and "__uniqueSuffix__0" is predefined suffix 24-Feb-2017 - it is xValue3_date If a customer selects the 4th type of additional parameter, the system yields the sequenceDescription field and description (see example): seq-desc-0004description for sequenceDescription |
|||
| xValue2From | date | ||||
| xValue2To | date | ||||
| xValue3 | map | ||||
| xValue3_text | string | ||||
| xValue3_date | date | ||||
| xValue4 | string | ||||
| string | Contact Email | The email is used to notify the applicant in case of change in application status. Must be valid email format. |
The value must represent a valid e-mail, the validation mask is ^([\sa-zA- Z0-9._%-]+@[azA-Z0-9.-]+\.[azA-Z]{2,4})$ |
||
m1-au-nees v. 2.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esubmissionIdentifier | string |
eSubmission Identifier |
The Application Number as provided by the agency. Default value is Application Code. |
The value should consist of the small EN letter and 6 digits ([a-z] ([0-9]{6}) |
|
| applicant | string | eBS Client ID |
Identifies the type of activity that is being submitted with the sequence, either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| australianApprovedNames | string | Approved Name(s) |
The name of the active ingredients that are accepted for inclusion in the Australian Approved Name list. Multiple comma-separated values can be provided. |
||
| productName | string | Trade Name(s) |
The name or proposed product (trade) name to be used on the Certificate of Registration. Multiple commaseparated values can be provided. |
||
| artgNumber | string |
ARTG Number(s) |
The Australian Register of Therapeutic Goods number should be provided if available. |
The ARTG can be a four, five, or six digit number |
|
| submissionOrApplicationNumber | string |
Submission of Application Number(s) |
The submission number(s) or application number(s) applicable to the sequence being submitted. Multiple comma-separated values can be provided. |
||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| relatedSequenceNumber | string |
Related Sequence Number |
Four-digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity. | ||
| regulatoryActivityLead | string | Regulatory Activity Lead |
Identifies the group within the TGA which is expected to take the lead in the review process. The regulatory activity lead defined list of codes and values is managed at <http:// apps.tga.gov.au/ downloads/regactivity-lead.xml>. Applicants should refer to this list for current list values. |
eCTD Code value from Data Administration > Regulatory Activity Lead Values |
|
| submissionMode | string |
Submission Mode |
Until the work grouping and work sharing functions are sufficiently developed for specific guidance to be published, the only valid mode is 'single' which denotes a single regulatory activity. |
One of "single", "work-sharing", "work-grouping" |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceType | string | Sequence Type |
Identifies the type of activity that is being submitted with the sequence: either the regulatory activity type if it is the first sequence of the regulatory activity, or supplementary information if it is a follow-up to information already submitted for the regulatory activity. The sequence type defined list of codes and values is available from <http:// apps.tga.gov.au/ downloads/ sequencetype.xml>. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceDescription | string | Sequence Description |
Content description for the submitted sequence should be one of the values from the defined list. Codes have been implemented to help provide consistency of input and reduce validation issues based on semantics of values. The sequence description defined list of codes and values is available from <http:// apps.tga.gov.au/ downloads/ sequencedescription.xml>. |
eCTD Code value from Data Administration > Sequence Description Values |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| xValue1 | date | Belongs to the sequenceDescription | |||
| xValue2From | date | field. | |||
| xValue2To | date | In the UI, the sequenceDescription field is a list with values, some values | |||
| xValue3 | map | have or do not have additional | |||
| xValue3_text | string | parameters. | |||
| xValue3_date | date | If customer selects a value with no additional parameter, then the system | |||
| xValue4 | string | yields the following XML (see example): | |||
|
<extensions> <extension type="m1-aunees" version="2.0"> <field name="sequenceDescription" type="string" >seqdesc-0000</field> </extension> </extensions> |
|||||
|
There are four types of additional parameters:
If a customer selects the 1st type of additional parameter, the system yields the sequenceDescription field and date (see example): |
|||||
|
<extensions> <extension type="m1-aunees" version="2.0"> <field name="sequenceDescription" type="string" >seqdesc-22</field> <field name="xValue1" type="date" >1487887200000</field> </extension> </extensions> If a customer selects the 2nd type of additional parameter, the system yields the sequence |
|||||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| string | Contact Email | The email is used to notify the applicant in case of change in application status. Must be valid email format. |
The value must represent a valid e-mail, the validation mask is ^([\sa-zA- Z0-9._%-]+@[azA-Z0-9.-]+\.[azA-Z]{2,4})$ |
m1-additional
m1-additional v. 1.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-additional v. 1.2.1
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-additional v. 2.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-additional v. 3.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, edqm, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-additional v. 3.1
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
Show all EU countries, plus EMEA and Common. List of countries: at, be, bg, common, cy, cz, de, dk, edqm, ee, el, es, ema, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk, xi. |
Defaults based on application country. |
| language | string | Language | The Language that is being used for submission in the defined country. | List of languages: bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv. |
m1-ca
m1-ca v. 1.0
| Field Name | Field Type |
Matching UI Ffield |
Description | Acceptable Values | Default Value |
| applicant | string | Applicant | The name of the company that is submitted the approval. | ||
| productName | string | Product name | The Product name that is being submitted for approval. | ||
| relatedSequenceNumber | string |
Related Sequence Number |
The related sequence number for this submission. | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. Will default from the Sequence Code, but can be overridden. |
Sequence Code (without prefix "P") |
|
| submissionDate | date | Submission Date | The date the submission is to be submitted. |
Date format - Unix Timestamp. |
|
| submissionIdentifier | string |
Submission Identifier |
The Application Number as provided by the agency. |
Application Code |
|
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— CTA — CTA-A — IND — NDS — SNDS — ANDS — ABNDS — SANDS — ABSNDS — NC — DIN — ADMIN |
m1-ca v. 2.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicant | string | Applicant | The name of the company that is submitted the approval. | ||
| productName | string | Product name | The Product name that is being submitted for approval. | ||
| dossierIdentifier | string | Dossier Identifier | The Application Number as provided by the agency. | Application Code | |
| dossierType | string | Dossier Type |
The high-level type of the Application. |
— Biologic Dossier — Drug Master File Dossier — Pharmaceutical Dossier |
|
| regulatoryActivityType | string | Regulatory Activity Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
NDS, SNDS, SNDS-C, ANDS, SANDS, NC, CTA, CTA-A, DINA, DINB, PDC, PDC-B, PSUR-C, PSURPV, UD-PV, RMP-PV, Level III, YBPR, MPNDS, MPSNDS, MPNC, MPDIN, PRECTA, PRNDS, PRSNDS, PAND, DMF type I, DMF type II, DMF type III, DMF type IV, EU NDS, EU SNDS, UDRA, DSUR |
|
| regulatoryActivityLead | string | Regulatory Activity Lead | Defines the group in Health Canada that will perform the review. |
— Pharmaceutical — Biological — Post-Marketed Pharmacovigilance — Drug Master File |
|
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. | Sequence Code (without prefix "P") | |
| sequenceDescription | string | Submission Description |
The description of the Submission to be included in the XML. Note: The numeric values are not supported. |
||
| relatedSequenceNumber | string |
Related Sequence Number |
The related sequence number for this submission. |
m1-ch
m1-ch v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Available Values | Default Value |
| agencyName | string | Agency | The name of the agency that the submission is being sent to. | ||
| applicant | string | Applicant | The name of the applicant filing the submission. | ||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Multiple comma-separated values can be provided. | Application Code | |
| dmfHolder | string | DMF Holder | The Drug Master File Holder for the Product the submission is for. |
| Field Name | Field Type | Matching UI Field | Description | Available Values | Default Value |
| dmfNumber | string | DMF Number | The Drug Master File Number for the Product the submission is for. | ||
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. Multiple comma-separated values can be provided. |
||
| paragraph13LTP | string | Paragraph 13 LTP |
Identifies the submission as Paragraph 13 TPA. |
— yes — no |
|
| pmfHolder | string | PMF Holder | The Plasma Master File Holder for the Product the submission is for. | ||
| pmfNumber | string | PMF Number | The Plasma Master File Number for the Product the submission is for. | ||
| relatedSequence | string | Related Sequence | This is the Sequence number of a previous submission to which this submission relates. Multiple related sequence numbers may be entered as commaseparated values. | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. | ||
| Field Name | Field Type | Matching UI Field | Description | Available Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
na-nas, na-ngf, na-nko, na-bws, na-gen, na-ie, nande, na-ndo, notification, varauthorisationscientific, varauthorisationadmin, renewal, psur, pi, eas, comarketing, withdrawal, varpi, transfer, dmf, pmf, reformat, supplementalinfo-to, corrigendum |
m1-ch v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string | Agency | The name of the agency that the submission is being sent to. | ||
| applicant | string | Applicant | The name of the applicant filing the submission. | ||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Multiple comma-separated values can be provided | Application Code | |
| dmfHolder | string | DMF Holder | The Drug Master File Holder for the Product the submission is for. | ||
| dmfNumber | string | DMF Number | The Drug Master File Number for the Product the submission is for. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. Multiple comma-separated values can be provided. | ||
| paragraph13LTP | string | Paragraph 13 TPA |
Identifies the submission as Paragraph 13 TPA. |
— yes — no |
|
| pmfHolder | string | PMF Holder | The Plasma Master File Holder for the Product the submission is for. | ||
| pmfNumber | string | PMF Number | The Plasma Master File Number for the Product the submission is for. | ||
| relatedSequence | string | Related Sequence | This is the Sequence number of a previous submission to which this submission relates. Multiple commaseparated values can be provided. | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
na-nas, na-ngf, na-nko, na-bws, na-gen, na-ie, nande, na-ndo, notification, varauthorisationscientific, varauthorisationadmin, renewal, psur, pi, eas, comarketing, withdrawal, varpi, transfer, dmf, pmf, reformat, supplementalinfo, corrigendum |
m1-ch v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string | Agency | The name of the agency that the submission is being sent to. | ||
| applicant | string | Applicant | The name of the applicant filing the submission. | ||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Multiple comma-separated values can be provided. | Application Code | |
| dmfHolder | string | DMF Holder | The Drug Master File Holder for the Product the submission is for. | ||
| dmfNumber | string | DMF Number | The Drug Master File Number for the Product the submission is for. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided | ||
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. Multiple comma-separated values can be provided | ||
| paragraph13LTP | string | Paragraph 13 TPA |
Identifies the submission as Paragraph 13 TPA. |
— yes — no |
|
| pmfHolder | string | PMF Holder | The Plasma Master File Holder for the Product the submission is for. | ||
| pmfNumber | string | PMF Number | The Plasma Master File Number for the Product the submission is for. | ||
| relatedSequence | string | Related Sequence | This is the Sequence number of a previous submission to which this submission relates. Multiple related sequence numbers may be entered as commaseparated values. | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
eas, co-marketing, corrigendum, dmf, na-gen, na-bws, na-nas, na-nko, na-nde, na-ndo, na-ngf, na-ie, orphan-fasttrack, pi, psur, pmf, reformat, renewal, supplemental- info, transfer, varpi, varauthorisationscientific, notification, varauthorisationadmin, withdrawal |
m1-ch v. 1.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string | Agency | The name of the agency that the submission is being sent to. | ||
| applicant | string | Applicant | The name of the applicant filing the submission. | ||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Multiple commaseparated values can be provided. | Application Code | |
| dmfHolder | string | DMF Holder | The Drug Master File Holder for the Product the submission is for. | ||
| dmfNumber | string | DMF Number | The Drug Master File Number for the Product the submission is for. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided | ||
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. Multiple commaseparated values can be provided. | ||
| paragraph13LTP | string | Paragraph 13 TPA | Identifies the submission as Paragraph 13 TPA. |
— yes — no |
|
| pmfHolder | string | PMF Holder | The Plasma Master File Holder for the Product the submission is for. | ||
| pmfNumber | string | PMF Number | The Plasma Master File Number for the Product the submission is for. | ||
| relatedSequence | string | Related Sequence | This is the Sequence Number of a previous submission to which this submission relates. Multiple related sequence numbers may be entered as commaseparated values | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. | ||
| submissionType | string | Submission Type |
The Filing Type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
m1-ch v. 1.4
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string | Agency | The name of the agency that the submission is being sent to. | N/A | N/A |
| applicant | string | Applicant | The name of the applicant filing the submission. | N/A | N/A |
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Multiple commaseparated values can be provided. | Application Code |
Application Code |
| dmfHolder | string | DMF Holder |
The Drug Master File Holder for the Product the submission is for. |
N/A | N/A |
| dmfNumber | string | DMF Number |
The Drug Master File Number for the Product the submission is for. |
N/A | N/A |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided | N/A | N/A |
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. Multiple comma-separated values can be provided. |
N/A | N/A |
| paragraph13LTP | string | Paragraph 13 TPA |
Identifies the submission as Paragraph 13 TPA. |
— yes — no |
N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| pmfHolder | string | PMF Holder |
The Plasma Master File Holder for the Product the submission is for. |
N/A | N/A |
| pmfNumber | string | PMF Number |
The Plasma Master File Number for the Product the submission is for. |
N/A | N/A |
| relatedSequence | string | Related Sequence | This is the Sequence Number of a previous submission to which this submission relates. Multiple related sequence numbers may be entered as commaseparated values | N/A | N/A |
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
N/A |
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. | N/A | N/A |
| submissionType | string | Submission Type | The Filing Type of the submission. Based on the Filing Type eCTD Code of the Sequence in Ennov InSight , otherwise blank. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
N/A |
m1-ch v. 1.5
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string | Agency | Name of the agency that the submission is being sent to. | N/A | N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicant | string | Applicant | Name of the company filing the submission. | N/A | N/A |
| applicationNumber | string |
Application Number |
Application Number provided by the agency. Multiple comma-separated values can be provided. |
Application Code |
Application Code |
| dmfHolder | string | DMF Holder | Drug Master File Holder for the Product the submission is for. | N/A | N/A |
| dmfNumber | string |
DMF Number |
Drug Master File Number for the Product the submission is for (alphanumeric). | N/A | N/A |
| inn | string | INN | INN of the product being submitted for approval. Each INN is a unique name that is globally recognized and is public property. Multiple commaseparated values can be provided | N/A | N/A |
| inventedName | string |
Invented Name |
Invented name of the Product being submitted. Multiple comma-separated values can be provided. | N/A | N/A |
| paragraph13LTP | string |
Article 13 TPA |
Identifies the submission as Article 13 TPA. |
— yes — no |
N/A |
| pmfHolder | string | PMF Holder | Plasma Master File Holder for the Product the submission is for. | N/A | N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| pmfNumber | string |
PMF Number |
Plasma Master File Number for the Product the submission is for. |
N/A | N/A |
| relatedSequence | string | Related Sequence | Sequence Number of a previous submission to which this submission relates. Multiple related sequence numbers may be entered as commaseparated values | N/A | N/A |
| sequenceNumber | string | Sequence Number | Sequence Number for this submission. |
Sequence Code (without prefix "P") |
N/A |
| submissionDescription | string | Submission Description | Description of the Submission to be included in the XML. | N/A | N/A |
| submissionType | string | Submission Type | Filing Type of the submission. Based on the Filing Type eCTD Code of the Sequence in Ennov InSight , otherwise blank. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
N/A |
m1-ch-additional
m1-ch-additional v. 1.0
No additional fields for folder.
m1-ch-common-form
m1-ch-common-form v. 1.0
No additional fields for folder. m1-ch-galenic-form m1-ch-galenic-form v. 1.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| galenicFormName | string |
Galenic Form Name |
The name of the galenic form. |
||
| swissMedicNumber | string | SwissMedic Number |
The number for the galenic form from the SwissMedic agency. |
Example: "12345", or "pending" | |
| galenicNameLanguage | map |
Galenic Language Name |
The language of the galenic form. |
— de — fr — it — en Example: <field name="galenicNameLanguage" type="map"><value key="en" value="english" /></field> |
m1-ch-galenic-form v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| galenicFormName | string |
Galenic Form Name |
The name of the galenic form. | ||
| swissMedicNumber | string | SwissMedic Number | The number for the galenic form from the SwissMedic agency. |
Example: "12345", or "pending" |
|
| galenicNameLanguageSelect | string |
Galenic Language Name |
The language of the galenic form. |
— de — fr — it |
|
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| galenicNameLanguageText | string |
Galenic Language Text |
The Galenic Language Text. |
m1-ch-responses m1-ch-responses v. 1.0
No additional fields for folder.
m1-ua-responses m1-ua-responses v.1.0
No additional fields for folder.
clinical_indication clinical_indication v.1.0, v.1.1
| Field Name | Matching UI Field | Matching UI Field | Description | Acceptable Values | Default Value |
| indication | string | Indication | The indication for the product being submitted. |
m1-cn v. 1.0 m1-cn v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicationId | string |
Application Number |
The unique identification number for an application in its full lifecycle assigned by the regulatory agency. | A lowercase letter or a digit followed by nine digits. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicationType | string |
Application Type |
Describes the application purpose. |
— cnapt1 — cnapt2 — cnapt3 |
Defaults based on Application Type from the parent Application. |
| productType | string | Product Type | Describes the product classification information |
— cnprt1 — cnprt2 |
|
| productNumber | string |
Original Number |
The basic and permanent number given to a drug entering the registration approval process. The original number is assigned by the regulatory agency and is used as the unique identification code to identify the applicant, active ingredient (API) and dosage form. |
10 digits | |
| relatedSequence | string | Related Sequence |
The sequence first submitted in a regulatory activity is called the related sequence of all sequences submitted in the regulatory activity. |
One value, 0000-9999 |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| regulatoryActivityType | string |
Regulatory Activity Type |
The type of regulatory activity: i.e. the regulatory purpose the filing is addressing. |
— cnrat1 — cnrat2 — cnrat3 — cnrat4 — cnrat5 — cnrat6 — cnrat7 |
Defaults based on Filing Type from the parent Sequence, for initial Sequence Assembly. |
| sequenceNumber | string | Sequence Number | The applicant should submit the application from 0000 and the sequence number should be increased by 1 for each time of submission. The application will be submitted based on sequence. | One value, 0000-9999 | |
| sequenceTypeCn | string | Sequence Type | Describes the purpose of the sequence. |
— cnsqt1 — cnsqt2 — cnsqt3 — cnsqt4 |
|
| sequenceDescriptionCn | string | Sequence Description |
A brief description of the sequence purpose, which is used to distinguish the sequence of similar type. |
Unicode symbols for all text values must be encoded using numeric character reference, for example: 样本. |
|
| sequenceContactName | string |
Sequence Contact Name |
The name of the contact person responsible for the sequence. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceContactPhone | string |
Sequence Contact Telephone Number |
The phone number of the contact person responsible for the sequence. | ||
| sequenceContactEmail | string |
Sequence Contact |
The email address of the contact person responsible for the sequence. | Should be in the format: [email protected] |
drug_appendix drug_appendix v. 1.0, v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| manufacturer | string | Manufacturer | The manufacturer of the drug product. | ||
| substance | string | Substance | The Active Ingredient of the product being submitted. | ||
| dosageForm | string | Dosage Form | The dosage form of the product being submitted. | ||
| productName | string | Product Name | The Product Name that is being submitted. |
drug_product drug_product v. 1.0, v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| drugProductName | string |
Drug Product Name |
The Product Name that is being submitted. | ||
| dosageForm | string | Dosage Form | The dosage form of the product being submitted. | ||
| drugProductManufacturer | string | Drug Product Manufacturer | The manufacturer of the drug product. |
drug_substance drug_substance v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| dosageForm | string | Dosage Form | This field is not used for import. | ||
| drugProductManufacturer | string | Drug Product Manufacturer | This field is not used for import. | ||
| drugProductName | string |
Drug Product Name |
This field is not used for import. | ||
| drugSubstanceManufacturer | string | Drug Substance Manufacturer |
The manufacturer of the Active Ingredient. |
||
| drugSubstanceName | string |
Drug Substance Name |
The Active Ingredient Name of the Product being submitted. |
m1-eu
m1-eu v. 3.1
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines the country the envelope information is related to. Defaults based on the application country. Show all EU countries, plus EMEA and Common. |
at, be, bg, common, cy, cz, de, dk, edqm, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt,lu, lv, mt, nl, no, pl, pt, ro, se,si, sk, uk |
|
| language | string | Language | The language that is used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, is, it, lt, lv, mt,nl, no, pl, pt, ro, sk, sl, sv |
m1-eu v. 1.0
No additional fields for folder. envelope envelope v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Defaults based on the Application's Country. | ||
| applicant | string | Applicant | The name of the company submitting the Application. | ||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. | ||
| atc | string | ATC | The ATC of the Product being submitted. | ||
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application's Country. Show all EU countries, plus EMEA and common. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| inn | string | INN | The INN of the product being submitted for approval. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| procedureType | string | Procedure Type |
The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual-recognition |
|
| relatedSequence | map | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common, and EMEA. |
Example: <field name="relatedSequence" type="map"><value key="emea" value="1234" /></field> | |
| sequence | string | Sequence | The Sequence Number for this submission. | Sequence Code (without prefix "P") | |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— arbitration — cond-specific-obligation — dmf — follow-up — initial-maa — psur — renewal — safety — sepcific-obligation — supplemental-info — var-type1a — var-type1b — var-type2 |
|
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionDescription | string | Submission Description |
The description of the Submission to be included in the XML. |
envelope v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Defaults based on Application's Country. | ||
| applicant | string | Applicant | The name of the company submitting the Application. | ||
| applicationNumber | string |
Application Number |
The Application Number provided by the agency. |
||
| atc | string | ATC | The ATC of the Product being submitted. | ||
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application's Country. Show all EU countries, plus EMEA and Common. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. | ||
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| procedureType | string | Procedure Type |
The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual-recognition |
|
| relatedSequence | map | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common, and EMEA. |
Example: <field name="relatedSequence" type="map"><value key="emea" value="1234" /></field> | |
| sequence | string | Sequence | The Sequence Number for this submission. | Sequence Code (without prefix "P") | |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— arbitration — cond-specific-obligation — dmf — follow-up — initial-maa — psur — renewal — safety — sepcific-obligation — supplemental-info — var-type1a — var-type1b — var-type2 |
|
| submissionDescription | string | Submission Description |
The description of the Submission to be included in the XML. |
envelope v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Defaults based on the Application's Country. | ||
| applicant | string | Applicant | The name of the company submitting the Application. | ||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| atc | string | ATC | The ATC of the Product being submitted. | ||
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application's Country. Show all EU countries, plus EMEA and common. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| inn | string | INN | The INN of the product being submitted for approval. | ||
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| procedureType | string | Procedure Type |
The procedure type being used to submit. Based on the Application's Procedure Type |
— centralised — national — mutual-recognition |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| relatedSequence | map | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common, and EMEA |
Example: <field name="relatedSequence" type="map"><value key="emea" value="1234" /></field> | |
| sequence | string | Sequence | The Sequence Number for this submission. | Sequence Code (without prefix "P") | |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— arbitration — cond-specific-obligation — dmf — follow-up — initial-maa — psur — renewal — safety — sepcific-obligation — supplemental-info — var-type1a — var-type1b — var-type2 |
|
| submissionDescription | string | Submission Description |
The description of the Submission to be included in the XML. |
envelope v. 1.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Defaults based on the Application's Country. |
AT-AGES, BE-FAMHP, BG- BDA, BG-NVS, CY-VS, CZ- SUKL, CZ-USKVBL, DEBFARM, DE-BVL, DE-PEI, DK-DKMA, EE-SAM, ELEOF, ES-AGEMED, FINAM, FR-AFSSAPS, FR- ANMV, HU-IVMP, HUOGYI, IE-IMB, IE-DAFF, IS-IMCA, IT-AIFA, IT-LMV, IT-SPV, LI-LLV, LT-SMCA, LT-VVPI, LT-VMVT, LUMINSANT, LV-ZVA, MTMRU, MT-MEDAUTH, NLMEB, NO-NOMA, PL-URPL, PT-DGV, PT-INFARMED, RO-ANM, SE-MPA, SI- JAZMP, SK-SIDC, SKUSKVBL, UK-MHRA, UKVMD, EU-EMEA |
|
| applicant | string | Applicant |
The name of the company submitting the Application. |
||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. | ||
| atc | string | ATC | The ATC of the Product being submitted. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application's Country. Show all EU countries, plus EMEA and Common. |
at, be, bg, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| inn | string | INN | The INN of the product being submitted for approval. | ||
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| procedureType | string | Procedure Type | The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual-recognition |
|
| relatedSequence | string | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common, and EMEA. |
||
| sequence | string | Sequence | The Sequence Number for this submission. | Sequence Code (without prefix "P") |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— initial-maa — supplemental-info — fum — specific-obligation — var-type1a — var-type1b — var-type2 — extension — psur — renewal — asmf — referral — annual-reassessment — usr — article-58 — notification-61-3 — transfer-ma, — corrigendum — lifting-suspension — withdrawal — paed-article-29 — var-nat — reformat |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope v. 1.4
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Defaults based on the Application's Country. |
AT-AGES, BE-FAMHP, BG- BDA, BG-NVS, CY-VS, CZ- SUKL, CZ-USKVBL, DEBFARM, DE-BVL, DE-PEI, DK-DKMA, EE-SAM, ELEOF, ES-AGEMED, FINAM, FR-AFSSAPS, FR- ANMV, HU-IVMP, HUOGYI, IE-IMB, IE-DAFF, IS-IMCA, IT-AIFA, IT-LMV, IT-SPV, LI-LLV, LT-SMCA, LT-VVPI, LT-VMVT, LUMINSANT, LV-ZVA, MTMRU, MT-MEDAUTH, NLMEB, NO-NOMA, PL-URPL, PT-DGV, PT-INFARMED, RO-ANM, SE-MPA, SI- JAZMP, SK-SIDC, SKUSKVBL, UK-MHRA, UKVMD, EU-EMEA |
|
| applicant | string | Applicant |
The name of the company submitting the Application. |
||
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. | ||
| atc | string | ATC | The ATC of the Product being submitted. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application's Country. Show all EU countries, plus EMEA and common |
at, be, bg, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| inn | string | INN | The INN of the product being submitted for approval. | ||
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| procedureType | string | Procedure Type | The procedure type being used to submit. Based on the Application's Procedure Type |
— centralised — national — mutual-recognition |
|
| relatedSequence | string | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common, and EMEA. |
||
| sequence | string | Sequence | The Sequence Number for this submission. | Sequence Code (without prefix "P") |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— initial-maa — supplemental-info — fum — specific-obligation — var-type1a — var-type1b — var-type2 — extension — psur — renewal — asmf — pmf — referral — annual-reassessment — usr — article-58 — notification-61-3 — transfer-ma, — corrigendum — lifting-suspension — withdrawal — paed-article-29 — paed-article-46 — var-nat — reformat |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope v. 2.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Defaults based on the Application’s Country. |
AT-AGES, BE-FAMHP, BG- BDA, CY-PHS, CZ-SUKL, DE-BFARM, DE-PEI, DK- DKMA, EE-SAM, EL-EOF, ES-AEMPS, FI-FIMEA, FR- ANSM, HR-HALMED, HU- OGYI, IE-IMB, IS-IMCA, IT-AIFA, LI-LLV, LT-SMCA, LU-MINSANT, LV-ZVA, MT-MEDAUTH, NL-MEB, NO-NOMA, PL-URPL, PT- INFARMED, RO-ANMMD, SE-MPA, SI-JAZMP, SKSIDC, UK-MHRA, EU-EMA |
|
| applicant | string | Applicant |
The name of the company submitting the Application. |
||
| applicationNumber | string |
Application Number |
The Application Number provided by the agency. | ||
| atc | string | ATC | The ATC of the Product being submitted. | ||
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMEA and Common. |
at, be, bg, cy, cz, de, dk, ee, el, ema, es, fi, fr, hu, hr, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| inn | string | INN | The INN of the product being submitted for approval. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| procedureType | string | Procedure Type | The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual-recognition |
|
| relatedSequence | string | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common, and EMEA. |
||
| sequence | string | Sequence | The Sequence Number for this submission. | Sequence Code (without prefix "P") |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— initial-maa — supplemental-info — fum — specific-obligation — var-type1a — var-type1b — var-type2 — extension — psur — renewal — asmf — pmf — referral — annual-reassessment — usr — article-58 — notification-61-3 — transfer-ma, — corrigendum — lifting-suspension — withdrawal — paed-article-29 — paed-article-46 — var-nat — reformat — rmp |
|
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope v. 3.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on Application's Country. |
at, be, bg, cy, cz, de, dk, ee, edqm, el, ema, es, fi, fr, hu, hr, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| uuid | string | UUID |
A UUID as specified by ISO/IEC 11578:1996 and ITU-T Rec X.667 | ISO/IEC 9834-8:2005. The same UUID must be used for all sequences of an eCTD application. Defaults based on the UUID from the parent Application. |
The UUID must be in the form of xxxxxxxx-xxxxMxxx-Nxxxxxxxxxxxxxxx, where: — x is a hexadecimal number — M is 1-5 — N is 8, 9, a or b |
|
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| submissionMode | string |
Submission Mode |
The mode of the submission, either Single, Grouping, or Worksharing. |
— single — grouping — worksharing |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| highLevelSubmissionNumber | string |
High Level/ Worksharing Submission Number |
The high level submission number for the specific submission, used when the submission mode is Grouping or Worksharing. |
||
| applicationNumber | string |
Application Tracking Number |
The Application Number as provided by the agency. Multiple commaseparated values can be provided. | ||
| submissionUnit | string | Submission Unit Type | Submission unit type describes the content at a lower level (a “subactivity”) which is submitted in relation to a defined regulatory activity. |
— initial — validationresponse — response — additional-info — closing — consolidating — corrigendum — reformat |
|
| applicant | string | Applicant | The name of the company submitting the Application. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Based on the Application's Country. |
AT-BASG, BEFAMHP, BG-BDA, CY-PHS, CZ-SUKL, DE-BFARM, DE- PEI, DK-DKMA, EE-SAM, EL-EOF, ES-AEMPS, FIFIMEA, FR-ANSM, HR-HALMED, HU- OGYI, IE-HPRA, IS-IMCA, IT-AIFA, LI-LLV, LT-SMCA, LU-MINSANT, LV- ZVA, MT- MEDAUTH, NLMEB, NO-NOMA, PL-URPL, PTINFARMED, ROANMMD, SE-MPA, SI-JAZMP, SKSIDC, UK-MHRA, EU-EMA, EUEDQM |
|
| procedureType | string | Procedure Type | The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual- recognition — decentralised |
|
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. Multiple comma-separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| sequence | string | Sequence | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence |
This is the sequence number of previous submission(s) to which this submission relates, for example the responses to questions to a particular variation. If value of submissionUnit field is ‘initial’ and ‘reformat’ then value of relatedSequence field is identical to the value of sequence field. Multiple commaseparated values can be provided. |
||
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope v. 3.0.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMA and EDQM. |
at, be, bg, cy, cz, de, dk, ee, edqm, el, ema, es, fi, fr, hu, hr, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| uuid | string | UUID |
A UUID as specified by ISO/IEC 11578:1996 and ITU-T Rec X.667 | ISO/IEC 9834-8:2005. The same UUID must be used for all sequences of an eCTD application. Defaults based on the UUID from the parent Application. |
The UUID must be in the form of xxxxxxxx-xxxxMxxx-Nxxxxxxxxxxxxxxx, where: — x is a hexadecimal number — M is 1-5 — N is 8, 9, a or b |
|
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| submissionMode | string |
Submission Mode |
The mode of the submission, either Single, Grouping, or Worksharing. |
— single — grouping — worksharing |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| highLevelSubmissionNumber | string |
High Level/ Worksharing Submission Number |
The high level submission number for the specific submission, used when the submission mode is Grouping or Worksharing. |
||
| applicationNumber | string |
Application Tracking Number |
The Application Number as provided by the agency. Multiple commaseparated values can be provided. | ||
| submissionUnit | string | Submission Unit Type | Submission unit type describes the content at a lower level (a “subactivity”) which is submitted in relation to a defined regulatory activity. |
— initial — validationresponse — response — additional-info — closing — consolidating — corrigendum — reformat |
|
| applicant | string | Applicant | The name of the company submitting the Application. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Based on Application's Country. |
AT-BASG, BEFAMHP, BG-BDA, CY-PHS, CZ-SUKL, DE-BFARM, DE- PEI, DK-DKMA, EE-SAM, EL-EOF, ES-AEMPS, FIFIMEA, FR-ANSM, HR-HALMED, HU- OGYI, IE-HPRA, IS-IMCA, IT-AIFA, LI-LLV, LT-SMCA, LU-MINSANT, LV- ZVA, MT- MEDAUTH, NLMEB, NO-NOMA, PL-URPL, PTINFARMED, ROANMMD, SE-MPA, SI-JAZMP, SKSIDC, UK-MHRA, EU-EMA, EUEDQM |
|
| procedureType | string | Procedure Type | The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual- recognition — decentralised |
|
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. Multiple comma-separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| sequence | string | Sequence | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence |
This is the sequence number of previous submission(s) to which this submission relates, e.g. the responses to questions to a particular variation. If value of submissionUnit field is ‘initial’ and ‘reformat’ then value of relatedSequence field is identical to the value of sequence field. Multiple commaseparated values can be provided. |
||
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope v. 3.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMA and EDQM. |
Show all EU countries, plus EMA and EDQM. The list is: at, be, bg, cy, cz, de, dk, edqm, ee, el, es, ema, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk, xi. |
|
| uuid | string | UUID |
A UUID as specified by ISO/IEC 11578:1996 and ITU-T Rec X.667 | ISO/IEC 9834-8:2005. The same UUID must be used for all sequences of an eCTD application. Defaults based on the UUID from the parent Application. |
The UUID must be in the form of xxxxxxxx-xxxxMxxx-Nxxxxxxxxxxxxxxx, where: — x is a hexadecimal number — M is 1-5 — N is 8, 9, a or b |
|
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| submissionMode | string |
Submission Mode |
The mode of the submission, either Single, Grouping, or Worksharing. |
— single — grouping — worksharing |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| highLevelSubmissionNumber | string |
High Level/ Worksharing Submission Number |
The high level submission number for the specific submission, used when the submission mode is Grouping or Worksharing. |
||
| applicationNumber | string |
Application Tracking Number |
The Application Number as provided by the agency. Multiple commaseparated values can be provided. | ||
| submissionUnit | string | Submission Unit Type | Submission unit type describes the content at a lower level (a “subactivity”) which is submitted in relation to a defined regulatory activity. |
— initial — validationresponse — response — additional-info — closing — consolidating — corrigendum — reformat |
|
| applicant | string | Applicant | The name of the company submitting the Application. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. Based on Application's Country. |
AT-BASG, BEFAMHP, BG-BDA, CY-PHS, CZ-SUKL, DE-BFARM, DE- PEI, DK-DKMA, EE-SAM, EL-EOF, ES-AEMPS, FIFIMEA, FR-ANSM, HR-HALMED, HU- OGYI, IE-HPRA, IS-IMCA, IT-AIFA, LI-LLV, LT-SMCA, LU-MINSANT, LV- ZVA, MT- MEDAUTH, NLMEB, NO-NOMA, PL-URPL, PTINFARMED, ROANMMD, SE-MPA, SI-JAZMP, SKSIDC, UK-MHRA, EU-EMA, EUEDQM |
|
| procedureType | string | Procedure Type | The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual- recognition — decentralised |
|
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. Multiple comma-separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| sequence | string | Sequence | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence |
This is the sequence number of previous submission(s) to which this submission relates, e.g. the responses to questions to a particular variation. If value of submissionUnit field is ‘initial’ and ‘reformat’ then value of relatedSequence field is identical to the value of sequence field. Multiple commaseparated values can be provided. |
||
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope-eaeu envelope-eaeu v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | List of country codes associated to EAEU region. | Two letters country code, upper case. | |
| eDocId | string | EDoc Id |
Electronic Document ID. |
UUID format. | |
| eDocRefId | string |
EDoc Reference Id |
Electronic Document ID of the document the current document is referred to. |
UUID format. | |
| eDocDateTime | string | EDoc Date Time | Creation timestamp. Date of the assembly creation. | Date format - Unix Timestamp. | |
| registrationNumberId | string |
Registration Number Id |
Registration Number. | Six digits. | |
| applicationId | string | Application Id | Application Id. | ||
| registrationKindCode | string | Registration Kind Code | Defines a procedure. |
— 01 – mutual recognition: MRP. — 02 - decentralized: DCP. |
|
| submissionSequence | string | Submission Sequence | Defines a current sequence code for all the leafs in the assembly. | Four digits. |
drug_solvent drug_solvent v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| drugSolventName | string | Solvent Name | Defines a current solvent name. | N/A | N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| drugSolventManufacturer | string |
Solvent Manufacturer |
Defines a current manufacturer name. | N/A | N/A |
envelope-gc envelope-gc v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | ae, common, bh, kw, om, qa, sa, ye | |
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Default value is Application Code. Multiple commaseparated values can be provided. | ||
| applicant | string | Applicant |
The name of the applicant filing the submission |
||
| agencyName | string | Agency Name | The name of the agency that the submission is being sent to. |
BH-MOH, KWMOH, OM-MOH, QA-NHA, YEMOPHP, SA-SFDA, AE-MOH |
|
| atc | string | ATC | ATC code. Multiple comma-separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— new-gen — new-nce — new-bio — new-rad — new-her — new-hea — new-vet — renewal — var-type1 — var-type2 — transfer-ma — withdrawal — responses — psur |
|
| procedureType | string | Procedure Type | Procedure type of the submission. |
— gcc — national |
|
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. Multiple comma-separated values can be provided. | ||
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| sequence | string | Sequence | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence | This is the Sequence number of a previous submission to which this submission relates. Multiple related sequence numbers may be entered as commaseparated values. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. |
envelope-gc v. 1.5
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | ae, common, bh, kw, om, qa, sa, ye | |
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. Multiple comma-separated values can be provided. | ||
| applicant | string | Applicant | The name of the applicant filing the submission. | ||
| agencyName | string | Agency Name | The name of the agency that the submission is being sent to. |
BH-MOH, KWMOH, OM-MOH, QA-NHA, YEMOPHP, SA-SFDA, AE-MOH |
|
| atc | string | ATC | ATC code. Multiple comma-separated values can be provided. | ||
| submissionType | string | Submission Type | The Filing type of the submission. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionUnitType | string | Submission Unit Type | The submission unit element of the envelope metadata set describes the content at a lower level (a "sub-activity") which is submitted in relation to a defined regulatory activity such as the applicant response to validation issues or list of questions or any other additional information. | ||
| procedureType | string | Procedure Type | Procedure type of the submission. |
— gcc — national |
|
| inventedName | string |
Invented Name |
The invented name of the Product being submitted. | ||
| inn | string | INN | The INN of the product being submitted for approval. Multiple comma-separated values can be provided. | ||
| sequence | string | Sequence | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence | This is the Sequence number of a previous submission to which this submission relates. | ||
| submissionDescription | string | Submission Description | The description of the Submission to be included in the XML. Multiple related sequence numbers may be entered as commaseparated values. |
envelope-hr envelope-hr v. 1.4
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | hr | |
| applicationNumber | string |
Application Tracking Number |
The Application Number as provided by the agency. | ||
| applicant | string | Applicant |
The name of the company submitting the Application. |
||
| agencyName | string |
Agency Name |
The name of the agency that the submission is being sent to. |
— HR-AZLMP — HR-VET |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionType | string | Submission Type |
The Filing type of the submission. Based on the Sequence's Filing Type eCTD Code in Ennov InSight , otherwise blank. |
— initial-maa — supplemental-info — fum — specific-obligation — var-type1a — var-type1b — var-type2 — extension — psur — renewal — asmf — pmf — referral — annualreassessment — usr — article-58 — notification-61-3 — transfer-ma — corrigendum — lifting-suspension — withdrawal — paed-article-29 — paed-article-46 — var-nat — reformat |
|
| submissionMode | string |
Submission Mode |
The mode of the submission, either Single, Grouping, or Worksharing. |
— single — grouping — worksharing |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| highLevelSubmissionNumber | string |
High Level Submission Number |
The high level submission number for the specific submission, used when the submission mode is grouping or worksharing. | ||
| procedureType | string | Procedure Type |
The procedure type being used to submit. Based on the Application's Procedure Type. |
— centralised — national — mutual- recognition — decentralised |
national |
| inventedName | string |
Invented Name |
The invented name of the product being submitted for approval. | ||
| inn | string | INN | The INN of the product being submitted for approval. | ||
| sequence | string | Sequence | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence |
The related sequence number as well as the country for the specific relation. Country values include all of Europe, Common and EMEA |
||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionDescription | string | Submission Description |
The description of the Submission to be included in the XML. |
eu-envelope eu-envelope v. 1.0
No additional fields for folder.
eu_module_1_country_specific_information eu_module_1_country_specific_information v. 1.0
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMEA and Common. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu_module_1_country_specific_information v. 1.2.1
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMEA and Common. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu_module_1_country_specific_information v. 2.0
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMEA and Common. | at, be, bg, common, cy, cz, de, dk, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu_module_1_country_specific_information v. 3.0
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. Defaults based on the Application’s Country. Show all EU countries, plus EMEA and Common. |
at, be, bg, common, cy, cz, de, dk, edqm, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu_module_1_country_specific_information v. 3.1
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
Show all EU countries, plus EMEA and Common. List of countries: at, be, bg, common, cy, cz, de, dk, edqm, ee, el, es, ema, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk, xi. |
|
| language | string | Language | The language used for submission in the defined country. | List of languages: bg, cs, da, de, el, en, es, et,fi, fr, ga, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv. |
eu_xml_application_form eu_xml_application_form v. 1.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu_xml_application_form v. 2.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu_module_1_labeling_information eu_module_1_labeling_information v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
eu_module_1_labeling_information v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
eu_module_1_labeling_information v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values |
| country | string | Country | Defines which country the envelope information is related to. |
Show all EU countries, plus EMEA and Common. List of countries: at,be,bg,common,cy,cz,de,dk,edqm,ee,el,es,ema,fi,fr,hr,hu,ie,is,it,li,l |
| language | string | Language |
The language used for submission in the defined country. |
List of languages: bg,cs,da,de,el,en,es,et,fi,fr,ga,hr,hu,is,it,lt,lv,mt,nl, |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
eu_module_1_labeling_information v.3.1
excipient excipient v. 1.0, v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| excipient | string | Excipient | The excipient of the product being submitted. |
envelope-jo envelope-jo v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicationNumber | string |
Application Reference Number |
Application Number as provided by the agency. Multiple commaseparated values can be provided. | ||
| applicant | string | Applicant | Name of the applicant filing the submission. | ||
| mah | string | MAH | Name of Marketing Authorization Holder. | ||
| agencyName | string | Agency | Name of the agency that the submission is being sent to. | JO-JFDA | |
| atc | string | ATC | ATC code. Multiple comma-separated values can be provided. | ||
| submissionType | string | Submission Type | Filing type of the submission. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| submissionUnitType | string | Submission Unit | Submission unit element of the envelope metadata set describes the content at a lower level (a "subactivity") which is submitted in relation to a defined regulatory activity such as the applicant response to validation issues or list of questions or any other additional information. | initial, response, additional-info, closing, correction, reformat | |
| procedureType | string | Procedure | Procedure type of the submission. |
— jo — national |
|
| inventedName | string |
Invented Name |
Invented name of the Product being submitted. |
||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN | INN of the product being submitted for approval. Multiple commaseparated values can be provided. | ||
| sequence | string | Sequence | Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string | Related Sequence | Sequence number of a previous submission to which this submission relates. | ||
| submissionDescription | string | Submission Description |
Description of the Submission to be included in the XML. Multiple related sequence numbers may be entered as comma-separated values. |
||
| number | string | Number | Reference number of the product allocated by the regulatory authority. If the number is not yet allocated at the time point of submission, 'to be advised' should be added instead and replaced by the number in follow-up submissions when registered. |
eu_pim_additional_documents eu_pim_additional_documents v. 1.0
No additional fields for folder.
m1-gc
m1-gc v. 1.2
No additional fields for folder. gc_module_1_country_specific_information gc_module_1_country_specific_information v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
— ae — common — bh — kw — om — qa — sa — ye |
|
| language | string | Language | The Language that is being used for submission in the defined country. |
— ar — en |
gc-m1-responses gc-m1-responses v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
— ae — common — bh — kw — om — qa — sa — ye |
gc_module_1_label gc_module_1_label v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. Defaults based on the Application's Country. Shows all GCC countries. |
— ae — common — bh — kw — om — qa — sa — ye |
|
| language | string | Language | The Language that is being used for submission in the defined country. |
— ar — en |
|
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — label — pil |
gc-m1-additional gc-m1-additional v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
— ae — common — bh — kw — om — qa — sa — ye |
gc-envelope gc-envelope v. 1.2
No additional fields for folder.
envelope-ua
Envelope-ua v.1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | ua | ua |
| procedureType | string | Procedure Type | The type of procedure for the submission. | national | national |
| relatedSequence | string | Related Sequence |
This is the sequence number of previous submission to which this submission relates. Example, the responses to questions to a particular variation. |
||
| submissionUnit | string | Submission Unit Type |
Submission unit type describes the content at a lower level (a "sub activity") which is submitted in relation to a defined regulatory activity. |
Can be one of the following values: — initial — validationresponse — response — additionalinfo — consolidatin g — reformat |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN |
International Non- proprietary Name, used to identify pharmaceutical substances or active pharmaceutical ingredients. A non-proprietary name is also known as a generic name. |
||
| submissionNumb ers | string | Submission Number | This number is used by regulatory authority to track the submission, in any procedure, in relation to a particular medicinal product. This is the number of the registration form or package of registration forms. | ||
| inventedName | string | Invented Name | The name of the medicinal product. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| uuid | string | UUID |
A UUID as specified by ISO/IEC 11578:1996 and ITU-T Rec X.667 | ISO/IEC 9834-8:2005. The same UUID must be used for all sequences of an eCTD application. Defaults based on the UUID from the parent Application. |
The UUID must be in the form ofxxxxxxxxxxxx-MxxxNxxxxxxxxxxxxxxx, where x is a hexadecimal number, M is 1-5, and N is 8, 9, a or b. | |
| agencyName | string | Agency Name | Regulatory authority which is The State Expert Center of MOH of Ukraine. | UA-SECMOH | |
| applicant | string | Applicant | The name of the company submitting the Application. | ||
| submissionType | string | Submission Type | The type of regulatory activity to which the content will be submitted. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequence | string | Sequence | This is the sequence number of the submission this should start at 0000 for the initial submission, and then increase incrementally with each subsequent submission related to the same medicinal product. |
Sequence Code (without prefix "P") |
|
| submissionDescri ption | string | Submission Description | This element is used to provide a short text description of the submission. | ||
| submissionMode | string |
Submission Mode |
The high-level handling of the information submitted as part of variation(s) and extension applications. The mode should only be used in variation or line extension regulatory activities and must be included in every sequence of that activity. |
Can be one of two values: — single — grouping |
m1-hr
m1-hr v. 1.0
No additional fields for folder.
hr-m1-additional hr-m1-additional v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country |
Defines which country the envelope information is related to. Defaults based on the Application's Country. |
hr | |
| language | string | Language | The language used for submission in the defined country. |
— de — en — hr |
hr-m1-3-1-spc-label-pl hr-m1-3-1-spc-label-pl v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | hr | |
| language | string | Language | The language used for submission in the defined country. |
— de — en — hr |
|
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
hr_module_1_country_specific_information hr_module_1_country_specific_information v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | hr | |
| language | string | Language | The language used for submission in the defined country. |
— de — en — hr |
hr-m1-responses hr-m1-responses v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | hr | |
| language | string | Language | The lLanguage used for submission in the defined country. |
— de — en — hr |
m1-jp m1-jp v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionNumber | string | Submission Number | The Application Number as provided by the agency. |
Application Code |
|
| brandName | string | Brand Name | The brand name of the product being submitted to the agency. | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| genericName | string | Generic Name | The generic name of the product being submitted to the agency. | ||
| applicant | string | Applicant | The company filing the application. | ||
| submissionDate | date | Submission Date | The date the submission is to be submitted. |
Date format - Unix Timestamp. |
|
| submissionType | string | Submission Type | The Filing type of the submission. | ||
| jpOperation | string | Operation | The operation of the element pointing to JP regional XML. |
— new — append — replace — delete |
new |
m1-jo m1-jo v. 1.0
No additional fields for folder.
jo_pi_doc jo_pi_doc v.1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| language | string | Language | The language used for submission in the defined country. |
— ar — en |
|
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — label — pil — spccomp — pilcomp |
jo-additional jo-additional v. 1.0 No additional fields for folder.
m1-th m1-th v. 0.92
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esubId | string |
eSubmission Identifier |
The Application Number as provided by the agency. Default value is Application Code. The entered values should be validated before saving. |
||
| sequenceType | string | Sequence Type | Identifies the type of activity that is being submitted with the sequence. If it is the first sequence then submit the regulatory activity type. If it is the second, third, etc. sequences then submit supplementary information. The value used in the XML should be taken from that matching eCTD Code. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| regActivityLead | string | Regulatory Activity Lead | Identifies the group within the THAI FDA, which is expected to take the lead in the review process. |
— Biologicals — Pharmaceuticals — Pharmacovigilance |
|
| licensee | string | Licensee | The licensee name that is legally responsible for the application in Thailand. The official registered name of the company should be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string |
INN/Generic Name |
The INN or Generic Name of the active ingredients used in the product. Multiple commaseparated values can be provided. | ||
| productName | string |
Product Name |
The name or proposed product (trade) name(s) to be used on the Certificate of Registration. If duplicate products are being submitted within one application, all products should be listed. Multiple commaseparated values can be provided. | ||
| sequence | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string |
Related Sequence Number |
Four digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity (without prefix "P"). |
||
| seqDescription | string | Sequence Description | Free text description of the submission. The description provided here should also be used in the node title for 1.0 Cover Letter and 1.R Response to Questions. |
m1-th v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| esubId | string |
eSubmission Identifier |
The Application Number as provided by the agency. | Application Code. The value should consist of the small EN letter and 7 digits ([a-z]([0-9]{7})) | |
| sequenceType | string | Sequence Type | Identifies the type of activity that is being submitted with the sequence. If it is the first sequence then submit the regulatory activity type. If it is the second, third, etc. sequences then submit supplementary information. The value used in the XML should be taken from that matching eCTD Code. |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| regActivityLead | string | Regulatory Activity Lead | Identifies the group within the THAI FDA, which is expected to take the lead in the review process. |
— Biologicals — Pharmaceuticals — Pharmacovigilance — Cosmetic — Medical-Devices |
|
| licenseeNumber | string |
Licensee Number |
The licensee number of the company that is legally responsible for the application in Thailand. | ||
| licenseeType | string | Licensee Type | The licensee type of Licensee Number for the application in Thailand. The licensee type of the company should be provided. |
— Importer — Manufacturer |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| licensee | string |
Licensee Name |
The licensee name that is legally responsible for the application in Thailand. The licensee name of the company should be provided in all capital letters. |
||
| inn | string |
INN/Generic Name |
The INN or Generic Name of the active ingredients used in the product. Multiple commaseparated values can be provided. | ||
| productName | string |
Product Name |
The name or proposed product (trade) name(s) to be used on the Certificate of Registration. If duplicate products are being submitted within one application, all products should be listed. Multiple comma-separated values can be provided. |
||
| sequence | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequence | string |
Related Sequence Number |
Four digit sequence number used for supplementary information indicating the initial sequence number of the regulatory activity. |
||
| seqDescription | string | Sequence Description | Free text description of the submission. The description provided here should also be used in the node title for 1.0 Cover Letter and 1.R Response to Questions. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| string | Contact Email | The email is used to notify the applicant in case of change in application status. Must be valid email format. | Example: [email protected] |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| identifier | string | Identifier |
A UUID as specified by ISO/IEC 11578:1996 and ITU-T Rec X.667 | ISO/IEC 9834-8:2005. The same UUID must be used for all sequences of an eCTD application. |
The entered values should pass the validation to match the format: a hexadecimal number in the form of xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx, having 32 digits and 4 hyphens. | Defaults based on the UUID from the parent applicati |
| submissionTypeTier1 | string | Submission Type Tier 1 | Domestic, Import, Export Only. | ||
| submissionTypeTier2 | string | Submission Type Tier 2 | New Drugs Application, Biological Drugs Application, Generic Drug Application, Active Pharmaceutical Ingredient. | ||
| submissionTypeTier3 | string | Submission Type Tier 3 |
Prescription, Over The Counter, Controlled Drugs, Nuclear Medicine, Biological Drugs, Biosimilar Drugs, Regenerative Medicine, Others. |
m1-tw
m1-tw v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionTypeTier4 | string | Submission Type Tier 4 |
New Chemical Entity, New Indication, New Combination, New Dosage Form, New Administration, New Dosage, New Strength, Genetic Engineering, Vaccine, Plasma Derivative, Cell Therapy, Gene Therapy, Tissue Engineering, Allergen, Safety Monitoring, Non-Safety Monitoring, Others. |
||
| submissionTypeTier5 | string | Submission Type Tier 5 |
New Chemical Entity, New Indication, New Combination, New Dosage Form, New Administration, New Dosage, New Strength, Comply With OTC Criteria, Not Comply With OTC Criteria, Others. |
||
| submissionObjective | string | Submission Objective |
Explains the main purpose of this submission. The high-level handling of the information submitted as part of variation(s) and extension applications. |
Change, Expiration, Extension, New. | |
| submissionUnitType | string | Submission Unit |
Submission unit type describes the content at a lower level (a “sub-activity”) which is submitted in relation to a defined regulatory activity. |
Initial, Validation Response, Response, Additional Info, Corrigendum, Reformat. | |
| applicantName | string |
Applicant Name |
The name of the company submitting the eCTD. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicantCertAuth | string |
Application Corporate Certification Authority |
Applicants should use Corporate Certification Authority IC Card for submission. |
||
| applicantPhoneNum | string |
Applicant Phone Number |
Phone number of the company. |
Multiple comma-separated values can be provided. | |
| applicantEmailAddr | string |
Applicant Address |
If entered value does not met [email protected] criterion Invalid e-mail address message appears. Multiple comma-separated values can be provided. |
||
| procedure | string | Procedure |
Defines the procedure in use with the submission National is the default and the only option to be chosen. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inventedName | map |
Invented Names (Name/ Drug Permit License/ PreAssigned Application Number/ Code) |
The group of fields that allows multiple sets of Invented Name. |
Example: field name="inventedName" type="map"><value key="2uniqueSuffix__1" value="22,3333" /><value key="2__uniqueSuffix__1" value="222" /><value key="2__uniqueSuffix__1" value="2222" /><value key="Invented NamesNameValue__uniqueSuffix__0" value="Drug Permit License" / ><value key="Invented NamesNameValue__uniqueSuffix__0" value="Pre-Assigned Application Number " /><value key="Invented NamesNameValue__uniqueSuffix0" value="Code" /> |
|
| inn | string | INN |
International Non- proprietary Name, used to identify pharmaceutical substances or active pharmaceutical ingredients. Each INN is a unique name that is globally recognized and is public property. A nonproprietary. |
Multiple comma-separated values can be provided |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequence | string | Sequence |
This is the sequence number of the submission – this should start at 0000 for the initial submission, and then increase incrementally with each subsequent submission related to the same product For example, 0000, 0001, 0002, 0003, etc. |
Only digits, if not, the error appears. |
m1-th-responses m1-th-responses v.1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| relatedSequence | string | Related Sequence | This is the sequence number of previous submission(s) to which this submission relates. For example, the responses to questions to a particular variation. In the case of submission unit types ‘initial’ and ‘reformat’, related sequence is identical to the sequence number. | Multiple comma-separated values can be provided. 'Related Sequence must be numeric' error message appears if the value is not numeric. | |
| submissionDescription | string | Submission Description | This element is used to provide a free text description of the submission. |
No additional fields for folder.
m1-th-additional m1-th-additional v.1.0
No additional fields for folder.
m1-ua-additional
m1-ua-additional v.1.0
No additional fields for folder.
m1-ua
m1-ua
No additional fields for folder.
m1-us
m1-us v.1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| companyName | string | Company Name | The name of the company sending the submission. | ||
| submissionDate | date | Submission Date | The date the submission is to be submitted. |
Date format - Unix Timestamp |
|
| applicationNumber | string |
Application Number |
The Application Number provided by the agency. | ||
| productName | string |
Product Name |
The name or proposed product (trade) name(s) to be used in the Certificate of Registration. If duplicate products are being submitted within one application, all products should be listed. Multiple comma-separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicationType | string |
Application Type |
The Application Type for this Application. Based on a mapping of the eCTD code to the Application Type selected on the related Application. |
— nda — anda — bla — dmf — ind — master-file |
|
| submissionType | string | Submission Type | The Filing type of the submission. Will default from the Sequence's Filing Type. |
— amendment — annual-report — chemistrymanufacturingcontrolssupplement — efficacysupplement — establishmentdescriptionsupplement — labelingsupplement — originalapplication — other — presubmission — resubmission |
|
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| relatedSequenceNumber | string |
Related Sequence Number |
The related sequence number for this submission. |
m1-us v. 3.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicantContact | string | Applicant Contact | The Applicant Contact for this submission. |
Applicant Contact Name value from Data Administration > Applicant Contact Values |
|
| applicantId | string | Applicant ID |
The Applicant's ID. Values from Data Administration. Default displays the Application Level value, if defined. |
Applicant ID value from Data Administration > Applicant ID Values |
|
| applicationNumber | string |
Application Number |
The Application Number as provided by the agency. | ||
| applicationType | string |
Application Type |
The Application Type for this Application. Based on a mapping of the eCTD code to the Application Type selected on the related Application. |
eCTD Code value from Data Administration > Applicant Contact Values > Application Type eCTD Code |
|
| companyName | string | Company Name |
Applicant Name from Data Admin, or editable field if no default Applicant ID. Refreshes based on Applicant ID Selected. |
||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
|
| submissionDescription | string | Submission Description | The description of the Submission. | ||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionSubType | string | Submission Sub-Type | The Filing/Submission Sub Type for this Submission. Dependent on the value selected for Submission Type (eCTD code). |
eCTD Code value from Data Administration > Sub Filing Type Values > Sub Filing Type eCTD Code |
|
| submissionType | string | Submission Type |
The Filing/Submission Type for this Submission. Values from Data Administration - All active US Regulatory Region values in the Filing Type table. Dependent on Application Type selected (eCTD code). |
eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code |
|
| supplementEffectiveDate | string |
Supplement Effective Date Type |
Supplement Effective Date Type for this Submission. Dependent on the Submission Type selected (eCTD code). |
eCTD Code value from Data Administration > Supplement Effective Date Type Values > Supplement Effective Date Type eCTD Code |
m1-us-form m1-us-form v. 3.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| formType | string | Application Form Type | Defines the form type of the form included into the submission (eCTD code). |
Regulatory Code value from Data Administration > Application Form Type Values |
m1-us-admin-form m1-us-admin-form v. 3.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| adminFormType | string | Application Form Type | Defines the form type of the form included into the submission (eCTD code). |
Regulatory Code value from Data Administration > Application Form Type Values |
|
| applicationNumber | string |
Application Number |
Defines the application number of the application that the form refers to. All Application Number values defined in the metadata library for the US 3.3 admin section. |
m1-who
m1-who v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| identifierWho | string | Identifier |
The Universally Unique identifier (UUID) used for all sequences of an eCTD application. |
UUID format | |
| productTypeWho | string | Product Type | Product code for product type. | ||
| productSubType | string | Product Subtype |
Description of the product type. Mandatory for FPP only. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| productId | string | Product Name |
The name or proposed product (trade) name used on the Certificate of Registration. FPPs equates to the SF field Generic Name. FVPs equates to the SF field WHO vaccine name (full). APIMFs and APIPQs equates to the SF field Active Pharmaceutical Ingredient. |
||
| applicationTypeW ho | string |
Application Type |
Provides administrative information associated with the submission. The type of regulatory activity to which the content is submitted. |
||
| applicationSubTy pe | string | Application Subtype | Provides further information about the submission. Mandatory for FPP. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionUnitTy peWho | string | Submission Unit Type |
Submission unit type describes the content at a lower level (a "sub-activity") which is submitted in relation to a defined regulatory activity. |
||
| applicantWho | string | Applicant | The name of the company submitting the eCTD. | ||
| contactEmail | string | Contact E-mail | Email Address of the Contact from Applicant. | ||
| productId | string | Product ID |
Unique product record identifier, following the format WHO Product ID: Issued by Salesforce. |
||
| sfCaseId | string | SF Case ID |
A Salesforce generated number, unique to the application submitted. It follows a simple 8 digit number format. |
||
| sequenceWho | string | Sequence | The Sequence Number for this submission. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
|
relatedSequence Who |
string | Related Sequence | This is the sequence number of previous submission(s) to which this submission relates. For example, the responses to questions to a particular variation. In the case of submission unit types 'initial' and 'reformat' related sequence is identical to the sequence number. | ||
| submissionDescri ptionWho | string | Submission Description |
The description of the Submission to be included in the XML. |
m1-za
m1-za v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicationNumber | string |
Application Number |
This is the number issued for the product by the MCC and remains for the full lifecycle of the product from the first data submission. Multiple comma- separated values can be provided. |
||
| applicant | string | Applicant | The name of the applicant/HC R submitting the eCTD. | ||
| submissionType | string | Submission Type |
The type of regulatory submission that this data submission relates to. |
na-nce-ph, na-nce-b, na-ms, na-bs, na-le, na-cu, na-cams, pre-reg-pa, pre-reg-cl, pre-reg-pn, pre-reg-sch, pre-reg-insp, pre-reg-pa-insp, prereg-biol, pre-reg-cams, pre-reg-cr, post-reg-insp, post-reg-pa, post-regpa-insp, post-reg-cl, post-reg-pn, post-reg-pn-update, post-reg-hcr, post-reg-biol, post-reg-cams, withdrawal, cancellation |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| proofEfficacy | map |
Proof of Efficacy |
The data type submitted as proof of efficacy and a description of the data type if "other" is selected as data type. |
— non-cl — cl — be — other — na Example: <field name="proofEfficacy" type="map"><value key="other__uniqueSuffix__0" value="123456" /></field> |
|
| proprietaryName | string |
Proprietary Name |
The name of the medicinal product. Include even if not yet approved. Multiple comma- separated values can be provided. |
||
| dosageForms | string | Dosage Form |
The dosage form of the medicinal product. Multiple comma- separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN |
The INN of the API(s) accompanied by its salt or hydrate form (if relevant) or chemical description of the API(s). Multiple comma- separated values can be provided. |
||
| sequence | string | eCTD Sequence |
The Sequence Number for this submission. |
Sequence Code (without prefix "P") | |
| relatedSequences | string | Related Sequence |
This is the sequence number of a previous submission to which this submission relates. Multiple comma- separated values can be provided. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| duplicateApplications | map |
Duplicated Applications (Proprietary Names / Application Numbers |
The name of the multiple / duplicate applications of the medicinal product (include even if the name is not yet approved) plus the date of application of the duplicate applications. Multiple paired values can be provided. |
Example: <field name="duplicateApplications" type="map"><value key="value1__uniqueSuffix__0" value="1" /></field> | |
| supportProofDD | string | This field is not used for import. | |||
| supportProofText | string | This field is not used for import. | |||
| supportTestDD_text | string | This field is not used for import. | |||
| supportTestDD_text2 | string | This field is not used for import. |
m1-za v.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| applicationNumber | string |
Application Number |
This is the number issued for the product by the MCC and remains for the full lifecycle of the product from the first data submission. Multiple comma- separated values can be provided. |
||
| applicant | string | Applicant | The name of the applicant/HC R submitting the eCTD. | ||
| submissionType | string | Submission Type / Proof of Efficacy | This field is not used for import. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| proofEfficacy | map | Submission Type / Proof of Efficacy | The data type submitted as proof of efficacy and a description of the data type if "other" is selected as data type. |
— non-cl — cl — be — other — na Example: <field name="proofEfficacy" type="map"> <value key="postreg-hcr__uniqueSuffix__1" value="other" /> <value key="post-reghcr__uniqueSuffix__1" value="comments text" /> <value key="post-reghcr__uniqueSuffix__0" value="other" /> <value key="post-reghcr__uniqueSuffix__0" value="comments text" /></ field> Where: — post-reg-hcr is an eCTD Code value from Data Administration > Filing Type Values > Filing Type eCTD Code — other is a Proof of Efficacy value. — comments text is a free text value, can be empty. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| proprietaryName | string |
Proprietary Name |
The name of the medicinal product. Include even if not yet approved. Multiple comma- separated values can be provided. |
||
| dosageForms | string | Dosage Form |
The dosage form of the medicinal product. Multiple comma- separated values can be provided. |
||
| inn | string | INN |
The INN of the API(s) accompanied by its salt or hydrate form (if relevant) or chemical description of the API(s). Multiple comma- separated values can be provided. |
||
| sequence | string | eCTD Sequence |
The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| relatedSequences | string | Related Sequence |
This is the sequence number of a previous submission to which this submission relates. Multiple comma- separated values can be provided. |
||
| duplicateApplications | map |
Duplicated Applications (Proprietary Names / Application Numbers |
The name of the multiple / duplicate applications of the medicinal product (include even if the name is not yet approved) plus the date of application of the duplicate applications. Multiple paired values can be provided. |
Example: <field name="duplicateApplications" type="map"><value key="value1__uniqueSuffix__0" value="1" /></field> | |
| supportProofDD | string | This field is not used for import. | |||
| supportProofText | string | This field is not used for import. | |||
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| supportTestDD_text | string | This field is not used for import. | |||
| supportTestDD_text3 | string | This field is not used for import. |
m1-za v.3.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceNum ber | string | Sequence Number | Four-digit number matching the Sequence folder being submitted | N/A | N/A |
| applicationTyp e | string | Application Type | Defines an application type. |
— app- type-1 — app- type-2 — app- type-3 — app- type-4 — app- type-5 — app- type-6 — app- type-7 |
N/A |
| smfNumber | string | SMF Number |
The Site Master File (SMF) Number for all manufacturers referenced in the eCTD application should be added as issued. Multiple comma-separated values can be provided. |
N/A | N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| sequenceDescr iptionZa | string | Sequence Description | The Sequence Description attribute gives the Applicant an opportunity to better describe what is being done in the Sequence. | N/A | N/A |
| applicationNu mber | string |
Application Number |
A unique number automatically issued by SAHPRA for each product, strength, replica/ clone/duplicate once an application is created or a new replica/clone is added to the existing application on SAHPRA application portal. Multiple commaseparated values can be provided. | N/A | N/A |
| dosageForm | string | Dosage Form | The dosage form of the medicinal product. Multiple comma-separated values can be provided. | N/A | N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| inn | string | INN |
The recognised International Nonproprietary Name should be given for the active ingredients and pharmaceutical drug if available. It should be written in all lower-case letters and provided exactly as officially listed in international lists like WHO INN, British Approved Names (BAN), United States Pharmacopoeia (USP) and so on without abbreviations. Multiple commaseparated values can be provided. |
N/A | N/A |
| apimfNumber | string | APIMF Number |
A number for certified Active Pharmaceutical Ingredient Master File (APIMF). Populated, if APIMF is referenced in the eCTD application. Multiple commaseparated values can be provided. |
N/A | N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| vamfNumber | string | VAMF Number | A number for certified Vaccine Master File (VAMF). Populated, if VAMF is referenced in the eCTD application. Multiple commaseparated values can be provided. | N/A | N/A |
| applicationIde ntifier | string | Application ID |
A unique 14character identifier number automatically issued by SAHPRA for an application once it is created on SAHPRA application portal. Application ID is used for all sequences of an eCTD application and cannot be changed |
N/A |
Current Application Code |
| sequenceDate | string | Sequence Date |
The date when the sequence was submitted. The date should correlate but should not necessarily be identical to the date shown in the Letter of Application and the Application Form. Sequence Date is mainly used to ensure the validity of the codes taken from the Defined Lists. |
171745920 0000 |
N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
|
proprietaryNa me |
string | Proprietary Name | The name as proposed or registered. For API Master Files, insert drug substance name and APIMF holder name. Multiple commaseparated values can be provided. | N/A | N/A |
| submissionInfo Combination | map |
Submission (Submission Type / Evaluation Pathway / Submission Lead / Submission Number) |
Contains all the submission-related information for the regulatory activity that is not related to a specific sequence. Multiple Submission sets can be provided if the combination is allowed in the Submission Type Matrix. |
<field name="sub missionInfo Combination " type="map" > <value key="subtype-31__u niqueSuffix_ _0" value="evalpath-1"/> <value key="subtype-31__u niqueSuffix_ _0" value="sublead-2"/> <value key="subtype-31__u niqueSuffix_ _0" value="num 1,num1b"/> </field> |
N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| pmfNumber | string | PMF Number |
A number for the certified Active Plasma Master File (PMF). Populates, if PMF is referenced in the eCTD application. Multiple commaseparated values can be provided. |
N/A | N/A |
| multipleApplic ations | map |
Multiple Applications (Application Number / Proprietary Name) |
The data type submitted as proof of efficacy and a description of the data type if other is selected as data type. Multiple paired values can be provided. The value is not required to populate but it is required to have both Application Number and Proprietary Name either populated or empty. If only one field is populated, a validation message is displayed. |
<field name="mult ipleApplicati ons" type="map" > <value key="appnu m01__uniqu eSuffix__0" value="prop name01"/> </field> |
N/A |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| submissionSub Type | string | Sequence Type |
The Sequence Element section contains all the Sequence-related information. It identifies what is happening to the Submission with the Sequence being submitted. Only one Sequence Element section can be specified per Sequence, however multiple types of Responses can be specified as types. Responses can only be combined with other responses. Multiple values can be provided |
N/A | N/A |
| submissionCon tact | string | Contact | Multiple contacts may be provided in the Envelope. The Contact Name and Contact Email must be provided for each contact, along with the Type of Contact. At least one Local Applicant contact must be provided. | N/A | N/A |
m1-15-2-materials m1-15-2-materials v. 3.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| promotionalMaterialDocType | string |
Promotional Material Doc Type |
Defines the promotional material document type of US region. |
Regulatory Code value from Data Administration > Promotional Material Doc Type Values |
m1-15-promotional-material m1-15-promotional-material v. 3.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| promotionalMaterialAudienceType | string |
Promotional Material Audience Type |
Defines the promotional material audience type of US region. |
Regulatory Code value from Data Administration > Promotional Material Audience Type Values |
m1-15-2-1-material m1-15-2-1-material v. 3.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| issueDate | date | Issue Date | The date of the initial dissemination of the promotional labeling or the date of initial publication for an advertisement. | Date format - Unix Timestamp. | |
| promotionalMaterialId | string | Promotional Material ID | The applicant identification code or other designation of the specific promotional material. | ||
| promotionalMaterialType | string | Promotional Material Type | Defines the promotional material document type of US region. |
Regulatory Code value from Data Administration > Promotional Material Type Values |
m1-responses m1-responses v. 1.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-responses v. 1.2.1
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-responses v. 2.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
m1-responses v. 3.0
|
Field Name |
Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, edqm, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv |
eu-m1-responses v. 3.1
|
Field Name |
Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
Show all EU countries, plus EMEA and Common. List of countries: at, be, bg, common, cy, cz, de, dk, edqm, ee, el, es, ema, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk, xi. |
Defaults based on application country. |
| language | string | Language | The Language that is being used for submission in the defined country. | List of languages: bg, cs, da, de, el, en, es, et, fi, fr, ga, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv. |
m1-3-1-spc-label-pl m1-3-1spc-label-pl v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
m1-3-1spc-label-pl v. 1.2.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, emea, es, fi, fr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
m1-3-1spc-label-pl v. 2.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | at, be, bg, common, cy, cz, de, dk, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk | |
| language | string | Language | The Language that is being used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
m1-3-1spc-label-pl v. 3.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. |
at, be, bg, common, cy, cz, de, dk, edqm, ee, el, ema, es, fi, fr, hr, hu, ie, is, it, li, lt, lu, lv, mt, nl, no, pl, pt, ro, se, si, sk, uk |
|
| language | string | Language | The language used for submission in the defined country. | bg, cs, da, de, el, en, es, et, fi, fr, hr, hu, is, it, lt, lv, mt, nl, no, pl, pt, ro, sk, sl, sv | |
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
— spc — annex2 — outer — interpack — impack — other — pl — combined |
m1-3-1spc-label-pl v. 3.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| country | string | Country | Defines which country the envelope information is related to. | All EU countries. | Defaults based on application country. |
| language | string | Language | The language used for submission in the defined country. | ||
| labelingType | string | Labeling Type | Defines the type of label reference in the submission. |
m1-3-1-pim m1-3-1-pim v. 1.0
No additional fields for folder. m2-3-introduction m2-3-introduction v. 1.0 No additional fields for folder.
m2-3-quality-overall-summary m2-3-quality-overall-summary v. 1.0
No additional fields for folder.
stf stf v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| stfOperation | string | Operation |
Defines the lifecycle operation of the Study Report (New, Replace, Append, Delete). |
— new — replace — append — delete |
new |
| fullReportTitle | string | Full Report Title | The Full name of the Report being submitted. | ||
| reportNumber | string | Report Number | The Report number of the report being submitted. | ||
| species | string | Species | The species that was used in the study. |
— mouse — rat — hamster — other-rodent — rabbit — dog — non-humanprimate — other-non-rodentmammal — non-mammals |
|
| routeOfAdministration | string |
Route of Administration |
The route of administration that was used in the study. |
— oral — intravenous — intramuscular — intraperitoneal — subcutaneous — inhalation — topical — other |
|
| duration | string | Duration | The duration of the study. |
— medium — long — short |
|
| typeOfControl | string | Type of Control | The type of control used during the study. |
— placebo — no-treatment — dose-responsewithout-placebo — active-controlwithout-placebo — external |
|
| docId | string | This field is not used for import. |
stf v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| stfOperation | string | Operation |
Defines the lifecycle operation of the Study Report (New, Replace, Append, Delete). |
— new — replace — append — delete |
new |
| fullReportTitle | string | Full Report Title | The Full name of the Report being submitted. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| reportNumber | string | Report Number | The Report number of the report being submitted. | ||
| species | string | Species | The species that was used in the study. |
— mouse — rat — hamster — other-rodent — rabbit — dog — non-human-primate — other-non-rodentmammal — non-mammals |
|
| routeOfAdministration | string |
Route of Administration |
The route of administration that was used in the study. |
— oral — intravenous — intramuscular — intraperitoneal — subcutaneous — inhalation — topical — other |
|
| duration | string | Duration | The duration of the study. |
— medium — long — short |
|
| typeOfControl | string | Type of Control | The type of control used during the study. |
— placebo — no-treatment — dose-responsewithout-placebo — active-controlwithout-placebo — external |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | The subject matter for the specific study. |
pre-clinical-study-report, legacy-clinical-studyreport, synopsis, studyreport-body, protocol-oramendment, samplecase-report-form, iec-irbconsent-form-list, listdescription-investigatorsite, signaturesinvestigators, listpatients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methodsinterim-analysis-plan, inter-laboratorystandardisationmethods-qualityassurance, publicationsbased-on-study, publications-referencedin-report, discontinuedpatients, protocoldeviations, patientsexcluded-from-efficacyanalysis, demographicdata, compliance-anddrug-concentration-data, individual-efficacyresponse-data, adverseevent-listings, listingindividual-laboratorymeasurements-by- patient, available-onrequest, completepatient-list, seriousadverse-event-patientlist, adverse-eventpatient-list, abnormallab-values-patient-list, data-tabulation-dataset, data-tabulation-datadefinition, data-listingdataset, data-listingdata-definition, analysisdataset, analysis-program, analysis-data-definition, annotated-crf, ecg, image, subjectprofiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| docId | string | This field is not used for import. |
stf v. 3.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| stfOperation | string | Operation |
Defines the lifecycle operation of the Study Report (New, Replace, Append, Delete). |
— new — replace — append — delete |
new |
| fullReportTitle | string | Full Report Title | The Full name of the Report being submitted. | ||
| reportNumber | string | Report Number | The Report number of the report being submitted. | ||
| species | string | Species | The species that was used in the study. |
— mouse — rat — hamster — other-rodent — rabbit — dog — non-human-primate — other-non-rodentmammal — non-mammals |
|
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| routeOfAdministration | string |
Route of Administration |
The route of administration that was used in the study. |
— oral — intravenous — intramuscular — intraperitoneal — subcutaneous — inhalation — topical — other |
|
| duration | string | Duration | The duration of the study. |
— medium — long — short |
|
| typeOfControl | string | Type of Control | The type of control used during the study. |
— placebo — no-treatment — dose-responsewithout-placebo — active-controlwithout-placebo — external |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | The subject matter for the specific study. |
pre-clinical-study-report, legacy-clinical-studyreport, synopsis, studyreport-body, protocol-oramendment, samplecase-report-form, iec-irbconsent-form-list, listdescription-investigatorsite, signaturesinvestigators, listpatients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methodsinterim-analysis-plan, inter-laboratorystandardisationmethods-qualityassurance, publicationsbased-on-study, publications-referencedin-report, discontinuedpatients, protocoldeviations, patientsexcluded-from-efficacyanalysis, demographicdata, compliance-anddrug-concentration-data, individual-efficacyresponse-data, adverseevent-listings, listingindividual-laboratorymeasurements-by- patient, available-onrequest, completepatient-list, seriousadverse-event-patientlist, adverse-eventpatient-list, abnormallab-values-patient-list, data-tabulation-datasetlegacy, data-tabulationdataset-sdtm, datatabulation-dataset-send, me="data-tabulationdataset, data-tabulation-dataset-sdtm, data-tabulation-dataset-send, me="data-tabulation-dataset, data-tabulation-data-definition, data-listing-dataset, data-listing-data-definition, analysis-dataset-adam, analysis-dataset-legacy, e="analysis-dataset, analysis-program, analysis-data-definition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| docId | string | This field is not used for import. |
stf v. 5.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| stfOperation | string | Operation |
Defines the lifecycle operation of the Study Report (New, Replace, Append, Delete). |
— new — replace — append — delete |
new |
| fullReportTitle | string | Full Report Title | The Full name of the Report being submitted. | ||
| reportNumber | string | Report Number | The Report number of the report being submitted. | ||
| species | string | Species | The species that was used in the study. |
— mouse — rat — hamster — other-rodent — rabbit — dog — non-human-primate — other-non-rodentmammal — non-mammals |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| routeOfAdministration | string |
Route of Administration |
The route of administration that was used in the study. |
— oral — intravenous — intramuscular — intraperitoneal — subcutaneous — inhalation — topical — other |
|
| duration | string | Duration | The duration of the study. |
— medium — long — short |
|
| typeOfControl | string | Type of Control | The type of control used during the study. |
— placebo — no-treatment — dose-responsewithout-placebo — active-controlwithout-placebo — external |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | The subject matter for the specific study. |
pre-clinical-study-report, legacy-clinical-studyreport, synopsis, studyreport-body, protocol-oramendment, samplecase-report-form, iec-irbconsent-form-list, listdescription-investigatorsite, signaturesinvestigators, listpatients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methodsinterim-analysis-plan, inter-laboratorystandardisationmethods-qualityassurance, publicationsbased-on-study, publications-referencedin-report, discontinuedpatients, protocoldeviations, patientsexcluded-from-efficacyanalysis, demographicdata, compliance-anddrug-concentration-data, individual-efficacyresponse-data, adverseevent-listings, listingindividual-laboratorymeasurements-by-patient, available-onrequest, completepatient-list, seriousadverse-event-patientlist, adverse-eventpatient-list, abnormallab-values-patient-list, data-tabulation-datasetlegacy, data-tabulationdataset-sdtm, datatabulation-dataset-send, me="data-tabulationdataset, data-tabulation-dataset-sdtm, data-tabulation-dataset-send, me="data-tabulation-dataset, data-tabulation-data-definition, data-listing-dataset, data-listing-data-definition, analysis-dataset-adam, analysis-dataset-legacy, e="analysis-dataset, analysis-program, analysis-data-definition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
| ield Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| docId | string | This field is not used for import. |
study_patient_information_folder study_patient_information_folder v. 1.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | The subject matter for the specific study. | pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-reportbody, protocol-or-amendment, samplecase-report-form, iec-irb-consent-formlist, list-description-investigator-site, signatures-investigators, list-patientswith-batches, randomisation-scheme, audit-certificates-report, statisticalmethods-interim-analysis-plan, interlaboratory-standardisation-methodsquality-assurance, publications-basedon-study, publications-referenced-inreport, discontinued-patients, protocoldeviations, patients-excluded-fromefficacy-analysis, demographic-data, compliance-and-drug-concentrationdata, individual-efficacy-response-data, adverse-event-listings, listing-individuallaboratory-measurements-by-patient, available-on-request, complete-patientlist, serious-adverse-event-patient-list, adverse-event-patient-list, abnormal-labvalues-patient-list, data-tabulationdataset, data-tabulation-data-definition, data-listing-dataset, data-listing-datadefinition, analysis-dataset, analysisprogram, analysis-data-definition, annotated-crf, ecg, image, subjectprofiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pmdescription, nonclinical-data, casereport-forms |
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| site | string | Site | The name of the site where the study was conducted. |
study_patient_information_folder v. 3.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | The subject matter for the specific study. | pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-reportbody, protocol-or-amendment, samplecase-report-form, iec-irb-consent-formlist, list-description-investigator-site, signatures-investigators, list-patientswith-batches, randomisation-scheme, audit-certificates-report, statisticalmethods-interim-analysis-plan, interlaboratory-standardisation-methodsquality-assurance, publications-based-onstudy, publications-referenced-in-report, discontinued-patients, protocoldeviations, patients-excluded-fromefficacy-analysis, demographic-data, compliance-and-drug-concentration-data, individual-efficacy-response-data, adverse-event-listings, listing-individuallaboratory-measurements-by-patient, case-report-forms, available-on-request, complete-patient-list, serious-adverseevent-patient-list, adverse-event-patientlist, abnormal-lab-values-patient-list, data-tabulation-dataset-legacy, datatabulation-dataset-sdtm, data-tabulationdataset-send, me="data-tabulationdataset, data-tabulation-data-definition, data-listing-dataset, data-listing-datadefinition, analysis-dataset-adam, analysis-dataset-legacy, e="analysisdataset, analysis-program, analysis-datadefinition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description | |
| site | string | Site | The name of the site where the study was conducted. |
study_data_folder study_data_folder v. 1.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| dataset | string | Dataset | The type of dataset contained in the folder. | ||
| subjectMatter | string | Subject Matter | The subject matter for the specific study. |
pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-reportbody, protocol-or-amendment, samplecase-report-form, iec-irb-consent-formlist, list-description-investigator-site, signatures-investigators, list-patientswith-batches, randomisation-scheme, audit-certificates-report, statisticalmethods-interim-analysis-plan, interlaboratory-standardisation-methodsquality-assurance, publications-basedon-study, publications-referenced-inreport, discontinued-patients, protocoldeviations, patients-excluded-fromefficacy-analysis, demographic-data, compliance-and-drug-concentrationdata, individual-efficacy-response-data, adverse-event-listings, listing-individuallaboratory-measurements-by-patient, case-report-forms, available-on-request, complete-patient-list, serious-adverseevent-patient-list, adverse-event-patientlist, abnormal-lab-values-patient-list, data-tabulation-dataset, data-tabulationdata-definition, data-listing-dataset, datalisting-data-definition, analysis-dataset, analysis-program, analysis-datadefinition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
study_data_folder v. 3.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| dataset | string | Dataset | The type of dataset contained in the folder. | ||
| subjectMatter | string | Subject Matter | The subject matter for the specific study. | pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-report-body, protocol-or-amendment, sample-casereport-form, iec-irb-consent-form-list, list-description-investigator-site, signatures-investigators, list-patientswith-batches, randomisation-scheme, audit-certificates-report, statisticalmethods-interim-analysis-plan, interlaboratory-standardisation-methodsquality-assurance, publications-based-onstudy, publications-referenced-in-report, discontinued-patients, protocoldeviations, patients-excluded-fromefficacy-analysis, demographic-data, compliance-and-drug-concentration-data, individual-efficacy-response-data, adverse-event-listings, listing-individuallaboratory-measurements-by-patient, case-report-forms, available-on-request, complete-patient-list, serious-adverseevent-patient-list, adverse-event-patientlist, abnormal-lab-values-patient-list, data-tabulation-dataset-legacy, datatabulation-dataset-sdtm, data-tabulationdataset-send, me="data-tabulationdataset, data-tabulation-data-definition, data-listing-dataset, data-listing-datadefinition, analysis-dataset-adam, analysis-dataset-legacy, e="analysisdataset, analysis-program, analysis-datadefinition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
module_studies module_studies v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| createStudyFolders | string | Create Study Folders |
Choose if Study Report Folders are created automatically when publishing. |
— Y — N |
Y |
| studyOrganizationInXml | string | Study Organisation in XML | Defines how studies should be organised within the published XML. |
— stfs — study_elem_in_index — node_ext_in_index — leaf_elem_only |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | Defines the subject matter of the study reports within that section. Can be overridden at the lower levels. | pre-clinical-study-report, legacy-clinical-study-report, synopsis, study-report-body, protocol-or-amendment, sample-case-report-form, iec-irb-consent-form-list, list-description-investigatorsite, signatures-investigators, list-patients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methods-interimanalysis-plan, interlaboratory-standardisationmethods-quality-assurance, publications-based-on-study, publications-referenced-inreport, discontinuedpatients, protocol-deviations, patients-excluded-fromefficacy-analysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacy-responsedata, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, case-report-forms, availableon-request, completepatient-list, serious-adverseevent-patient-list, adverseevent-patient-list, abnormallab-values-patient-list, datatabulation-dataset, datatabulation-data-definition, data-listing-dataset, datalisting-data-definition, analysis-dataset, analysisprogram, analysis-datadefinition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description, nonclinical-data |
module_studies v. 3.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| createStudyFolders | string | Create Study Folders |
Choose if Study Report Folders are created automatically when publishing. |
— Y — N |
Y |
| studyOrganizationInXml | string | Study Organisation in XML | Defines how studies should be organised within the published XML. |
— stfs — study_elem_in_index — node_ext_in_index — leaf_elem_only |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | Defines the subject matter of the study reports within that section. Can be overridden at the lower levels. | pre-clinical-study-report, legacy-clinical-study-report, synopsis, study-report-body, protocol-or-amendment, sample-case-report-form, iec-irb-consent-form-list, listdescription-investigator-site, signatures-investigators, listpatients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methods-interimanalysis-plan, interlaboratory-standardisationmethods-quality-assurance, publications-based-on-study, publications-referenced-inreport, discontinued-patients, protocol-deviations, patientsexcluded-from-efficacyanalysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacy-responsedata, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, case-report-forms, availableon-request, completepatient-list, serious-adverseevent-patient-list, adverseevent-patient-list, abnormallab-values-patient-list, datatabulation-dataset-legacy, data-tabulation-datasetsdtm, data-tabulationdataset-send, me="datatabulation-dataset, datatabulation-data-definition, data-listing-dataset, datalisting-data-definition, analysis-dataset-adam, analysis-dataset-legacy, e="analysis-dataset, analysis-program, analysis-data-definition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
module_4_studies module_4_studies v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| createStudyFolders | string | Create Study Folders | Choose to automatically create Study Report Folders when publishing. |
— Y — N |
N |
| studyOrganizationInXml | string | Study Organisation in XML | Defines how studies should be organized within the published XML. |
— stfs — study_elem_in_index — node_ext_in_index — leaf_elem_only |
module_4_studies v. 1.2
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| createStudyFolders | string | Create Study Folders |
Choose if Study Report Folders are created automatically when publishing. |
— Y — N |
N |
| studyOrganizationInXml | string | Study Organisation in XML | Defines how studies should be organised within the published XML. |
— stfs — study_elem_in_index — node_ext_in_index — leaf_elem_only |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | Defines the subject matter of the study reports within that section. Can be overridden at the lower levels. | pre-clinical-study-report, legacy-clinical-study-report, synopsis, study-report-body, protocol-or-amendment, sample-case-report-form, iec-irb-consent-form-list, list-description-investigatorsite, signatures-investigators, list-patients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methods-interimanalysis-plan, interlaboratory-standardisationmethods-quality-assurance, publications-based-on-study, publications-referenced-inreport, discontinuedpatients, protocol-deviations, patients-excluded-fromefficacy-analysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacy-responsedata, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, case-report-forms, availableon-request, completepatient-list, serious-adverseevent-patient-list, adverseevent-patient-list, abnormallab-values-patient-list, datatabulation-dataset, datatabulation-data-definition, data-listing-dataset, datalisting-data-definition, analysis-dataset, analysisprogram, analysis-datadefinition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description, nonclinical-data |
module_5_studies module_5_studies v. 1.1
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| createStudyFolders | string | Create Study Folders | Choose if Study Report Folders are created automatically when publishing. |
— Y — N |
Y |
| studyOrganizationInXml | string |
Study Organisation in XML |
Defines how studies should be organised within the published XML. |
— STFs — Node extension in index.xml — Leaf elements only - no differentiation between studies |
STFs |
module_5_studies v. 1.2
No additional fields for folder.
module_5_studies v. 1.3
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| createStudyFolders | string | Create Study Folders |
Choose if Study Report Folders are created automatically when publishing. |
— Y — N |
Y |
| studyOrganizationInXml | string | Study Organisation in XML | Defines how studies should be organised within the published XML. |
— stfs — study_elem_in_index — node_ext_in_index — leaf_elem_only |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | Defines the subject matter of the study reports within that section. | pre-clinical-study-report, legacy-clinical-study-report, synopsis, study-report-body, protocol-or-amendment, sample-case-report-form, iec-irb-consent-form-list, listdescription-investigator-site, signatures-investigators, listpatients-with-batches, randomisation-scheme, audit-certificates-report, statistical-methods-interimanalysis-plan, interlaboratory-standardisationmethods-quality-assurance, publications-based-on-study, publications-referenced-inreport, discontinued-patients, protocol-deviations, patientsexcluded-from-efficacyanalysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacy-responsedata, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, case-report-forms, availableon-request, completepatient-list, serious-adverseevent-patient-list, adverseevent-patient-list, abnormallab-values-patient-list, datatabulation-dataset, datatabulation-data-definition, data-listing-dataset, datalisting-data-definition, analysis-dataset, analysisprogram, analysis-datadefinition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description, nonclinical-data |
node-extension node-extension
No additional fields for folder.
Leaf Extensions japanese_leaf japanese_leaf v.1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| leafSequenceNumber | string | Leaf Sequence |
The Sequence Number for the specific leaf (JP Only). |
Example: 01 |
study_report_leaf study_report_leaf v. 1.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| subjectMatter | string | Selection | The subject matter for the specific study. | pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-report-body, protocol-or-amendment, sample-casereport-form, iec-irb-consent-form-list, listdescription-investigator-site, signaturesinvestigators, list-patients-with-batches, randomisation-scheme, audit-certificatesreport, statistical-methods-interimanalysis-plan, inter-laboratorystandardisation-methods-qualityassurance, publications-based-on-study, publications-referenced-in-report, discontinued-patients, protocol-deviations, patients-excluded-from-efficacy-analysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacyresponse-data, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, available-onrequest, complete-patient-list, seriousadverse-event-patient-list, adverse-eventpatient-list, abnormal-lab-valuespatientlist, data-tabulation-dataset, datatabulation-data-definition, data-listingdataset, data-listing-data-definition, analysis-dataset, analysis-program, analysis-data-definition, annotated-crf, image, safety-report, antibacterial, specialpathogen, antiviral, iss, ise, pm-description, nonclinical-data |
study_report_leaf v. 1.1
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| subjectMatter | string | Selection | The subject matter for the specific study. | pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-report-body, protocol-or-amendment, sample-casereport-form-, iec-irb-consent-form-list, listdescription-investigator-site, signaturesinvestigators, list-patients-with-batches, randomisation-scheme, audit-certificatesreport, statistical-methods-interimanalysis-plan, inter-laboratorystandardisation-methods-qualityassurance, publications-based-on-study, publications-referenced-in-report, discontinued-patients, protocol-deviations, patients-excluded-from-efficacy-analysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacyresponse-data, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, available-onrequest, complete-patient-list, seriousadverse-event-patient-list, adverse-eventpatient-list, abnormal-lab-values-patientlist, data-tabulation-dataset, datatabulation-data-definition, data-listingdataset, data-listing-data-definition, analysis-dataset, analysis-program, analysis-data-definition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, special-pathogen, antiviral, iss, ise, pm-description |
study_report_leaf v. 3.0
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values | Default Value |
| subjectMatter | string | Selection | The subject matter for the specific study. | pre-clinical-study-report, legacy-clinicalstudy-report, synopsis, study-report-body, protocol-or-amendment, sample-casereport-form, iec-irb-consent-form-list, listdescription-investigator-site, signaturesinvestigators, list-patients-with-batches, randomisation-scheme, audit-certificatesreport, statistical-methods-interimanalysis-plan, inter-laboratorystandardisation-methods-qualityassurance, publications-based-on-study, publications-referenced-in-report, discontinued-patients, protocol-deviations, patients-excluded-from-efficacy-analysis, demographic-data, compliance-and-drugconcentration-data, individual-efficacyresponse-data, adverse-event-listings, listing-individual-laboratorymeasurements-by-patient, available-onrequest, complete-patient-list, seriousadverse-event-patient-list, adverse-eventpatient-list, abnormal-lab-values-patientlist, data-tabulation-dataset-legacy, datatabulation-dataset-sdtm, data-tabulationdataset-send, me="data-tabulation-dataset, data-tabulation-data-definition, datalisting-dataset, data-listing-data-definition, analysis-dataset-adam, analysis-datasetlegacy, e="analysis-dataset, analysisprogram, analysis-data-definition, annotated-crf, ecg, image, subject-profiles, safety-report, antibacterial, specialpathogen, antiviral, iss, ise, pm-description |
study_patient_information_leaf study_patient_information_leaf v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| subjectMatter | string | Subject Matter | The subject matter for the specific study. |
— case-reportforms — subject-profiles |
|
| site | string | Site | The name of the site where the study was conducted. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| registrationFileIndicator | string | Registration File Indicator | Defines if element belongs to a registration dossier or a drug master file. | true/false | true |
eu-envelope eu-envelope v. 1.0
No additional fields for folder.
jo-envelope jo-envelope v. 1.0
No additional fields for leaf.
eaeu-envelope eaeu-envelope v.1.0
No additional fields for leaf.
eaeu_leaf eaeu_leaf v. 1.0
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| drugRegistrationDocCode | string |
Drug Registration Document Code |
Defines a purpose of the leaf in the output, according to the assembly template. | Five digits, according to classifier. | |
| drugRegistrationDocumentName | string |
Drug Registration Document Name |
Name is specified if Drug Registration Document Code is not specified or there is no appropriate code in the classifier. |
||
| drugRegistrationFileCodeSection | string |
Drug Registration File Section |
Helps to sort out value from Drug Registration File Code list. | Two digits | |
| drugRegistrationFileCode | string |
Drug Registration File Code |
Defines the Drug Registration File Code value. | Four digits | |
| drugRegistrationFileName | string |
Drug Registration File Name |
Name is specified if Drug Registration File Code is not specified or there is no appropriate code in the classifier. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| docCreationDate | date |
Document Creation Date |
Date of document creation. |
Date format - Unix Timestamp. If empty, this message appears: "Document Creation Date is required" message is displayed. If the entered data cannot be recognized as a date, "Invalid date specified". |
|
| docValidityDate | date |
Document Validity Date |
Date when document expires. |
Date format - Unix Timestamp. If entered data cannot be recognized as a date, this message appears: "Invalid date specified". |
|
| businessEntityName | string |
Business Entity Name |
Organization name issued registration dossier. |
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
| drugAttributeText01 | date |
Request Response Date |
Response to request must be provided before specified date. |
Date format - Unix Timestamp. If entered data cannot be recognized as a date, this message appears: "Invalid date specified". |
|
| drugAttributeText02 | string |
Reason Document Number |
Reason Document Number. |
||
| drugAttributeText03Section | string |
Requested Drug Registration File Section |
Helps to sort out value from Drug Registration File Code list . | Two digits | |
| drugAttributeText03Code | string |
Requested Drug Registration File Code |
Defines Drug Registration File Code value. |
Four digits | |
| drugAttributeText04 | string |
Requested Drug Registration Document Code |
Code that defines purpose of the leaf in the output, according to assembly template. | Five digits, according to classifier | |
| drugAttributeTexts99 | string |
Other Information |
User may add several text boxes using the Add button. | ||
| drugAttributeTextName | string |
General Information |
Defines general information. |
| Field Name | Field Type |
Matching UI Field |
Description | Acceptable Values |
| applicationContainsFiles | string | Application Contains Files? |
Will this submission contain files or not. |
— Y — N |
| applicationNumber | string | Application Contains Files? |
The Application Number provided by the agency. |
Example: 123456 |
| crossReferenceApplication | map |
Cross Reference Application |
These fields must allow for the Application Number and |
<field name="crossReferenceApplication" type="map"><value key="1195__uniqueSuffix__0" value="123456" /></field> |
| crossReferenceApplicationNumber | string |
Cross Reference Application |
Application Type (eCTD code) to be entered, | Example: 1234 |
| crossReferenceApplicationType | string |
Cross Reference Application |
and then for additional Application Numbers and Types to be entered. The values must be paired. |
eCTD Code value from Data Administration > Application Type Values > Application type eCTD Code |
| sequenceNumber | string | Sequence Number |
The Sequence Number for this submission. |
Sequence Code (without prefix "P") |
PublisherMetaData
m1-us-meta-data-application
| Field Name | Field Type | Matching UI Field | Description | Acceptable Values | Default Value |
|---|---|---|---|---|---|
| applicationContainsFiles | string | Application Contains Files? | Will this submission contain files or not. |
|
Y |
| applicationNumber | string | Application Contains Files? | The Application Number provided by the agency. | Example: 123456 | |
| crossReferenceApplication | map | Cross Reference Application | These fields must allow for the Application Number and Application Type (eCTD code) to be entered, and then for additional Application Numbers and Types to be entered. The values must be paired. |
|
|
| crossReferenceApplicationNumber | string | Cross Reference Application | Example: 1234 | ||
| crossReferenceApplicationType | string | Cross Reference Application | eCTD Code value from Data Administration > Application Type Values > Application type eCTD Code | ||
| sequenceNumber | string | Sequence Number | The Sequence Number for this submission. | Sequence Code (without prefix "P") | |
| submissionId | string | Submission ID | Identifies each individual regulatory activity (original application, supplement, annual report, etc.) in an application. | Example: 0001 |
